I wish someone would do this for Apple Music. Their app is dreadful!
Fastpotify
171–180 of 583 posts
Re: Fastpotify
#172Earlier quoted context omitted.
the commits are very fine grained and the text is unusually not AI. I mean you can beat AI to do anything nowadays, but this looks not that bad
The volume of commits is quite crazy. For example, he wrote a +486/-51 commit in 20 minutes (33287cb) with quite dense rust code. That's about 25 changes per minute -- very impressive! The docs also smell of LLM output, for example describing the app as native despite using egui/wgpu. But hey, he's here, we can just ask him! @earcar
What about egui and wgpu is not native?
Those are both generally what is considered running something natively. Both even mention running "natively" in their descriptions.
I guess what you mean is "OS-provided controls". In that case, ye that is not what this is.
Re: Fastpotify
#173Earlier quoted context omitted.
I've tested Deezer for half a year. The software quality was horrible. Had a lot of crashes, it often took many many seconds to change between the songs and often getting stuck, the buffering algorithm was nuts and eating a lot of bandwidth. Everything on a standard Pixel. Full 5G coverage was available. Alternatives?
Also, I know it's a bit niche, but Deezer does not have an equivalent of "Spotify Connect" protocol, which means that Network Integrated Amplifiers (like Onkyo A-50), CANNOT implement a player with good UX. Spotify is now king since they introduced lossless quality which is enabled by default in such amplifiers. The benefit is that there is no local streaming (e.g. Bluetooth) and no latency. The data come from Spotif…
>The benefit is that there is no local streaming (e.g. Bluetooth)
how is a lack of an offline, standard, widely supported option a benefit?
Re: Fastpotify
#174Lots 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.
Re: Fastpotify
#175I realise I’m pissing into the wind here, but I find the LLM text on the homepage and docs quite funny/ awkward. > “Ctrl+M turns it into a tiny player that wears any classic Winamp 2 skin, spectrum analyser, equalizer, and playlist included. 2000s vibes, pixel for pixel.” Everything is said with too much intensity, and phrasing that sounds impressive but doesn’t really mean that much. Like “wears any classic Winamp 2…
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 the past, these documentations also had little text. So they were easier to digest. Now, we get great walls of text that are hard to read. I cannot say that I like that.
Re: Fastpotify
#176Spotify used to use Qt for its desktop client. Good times.
Good times. The old Spotify client was native and fast. I miss that. The new one is heavy and clunky.
Re: Fastpotify
#177Vibe coded or not, Spotify is a disgusting company for artists, however fast or fancy it's made.
Re: Fastpotify
#178I realise I’m pissing into the wind here, but I find the LLM text on the homepage and docs quite funny/ awkward. > “Ctrl+M turns it into a tiny player that wears any classic Winamp 2 skin, spectrum analyser, equalizer, and playlist included. 2000s vibes, pixel for pixel.” Everything is said with too much intensity, and phrasing that sounds impressive but doesn’t really mean that much. Like “wears any classic Winamp 2…
Slop code is already hard to tolerate, but any hint of slop in text will immediately make me chuck it into the bin / close the tab, no exceptions. My lifetime is finite, I'm sure as fuck not gonna spend time reading something that a person could not even be arsed to write themselves. I'm only annoyed that it takes sometimes a few seconds, sometimes a few minutes, to detect that I'm actually not reading a person's thoughts but only a machine simulacrum of such.
I highly recommend anybody to take up a similar rule, in any context. Slop in a website? Close. Slop in an email? Bin. Slop in a code comment? Skip.
Re: Fastpotify
#179Lots 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?
Re: Fastpotify
#180What do you all use to buy music these days? I've been slowly trying to stop my spotify usage and replace it with owned audio files. Mostly I try to use Bandcamp but many artists are not there. Sometimes I just rip the audio from youtube but would prefer a way to buy that gives most of the money to the artist.
I don't stream and buy all my music (aside from radio etc), I get music from:
- Bandcamp (for new music)
- Second hand CDs for charity shops and discogs (for older music)
- Quoboz / Amazon (for new music not on bandcamp or something specific I can't find elsewhere)