I think you lived in a strange bubble when you were a kid. When I was a teenager in the 90s, we'd have paper maps that we'd bring with us. We had no GPS. I don't think we knew what GPS was.
In the late 90s we'd print out directions from MapQuest. That was a game-changer. Still no GPS, though.
As an adult in the early 00s, I was still printing out MapQuest maps. In 2004 I got a car with a built-in navigation system! (Complete with a DVD drive in the trunk with a disc holding the maps.) It was still incredibly uncommon; I was one of the few people I knew who had one. I did know a few people who had Garmin GPS devices that they'd suction-cup to their windshield, but not many.
By 2007 most people were aware of GPS devices with little screens that you could bring into the car, though I'd guess maybe 25% of the drivers I knew then had one.
If your dad was bringing a laptop with a GPS dongle in the car in the 90s, I think you were very unusual. Hell, I didn't even have a laptop until 2004, and even then it was a hand-me-down from my dad's work. And I was in my 20s by then!
I agree with you on the work shifting. Whenever someone takes some of our work burden from us, someone else just gives us more tasks to do, and we end up working for the same amount of time. Maybe the work ends up being more interesting or rewarding, though. But sometimes trivial work is a nice physical/mental break, too.
> They really didn't fall short. A lot of people who would've had assistants no longer do, now it's really just the executives like you said. But fairly low managers used to have them and now they don't.
I think the reason for this is labor cost, and "good enough". I don't think a smartphone is an equivalent replacement for a dedicated assistant. The average mid-level manager who would have had an assistant 30 years ago likely (today) spends more time on "assistant-y" work than they would if they had an assistant today. It's just that now they do 30% of the work the assistant did, and their phone handles the other 60%. That kind of ratio is enough to make upper management believe that human assistants for the lower-level folks isn't worth the cost. (While they themselves of course still have human assistants.)
I just booked a round trip for myself, plus two more flights for quicker hops while I'm away, and I didn't spend much time on it at all. I just looked at Google flights, picked the flights I wanted, and then ended up buying them through Chase with points. Chase's travel website is among the worst I've ever used, but it wasn't hard. Then I went to the airline's website and changed my seats (Chase doesn't know I have status and couldn't directly book the seats I wanted) and did an upgrade for one of the legs using miles I had at the airline. Half hour of work, maybe?
The price-setting algorithms are garbage, but an LLM isn't going to fix that.
Agree with the other sibling posters that if this annoys you so much, you should just call up a human travel agent. I haven't used one in many years, but when I did (mostly for business travel), it was always pleasant, and the agent knew my preferences and took care of things if there were any snags or changes needed. At the time, they usually got me flights cheaper than if I were to book them myself, even with their fee on top.
But I do wonder what the profession is like now. I can imagine some sort of website where you often don't even deal with the same person, who won't get to know your preferences and will be sort of like a customer service agent, just trying to close as many cases as fast as they can. But hopefully there are still smaller shops around, where you can talk to the same person (either phone or email) every time. Dunno.
To be fair, you can cancel flight reservations for a full refund within 24 hours, so if the LLM gets it wrong, you're not on the hook for anything.
But in general I do agree: flight bookings are something I want to do myself, because even I don't fully know my preferences when it comes to timing and price until I see what's available. And in general I don't find it all that difficult to do. A couple days ago I booked a multi-city travel itinerary with four different destinations, and it took me about a half hour?
Sure, if an LLM can do that in under a minute, that would be cool, but in absolutely zero situations would I not need to check its work, and if it did get it wrong, I'd have to do it all myself anyway.
>> But, in 2026, writing a greenfield application in a memory-unsafe language like C++ is a crime.
> Don't be swayed by the propaganda. Especially if your application has essentially no untrusted input.*
Eh. I spent many years writing cloud/backend software on the JVM, in between stints writing desktop software. When I was first writing desktop software, it was all in C and C++, and I got used to it, but it wasn't pleasant.
When I came back to writing desktop software in C again (just a few years ago), after writing in memory-safe languages for so long (Java, Scala, Rust, Go), I found going back to C to be just so tedious and annoying. It's just incredibly unpleasant to be chasing down segfaults and data races and crap.
So I think saying it's a "crime" is hyperbole, but even for apps that don't have untrusted input, it's still much more pleasant writing in a language that doesn't let you write memory safety bugs.
(Absolutely agree with you on how it's possible to make nice, small, non-trivial Win32 apps, though I haven't done Windows app development in a couple decades. But I think a lot of people would save themselves a lot of time and headaches if they reached for .NET or something higher level.)
I agree the portals thing is a horrid mess, but you don't need them to take a screenshot unless you're a sandboxed application. Which is probably a good thing.
You can write a simple Wayland screenshot app with a few hundred lines of code[0], and a compositor that supports the ext-image-capture source and ext-image-copy-capture extensions implemented. (Or the older wlr-screencopy.)
I have plenty of criticism for Wayland and its ecosystem, but if you're going to criticize, don't spread FUD.
(I don't like being the guy who has to assert his credentials, but: I've implemented all three of those screenshot/screencast protocols in a Wayland compositor, just a month or so ago, and know how they work, and what it takes to talk to them from a client.)
Also I read through the link you posted. There's a lot of truth to many of those frustrations, but a lot of it is based on misunderstandings of what Wayland actually is. Yes, most people should be using a toolkit. No, it's not great that the main choices are GTK and Qt. I think there's absolutely room for a mid-level toolkit that lets you do the basics without requiring all the Wayland boilerplate. smithay-client-toolkit is one such effort, and I think it's a good start, though something even higher-level on top of it would be nice.
I also don't get the callback hate. I much prefer registering callbacks over a ginormous switch statement that has to dispatch every event under the sun. Toolkits use callbacks too; does the author hate all toolkits as well? You actually could talk to a Wayland compositor with a big switch statement if you wanted, though you'd need to modify libwayland-client to return events as you iterate its event queue rather than dispatch things to callbacks. That could be a fun project for someone who wanted to make Wayland event handling just like libX11 event handling. (See: just a fundamental misunderstanding of what Wayland is.)
And comparing raylib to libwayland-client is silly; they're fundamentally different things. And you can use raylib to talk to a Wayland compositor. It's just a bad-faith argument.
If you want to compare libwayland-client to something, you have to compare it to libX11 or libxcb. And while yes, getting a simple window on-screen is indeed simpler with libX11/libxcb, doing anything more complicated than that is on par with what you'd end up doing with libwayland-client.
[0] Not counting the protocol code that wayland-scanner will generate for you, because that's like saying you have to count the lines of code in libX11 to write an X11 screenshot app.
> Window managers in general, xdotool, all kinds of input mapping and automation or the fact that you can write a screenshot tool in less than 500 LOC are only possible if you talk to X directly.
Honestly I think this is a pretty fair approximation of "no one". How many people are writing tools like this vs. the number of people writing regular applications? A very small number, I'd say.
And after working extensively with both libX11/libxcb and libwayland-client directly, I can say that none of them are particularly pleasant to work with. Actually, no, that's not true: libwayland-client wins, easily. Every single Wayland protocol has code generated for it that works exactly the same way. I suppose the same is (more or less) true of libxcb, but libX11 (and all the other libraries you might have to use, like libXrender, libXrandr, libXext...) are a complete mess.
And even then, libwayland-client has a much lower number of concepts you have to understand than libxcb does, simply because the Wayland protocol has a small number of concepts you need to understand. libxcb is definitely an improvement over libX11, but it can't magically make all the underlying X11 protocol concepts become unified.
wayland.app just HTML-renders the contents of the specification XML files. If a compositor or client is not interpreting nullability the same way wayland.app says it should be interpreted, then that's a bug in the compositor or client.
In the late 90s we'd print out directions from MapQuest. That was a game-changer. Still no GPS, though.
As an adult in the early 00s, I was still printing out MapQuest maps. In 2004 I got a car with a built-in navigation system! (Complete with a DVD drive in the trunk with a disc holding the maps.) It was still incredibly uncommon; I was one of the few people I knew who had one. I did know a few people who had Garmin GPS devices that they'd suction-cup to their windshield, but not many.
By 2007 most people were aware of GPS devices with little screens that you could bring into the car, though I'd guess maybe 25% of the drivers I knew then had one.
If your dad was bringing a laptop with a GPS dongle in the car in the 90s, I think you were very unusual. Hell, I didn't even have a laptop until 2004, and even then it was a hand-me-down from my dad's work. And I was in my 20s by then!
reply