Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
The worst is that people will claim that it is "easier to maintain", in spite of all in-your-face evidence is that the extra layers have to be analysed, thoroughly understood and then fought through. Modern code is slow, fragile and usually has to be hosted on more powerful hardware at vast expense.
-
@Fast-Nop Only 500kb and 300kb? That would be great. For most websites nowadays it's several MB with multiple files across multiple domains
-
@Fast-Nop Yup. Every time someone talks about the success of the modern web environment, I can't help but politely disagree
-
@ars1 And how can't we be? honestly, not keeping up with this madness means being left behind, which is not good for our wallets
-
I feel like pipelines and their ilk started as a way to help check the nitpicks stuff quickly. “I updated this package locally, did I also update it on the server?” Type stuff that is so common you might have done something similar recently and feel like you did that specific thing already.
However, now they have become their own sort of dick-measuring contest, to see who’s pipeline can be the most automated or the most complicated or check the most things. This leading to the issue that the pipeline was supposed to solve. It was supposed to check, is the build good from a technical perspective? But now we have to know is the pipeline good from a technical perspective before we can even know that. -
@AleCx04 The good thing: browsers still do understand actual websites, even better than ever before. You can make useful, responsive, and accessible stuff in under 16k transfer size, including markup, styles, and scripts.
-
@DarkSwan and subsequently, our demise
-
@Fast-Nop true, but for us in this side of the field is almost always as if "If you don't use NOde and a bazillion packages we do not want you!" even if the end result can be done with 0 deps and just proper markup and CSS, even with as little JS as possible, the industry just seems to not want that.
-
@AleCx04 fuck those requirements!
-
@AleCx04 I actually see an opportunity here especially for small brochure sites of B&M shops and the like. In practice, they never edit the content so that this point of e.g. WP is moot.
However, a slim, static site is not only amazingly fast, it also requires no ongoing maintenance (except the server itself which is unproblematic). No WP/PJP/plugin/theme security holes that require updates which then break shit. The recurring maintenance cost then is pretty much 0.
I'd think that this would be a compelling argument for these customers. With an SSG behind, even editing content wouldn't be much effort.
We can compile, transpile, and do all sorts of fucky internet things through an entire development pipeline and then troubleshoot through all sorts of hackery and dev sorcery to output html.
Or I can just index.php and be done with it.
I dunno man, I dig frontend and using the popular js libs to put shit online and be done without having to deal with the fuckery that is wasm or use something similar to Rust to bring shit to my clients.
9 times out of 10, these dudes have been well served with the php or node or even golang that i give them.
Seems that a lot of tools coming up just make shit harder.
Even VBScript seems simpler compared to the amount of web fuckery going on right now.
Yeah I keep current, but fuck, every day it seems as if shit was just getting more and more complex
rant
just saying