Typing in a box on a website provided by someone else can be done by practically anyone, even the boss themselves at a pinch. Heck, some of them love doing that.
Maintaining a server (or a service on a server) requires someone with more skills, which generally costs more money.
Yeah, but then they have to pay someone to maintain it. And low though that cost may be, it's precisely the sort of thing that C-levels like to cut when they feel like pretending that they actually do something.
It's a hard thing for a C-level's ego to set something up that they know someone else is going to cut later, or worse that they might be the one to "have to" cut it.
Very little of what is your body now will remain in a few years. That's less terrifying than it sounds because we replace bits of ourselves on a constant basis. With every breath we lose carbon that may have been in us for years. Every bathroom visit contains not just food remnants but little bits of ourselves that have already been replaced and broken down.
About the only things that don't get some level of replacement are our teeth and the floaters in our eyes.
Geolocation is done by IP address if nothing else is available. It's not exact, but if, for example, you use a US-based internet provider, all their customer IP exit points will already be marked as US-based, and any access from one of those to a Google service will get the new name.
Twenty or so years ago, there was a brief period when going full AMD (or AMD+ATI as it was back then; AMD hadn't bought ATI yet) made sense, and then the better part of a decade later, Intel+NVIDIA was the better choice.
And now I have a full AMD PC again.
Intel are really going to have to turn things around in my eyes if they want it to swing back, though. I really do not like the idea of a CPU hypervisor being a fully fledged OS that I have no access to.
My first guess would be to take out that semicolon on line 264. JavaScript will often happily take a new line as end of statement if it makes sense to do that, so in theory, that semicolon is not needed. And it might be a Greek question mark your prankster colleague put in your code when you weren't looking.
And then I'd be tracing parentheses, curlies, quotes and so on, because that error could be the point the parser gave up trying to make sense of the code rather than where the error actually is.
And if that didn't find it, I'd put in a deliberate error at an earlier, known line to see where the parser thinks that error is. If it's offset by 20 lines, then I know the original error is probably offset by a similar amount.
This isn't strictly true. Most houses built between WWII and the '90s were built with sockets that didn't have switches on them. It was only later safety regulations / suggestions that made the switches preferable.
Where I live was built in the late '80s right before switched sockets became more common. All the original sockets have no switch. Some in the kitchen have switches, but it's clear these were added at a later date.
I'm not sure of the exact rulings and where and when a socket must have a switch, but you can still find switchless sockets for sale at the sorts of retailers who sell those sorts of things, so there are definitely places where those sockets are still allowed.
It's a rich text box with a few controls to enable or disable those features at certain points in the text. The whole thing was entirely built from components used elsewhere in the OS, or at least the earlier versions were. One competent employee could manage it in an afternoon; a week at the outside. If Microsoft has let it get so ridiculously bloated that it's now unmanageable by one person, that's on them.
They could have just renamed it. Wordpad's Win3.11 predecessor was called "Write", for example, so that name could have been revived.
For a long time, write.exe still existed and all it did was launch Wordpad, so they'd only have to reverse that.
They could also have chosen another name entirely. Or, since they've recently added a bunch of unnecessary crap to Notepad, they might as well have merged the two.
Straight up killing a known criminal is not the accepted way to mete out justice, no matter how right it seems. We have (international) courts for a reason, even when the case is open and shut, and even if the same courtesy would be unlikely if the situation was reversed.
It would almost certainly be a requirement to prosecute and then likely lock Zelenskyy up if he did that, even if he might be doing us all a favour. And even the nicest prison is still a prison.
It would be better if there was a way to have the targets neutralise each other.
Ah, misleading use of terminology that indicates one thing, but will win in court even if it actually means, or can later be said to mean, another.
I hope those involved in helping companies win these lawsuits choke on bones from food sold as boneless. Because that won a court case after "boneless" was redefined as a cooking method.
I don't want them to choke to death. Just a little lesson, you know?
Very much this. I can see one potential future Microsoft product being something that is to be installed on a thin client PC sold to consumers for cheap. It will run not much more than a browser in which all apps will load from Microsoft servers, and all storage will be on the Microsoft cloud. And if you miss a monthly payment they'll basically hold all your files for ransom until you start paying again.
I can practically hear the Microsoft execs making some very unsavoury noises about that idea.
As for (admittedly somewhat weak) proof they're headed in this direction: Wordpad is a useful small program that would easily fit onto a thin client and there'd be room for documents created by it on the limited storage available. It has to have some storage for browser cache after all.
Wordpad was recently cancelled, and users urged to use Word instead. Which is not free of (further) cost like Wordpad was.
I guess I do. I put the computer (a desktop) into suspend most nights so that it's pretty much up and running as soon as I turn it on the next day.
Even so, rebooting doesn't take that long. 30 seconds tops. Definitely not enough time to visit the bathroom or make a hot drink.
But the advantages to suspend are that it's quick and all my programs are as I left them. A reboot undoes most of that.
Yes, hibernating is also an option to keep open programs, but why do that when it can be quicker?
My only real concern with putting the machine into suspend is if there's a power cut and things end up in a weird state or I lose work because programs weren't closed properly, but then, that could happen at any point when I'm using it too.
Typing in a box on a website provided by someone else can be done by practically anyone, even the boss themselves at a pinch. Heck, some of them love doing that.
Maintaining a server (or a service on a server) requires someone with more skills, which generally costs more money.