That just shows a "not available outside the US" error page.

In your case it might simply be that there was not enough of this kind of tasks in the training data.

I agree in general, but not with this strong phrasing. I've let AI build a good amount of non-trivial code. But my consistent experience is that it works best when guided by an experienced coder who can correct it, and when implementing well-known algorithms rather than coming up with novel solutions.

Example: I let it write up a quadtree implementation in a language for which there was no ready solution online. It took 2-3 correcting prompts to get a good result. I could've done it myself but it would've likely taken a few hours to get it all right instead of the half or so hour it took with AI. The important part for me was that there's nothing unknown in how to implement a quadtree. All the AI needs to do is take the 100s of existing implementations and translate them into a different language.

True but too simplified. The Luddites had an entirely different motivation: The fact that factories now employed women and children at very low rates meant that the men lost their status in the family as bread winners and head of household. That was a major social disruption, which we don't have with AI.

I'd compare it more to teamsters or wagoners when cars became common. Your job is threatened by a different way of doing the same thing, a way to which your skills don't cleanly transition. Some choose to pick up the new tech, some want the old ways to persist.

In the end, coachmen became chauffeurs, because rich people prefer to be driven around oder driving themselves, no matter if it's a horse or an engine doing the pulling. But much fewer teamsters and wagoners became truck drivers.

It usually goes to the lowest-ranking person on the team or the one everyone's trying to keep away from actual coding.

It remains worth the effort to write a novel around your code - not just what you did and why you did certain things a certain way, but the meta-reasons. The more those who come after you understand, the easier it is for them to figure out and maintain your code. It also tends to focus you more on writing good code, because you don't want to document, "Well, it looked good enough and didn't immediately produce errors and I'm tired of this and want to move on".

AI code? Well, AI should be very good at generating plain-language documentation of 'what', but it is absolutely going to fail at 'why'.

The additional cost over a normal horizontal ducted turbine is, of course, the new shell and the actuator it requires.

It's like you didn't bother actually reading my post and just responded in ignorance.

It happens here, but perhaps you'd be happier on Reddit?

Ditto

Start with a ducted horizontal wind turbine. If you imagine a bunch of salad bowls stacked with spacers and you get the idea of what it would look like from the outside.

The ducts collect air from any direction and drive it down, through the turbine, and out the bottom. Water doesn't turn corners quiet as easily as air, so you can use the ducts to separate out the majority of liquid and drain it away from your turbine.

Then you and an armored shell of horizontal bands that can be moved up and down to reduce or enlarge the duct input slot area. Instead of having to worry about wind load and braking at the turbine, you control dangerous wind load at the intake.

There's your monsoon-resistant wind turbine.

It wasn't a big theatre-experience movie, it was more like a handful of really good television episodes strung together.

In that sense, it was both a good movie and deserved the bad reviews it got.

1) Not tied to frequent fuel deliveries

2) Does not require much that humans don't already need - sun and air. (Variability will affect your power storage needs)

3) It can be deployed almost anywhere, and even be portable.

The main issue is energy density - if you want to drive hundreds of kilometers a day, run your AC all summer and heat all winter, etc., you're going to need a lot of land dedicated to power collection.

I imagine there are a lot of places in a continent like Africa where people might be happy to get by on what solar can give them in return for not having to worry about burning oil or anything else to get electricity.

BOTH of them? :-)

Everyone knows that 10x engineers validate inputs and carefully manage dependencies; so clearly there's no risk of unexpected behavior.

It seems worth noting that one of the items in Wyden's rather pointed inquiry is the fact that the feasibility of doing this is known to have been demonstrated for the DoD by outside people familiar with it at least as early as 2016; so while this is the first confirmed case of adversarial use it's the outcome of at least a decade of just ignoring the problem; and a significantly longer period of failing to reasonably anticipate the problem. It's not like there's No Such Agency you could ask about "how could you spy on someone with the internet even?" if you wanted to know how well or poorly readily available information matched a nation state signals intelligence apparatus.

Purely as a matter of cellphones being expensive and somewhat tepidly capable in the before times I assume that there was a period within living memory when merely telling people not to Gordon Gekko on their DynaTAC where the russians can hear you was good enough; but that would have clearly and rapidly been getting less true for at least a quarter century.

The whole 'responsible disclosure' preaching and the not-terribly-subtle threats seem particularly bad given that there's an entire industry of actively more dangerous people who are not only treated as legal but actively courted by state agents and cops(and often even less savory customers, though they tend to be cagey about those); the ones who actively seek to keep vulnerabilities quiet so that they can continue to sell exploit tools and services based on them. Throwing zero days on github isn't ideal vs. getting them fixed; but it gets them fixed faster than if Cellebrite wants to hang on to a bitlocker bypass or Trenchant, and L3Harris Technologies Company, wants to keep selling 'network investigative techniques' that can bypass default windows defender configurations or whatever the situation is.

From the outside it's hard to know whether MS actually mistreated the researcher badly enough to justify their displeasure(the consensus appears to be that MSRC was never the best to deal with and has actively gone downhill; but this person's position seems significantly angrier than average) or whether they are perhaps wound a little tight; but implying that their legal status is the same as people actively running attacks against user systems is blatantly false and totally ignores the class of researchers who do actively run attacks while being treated as respectable.

It's a particularly bad look when at least Facebook got into a public legal fight with the NSO group over their nerd-merc work against their users; not like that actually solved the problem of attacks on cellphones; but it was an all-too-rare case of industry pushing back against the 'respectable' arms dealers; and not one that MS has an analog to.