HN user

ramones13

120 karma
Posts0
Comments36
View on HN
No posts found.

I can’t comment on this one specifically, but SVG animations take notably more CPU usage to render/animate in Chromium browsers compared to GIF or WAAPI. And they block the main thread for at least some animations.

I didn’t say don’t use libraries at all. There’s a wide spectrum between rolling your own everything and putting a massive abstraction layer framework between you and the platform.

My experiences don’t really align with yours - most people are playing “follow the leader” with tech - “X uses Y, so we should to” and that’s it.

To your point though - use the platform. Vanilla HTML, CSS, and JS. All of that will be reusable no matter where you pivot and not lock you in to a pattern that might not work well for where you land.

To your third point - the author would recommend doing research and prototyping with all the options you might consider based on your use-cases. He actively avoids being prescriptive in generic contexts like this because he wants to avoid arbitrary dogmatic solutions (like React tends to be).

Source: I work closely with him and have been frustrated with this stance until I saw people using Next and Remix for things like landing or contact pages.

I’ve had a project I’ve been doing for ~6 months learning python through Copilot+ChatGPT. It feels like any other project that accrues technical debt, but that debt is just a lot weirder. It was rough at first, but refactoring has gotten a lot better recently with bigger context sizes.

Metaverse? Llama? They’re doing both.

How well they’re doing those is up for debate, but they’re doing interesting stuff too.

Talking about “actually” learning something feels very “no true Scotsman”. You could replace GPT in your comment with StackOverflow, Google, or a textbook and they’d read like the same criticism, right? Referencing something until you remember it is normal learning?

It's pretty easy to find that the example I gave isn't gamed... A cursory search on GitHub can find a couple examples like dotenv [1] and npm's cli [2] both use it via an older version of nodejs/readable-stream [3].

There's also the classic left-pad debacle - https://github.com/left-pad/left-pad/issues/4

[1] https://github.com/motdotla/dotenv/blob/master/package-lock....

[2] https://github.com/npm/cli/blob/latest/package-lock.json

[3] https://github.com/nodejs/readable-stream/

This is how you end up with massive tech debt though right? Replacing a dependency is going to be more expensive than writing something yourself, especially if it’s been around a long time.

IMO, aggressive npm install is the superset of the framework problem. We code review every line written by other developers at our company with a fine toothed comb, but will add a dependency from a massive advertising company or some dude in Russia without a second thought. It’s wild.

I helped out with this post a bit - The examples he goes through are taken from actual performance investigations done on Microsoft apps that contributed to this feature being developed.

It’s not trying to say everyone should adopt those optimizations, but intended to be a hands-on “try it out” without the reader needing to have their own app handy :)