s6af7ygt

I'm a dunce

I'm a dunce

(Sarcasm warning). Surely the music industry will be fine in the long term when everyone switches to Google, Apple, and Amazon.

That is just serving customers worse music.

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.

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.

How much is just survivorship bias?

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.

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.

Different people have different preferences and life circumstances.

Great work!

I played for a few minutes but then I couldn't pick up anything because I could only carry 6 items. After a few cycles of "let's see what I can drop to pick up the new thing" I just stopped playing, because that is not a fun loop to me.

I dislike TypeScript, and I feel it's mostly fake. There are plenty of ways to accidentally bypass the "type system" and do stuff that should be illegal in a statically typed language but work because there's JavaScript underneath. I feel TypeScript adds extra cognitive load that isn't necessary and isn't really adding much value. JavaScript is simple, easy, and works well. I wish more people would invest in learning to write better JavaScript, than to have the flaky facade on top of it.

Then again, I'm not a front-end dev, I just do hobby projects with JS.

I don't get why to use an ORM in the first place. Just define a bunch of structs, run a query, map results to structs. It's a few lines of simple code. You're in control of everything (the SQL, the running, the mapping). It's transparent. With any ORM, you give away control and make everything more complex, only to make it slightly easier to run a query and map some results.

I think the whole problem is just terminology. For example take your comment. You start talking about unit tests and units, but then suddenly we're talking about components. Are they synonymous to units? Are they a higher level, or a lower level concept?

People have such varying ideas about what "unit" means. For some it's a function, for others it's a class, for others yet it's a package or module. So talking about "unit" and "unit test" without specifying your own definition of "unit" is pointless, because there will only be misunderstandings.

I just hate the fact that Go is super simple and clear but people try to make it complex with this kind of stuff. :( Makes me sad.

The example on the blog post is one of those that makes me severely question HTMX and the stuff that we're doing. Doing HTTP requests to increase a counter, or affecting any local-only state change at all, seems so wild to me.

Can you elaborate a bit more, so us ignorant people may share in your excitement? I've seen many people switch from JVM to Go, but I've not seen a lot of people switch from Go to JVM.