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

181–190 of 192 posts

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

#181

Post by TX81Z »

SkyPuncher wrote: post #157
TX81Z wrote: post #153

Earlier quoted context omitted.

Curious what you mean by “almost always something” that makes you use JS? What besides shitty/illegal tracking code and cookies do you need to include? Honest question.

In my case, we wanted to gather feedback on a product we were launching. Because we wanted to move fast, we’re in a regulated industry, and our initial tests were simple, we decided to built a simple “chatbot” style feedback tool. More generally, forms. Forms always seems to morph into more than just simple inputs.

Thanks for the reply, forms are such a pain in the ass. Of course you need hard input sanitizing on the backend but just helping people fill out a form correctly can require some JS.

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

#182

Post by ehnto »

c-hendricks wrote: post #178
ehnto wrote: post #177

Earlier quoted context omitted.

No I was saying the opposite, a static site is necessarily not dynamic. I would not want to pre-generate those pages. Your static files on an S3 bucket are still served by a webserver. Anyway, can you honestly say, hand over heart, that server side rendered JSX or React is a robust and simple solution comparable to SSI or I don't know, a bit of copy pasting? Of course not. Server side rendering is a complex toolchain…

Yeah at this point I have literally no idea what you're talking about? The thread is about pregenerating static content, "can you honestly say, hand over heart, that server side rendered ..." is way off base. Seems like"static site" means "assets can be plopped into any server that can serve static assets" to one set of people, and to others it's an invitation to balk? I'm in the former camp, if that wasn't obvious.…

Yeah I was going to point out this is getting pretty obtuse but didn't want to be rude. I think we're talking past eachother, or I'm missing something.

My TL;DR I guess, pregenerating/SSR, is a more complicated toolchain than is needed for a simple site (and what I interpreted the topic comment's point to be). How you serve it wasn't really the issue, that is the easy part. I might leave it at that, cheers for being gracious.

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

#183

Post by ukuina »

mettamage wrote: post #179
ukuina wrote: post #166

Earlier quoted context omitted.

Which part of that curriculum was core CS?

None of it, as those skills were not asked for by the labor market. And I tend to agree with it (as a CS bachelor and master graduate). What you need to learn is programming in a specific way. CS teaches a broad scope of things that are all helpful but they are not strictly necessary to know, especially not as a junior. I think doing a CS degree after having done web dev for 3 years in the field is a much wiser decis…

You are describing the distinction between a scientist/engineer and a technician. Technicians only need thin slices of knowledge about the underlying abstractions.

The problem with _aiming_ only high enough to create technicians, though, is that you create a good chunk of _operators_, instead, who make do with both thin _and shallow_ slices of knowledge, making them poorly suited to any kind of generalization.

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

#184

Post by eropple »

paulryanrogers wrote: post #175
robertoandred wrote: post #159

Earlier quoted context omitted.

It’s a build step that happens every time the page is loaded instead of once when it’s deployed.

Then arguably JS is worse, since any 'build' steps preceding it don't bypass the (client side) interpreter either. Except perhaps if WASM is involved.

That's not true, though; JSX can be entirely prerendered server-side. If you don't write client-side JavaScript, you're not going to get client-side JavaScript (modulo maybe a thin hydration layer if you're using particularly old tools, but nothing running pervasively). Your code becomes HTML files. It's more Hugo/Jekyll than it is "a SPA".

I am unaware of a major PHP framework that is designed around similar, though it may exist.

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

#185

Post by imiric »

> A developer needs a website to prove they can build a website.

Not really. Doesn't your experience, reflected in your CV and the technical interview, already prove that? A portfolio site is nice to have, particularly if you're a designer and want to showcase your work, but it shouldn't be a requirement for a developer, frontend or otherwise.

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

#186

Post by KnobbleMcKnees »

pc86 wrote: post #104
tzhenghao wrote: post #83

Earlier quoted context omitted.

Yeah, I was just chatting with another principal eng friend recently where maybe a whole new generation of programmers may be several degrees away from topics like operating systems, compilers, computer security and networking. Once in a while, (lower level) software needs to be rewritten as underlying invariants go out of fashion. Think filesystems due to hardware access patterns etc. - to unlock magnitudes of perfo…

This is sort of a FUD argument IMO. There will always be people who focus on low level software engineering. There will always be people who want to learn about the hardware of computers much more than the software. Proportionally there will almost certainly be less (we don't need nearly as many computer engineers as we do software engineers) but as long as the salaries remain competitive there will be plenty.

It's not just this but also the fact that there are many more layers of abstraction now than there were even 10 years ago, never mind 20/30/40 years ago, and the real world incentive to understand the entire stack of those abstractions is virtually nil in modern engineering environments.

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

#187

Post by paulryanrogers »

eropple wrote: post #184
paulryanrogers wrote: post #175

Earlier quoted context omitted.

Then arguably JS is worse, since any 'build' steps preceding it don't bypass the (client side) interpreter either. Except perhaps if WASM is involved.

That's not true, though; JSX can be entirely prerendered server-side. If you don't write client-side JavaScript, you're not going to get client-side JavaScript (modulo maybe a thin hydration layer if you're using particularly old tools, but nothing running pervasively). Your code becomes HTML files. It's more Hugo/Jekyll than it is "a SPA". I am unaware of a major PHP framework that is designed around similar, though…

JSX SSR would be in real time again, correct?

If you mean rendered once for all, i.e. statically, there are some PHP wikis, frameworks, and caching plugins that can/do work that way.

Post reply on HN