• 1 Post
  • 252 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle



  • The feedback in the article was obviously far from perfect, but from the sound of it, “good attempt” could be an actively harmful thing to say. Lots of effort had gone into making the wrong thing and making it fragile, which isn’t good at all, it’s bad. If you’d asked an employee to make a waterproof diving watch, and they came back with a mechanical clock made from sugar, even though it’s impressive that they managed to make a clock from sugar, it’s completely inappropriate as it’d stop working the instant it got wet. You wouldn’t want to encourage that kind of thing happening again by calling it good, and it’s incompatible enough with the brief that acknowledging it as an attempt to fit the brief is giving too much credit - someone who can do that kind of sugar work must know it’s sensitive to moisture.

    The manager can apologise for not checking in sooner before so much time had been spent on something unsuitable and for failing to communicate the priorities properly, and acknowledge the effort and potential merit in another situation without implying it was good to sink time into something unfit for purpose without double checking something complicated was genuinely necessary.





  • Also, the overwhelming majority of USB plugs have the logo on the side away from the plastic bit, and sockets have their plastic bits towards the top of the device. You want the plastic bits on opposite sides (as physical objects don’t like to overlap), so that means that if you can feel the logo with your thumb, that side goes up when you plug it in, and you don’t even have to look.







  • Arch is at least more likely to update to a fixed version sooner, and someone getting something with pacman is going to be used to the idea of it breaking because of using bleeding edge dependencies. The difference with the Flatpak is that most users believe that they’re getting something straight from the developers, so they’re not going to report problems to the right people if Fedora puts a different source of Flatpaks in the lists and overrides working packages with ones so broken as to be useless.


  • People fall off rooftops fitting solar panels, burn to death repairing wind turbines that they can’t climb down fast enough to escape, and dams burst and wash away towns. Renewable energy is much less killy than fossil fuels, but per megawatt hour, it’s comparable to nuclear, despite a few large incidents killing quite a lot of people each. At the moment, over their history, hydro is four times deadlier than nuclear, wind’s a little worse than nuclear, and solar’s a little better. Fission power is actually really safe.

    The article’s talking about fusion power, though. Fission reactions are dangerous because if you’ve got enough fuel to get a reaction at all, you’ve got enough fuel to get a bigger reaction than you want, so you have to control it carefully to avoid making it too hot, which would cause the steam in the reactor to burst out and carry chunks of partially-used fuel with it, which are very deadly. That problem doesn’t exist with fusion. It’s so hard to make the reaction happen in the first place that any problem just makes the reaction stop immediately. If you somehow blew a hole in the side of the reactor, you’d just get some very hot hydrogen and very hot helium, which would be harmless in a few minutes once they’d cooled down. It’s impossible for fusion power, once it’s working, not to be the safest way to generate energy in history because it inherently avoids the big problems with what is already one of the safest ways.



  • That’s misleading in the other direction, though, as PhysX is really two things, a regular boring CPU-side physics library (just like Havok, Jolt and Bullet), and the GPU-accelerated physics library which only does a few things, but does them faster. Most things that use PhysX just use the CPU-side part and won’t notice or care if the GPU changes. A few things use the GPU-accelerated part, but the overwhelming majority of those use it for optional extra features that only work on Nvidia cards, and instead of running the same effects on the CPU if there’s no Nvidia card available, they just skip them, so it’s not the end of the world to leave them disabled on the 5000-series.



  • If you write cross-platform software, the easiest solution is usually to pretend everything’s Unix. You’ll hit some problems (e.g. assuming all filesystem APIs always use UTF-8 will bite you on Windows, which switched to UCS2 before UTF-8 or UTF-16 were invented, so now uses UTF-16 for Unicode-aware functions as that’s the one that’s ABI compatible with UCS2, and passing UTF-8 to the eight-bit-char functions requires you to opt into that mode explicitly), but mostly everything will just work. There’s no XDG_CONFIG telling you to put these files anywhere in particular, as Windows is Windows, so most things use ~ as a fallback, which Windows knows to treat as %USERPROFILE%.