Somewhat related, a couple years ago Swiss police wanted to use AI software to predict burglaries. However, there were not enough burglaries in the country to get enough training data, so the project was shelved.
671 karma · joined August 8, 2017
For example, 98% of the atoms in your body are replaced every year. Doesn't it make more sense to think of software in this way, as opposed to e.g. a car or a building? I guess even a building needs maintenance (roof is replaced, windows are replaced, ...), but it's on such long timescales that we think of it as "finished".
If you think of software as a living thing where X% of it needs to be replaced every year just to keep it where it is, then there is no need for a "big rewrite".
And now they spend 30% of their income on medical costs.
Installed software is considered to have a distributor, ie. a legally responsible entity that can be punished for any shenanigans.
I believe this is an outdated model and that with better tooling we could do what you envision.
I mean you can just write SQL instead of using the ORM if your project consists of a single table with no indexes that will never change, sure.
Hard disagree. You just re-implemented a database engine in your application code. Poorly.
Let me introduce you to the Molten-Salt Reactor Experiment[1].
What you probably meant is that none have been built commercially. That is true, but again as I mentioned, not because of their technical drawbacks but because of politics. In fact, the inventor of the light water reactor, Alvin Weinberg[2], was a strong proponent of the molten salt reactor over his own invention. So strong that he fired was from ORNL because he was claiming that light water reactors are inherently unsafe and that MSR is a better design.
Nixon ultimately sacked him because he (Nixon) chose to support LMFBR (Liquid Metal Fast Breeder Reactor) because it was being built in California, and in return he got political support that he needed. MSR ultimately lost due to pork-barrelling.
> This is easy to bypass, put something over the plug that won't melt.
I mean you're shifting goalposts here. The "operator" has a specific meaning - someone controlling the reactor from the control room. They don't have access to the freeze plug during normal reactor operation.
But even if they did do what you're suggesting, the pressures inside the MSR are so low (on the order of couple of bars) that the damage would be quite limited.
[1] https://en.wikipedia.org/wiki/Molten-Salt_Reactor_Experiment [2] https://en.wikipedia.org/wiki/Alvin_M._Weinberg
That's not true. There are many designs (e.g. molten salt reactors) where the operator cannot do anything to cause the reactor to fail.
The reason we're stuck with water reactors is mainly politics, and somewhat laziness.
And this one in Ireland due to a rag: https://www.irishtimes.com/news/helicopter-crash-caused-by-c...
If you have a programmable keyboard, feel free to experiment with symbols, letters, etc. Home-row mods are also something that I warmly recommend.
Can't agree enough.
Whenever you burn something in a nitrogen atmosphere, NOx are created. They contribute to acid rain and the formation of smog, and are a trigger for asthma.
E.g. try typing ls -la on Dvorak.
Mate desktop environment in my opinion comes closest to the simplicity of the Windows 95/GNOME 2 environments of the old: https://mate-desktop.org/.
Not sure how hardware-frugal it is since maintaining it under GTK 2 was not feasible and it's now developed against GTK 3 (with still maintaining the look and feel of GNOME 2).
Think of a mirror-image of a regular nib.