Live data from Hacker News

Fastpotify

fastpotify.rocks

511–520 of 583 posts

Re: Fastpotify

#511
post #199

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?

Not OP but I don’t really care if it was or not. All I know is that I’ve been using the Spotify app 10+ years and it works well. I don’t know if this random app works, and if it hasn’t been supervised I doubt it does.

Gave it a quick try today, it works pretty well and is noticeably faster than the official app.

Re: Fastpotify

#513
post #201

I 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…

Author here. Yes, the code is generated. Yes, the docs are generated. I agree LLM copy is annoying and will rewrite them myself. But I built this for myself out of frustration with the official client, and I use it every day, so every bug I find is fixed immediately. I also care about bugs and PRs from other people, as you can see the amount that have been closed on the repo. The only reason I would stop maintaining…

>Author here.

Not author. LLM manager, technical producer (if we're borrowing game development language), advanced AI user; not author. Authors are those whose code was used to train LLM(s) you were using while producing this fine piece of software. I'm saying this having neither positive nor negative emotions. Just clarifying.

Re: Fastpotify

#514
For me, stock Spotify client on Mac is using ~200MB RAM (no videos / canvas). I probably need to try a leaner build on Fastspotify (built it myself from source), bug the damn thing was using ~350MB RAM. Both RAM counts were based on initial load + playing one song.

Re: Fastpotify

#515
> It starts in well under a second and typically uses 100–250 MB of RAM.

Hmm, a music player now use much RAM :/

Re: Fastpotify

#517
post #238

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 truly has been one of the worst UX experiences and poorly made apps that ever made it to mainstream. I remember a decade or so ago there being a bunch of buzz about them in software dev because they were a microservice node.js/react stack or something with each UI element or portion of back-end having a separate dev team. I can vividly remember thinking "oh that's probably why when I change song sometimes the albu…

> your product doesn't even need to be that good you just need to be first to market and not really piss anyone off.

The product is more than the tech stack

Re: Fastpotify

#518

For me, stock Spotify client on Mac is using ~200MB RAM (no videos / canvas). I probably need to try a leaner build on Fastspotify (built it myself from source), bug the damn thing was using ~350MB RAM. Both RAM counts were based on initial load + playing one song.

have you summed up all the Spotify Helper processes from Chrome? alas its way beyond 200MB. But I just built and ran release build of fastpotify and its also hovering in 500s

Re: Fastpotify

#519

Earlier quoted context omitted.

It truly has been one of the worst UX experiences and poorly made apps that ever made it to mainstream. I remember a decade or so ago there being a bunch of buzz about them in software dev because they were a microservice node.js/react stack or something with each UI element or portion of back-end having a separate dev team. I can vividly remember thinking "oh that's probably why when I change song sometimes the albu…

Totally agree. They also have some stickiness going for them (at least for me). Now that I've organized my music in Spotify and have my habits in place that deal with the crummy UX, I've gotten numb to the poor UX. Case in point, I make a daily playlist for running and that UX is frequently changing and often for the worse, but I deal with it because it's a habit that costs me a few seconds maybe a minute per day. Th…

I definitely enjoy Wrapped. But also something that keeps me in Spotify is the social aspect. If I want to make a playlist for someone, 95% of people I know use Spotify, so I need to have Spotify.

Re: Fastpotify

#520
post #500
post #391

Earlier quoted context omitted.

Apple music still gets a bit of a bad rap, the first iteration of the desktop and mobile apps for it were god awful. And if you lived outside of the west coast of the US, buffering was a noticable issue as they rather stupidly centralised all streaming out of one location in California for a long time. If you hit skip a handful of times from a UK/EU machine for example that was it, game over, apps locked up and you'v…

"...and the recommendations are pretty good" This is so confusing to me, many people say that, but a year ago my wife and I tried to switch to Apple Music. Bad recommendations were the main reason why it didn't stick for us. Every time my children would listen to some kids songs a few minutes later it would start playing "random" songs. Maybe it's similar to Apple Maps, it works good for the American market, but once…

You can disable that behavior in the settings.
Post reply on HN