251–260 of 588 posts
My spouse, for example, doesn't interact with her clock app anymore—she just talks to it.
Wouldn't many programs just use a local LLM to perform whatever is needed?
Earlier quoted context omitted.
Devs are constantly making the mistake of falling in love with immediate mode GUIs... because it's convenient for them , the developer. For the user, it's almost always a worse experience as things don't behave in the same way as the rest of the platform they're on. egui is great for video game debug UI overlays and internal tools, and maybe some specialized graphical tools. Otherwise its quirks are too annoying for…
Can you list your exact complaints? It's a GUI like any other.
Lots of people seem to care about whether a project was built by hand over time by a few committed developers, or if it was vibe-coded in the past week by a single person. Whether the distinction matters or not, it would be nice for everyone involved if projects falling into the second category were more upfront about that.
As a matter of interest, would seeing a full disclosure that vibe coding was used sway your decision one way or the other?
Earlier quoted context omitted.
If it can transform into Winamp I don't care if the code is LLM generated, typed by infinite monkeys or found in some ancient scrolls. Jokes aside, how can you be sure that the official Spotify app (or any app, or Windows) was not written by a LLM without supervision?
The official Spotify app has some skin in the game. Random dudes self promotion project, not so much.
Earlier quoted context omitted.
Interestingly enough, https://fastpotify.rocks/winamp/ shows what I dislike about LLM-generated text: From "The buttons do what they say [...]" to "[...] a different format and are not supported" is just a huge wall of text without any visual guidance. It's as if the person writing these lines didn't care about the result. One could argue that people not caring about written documentation isn't anything new, but in t…
I prioritized shipping over carefully crafting docs. I thought nobody would read them and they'd rather enjoy the software. I was wrong. I'll rewrite them.
Earlier quoted context omitted.
Interestingly enough, https://fastpotify.rocks/winamp/ shows what I dislike about LLM-generated text: From "The buttons do what they say [...]" to "[...] a different format and are not supported" is just a huge wall of text without any visual guidance. It's as if the person writing these lines didn't care about the result. One could argue that people not caring about written documentation isn't anything new, but in t…
I never thought ubiquitous human-written marketing wank was any better.
Spotify is, without doubt, the worst piece of software that I still use on a daily basis. It's incredibly buggy, incredibly slow, and the UI has so many "usability inconsistencies". I find the Android app particularly bad, just a couple of examples: - Under a playlist you get a list of suggested songs, the UI element looks like a "regular song", but unlike every other "song" element the user has been trained to recog…
It's a music player, and it's way too heavy for what it does. Well, it does a lot it doesn't need to, too. Uses 1.5GB of RAM on my laptop atm. Since I only have 16GB on my work laptop that's noticeable. I'd love it if Spotify AB could replace its client with a native Rust one, although using an immediate-mode GUI library like fastpotify does might not be the best option... Is there any music streaming service with fa…
Obviously streaming was the big selling point, something that iTunes didn’t offer at the time, but I swear the client was written in some native UI framework, along with the C/C++ library.
Or was the spotify UI always just a browser engine skin and the perception of speed was from the playback engine?
Anyway, cool to see projects like this