1. use this web component, it has zero dependencies, weighs 4KB, shipped in 2018—still works great
2. OR, you can use this react component—it has many dependencies, requires a transpiler, weighs 200KB+, uses outdated react best practices from 3 months ago
you gotta choose #2, right? otherwise they’re gonna make fun of you
54 replies
@zachleat more code, more $$$
@konnorrogers @zachleat and more devs! can't forget the critical corporate headcount flex 💪💪💪
@zachleat Unfortunately, managers sometimes tend to give you the salary increase for the overengineered 200kb thing, not for the smol 4kb one 🙈.
@lea dang are people out there getting paid by the KB
@ardouglass @zachleat it actually is a business concept for some consulting agencies. I should maybe blog/give a ted talk on this.
I remember a conversation with one of my former supervisors which was like "yes, you must deal with $framework, $subframework and $architecture even if it is over-engineered. Our business model foots on dealing with complex code. If it was simpler, the clients wouldn't reach out to us"
Ideally, you deal with the complex code by making it simpler, but :D
@lea @ardouglass @zachleat this sounds like a fun talk!
@lea @ardouglass @zachleat I have had the same experience. I often think that many of the ills of software development were created by our consultant origins.
-
-
@zachleat Just 4kb? That can’t be right. Seems completely opposite to the estimated size mentioned in our JIRA ticket. 2018? That sounds really old for our Angular 2 app.
@zachleat Web devs are so bleeding edge they don't know that projects can actually be finished -- they're either permanently maintained or outdated.
@wortwart finished 🤝 feature incomplete
@zachleat
That's called progress isn't it?@kneworldodor sir this is a wendy’s
@zachleat
Lol. The world and the word are funny. Grandparents had furniture that could be passed down for generations. We have furniture made out of glue and wood chips that melts if you move on a rainy day or breaks if it's good weather. It's too damn heavy to move as you age too. Almost like it's made to be replaced ASAP and put cash in an offshore tax haven. Progress.
@zachleat That reminds me of this post that I think about a lot.
“You don't hear about TextMate because TextMate is old. What would I tweet? *Still using TextMate. Still good.*”
@zachleat Can't choose #1 when #2 is the only way you know…
@zachleat Even without the React/size thing, I frequently encounter people who simply will not use anything that was last updated 2018, because that means it's "dead". Only projects that are recently updated (even if it's updating the readme once a year) get used. I have no idea where this mindset comes from
@tomw @zachleat I do take a moment to check when I see this. Also yes "it hasn't been updated since 2018" - but due to bad practices I have seen perfectly good dependencies light up the security board - one library shipped their entire Docker file with root setup and trivy did not like this.
FWIW I wrote a script that recursively cleans up node_modules - just deleting markdown files, configs and other stuff that should be in npm ignore cleans up 30-50mb of crap
@tanepiper @zachleat Yes OK, "uses Docker and hasn't been updated since 2018" I wouldn't use. But it's OK for a little JS library!
@tomw @zachleat wasn't even "uses docker" - it was for the automated test setup of a javascript library that is a translative dependency - they hadn't put the Dockerfile in .npmignore - the problem is suddenly I'm getting critical alert scans.
Raised this in May, it'll likely never get fixed - https://github.com/surma/rollup-plugin-off-main-thread/issues/59
@zachleat this is why I constantly find myself returning to the little JS framework I developed over a decade ago. It’s lightweight, fits into what I’m doing and I don’t need a whole monster of a system just to get things done. Hm, should update it though to modern JS best practices :)
-
-
@zachleat Any recs on decent YouTube facade? I recently changed one from react to web components and it's not actually better :-(
-
-
@jlarky what did you use before?
-