There is no music monopoly and customers have a choice in which music they listen to and what service they use (Spotify, Apple, Google/Youtube, Amazon, Bandcamp, buying CDs).
Surely if users get served worse music, they will dislike it, and move to another service or another way to listen to music.
How big (and noticeable) does the reduction in quality need to be. Especially because spotify is such an easy platform.
Changing to another streaming service requires learning a new app, moving over all playlists, and likely means still a pretty bad music suggestion service. Because spotify has a pretty good recommendation engine.
it's not for me. YT was. SoundCloud too. (Now SoundCloud also wants folks to sign in aggressively. I think you can't fast-forward otherwise, but at least listening works without signing in.)
Also ... you can upload to YT and SoundCloud, but not to Spotify. So their catalog is just meh. (So even if their recommendations are great in some genres, in general they are not for everyone.)
I think it's a joking dig, saying that dynamic (interpreted) languages are stupid while compiled languages are not. `im_stupid()` is not defined, so there should be a compilation error. If it first prints the output of `print` before giving an error about `im_stupid` not being defined, it's a dynamic language, and (according to the author) that's stupid.
I agree with all of the points, except the last. Protobuf is a nice transfer format but it's horrible once a human wants to inspect or copy/paste a payload.
Exactly. And this is an extremely important detail. It makes your development process go from using glass tubes where you see everything as it is sent/received to black boxes of binary data.
JSON is self describing, you can mostly just call the API, read the JSON response and figure it out from there.
Ignoring that detail is ignoring the elephant in the room.
100%. The topic is to post side projects making $500/month. Not to post failed side projects, projects that generate little to no money, or that cost money.
> they only started to look nice when React moved to Hooks and functional components
Is this a widely held opinion? Call me crazy, but I really liked class components. It was nice to see the lifecycle stages in the actual method names, and encapsulate the behavior inside of a method block. To me that was really nice to read.
With hooks, everything is inside a function without clear delineation. The lifecycle stages are put anywhere in there with (to me) strange looking calls to useEffect and such.
Before, I used to love whipping up a quick UI in React, but since hooks I loathe doing that. I really don't want to upgrade my existing apps to newer versions. And for potential future project I'm looking for an alternative.
Perhaps I don't like it so much because I'm primarily a back and systems engineer, and only do small frontends on the side.
Hooks are awful. They’re a faux-functional interface, accessing implicit local state, with so much magic going on behind the scenes that it’s obscene. At least in class component days it was obvious which components were stateful. Now you’ve got to remember which magic hook incantation is causing your “functional” component to improperly cache state and why. I cannot for the life of me see it as an improvement in any way other than “it looks nicer,” which aligns with the top-level parent’s point.
Anyway I think react in general is kind of terrible. I’ve worked at three places whereFE teams made a react codebase that wound up being so scary and difficult to work in that essentially no one would touch it, until it eventually got rewritten. Two of those just rewrote it in react again, hoping that whatever faddish state library would save them from themselves. At the third, they rewrote it in svelte, which went much better. At least for me as someone who only writes FE code when I have to, svelte is much more comprehensible and sensible.
Zero power draw is still less than a little power draw. A couple million of these babies running on idle is a considerable amount of power. Please, turn off devices when you're not using them.
Any modern computer system uses a lot of power for a few minutes after bootup. If you use the machine a few times per day you're wasting energy (and your own time) by turning it off instead of using sleep mode.
Completely agree! We just 3D printed a base switch that makes it easy to turn your Mini on and off. Here's a link: https://m4button.com/ (if you have a 3D printer, you don't need this).
