> So this only works on products that was developed before ~now.
You're under the assumption that the companies producing these give a shit about security. It'll probably increase a bit but I doubt it will be by much. If they have shipped devices that leave the doors wide open for almost any intrusion, they won't invest engineering/AI time and money to make these better than before and certainly won't review the code that the model spit out beyond a quick check if the promised base functionality still works.
One example is a field that clips its contents to contain zalgo, but inadvertantly to the point where some glyphs can render completely out of bounds. Sometimes the clipping is so egregious that even descenders of normal letters like 'g' get cut off. (This is more common than you'd think.)
True, rendering out of bounds doesn't make something actually whitespace, it just means it could look like whitespace. Though, consider the case where someone is looking to detect if a character is whitespace, when what they actually want is to detect if it could look like whitespace. That's where context comes into play. Irrelevant if it's not about the looks, but potentially relevant if it is, hence why I figured I'd leave a quick comment about it here.
"One implementation of a feature had a bug, therefore this feature should be turned off on all implementations by default" is probably not going to convince people who think the feature is good.
If you don't want to be able to have clickable hyperlinks, by all means use Konsole — no one is forcing you to use Ghostty. But if you want to know why people like Ghostty's approach vs Konsole's, it's because Ghostty pushes terminal emulator features forward and is low latency. Konsole is low latency and adopts some but not all features that other people invent. It's a noticeable difference and so people who like the feature part of the former like Ghostty/WezTerm/Kitty more than Konsole. If you don't care or dislike that part, and want a more conservative terminal (that is also low latency), Konsole and many others further on the conservative spectrum exist.
It’s not just one implementation. Browsers have been struggling to get this right for decades and now we are destined to repeat all the same problems all over again with an entirely new syntax of inlined markup.
Bugs are fine, but this wasn't really a bug. It was lack of foresight.
I haven't used Konsole, but I do like this "recent" focus on terminals and have used many of the newer ones. Dailydrived st,alacritty,wezterm,ghostty,kitty,foot (probably forgot some) and I live for the regex pattern matching copy shortcuts etc.
I learned about OSC8 because my terminal (whichever it was) used one of its features and I didn't know it was possible to do that. My immediate thought was, how is the security?
And it is very disappointing to see how little effort people have spent on that. That is really one part that I expect more from modern incarnations of the old terminals where I can sort of forgive them for the lack of security posture.
I like ghostty, I really do. But this is not a good look, and to be clear it isn't just ghostty. Without looking for it I've stumbled upon several OSC8 and OSC52 bugs (in other software) recently.
I'd say that balancing those aspects are exactly what an AI excels at. And an AI can iterate in a way a human wont. Completely redesign something because an edge-case could be slightly better.
AI isn't brute-forcing, or it would have been completely unusable for code.
Author here: as I wrote in the piece, I've recently dumped Photoshop for Pixelmator Pro. It doesn't currently support AVIF. Photoshop does, but not in a way that makes it easy to optimize an image for web export. JPEG XL is also exciting to me, but it's not generally available across browsers. WebP is the current best image format for my use-case, but I'm hoping others supplant it soon.
>but it's not generally available across browsers.
Note that this is changing rapidly. Safari ships JXL, Chrome did a few days ago, and Firefox will in the next few days. Once this flows through to all the chromium based browsers we will see pretty much 100% support on the web.
Would be cool to buzz the message itself in morse code, though todays buzzers are so weak I don't think I'd be able to make it out (if I knew morse code, that is).
But would be cool with a separate buzzer of sorts where you get the normal buzzer notification and then hold a finger somewhere specific and get details that way.
Would you also argue that the technical quality, efficiency, capacity, performance etc. of a piece of machinery, too, is way less important than the social and political values of its manufacturer? Say, a piece of medical equipment used in a hospital to keep a patient alive.
I'm sure nobody will, but I disagree that it's an apples and oranges thing. But for you I'm willing to instead offer an example of a CNC machine making parts for... anything. The question and comparison is at its core still just as valid and relevant. Is the result way less important than "feeling good" about the solution?
Most people don't use MS office by choice though so "goodness" isn't a particular relevant metric.
reply