Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Look ma, no React: I recoded my portfolio site with vanilla everything

clairefro.dev

Post reply on HN
Print view View original

111–120 of 192 posts

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#111

Post by nicoburns »

gedy wrote: post #71
yoavm wrote: post #28

Earlier quoted context omitted.

Agreed, but it's so rare nowadays though. I still remember when I saw a junior frontend dev struggling to get some element to look differently when hovered in React. They went though loops and hoops to style it using CSS-in-JS and mousemove, only because they didn't hear about :hover.

My favorite experience with Bootcamp folks was someone who came in do an interview, and she could talk , was professional, had nice looking blogs, etc. and seemed really awesome on paper. However, I had her do a really simple React exercise, and she was producing some really strange code like using Ruby inside of a JavaScript onClick handler? lol I think a failing of a lot of these bootcamps is they encourage people…

I think this is an unfortunate side effect of boot camps trying to impart best practices on their students. They don’t really have time to learn and apply the actual practice well, but the names stick with them.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#112

Post by cj »

papichulo2023 wrote: post #108
cj wrote: post #48

Earlier quoted context omitted.

> That statement indicates you don't know why react was developed. Why was it developed?

Hint: it was not because the performance nor the JS language limitations. You can google the rest.

I am friends with the original 2 React founders who I met at facebook. I don’t need to Google, I’m asking because the comment was lacking substance and wasn’t adding value to the conversation.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#113

Post by nicoburns »

revskill wrote: post #65
yoavm wrote: post #28

Earlier quoted context omitted.

Agreed, but it's so rare nowadays though. I still remember when I saw a junior frontend dev struggling to get some element to look differently when hovered in React. They went though loops and hoops to style it using CSS-in-JS and mousemove, only because they didn't hear about :hover.

Then what ? That junior dev could produce working software, and fix the css issue later (if needed). Give that "senior CSS developer" a day and figure out how to manage state, then what you get is a crap.

The problem is that if the end state you want is a clean codebase implementing your use case, that’s also easy to modify and extend, then the mess such a developer will produce is a much worse starting point than starting from scratch.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#114

Post by SkyPuncher »

city41 wrote: post #23

My website is also completely static, but made with React. That means no React at all at runtime, it is completely static. React does not automatically mean dynamic. I get all the benefits of both. I love the flexibility nextjs provides here.

I love React as a templating language. I find it very easy to use since JSX is very close to actual html.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#115

Post by [deleted] »

teg4n_ wrote: post #76
yoavm wrote: post #28

Earlier quoted context omitted.

Agreed, but it's so rare nowadays though. I still remember when I saw a junior frontend dev struggling to get some element to look differently when hovered in React. They went though loops and hoops to style it using CSS-in-JS and mousemove, only because they didn't hear about :hover.

Seems like just lack of experience. You can even do it simply with JS with onHoverIn / onHoverOut

[deleted]

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#116

Post by agumonkey »

carlossouza wrote: post #17

> I became a dev when everyone was hiring for React, so React is what I taught myself immediately after bootcamp in the scramble for a job A better education path (in a bootcamp, university, book, youtube, whatever) would start with the fundamentals and build it from the ground up... not the other way around. (I just realized how lucky I am for being taught in the best possible order, from the ground up... first the…

I have a strange feeling about the industry. It seems better received to know a framework 30% (or enough to make simple/intermediate things) even if you know next to nothing about the underlyings rather than the opposite. If you're an ES6 master but can't mesh well with react tasks / react convos in daily you will look as less useful.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#117

Post by madeofpalk »

lisasays wrote: post #103
madeofpalk wrote: post #101

Author made a two page static website without React. Okay? Congrats?

Actually, yes. The conventional wisdom these days is to do everything in React (or something similarly bloated). Because, you know, users just love seeing a bunch of grey boxes shimmer and dance on a white background for several seconds before the magic really starts to happen. So any exercise which demonstrates that there just might be an alternative to this philosophy should be applauded.

I don’t think this is the “conventional wisdom”!

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#118

Post by randomdata »

pc86 wrote: post #105
randomdata wrote: post #95

Earlier quoted context omitted.

And that's why learning is best left as an individual pursuit. For me, it is always best to start with a complex system and then work backwards, understanding the thoughts and decisions that went into each step along the way. When I start with the basics I don't get a feel for the bigger picture and it means nothing. I'm glad I've only been around the industry for 25-some-odd years. We already had many high level abs…

I hate to break it to you but if you've been in the professional world for 25 years, you're old :)

Well, yeah, but you'd have to be at least twice my age to have been starting out when this tech was in its primitive state. Comparatively, I'm still a spring chicken.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#119

Post by gochi »

evandale wrote: post #46

I've tried learning Ember, React, and Vue and have tapped out pretty early. Now I'm learning how to build a site using only vanilla JS and doing everything from scratch unless I find a reason to switch it. I think I'm making decent progress. I even wrote my own simple test framework that shoves the results on the bottom of a page. After adding a few features I decided to switch it to Jasmine. One thing I'm noticing i…

I'm confused by this, why do you think npm is needed? It just acts a central repo, you're free to self host the JS file yourself or pump it through a CDN.

Jest is a different story, it's not a single JS file and has many dependencies. Running it globally is an easy way to reduce the need to include it per project.

Re: Look ma, no React: I recoded my portfolio site with vanilla everything

#120

Post by sfn42 »

evandale wrote: post #46

I've tried learning Ember, React, and Vue and have tapped out pretty early. Now I'm learning how to build a site using only vanilla JS and doing everything from scratch unless I find a reason to switch it. I think I'm making decent progress. I even wrote my own simple test framework that shoves the results on the bottom of a page. After adding a few features I decided to switch it to Jasmine. One thing I'm noticing i…

People use package managers because it lets us find everything in one place, install it and keep it up to date easily.

I'd much rather do `npm i whatever` than having to hunt down a bunch of git repos and copying files over and when they're outdated having to do the same thing to update them etc.

Post reply on HN