• 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle





  • Ethereum’s been proof-of-stake rather than proof-of-work for couple of years now, so it’s no longer energy intensive.

    There inherently can’t be a way to make proof of work lies wasteful as long as there are people who want to do the work. If you make hardware more, then it makes it cheaper to do the same amount of work, so people buy more hardware and do more work and more power gets used. If you make hardware less efficient, people just use the old hardware. You have to abandon proof of work altogether and switch it to something else that isn’t inherently tied to energy usage.





  • 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.



  • The Free Software movement was generally a leftist objection to the limitations on computer use that capitalism was causing, and the open source movement was a pro-corporate offshoot to try and make the obvious benefits more compatible with capitalism (which it’s been pretty successful at, even if it has reintroduced some of the problems Free Software was trying to stop in the first place). Anyone who’s making a distinction between the two at the minimum is recognising that capitalism is why we can’t have certain specific nice things, so it’s not a huge leap to blame it for other problems, too.

    As for a sensible middle ground, the Free Software movement designed its licences to work in the capitalist societies they operated in, so the incompatibility with corporate use has never been as big a deal as it’s been made out to be. Corporations can use copyleft-licenced software just fine as long as they’re not unreasonable about it. It’s totally fine for a corporation to use a GPL tool internally and even have an internal fork as long as they put the source code for their internal fork on the company’s file share so the employees using the tool can improve it if they get the urge. They can even sell products that depend on LGPL or MPL libraries if they make the source of the builds of those libraries they used available on their website or otherwise accessible to their customers (and use a DLL/.so/.dylib build of the library of it’s LGPL). These restrictions are all less of a pain than making an MIT-licenced clone of an existing project, but companies have opted to make clones instead. The only bonus this gives them is that they can make it proprietary again later, and it has the added risk that one of their competitors could make a proprietary fork with a killer feature they can charge for, which isn’t a nice risk. There are other benefits to investing in making your own clone of something, but they don’t depend on the license it uses.







  • Tilting your head shouldn’t make a difference as ‘modern’ (as in the ones that cinemas started using fifteen years ago) 3D glasses use clockwise and anticlockwise circular polarisation filters, and obviously, turning something 90° doesn’t change whether it’s clockwise or anticlockwise. Other kinds of polarisation filters do care about being rotated, which is probably where the artist got the impression it applied to 3D glasses, but it would be dumb to try and use that kind as obviously, people tilt their heads.