Basically, yes. I believe the logic was "our keylogger will hook into the OS before any malicious keylogger does so it can prevent those bad guys getting your keystrokes"
Networking, as we all know, is a rats nest of complexity and edge cases. I think software started getting worse when a high speed internet connection became a given.
90s software ran mostly offline. It was simpler and more deterministic. I think that's why it felt more reliable. Your UI couldn't depend on laggy server round-trips. Things either worked or they didn't.
Yes, absolutely. I don't recall Winamp ever crashing on me (maybe after they introduced frame-breaking skins), meanwhile Apple Music needs to be restarted at least once a day. At the same time my local music server has been up for months without an issue. It's not really an issue of quality it's an issue of inconsistency with network state, which a lot of apps seems to want to make even worse by now passing their networked state to another AI process.
YouTube on Android gets into a state where it just ignores tap to expand the comments section (always the comment section that breaks like this) until you force stop the app.
Also, force stopping the app remembers the video you were watching, but deletes the queue of next videos you built up.
We elected to take some of the hardest problems in computing - networking, distributed systems, parallel and concurrent programming - and make them the defacto standard for a Tasks app.
The young'uns all cut their teeth on the web, where every project tends to reinvent the wheel (poorly).
It's funny (depressing) to me that there is now "web app" design language and a "native app" design language, and most new desktop apps are following the web because they are built in html and CSS.
As with most creative pursuits, the best things happen when there's a clear point of view.
Unfortunately, the best things aren't always the most commercially successful, because products are only a small part of what makes a company successful. I think we're seeing this play out in the software market.
JIRA might be objectively awful, but it still manages to print money!
> "what would happen if we only designed for large monitors?" What would it unlock if there were desktop designs that ignored laptops and only focused on widescreen monitors?
There's something to this thinking. Large workstation monitors are very much their own thing.
A real example l I've found: Niri (scrolling window manager) is really nice on a laptop but awful on my 6K display. The windows are way too tall, and the induced motion of large windows on a big screen is too much.
Have you tried turning your screen vertical, if it supports that? Way underrated. Instead of useless side space that would make lines too long to read if it was used, you get useful vertical space to display more of a document at once.
But episodic memory (the timeline so to speak) is powerful too. Consider "list all pictures I watched in the last two days".
Both are important. Combine it by saying "distribute them on the screen from left to right sorted by how long I looked at it in ascending order".
I think local AI would come in quite handy to tag files and keep the tagging consistent..
Personally, I think a lot of the enjoyment comes from learning to overcome challenges. Jumping in to an unfamiliar problem space, sucking at it, then grinding until it all clicks.
Generative AI takes away the grind, which takes away the learning. How do I master a new language if I'm expected to code via an LLM from day 1?
It's also well understood that the act of writing is when thinking actually happens. You have new ideas, opinions form, and so on. I think it's the same with writing code. But when you're not writing code any more, you don't go through this process.
I wonder if an LLM-authored project would even end up solving the same problems that a human-authored project would? If a human didn't write the code, then a human didn't have the chance to think in the same way. They didn't spend time trying to think of a good variable name, which made them realise the whole premise was wrong...
Agreed, there may be people working with their LLM tool to learn something new. In my experience this isn’t the way these tools are marketed, from where I sit it looks like this is being discouraged. If you aren’t really learning anything then all you get at the end is the product. For a certain type of person this is just not enough.
I bet people generated solutions end up significantly different from AI generated solutions. People learn more about the problem as they work it through and they don’t always end up with the thing they were imagining when they started.
> I bet people generated solutions end up significantly different from AI generated solutions. People learn more about the problem as they work it through and they don’t always end up with the thing they were imagining when they started.
Exactly!
And to be clear, you can learn a ton from LLMs. An expert teacher with infinite patience -- what an amazing thing. But there's a different kind of learning that only happens with practice, and that's what you don't get when a computer does the thinking.
Your brain is hardwired to find shortcuts. Once you have an LLM at your disposal, it'll be real hard to abstain from using it to do the hard bit.
Someone on Twitter put it well: using an LLM to learn is like using a forklift to lift weights in the gym. Yes, action is happening but the point of going to the gym is not to ensure weights get displaced up and down.
That's a bizarre analogy. If you're actually committed to learning (vs having the LLM spit out code you don't read), using an LLM as a teacher is more like working out using weight machines vs dumbbells. Just two different methods of arriving at the same destination, with different pros and cons.
>It's also well understood that the act of writing is when thinking actually happens.
For me the more interesting and productive thinking happens when I'm trying to understand what I want the code to do, not when I'm thinking about the implementation details.
IE6, ActiveX controls, and mandatory keyloggers for online banking: https://en.wikipedia.org/wiki/Web_compatibility_issues_in_So...