Thanks for making my point for me there bro

I'm going to go ahead and assume bad faith on your part, because otherwise you're very stupid. But nobody in your potential audience is stupid enough to believe there aren't lasting effects to being bombed to shit.

I take your point about this being before the dawn of ubiquitous tech companies, but what kind of chilling effect did the Bell monopoly have?

That's plausible.

I still hate it though. My first version of Office was 4.3, which included Word 6.0 and was ostensibly for Windows 3.1. I'd previously used Clarisworks on Macintoshes in school and before that I used a ghetto cheap program that called itself a word processor but was more of a glorified text editor in MS-DOS that worked well with an Epson dot matrix printer's formatting, so for me Word was great. I felt like the bumpers from Clarisworks had been removed, I had a lot more control over what I could do to a document.

Ribbon feels like they decided that power users didn't matter, and also corresponds with the end of the free Wordpad light-duty word processor and long after Microsoft Works was killed off.

Do you think about me when you're jerking off, too? I know you do.

It would take an AI to not get bored trying to construct working configs for SElinux

They seem to have forgotten why some of their most popular applications became most popular in their respective categories, and that wasn't just leveraging their OS marketshare OEM install dominance. It was a combination of reasonably good UI design that had a degree of intuitiveness along with fairly easy access to more advanced features, with an added dash of the ability to use data from one application in another without major headaches. Arguably MS Office in the days before Ribbon and Metro UIs exemplify this.

Unfortunately they chose to change the UI for change's sake, ie, because users wouldn't recognize that they now had a shiny new version of the product if they didn't flagrantly change the UI, and they chose UI designs that frankly sucked. They also seem to have harmed that interoperability by trying to push too much of it when it doesn't fully work right.

Obviously there have been software companies that had products that for the professionals constantly using them were better, like WordPerfect to Word, but those didn't generally work well for both the power user and the casual user. Originally Microsoft had managed to bridge that gap. But Ribbon and Metro interfaces have harmed the power user, it's now harder to do things than it should be, and power users have incentive to look for software that gives them the features without the bloat.

I doubt that Microsoft is going to understand this in this revamp. They're going to try to cram some UI change solely for the purpose of making it different than the prior version, and even if it's now "native" it's still going to suck. And they're going to try to force any remaining users on prior versions of Windows off of those and onto Windows 11.

Perhaps you did not buy a Tesla. They are probably the most service-hostile vehicle ever sold in the US. Not sure about the UK, I haven't heard stories (horror or otherwise) about service for Chinese EVs yet. They would have to try really hard to be worse than Tesla, though.

A year? I've regularly written that much in a month, and sometimes in a week. And, counter-intuitively, its during those sprints when I'm pumping out thousands of lines per day that I write the code that turns out to be the highest quality, requiring the fewest number of bugfixes later. I think it's because that very high productivity level can only happen when you're really in the zone, with the whole system held in your head. And when you have that full context, you make fewer mistakes, because mistakes mostly derive from not understanding the other pieces your code is interacting with.

Of course, that kind of focus is exhausting, and you can't do it long term.

By focusing on the structure, not the details. The LLM and the compiler and the formatter will get the low-level details right. Your job is to make sure the structure is correct and maintainable, and that the test suites cover all the bases, and then to scan the code for anomalies that make your antennas twitch, then dig into those and start asking questions -- not of product managers and developers, usually, but of the LLM!

But, yeah, it is challenging -- and also strangely addictive. I haven't worked more than 8 hours per day for years, but I find myself working 10+ hours per day on a regular basis, and then pulling out the laptop in bed at 11 PM to check on the last thing I told the AI to do, mostly because it's exhilarating to be able to get so much done, at such high quality, so quickly.

Google xkcd extrapolate

s/best/only/

No, I remember owning a calculator watch with phone directory because I could never remember phone numbers, outside of a few I used all the time. Then I got a cellphone and now I don't need to wear a watch.

Simp harder

I think they're arguing that they are the third thing, a message parlor.

With three wheels? No doubt they will, insert clip of Reliant Robins here :D