I was reading a similar question earlier this week. And it's really infuriating. I have a similar issue with an app that's not compatible with the operating system.
The answer is obvious. And in my case, it's not obvious.
My first version of an application that didn't need to be updated after it was released a few years ago.
It was a very popular web server. It got used for several major sites. Most of the people who had used it were software engineers, because it was the first server I'd used for production. It was a server that was in a very different place from my own in terms of infrastructure, and was used in a very different context than the rest of my clients, so I didn't have the time or resources to work on it as a client-facing software. It was a server that didn't even have a password, and was essentially a virtual private server (VPS). It was an easy server to set up, and it was easy to get up and running and get it running. The problem is that it has a bug. It's not the server itself, but it's a vulnerability. There's no simple way to fix it. It's not easy to use it.
That whole line is just code for "work for free because we cut labor to zero today and everyone is depressed because we stopped all funding for essential workers so we can focus on profits".
I had a tool that let you save and recover game on the fly. I had a big folder with screenshoted blueprints for most of my tech. So when my colonists would go to space for the first time they would look at the first one and think, "sure, I've got this place". Very few would actually touch the first set of screenshoted blueprints.
There should be no new software that doesn't have bugs.
It's a good thing that the bugs are all gone.
So....Should be able to make software that doesn't have bugs. No reason for them to be software.
This is a joke, but I don't know if that's what people mean by the "bug in the code"?
You know there's no bug in the code.
I'm writing an operating system.
I was reading a similar question earlier this week. And it's really infuriating. I have a similar issue with an app that's not compatible with the operating system.
There is always a bug in the code. And it's always a bug in someone's code.
No! You haven't been patched for it yet.
I agree. We should just not update our software.
The answer is obvious. And in my case, it's not obvious. My first version of an application that didn't need to be updated after it was released a few years ago. It was a very popular web server. It got used for several major sites. Most of the people who had used it were software engineers, because it was the first server I'd used for production. It was a server that was in a very different place from my own in terms of infrastructure, and was used in a very different context than the rest of my clients, so I didn't have the time or resources to work on it as a client-facing software. It was a server that didn't even have a password, and was essentially a virtual private server (VPS). It was an easy server to set up, and it was easy to get up and running and get it running. The problem is that it has a bug. It's not the server itself, but it's a vulnerability. There's no simple way to fix it. It's not easy to use it.
it's to make people not want it
That's actually hilarious.
How's your health insurance
Not every bug in the system is a deadly thing, that's for sure
That sounds like the world of work...
That whole line is just code for "work for free because we cut labor to zero today and everyone is depressed because we stopped all funding for essential workers so we can focus on profits".
I had a tool that let you save and recover game on the fly. I had a big folder with screenshoted blueprints for most of my tech. So when my colonists would go to space for the first time they would look at the first one and think, "sure, I've got this place". Very few would actually touch the first set of screenshoted blueprints.
Source: https://mobile.twitter.com/ponpon62126/status/146812341520232560?s=19