4 ms·
The confusion is that there are plenty of front-end developers that have no clue what they are doing, and then blame it on the tool. Believe me, I interview ple
by koonsolo 1y ago
The confusion is that there are plenty of front-end developers that have no clue what they are doing, and then blame it on the tool. Believe me, I interview plenty of front-end developers each month.
The main problem is that building a website is very different than programming a web application.
As a senior software engineer with a Masters degree in CS, NextJS works great for me.
Another poster here claims an <Image> drops his Three.js to 2 fps, and of course blames it on NextJS. I work with Three.js, and never seen such issue (React-three-fiber however does have some peculiarities). Before blaming some random tool, maybe first investigate where the problem lies. If you pinpointed it to NextJS, sure, it's NextJS. Before that, don't blame anyone but yourself.
I always laugh when I read HN and Lobster commenters. I use NextJS and LLM's, and I leave my competitors in the dust. So yeah, the proof is in the pudding, not in some random folks commenting on the internet.
This also reminds me of some commenter here on HN who was angry at Java because their sorting function was unstable for many years :D.
- jowday 1y agoDude, I explicitly replied that I pinpointed it to Next. The moment I removed the Image tag and replaced it with a regular <img />, it resolved itself. I didn’t even say I was using three, did I?
- koonsolo 1y agoMy above text was written before you replied to my other message. And besides, just because using <img> instead of <Image> doesn't imply that the actual issue was in <Image>, it might also be in another part and <Image> triggered it. As I told you, as long as you don't pinpoint the problem, you can't say where the problem lies. Maybe your definition of pinpointing is different than mine.