I do not use Internet of Trifles junk anywhere on my network for what does not exist is not available for exploitation.

Craving such fecality is pathetic and any consequences deserved because they were invited.

Slashdot doesn't need this clickbait.

A stupid rich vain asshole killed people so intensely silly they cared about Titanic, whose sole claim to fame IS fame. The world is slightly wiser in consequence.

Think about it. There is no reason a functioning adult should be morbidly fascinated by a mere shipwreck but people crave to masturbate to drama, and romantic death appeals to the bitch-made (a perfect hood term for a much wider degeneracy) mind.

The other casualties were so cravenly silly they utterly failed to perform THEIR OWN due diligence before becoming someone else's suicidal beta testers. They were sufficiently educated to understand the basics, including that ZERO reason exists not to copy proven hull designs zero reason existed to change let alone use an utterly absurd choice of hull.

Rush had Alvin--tier money but pure vanity is why he chose a childishly silly hull design no reason existed to want because nothing about it was better. His loss is as minor as a common auto accident. Ditto the "collateral damage" who knew what they signed up for.

This seems like a situation where it's very hard to get excited about the idea that it's the regulator's problem. Did some Canadian fed technically have the authority to inspect? Quite possibly. Is there some sort of justification for even the cost of performing the inspection, much less any undesired knock-on effects of the notion that literally all vessels must be inspected no matter what, in a case like this? Seems harder to make that case.

There are a lot of situations where large portions of the public have no choice but to use products and services that they have no reasonable ability to be "informed" about. Either it's simply not possible if you aren't in a position to legally compel honesty from the vendor or it's a case where "informed" is PhD-level work in the area, or a combination of the two; but some rando's aggressively contrarian submarine that loudly and proudly skips all industry certifications and is available on boutique scale for very wealthy customers doesn't seem like one of those cases.

The adult choice to be tech-ignorant in 2026 has consequences.

There is no excuse for that level of self-neglect. Boomers don't get a pass since they lived through the birth of the internet. If you're old in 2026 you had many decades beforehand to pull head from arse and learn.

Not only do we have the concept of a plan for negotiations for a peace agreement; the current level of disagreement between the agreeing parties suggests that we actually have at least three distinct concepts of a plan for negotiations for a peace agreement! Where a lesser leader might myopically interpret having a single agreed-upon set of terms as essential to a treaty; Great Leader understands that American Greatness requires more.

Is that really a bad thing? There are certainly plenty of examples of old things that suck; either because genuine improvements became available after they had already solidified or because they were always broken and are now running purely on denial-fueled risk tolerance; but, in principle, it seems like it should be a bad thing that age is seen as a bad thing. Especially when software is more like math than like civil engineering in terms of the tendency of its materials toward corrosion, embrittlement, and fatigue. (and when so many 'modernization' projects turn into expensive failures or go way behind schedule and over budget to eventually death march toward feature parity, sometimes even achieving it in time to be declared legacy themselves.)

I'm not calling for a crusade against 'fast fashion' software; if people want to bang out an app on the fast and cheap to catch the moment when people care they can do that; fine, whatever; but it seems like software built on real long term service timescales should get a lot more credit than it does. Absent specific criticisms; it's not "eww, there are people who weren't even born then", it's "the software has been in service for a generation".

All the more if there are a lot of outfits doing the same thing: having some unique oddball legacy thing means having potentially crushing maintenance requirements unless everything was gloriously secure from day 1, which it probably wasn't; but if there is some big mass of enterprise Java 8 why should we call it all eol and scramble rather than just maintaining java 8? Especially when we can do so in software, without some of the vendor and hardware inflexibility you see with things like old school mainframe applications where there's an implied commitment to a single old school mainframe vendor in perpetuity.

It's not elegant; but realistically we are far enough both into the history of computer science and the history of computers-as-hardware-you-can-buy that there's a lot less obvious, low-hanging, progress to be had by going 'modern' relative to the amount of fashion and fad chasing. Especially if (as is the case for a great many people and organizations) the scale of your problem has grown at or below the rate at which hardware advances have made systems not particularly well designed for scalability faster.

Obviously this would require coordinated action, and some people likely have other reasons to want to either poke at or kill legacy applications; but(since all those java versions are solidly post openjdk) I'd be very curious to know how the cost and risk associated with "modernize because java 18 is going eol!" would compare to just...not...having java 18 go eol. Unsexy maintenance project that you'd need to pay to have done, sure; but very plausibly better characterized and lower risk than trying to deal with a lot of the oddball internal accretions that would otherwise need updating; and, depending on how much people have running on java 18, certainly possible that they'll individually spend a fair bit more running the treadmill than it would cost to just keep kicking java 18 down the road until (almost) nobody cares.

Fire easily destroys or disables concentrated "force loss multiplier" fratricidal storage designs. Not just accidents, but terrorist-style attacks can take them out easily via drones using simple electric triggers.

https://theconversation.com/wh...

Disperse batteries far and wide and they'll be much more difficult to interfere with if they're designed to function without grid power during emergencies. A controlled, graceful shutdown is better than abrupt power interruption.

My response was specifically to the original poster who, for some reason, was taking a "we are losing the class wars; breed faster!" position rather than the "if you are already losing the class war why would you even think about putting in that much effort and cost so your children can deal with a bad or worse outcome?" position.

It would honestly not surprise me if that is a nontrivial contributing factor: If you aren't emotionally invested in children as an end in themselves the wage and cost of living numbers have done very little to encourage you to see them as affordable since roughly the late 70s(with a combination of substantial stagnation for anyone who is primarily wages rather than capital gains; and such good news as there is mostly confined to people who complete at least undergraduate education and remain in a career track full time) and people who are emotionally invested in children are often willing to go to considerable lengths to try to improve their children's outcomes; but are presumably discouraged by the prospect that they will most likely be downwardly mobile instead.

It's not a surprise that people who want labor, cannon fodder, or taxpayers to be abundant for them are fretting about it; but it's hard to see why most of us should care. Why do things that are good for society when society is pretty overtly disinterested in being good for you? You may be able to squeeze the current labor market a bit; because people who already exist tend to take the "or starve" possibility pretty seriously when deciding what they will put up with; but if you offer nothing but the demand for a toiling underclass to encourage people to have children that's not terribly compelling, either for those who aren't interested in sacrificing for children and see hitting education and career hard as increasingly existential or for people who would sacrifice a lot to better things for their children but are more or less accurate in seeing it as highly unlikely that they will be able to.

I'm rather doubtful of the plan's viability; but if they are willing to justify the company name by chaining Bezos to a rock so a bird can eat his liver repeatedly I could be persuaded.