![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
So, basically nothing new in Windows 11 that I want and a whole lot of things I don’t.
So, basically nothing new in Windows 11 that I want and a whole lot of things I don’t.
I have actually encountered those sort of potential differences between ground planes. They can indeed wreak havoc under the right circumstances.
I can’t decide whether to laugh or cry.
Turns out one of the video-editing programs I use (VideoRedo) has shut down anyway (I think the owner passed away) and so I’ll need to look for an alternative anyway - I don’t think I can activate it on new machines anymore.
Because I haven’t yet updated from Windows 10 to 11 and had been putting it off. In the past week, though, I have seen a number of news articles highlighting issues I am going to have with Windows 11 and this particular article, indicating that they have been effectively leaving systems vulnerable simply because they have applications they don’t like installed is just not good enough. I’d understand it if they were saying “we can’t guarantee your OS stability with these apps” or “we can’t guarantee these apps will work anymore” if they were removing older API support, but this is ridiculous.
Good to know. I don’t play many games, but do have some older ones from GoG that would be nice to keep.
Thanks, will do!
I was already dubious about upgrading from 10 to 11 and this is final straw. I will have to look at Linux options and see if my Windows-only programs will run effectively under WINE.
Given how bad the show’s writing has been for years and the declining in viewership in the Chibnell era, I’m actually surprised the BBC actually reversed course for once.
I think it’s just that we’re possessive/protective of “our” code, even more so if one is passionate about programming. We’ve put a lot of effort into it, then somebody else comes along and “ruins” our “perfect” (to our eyes) formatting/styling!
Some linters can do both. Getting one set up as an automated job whenever code is pushed to the repo is on my TODO list…
I felt that. I have a colleague whose coding style is different to mine and whenever they work on code that I originally wrote, I have to resist the temptation to modify things to camelCase.
Thanks for that. A very interesting read; I am inclined to believe the author, given how they describe the failure of processes.
Indeed. I’d hardly classify this as going “rogue”; rather, inadequate guard rails in place for this application.
The browser addon “AdNauseum” can help with that, although it’s not a complete solution.
That is better than a fuselage failure, but still disturbing if you’re correct - surely there are checks for exit door plugs since it would be at higher risk of failure.
Multiple news articles are reporting that this aircraft had its post-production certification only two months ago. For a problem of this magnitude to develop in such a short time is very disconcerting.
Huh? What does how a drive size is measured affect the available address space used at all? Drives are broken up into blocks, and each block is addressable.
Sorry, I probably wasn’t clear. You’re right that the units don’t affect how the address space is used. My peeve is that because of marketing targeting nice round numbers, you end up with (for example) a 250GB drive that does not use the full address space available (since you necessarily have to address to up 256GiB). If the units had been consistent from the get-go, then I suspect the average drive would have just a bit more usable space available by default.
My comment re wear-levelling was more to suggest that I didn’t think the unused address space (in my example of 250GB vs 256GiB) could be excused by saying it was taken up by spare sectors.
Ouch.