TFW an online store you ordered from regularly and worked just great replaces their "outdated" but perfectly-working server-rendered store with a Next.js abomination and now nothing works and they keep fucking losing orders.
-
TFW an online store you ordered from regularly and worked just great replaces their "outdated" but perfectly-working server-rendered store with a Next.js abomination and now nothing works and they keep fucking losing orders.
-
Marijke Luttekesreplied to Baldur Bjarnason last edited by
@baldur Modern front-end is the best! π₯³ (Sarcasm)
-
Emma (has_many_books of old)replied to Baldur Bjarnason last edited by
@baldur they should have learned css instead
-
Baldur Bjarnasonreplied to Emma (has_many_books of old) last edited by
@emma Right?! Just change the colours a bit and freshen the design, then tell management it's all modern and fancy. No need to throw out working code just to make a site feel "new".
-
Emma (has_many_books of old)replied to Baldur Bjarnason last edited by
@baldur and if the css was sorted out it would probably load faster and then you could make some management-pleasing graphs and get back to doing actual work
-
smallcircles (Humanity Now π)replied to Emma (has_many_books of old) last edited by
Oof, ha ha
Just yesterday I was pondering a migration from ye good old'e horse Jekyll to shiny new Astro. Because each infrequent update to a simple smolweb-ready static site https://fedi.foundation gives me some ruby / gem / bundler install horror. See:
smallcircles (Humanity Now π) (@[email protected])
#Ruby: π Piinng.. ATTN! If you don't use me for long periods I will sadistically make life hard for you come next runtime. Me: π But.. but.. I am trying to start up #Jekyll again to update an old website and find that all old setup couldn't possibly be more broken. #Ruby: π WOEHAHAHAAAH!! Me: π Please, please stop throwing me "bundle: cannot execute" for unknown reason. #Ruby: πΏ NO!
social.coop (social.coop)
Eerlier I had already ported the thing away from Bootstrap CSS, which was an effort.
Of course instead of Jekyll I might as well have used plaintext editor, but this was to be a multi-author site.
-
@mahryekuh @baldur I agree with the sentiment, but React just isnβt modern anymore.
Just about all other front-end frameworks have a consensus on signals being the main construct for reactivity (and not the components themselves).
React are stubbornly keeping to an idea everybody else reslise is deeply problematic.
Not that being modern is all that, but some thing stand the test of time, others donβt. At this point it should be clear that React simply donβt.
-
Torbreplied to smallcircles (Humanity Now π) last edited by
@smallcircles Astro has a similar philosophy to Jekyll though. As long as youβre careful with separating content from theme/logic/etc, moving from/to Jekyll/Hugo/Astro/Eleventy/etc isnβt too much of a hassle.
-
smallcircles (Humanity Now π)replied to Torb last edited by
@torb yes, thank you. I had an inkling that it probably wouldn't be too bad. The devil in terms of time you had planned is always in the tiny details with these things, in my experience.
Because it is not highest prio, I applied "Most Minimal Software Development Process" i.e. #MMSDM, and indeed spent Minimal time and took the day off..
-
@torb The industry doesn't seem to agree, as everyone and their mom is using or asking for React.
As much as I would love for ReactJS to shrivel up and die, I fear we will not be rid of it anytime soon.