Comment Re:How the fuck? (Score 2) 70
Maybe they do streaming backups, and he just duped the stream.
Maybe they do streaming backups, and he just duped the stream.
At first I was like "Yay! A win for Right to Repair!"
Then it occurred to me... How much does an average John Deere tractor/combiner cost?
They can be $500 Thousand, or even a $1 Million each? Then this $99 Million "fine" isn't that much at all.
Also, they only have to provide repair docs for 10 years? So in 15 years, farmers will be SOL again?
Great. I feel like nothing was actually fixed here. The fee was too lo, the fix is temporary. John Deere got away with a great deal here, as they will keep their customers and recoup their costs in a matter of a few weeks.
The only way I see this as a positive is if John Deere, in the course of these 10 years of open documentation, discovers the benefits of happy customers and a diverse repair ecosystem. But I doubt it.
It might be a hallucination, or it might be a real problem. And there are other possibilities. (E.g. earlier it was suggested that MS noticed a bad bug *somehow* and the government didn't want the bug to be fixed.)
If you want to be fair, it's been headed that way ever since the 1860's. And prior to that the individual states were headed that way.
People in power like to make their jobs easier.
"Security by obscurity" doesn't work by itself. It's a necessary component of every security policy, however. You can't just pick one. (It's called "defense in depth", but that's not really a good metaphor.)
If you thought what they could fake in the late 60's was impressive, imagine what they an do now.
It just sucks to see them screw up the illusion with such trivial mistakes. Are you seriously expecting me to believe they'd go with a broken toilet? Or use Outlook?
Or iPhones?
I have not seen AI code that is *more* efficient than human code, yet. I have seen AI write efficient, compact code when pressed, very, very hard to do so, but only then. Otherwise, in my hands, and those of my developer colleagues, AI produces mostly correct, but inefficient, verbose code.
Could that change? Sure, I suppose. But right now it is not the case, and the value system that is driving auto-generated code (i.e., the training set of extant code), does not put a premium on efficiency.
But you've got to do both. Doubting oneself is "critical thinking". Doubting other sources of authority is "independent thinking".
The thing is, nobody has enough expertise to be an independent thinker in every area. So you essentially MUST delegate your ideas in some areas (variable between people) to external authorities. At which point what you "believe" depends on which authorities you choose.
A related question is "how firm is that belief?". This also tends to vary wildly with little apparent (to me) reason behind it. This is one feature that *can* be related to IQ, but isn't always.
Web browsers are absolute hogs, and, in part, that's because web sites are absolute hogs. Web sites are now full-blown applications that were written without regard to memory footprint or efficiency. I blame the developers who write their code on lovely, large, powerful machines (because devs should get good tools, I get that), but then don't suffer the pain of running them on perfectly good 8 GB laptops that *were* top-of-the line 10 years ago, but are now on eBay for $100. MS Teams is a perfect example of this. What a steaming pile of crap. My favored laptop is said machine, favored because of the combination of ultra-light weight and eminently portable size, and zoom works just fine on it, but teams is unusable. Slack is OK, if that's nearly the only web site you're visiting. Eight frelling GB to run a glorified chat room.
The thing that gets my goat, however, is that the laptop I used in the late 1990s was about the same form factor as this one, had 64 MB (yes, MB) of main memory, and booted up Linux back then just about as fast. If memory serves, the system took about 2 MB, once up. The CPU clock on that machine was in the 100 MHz range. Even not counting for the massive architectural improvements, my 2010s-era laptop should boot an order of magnitude faster. It does not.
Why? Because a long time ago, it became OK to include vast numbers of libraries because programmers were too lazy to implement something on their own, so you got 4, 5, 6 or more layers of abstraction, as each library recursively calls packages only slightly lower-level to achieve its goals. I fear that with AI coding, it will only get worse.
And don't get me started on the massive performance regression that so-called modern languages represent, even when compiled. Hell in a handbasket? Yes. Because CPU cycles are stupidly cheap now, and we don't have to work hard to eke out every bit of performance, so we don't bother.
It's not just widespread, it's universal. What varies from person to person is the domain that they apply thinking to, and how they validate the authority they choose to trust.
Nobody is an "independent thinker" on every topic. Wherever one is an expert, one tends to be an "independent thinker" in that domain. Where you don't feel knowledgeable, you tend to accept an authoritative source...possibly after doing some amount of checking to see whether others think it reliable.
I don't think it's directly related to IQ. I also don't think it's restricted to chatbots. A lot of people are willing to accept the opinion of any authoritative source that they've accepted. Think religion or political party. Once they accept it, they stop questioning it's proclamations.
Note that this also applied to those who accept the proclamations of scientists or compilers. Once you accept an authoritative source, you pretty much stop questioning it. It's been multiple decades since I really argued with a compiler...unless it was a known bug from a source I trusted. I generally just assumed that I misunderstood what the language meant by that construct. (Of course, the few times I really didn't accept it, I eventually turned out to be wrong. Oh.)
A dummy load and some chemistry to use oxygen would do the same job with zero human risk.
If they're not putting boots on the Moon, they shouldn't have their asses in the rocket.
Remember kids, spaceflight is hard. Nature does not like us being in space, at all. She puts up serious, difficult barriers that we need to overcome. Just look how hard it was for a new program like Space X to start from scratch even with all of the existing knowledge developed by NASA, ESA, etc.. How many rapid unscheduled disassembly events did they suffer? I lost count. Even the Russians, who arguably have as much or more LEO experience than the US, continue to face challenges. Heck, so do we, as the current generation of engineers no longer has the direct experience from Gemini and Apollo to guide them. Space is deeply unforgiving of mistakes.
To the GP, if you think that your 5-second considered opinion is better than a fleet of talented folks, I'll wager that if you more time, did some research, you'd change your opinion. I hope you do.
What's the difference between a computer salesman and a used car salesman? A used car salesman knows when he's lying.