VibeSurgeon
@VibeSurgeon@piefed.social
- Comment on 1 week ago:
It doesn’t hurt to have the component that is optimized for drawing things to the screen be a bit more involved in drawing things to the screen.
Strictly speaking necessary? No. Does it hurt? Not at all.
- Comment on 1 week ago:
“Native” sort of loses its meaning in this context - this new client is not “native” in the sense of using the existing GUI tooling for each platform (Cocoa for macOS, any of Microsoft’s own frameworks on Windows, primarily Gnome/KDE on Linux).
It is using a universal framework in GPUI, so the experience will be the same on each platform.
It is “native” in the sense that it’s not web technology on any of the platforms.
- Comment on 1 week ago:
The price of memory-thing is probably not that important as compared to the AI-assisted coding thing. Making things in Rust when you have access to AI tools is dead simple, which was always the argument for making things in Electron. Porting things from one language to another also happens to be one of the sweet spots for AI coding tools, they thrive on tasks that have very clear specs - an already existing codebase with tests is just about as clear of a spec as you can get.
- Comment on 1 week ago:
I’d be willing to bet $100 that AI assistance was involved in creating this new client, yes.
Similarly I’d bet the same amount that AI assistance was involved in building the former electron-based client
- Comment on Plex vulnerabilities being exploited in the wild to drop a cryptominer 3 weeks ago:
Jellyfin is based on the Emby-codebase before they relicensed it as closed source.
- Comment on Mayonnaise: a macOS like UI framework for Linux (no QT, GTK) 4 weeks ago:
Hell of a choice to go for C++ over Rust if you’re just going to vibecode the whole thing anyway
- Comment on [deleted] 1 month ago:
This is a really strange thing to brag about
- Comment on [deleted] 2 months ago:
Who said anything about a problem?
- Comment on [deleted] 2 months ago:
Lots of podcasts come with sponsor segments baked in. This is basically shipping a SponsorBlock light on-platform
- Comment on Firm quietly boosts H.264 streaming license fees from $100,000 up to staggering $4.5 million 7 months ago:
It depends on what the receiving unit can decode. Sometimes there will be transcoding, but it’s usually something you want to avoid.
- Comment on Firm quietly boosts H.264 streaming license fees from $100,000 up to staggering $4.5 million 7 months ago:
These things always happen because of how dumb software patents are. There’s no guarantee the lawsuit will stick, nor do I necessarily expect it to
- Comment on Firm quietly boosts H.264 streaming license fees from $100,000 up to staggering $4.5 million 7 months ago:
Hardware encoder support I think is generally less critical. Decoding is the process that needs to happen real-time, while most encoding can be done far in advance, unless you’re live broadcasting or operating at YouTube-scale.
- Comment on Firm quietly boosts H.264 streaming license fees from $100,000 up to staggering $4.5 million 7 months ago:
AV1 already wins handily as a codec, and the only thing keeping it from being adopted more broadly than is currently the case is lack of hardware decoders on older hardware. This problem naturally solves itself as old hardware gets replaced.
Even then, dav1d is a remarkable piece of software, and software decoding is pretty viable for AV1 thanks to it. Many places have already adopted AV1, and you should expect to keep seeing it get adopted as time goes on.