[neepi]

So I needed a nice looking static page kicked up on a CloudFront endpoint the other week. Just one single static page which had corp branding on it and had some blurb, a title and a link to a dataset we publish occasionally on it. This is so we can send it out in an email.

I left it to our web team with that explicit requirement and they came back with a bloody react front end. Went back to them with a WTF and it turns out they actually can't do static html any more. No joke. I nearly died inside.

As I'm crap at HTML and CSS, ChatGPT did the job in the end and I cleaned it up a bit.

Perhaps it's the people?

[shoeb00m]

Eh, depending on the amount of content on the page astro + react is fine. Astro lets you output everything as static html so it doesn’t hurt your page scores

I find that there is a context switching cost going from react to vanilla html/js/css. So i just default to react on everything.

[neepi]

They took two days and used react components and all sorts of shit and we nearly missed the deadline due to it.

The page I did was less than 4K with all content and css embedded and took me 10 minutes.

There's doing the job and there's costing the company a boat load of money doing the job.

[jiggawatts]

"You see, I have this hammer."

"I need a screw driven."

"Hammer! I have a hammer. Just one. This one."

[shoeb00m]

Ok fair enough, but I think you just have incompetent devs

[neepi]

That is precisely my point.

[owebmaster]

There should be no context change from not using React, unless one is a very junior programmer

[Shorn]

o_O

Not sure what you were intending to say, but here's what I parsed when reading that post:

"There should be no context change from <changing the context>".