Dependency management fatigue, or why I forever ditched React for Go+Htmx+Templ

1

React.run

#Javascript UI Libraries #Front-End Frameworks #JS Library 194 social mentions

That's Go's out-of-the-box experience. Maybe you're looking for something to scaffold projects? There are plenty around, I've been using https://gowebly.org.

1 social mentions

3

YouTube

I was laid off just before Thanksgiving 2023[1] from a Principal Engineer role on a Platform Engineering team. I was employed there since 2018. I was very lucky to get referrals from a few folks that I social dance with in Seattle after that layoff, and I ended up with a job offer in a product area I knew very little about (networking, routing, programmable packet processing middleware with eBPF etc.) Despite my lack of domain knowledge, I was told I received the offer largely because of my demonstrated proficiency in Rust (I did all the interview whiteboarding sessions in Rust), and although this isn't something that is measured "officially" in the interview process, because there are many hours of me live programming online[2] for people to feel confident that they're not hiring a dud who has hyper-specialized in passing interviews which are not representative of real-world workloads. I general advise people in your situation to start looking further down the world's dependency tree, where things churn less frequently, and where the skills you acquire will last longer. This can be easier said than done, but since my very first job was as a React developer, I can at least share my path down the dependency tree: Frontend (React etc.) -> Backend (web APIs) -> Infrastructure / Platform / DevOps (started with a cloud automation focus, moved gradually towards to bare metal) -> Networking (I'm in ur VPCs, directing ur packets) All of this being said, the job market right now is very tough. I doubt I could walk out of this job and into another within 3 months like I did this time last year. [1]: A lot of my technical blog posts on https://lgug2z.com/articles around that time refer to this layoff [2]: https://youtube.com/@LGUG2Z.

#Video #Video Platform #Social Media 1905 social mentions

4

Preact.js

> <i>React is a small rendering library</i> Sorry, can't agree. React is a <i>state management</i> library that also attaches efficient rendering on top of the DOM diff it computes as it propagates the state changes. This allows React apps to remain so simple (one function per component) and so composable without turning into an unmanageable dish of callback / future spaghetti. There is a number of other VDOM libraries, but what sets React apart is the data / state flow strictly in one direction. This allows to reap many of the benefits of functional programming along the way, like everything the developer sees being immutable; not a coincidence. Regarding the size, preact [1] is mostly API-compatible, but also absurdly small (3-4 kB minified), actually <i>smaller</i> than HTMX (10 kB). But with preact you likely also want preact-iso, so the size grows a little bit. [1]: https://preactjs.com/.

#Javascript UI Libraries #JavaScript #Javascript Utilities & Libraries 94 social mentions