Can I write a React app and recompile it as a vanilla? For example to take all involved parts of the library and not take the rest.
Look ma, no React: I recoded my portfolio site with vanilla everything
61–70 of 192 posts
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#62Can I write a React app and recompile it as a vanilla? For example to take all involved parts of the library and not take the rest.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#63I don't have to use any of Hugo, Jelkyll,..., because i can cook my own SSG toolkit right inside React.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#64Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#65> 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…
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.
Give that "senior CSS developer" a day and figure out how to manage state, then what you get is a crap.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#66I don't get the value prop of all vanilla. The overhead involved in building a react app is nearly nil with all the tooling we have. Sure CRA was slow, but vite makes things sub-second again. It's like when remix people talk about progressive enhancement to me. Sure, cool, you can do things differently. But why? If you already know the ins and outs of a framework or tool and are productive with it, use it. I'm never…
> The overhead involved in building a react app is nearly nil with all the tooling we have. All the tooling we have is exactly why React has an overhead which is far from nil. Every package goes through a period of changing its best practices, some go through multiple. Entire packages go in and out of season, seemingly depending on the phase of the moon. There's a new bundler every year, each with its own quirks. For…
But if you're already doing that, because you work in the field, or are passionate about it, then that checkbox is ticked.
I wouldn't do all that JUST to build a static portfolio, but if you already learnt and kept up with all of that stuff, then I still don't see why not use it.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#67Yes you don’t need React for a static site. Is this news at this point? Also I find the colour scheme hard to read but maybe it’s just me.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#68Earlier quoted context omitted.
My comment even got downvoted. There’s certainly some React diehards around I guess who really don’t want to hear that their overconvoluted approach could be simpler and leaner 95% of the time.
Your comment is likely downvoted because of tone, not the sentiment.
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#69> 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…
Re: Look ma, no React: I recoded my portfolio site with vanilla everything
#70Jumping on the React hate train has become a trend these days, but it still has its place.