I don’t understand why a package manager needs lint support.
Because despite what the tagline says it's not a package manager, but a project manager.
Readit Newslucsky commented on Lux: A luxurious package manager for Lua github.com/lumen-oss/lux... · Posted by u/Lyngbakr
lucsky commented on Hyper – Outperform React on every metric nuejs.org/blog/introducin... · Posted by u/ZephyrBlu
Yes. I asked Claude to write the most idiomatic React to implement both the ShadCN and the old school React examples.
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... :>
lucsky commented on Hyper – Outperform React on every metric nuejs.org/blog/introducin... · Posted by u/ZephyrBlu
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.
lucsky commented on Jellyfin as a Spotify alternative coppolaemilio.com/entries... · Posted by u/coppolaemilio
Their point is at a higher level than a single artist's inclusion. What you're advocating is for artists to give up their rights (whether primarily or indirectly negotiated). "Just do what the lawyers say."
I didn't think Spotify had fanboy/fangirl followings, but based on your and others' comments, I stand corrected. What do I know!
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?
lucsky commented on Jellyfin as a Spotify alternative coppolaemilio.com/entries... · Posted by u/coppolaemilio
Meh, the two ideologies are a tradeoff decision.
If you own, you don't pay subscription and can use that money to buy. And in tenuous circumstances you have control.
If you subscribe, you don't pay money to buy massive library. But in tenuous circumstances you don't have control.
Everybody rates the risk of tenuous circumstances differently and so that affects the decision outcome.
+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.
lucsky commented on Jellyfin as a Spotify alternative coppolaemilio.com/entries... · Posted by u/coppolaemilio
Fan of Mazzy Star's music? Try playing one of their hit songs. Oh you can't because their music is not on the platform.
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.
lucsky commented on Show HN: Nue – Apps lighter than a React button nuejs.org/blog/large-scal... · Posted by u/tipiirai
> React’s baseline isn’t a monster.
Yes it is. It’s not size, it’s logic: Every time the component rerenders, the root loop is executed. Why? The root loop reassigns every useEffect, reruns every useState, every other hook (and useSearchParams is executed n times for n components that need it in the hierarchy) when only the HTML needs rerender.
(Yes the programmer can optimize/memoize, and yes “a hook’s execution time is very short” (but multiplied by every cell in the table, when needed)). Must be the fault of the programmer if the framework has a super-intensive concept at the root.)
> It’s not size
That's what TFA is complaining about: size. But nice pivot, hope your head isn't spinning too much.
lucsky commented on Canadian Devs Are Backing Out of Attending GDC wired.com/story/canadian-... · Posted by u/iancmceachern
Canada should take up the issue with Trump, not with Americans. I didn’t vote for Trump. I know only a handful of people that did. I highly doubt most of the people attending GDC did. No need to be a fair weather friend, in four years Trump will be gone and normalcy will be restored.
> ...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.
lucsky commented on JavaScript Fatigue Strikes Back allenpike.com/2025/javasc... · Posted by u/ingve
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.
lucsky commented on Rust Is Eating JavaScript (2023) leerob.com/n/rust... · Posted by u/MrBuddyCasino
JavaScript, in general, is awful as a language in terms of design, and more astute people have wasted many words on this before me.
It was originally designed for writing throwaway frontend code, but people liked it so much that they started using it to build their system architecture—only to realize it doesn’t work well for anything beyond glorified RPC backends.
The type system is wishy-washy, and TypeScript needs a massive type space to compensate for it. Python is also dynamically typed, but it has a strongly typed system that saves you from runtime blowups. JavaScript doesn’t even properly blow up at runtime—you just get [object Object] or some random undefined error. TypeScript is a fantastic piece of engineering from the C# guy, but even they couldn’t fix all of JavaScript’s language-level blunders.
Few people want to build mission-critical backends on a weakly typed language.
The ecosystem is a mess, and things randomly break after a few days. My Python and Go apps from 2018 still work exactly as they did on day one. Go’s gorm and Python’s SQLAlchemy are the default ORMs that pretty much everyone uses. And how many ORMs does the JS ecosystem have?
And let’s not even start with frontend frameworks—no one loves them two days later.
The Next.js project I built yesterday is already showing 69 vulnerabilities. This sorry excuse of a language, coupled with terrible design and an indecisively childish community, makes it difficult to take seriously.
> 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?