lucsky

A misspelling of "copy-on-write".

Because despite what the tagline says it's not a package manager, but a project manager.

And yet you claim that you have a "deep understanding" of how React works. Why did you ask an idiotic LLM then? Doing it yourself would have allowed you to be even more dishonest with your examples... :>

The author of this article and framework either doesn't have the slightest beginning of a clue how React works or is just being extremely dishonest. I'm all for alternative and new ideas, but this is not it and the way it is presented is just plain wrong.

Hard pass.

I fully support artists to decide what they want to do with their music, but artists who sign contracts with labels and music companies do give up their rights, like it or not, that's how it works. And yes, Spotify enforces contracts and geographical licensing deals that dumbfuck lawyers invent because reasons. What would you want them to do, break IP laws?

+1000

There's absolutely no way in hell I'm going back to hoarding stupid ass CDs or MP3/FLAC files when I can legally have immediate access to tens of millions of titles. I have absolutely zero interest in the "owning" part but I understand some people would prefer it.

Yes it is. If it's not available for you then blame the fucktard lawyers who made the call that it should not be available wherever you are for some dumbfuck reason. Spotify is not responsible for this, they just comply with the aforementioned fucktard lawyers.

It’s not size

That's what TFA is complaining about: size. But nice pivot, hope your head isn't spinning too much.

...in four years Trump will be gone and normalcy will be restored

Tell me you haven't been paying attention to what's going on in Trumpistan without telling me you haven't been paying attention to what's going on in Trumpistan.

Unbelievable.

I don't have "JavaScript fatigue", what I do have is "JavaScript is a dumpster fire and React is the spawn of Satan" daily blog post fatigue.

JFC.

My Python and Go apps from 2018 still work exactly as they did on day one

My NodeJS apps from 2014 still work exactly as they did on day one as well, what's your fucking point?

since Xcode only got this crappy recently

Xcode has been slow, messy, buggy and all around atrocious to use since day one. Being forced to migrate from MPW and Code Warrior to this utter piece of garbage has actually pushed me to web development.

Kitty is cross platform

In the absolute lowest sense possible, which means that it's been compiled for different platforms and it runs on different platforms, but it also looks and feels completely alien on anything else than a Linux machine with a tiling window manager.

That you can use without having 4 PhDs. It's pretty good. You should try it sometime when your done fully ingesting algebraic topology theory or whatever the fuck Nix requires to know just to install figlet.

Overriding standard language constructs with magic behaviors is a giant no-no and a recipe for disaster.

having worked with both more or less equally, I'd choose Vue 10/10 times over React

I have the exact opposite experience, I find Vue hilariously bad to the point of being repulsive. Now what?

Right, and people would obviously love those same apps if they were written with Vue instead. Of course.

Again, you can still use class components today, feel free and have fun.

1. Nobody said that classes are bad. Yes you can encapsulate logic and state in a singleton, that's not the issue, the issue is how you then "apply" it. There was a fantastic diagram that (most likely) Dan Abramov posted on Twitter a while ago (before it became the olympic pool of diarrhea that it is today) that was demonstrating the superiority of hooks in a beautiful and obvious way but I cannot find it anymore... :/

2. Sorry but if you keep using "weird", "hard" and "complicated" adjectives to define something that is quite honestly not so hard to grasp you make it hard to not go with "skill issues".

So he's basically publishing a 20 pages philosophical logorrhea to make the simple point that developers should pay more attention to the difference between a web SITE and a web APP and choose their stack accordingly, which is a totally fair point to which I 100% agree with.

What I fail to see is how React is responsible for any of this because this sort of reads like his wife left him for one of the React engineer or some shit.

Painfully so.

Nowadays there is layers upon layers of magic like Functional Components with State from Hooks.

1. you can still write class based components if you want, but if you are in a team everyone will hate you for that because... 2. the preferred and vastly more flexible and powerful way is functional components. That's it, there isn't any other way or any other mystical layer of magic.

What everybody in this umpteenth omfg-react-is-satan thread is that implementing complex things with simple things is a fucking pipe dream. Fucking deal with it.

The hooks API is just awful

Hard disagree. Hooks are 100% what is best about React these days and custom hooks make organizing or encapsulating and sharing behaviors between components a total breeze.

I haven't yet reached the end of the comments, but I'm also fully expecting at least one "Electron is a cancer that is eating my computer and the reason why my wife left me".

How in the everlasting love of rollerblading Jesus is a post about a new version of Blender devolving into a squillionth bullshit nonsensical rant about how boo-fucking-whoo Electron is so bad. My mind is blown. You guys are absolutely exhausting.

Agreed. This is dumb AF.

LXC vs... um... (sigh)...

Just did it:

  $ brew update && brew install deno
  $ deno --version
  deno 2.0.0 (stable, release, aarch64-apple-darwin)
  v8 12.9.202.13-rusty
  typescript 5.6.2

Seeking absolution from the music industry?!? From those exploitative bloodsucking parasites?! Pardon my French but fuck the music industry. Do you know that, here in France, when you buy ANY hardware that can potentially store digital music (a hard drive, a USB key, an mobile phone, whatever) you pay a tax that goes to the fucktards of the music industry? Today, in 2024, when pretty much everybody turned to streaming. Yep. I sincerely hope they all end up unemployed.

I vividly remember the moment when I turned on them: as soon as I started to have income during the 90's I used it on music. I was buying at least 5 or 6 CDs a week, I was tracking new releases obsessively and was making it a principle to pay for music. When MP3 exploded I started to encode the music I was buying, because that's pretty much how and where I was listening to it: on my various devices. But when the music industry started to feel the heat from the Napster and Limewire alike they reacted in the stupidest possible way: being user hostile and considering their own clients as potential thieves. The various copy protection systems they came up with started to be annoying but the nail in the coffin for me was a Jay Jay Johanson album that I simply could not play on any of my devices because of this. I gave them the middle finger and started to download, right this moment, without remorse. I only came back to paying when streaming started to be easier and better than downloading.

The music industry is mostly just disgusting pigs only worthy of contempt and disdain.

Not "hard" to use, no, nobody's saying that. But painful to use for anything else than scroll/click/play, absolutely yes.

Active music discovery is terrible, tracking your "progress" in your weekly releases listening is actively being made impossible (the list is seemingly being re-randomized, at random), the obsessive emphasis on tracks rather than albums or artists is very limiting, UIs are not flexible enough, and I could go on for a while.

All streaming clients are currently hot garbage. Again, not hard to use, just extremely user hostile for anything more than click and play.