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.

Finally an expert who knows things!

So the silvery disc-craft I saw in the sky over Jenks, OK was not exo-atmospheric capable - I've often wondered.

If you look in a mirror, you'll see excellent examples of both why it's falling and why it still needs to fall a lot farther.

They can't "lose" knowledge they never possessed in the first place, retards.

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.

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.

Let me guess: "They've never been right before but maybe this time??"

Sarcasm notwithstanding, Elon's accomplishments with SpaceX (namely, recruiting Ms. Shotwell!) would appear* to have earned him his success.

*Only idiots judge by appearance.

I'm not sure what confuses you here: everybody has an EoL, age related if nothing else, and they don't live on either through their class or their descendants. What do you gain by throwing more poor bastards into a sucker's game when you could just not?

Yeah, it's ultimately a matter of taste and what becomes economically and strategically feasible; but I figured that there is at least a conceptual distinction between weapons that are better at being obedient(basically any attempt at stable aerodynamics on the low end up to electromechanical gyroscopic stuff, to TERCOM and GNSS guidance; but you specify where you want it to go and the guidance system attempts to minimize or counteract outside influences), weapons that can independently follow a very specific instruction(at least the simpler acoustic and IR seekers where you need to point them toward a particular loud/bright object but they can compensate for it moving, to a degree); and finally the ones that can take fairly generalized instructions of the "anything that looks like a target in this area" flavor; which seemed like the best candidates for 'autonomous'.

I realize that it's a better hype piece if we assume that the 157000 'agents' are fancy chatbots; but this is just an HTTP API; on what basis are they distinguishing between 'agents' in the currently trendy sense and someone's little script around cURL or whatever?

I, for one, completely trust this objective and disinterested report from a company that has no stake in the ease of ramming datacenter approvals through.