They only recently rewrote their core in Rust (https://blog.cloudflare.com/20-percent-internet-upgrade/) -- given the newness of the system and things like "Over 100 engineers have worked on FL2, and we have over 130 modules" I won't be surprised for further similar incidents.
While I agree that monopolies suck, I _absolutely hate_ having to waste my time adjusting styles and writing workaround code just to make everything look and work consistently in a multitude of browsers. This is one of the reasons — among a hundred others — that I grew to somewhat hate front-end, doubly so with the rise of mobile devices. And the more rendering engines we have, the more developers will have to fight frustrating battles with inconsistencies and quirks.
Indeed front-end development in software can be painful. Much of the cruft can be attributed to computing's byzantine history of incremental experimentation. You might take some comfort in knowing that the biological analogue is vastly more complicated: the transformation of genotype to phenotype. Trying to figure out the evolutionary pressures and various mutational accidents that drove particular biological changes feels way harder than trying to figure out WTF Project X was thinking when they decided to pivot from being a social network for dog walkers to a low-latency query planner for a database no one has heard of.
Janitor Engineers [0] are already a thing? Damn. Also, all links in this article starting from the "Why AI code fails at scale" section are dead for some reason, even though it was written only 5 days ago. That raises some questions...
EDIT: Not trying to offend anyone with this [0], I've actually had the same half-joking retirement plan since the dawn of vibe coding, to become an "all-organic-code" consultant who untangles and cleans up AI-generated mess.
I’ve always found the pioneer, settler, town planner model to be a great way of thinking about this. Successful, long-term projects or organizations eventually can use all 3 types.
Maybe vibe coding replaces some pioneering work, but that still leaves a lot for settlers to do.
There's still a market, but when I looked into COBOL work out of curiosity (I've never been anywhere near it in real life), the salaries I found were surprisingly low, compared with common modern languages.
Perhaps the old adage "it's getting hard to find X employees [at the price we are willing to pay]" applies.
That surprised me because I've seen articles and heard podcasts for years where they've said COBOL programmers are well paid due to scarcity, though never quoting amounts.
It also has catalogs feature for defining versions or version ranges as reusable constants that you can reference in workspace packages. It was almost the only reason (besides speed) I switched a year ago from npm and never looked back.
‘pnpm’ is great, swapped to it a year ago after yarn 1->4 looked like a new project every version and npm had an insane dependency resolution issue for platform specific packages
pnpm had good docs and was easy to put in place. Recommend
A few years ago it didn't work in all cases when npm did. It made me stop using it because I didn't want to constantly check with two tools. The speed boost is nice but I don't need to npm install that often.
Personally, I'd be annoyed by both the resource-consuming animations and the blurry GIFs/canvas. Infisical does use the latter (canvas) for icons in their UI, and I somewhat hate it. I'd rather look at crisp, but static icons.
Canvas should never be blurry. If it is, something is doing a bilinear upscale. I'd guess someone forgot to take the scale factor of your display into account.
Or there are images being used in the canvas, which would defeat the purpose for the use case you described.
reply