@marcamos
Ehhh thanks lol. I'd rather not be searching for "my next great opportunity" this year, but what are you gonna do?
@marcamos
Yeah. I've just got 15 years of crap spread over netlify, bluehost, GoDaddy, heroku, and 3 months of piping hot severance, I'm thinking there must be something better I can do
@hollie
Are agile coaches and scrum masters still in demand? That's another direction she might check.
@castastrophe
That's great news! I'm gunna apply to this SO HARD
@patrickfulton
This looks like amazing compassionate work -- can the position be done remotely?
I'm serious, if you want nothing but html coming back at you from the server, please tell me because I have SO MANY QUESTIONS
Suggesting or greenlighting a new React-based project in 2023 is not a victimless act. It's the fast-track to team pain, P&L trouble, and user marginalisation.
Pay people to solve problems with HTML & CSS, not to make them with JS.
@cferdinandi
I don't even like writing php all that much, but it's a pretty good language that's very good at the things it's good at and I've been tired of the discourse for however long the wayback machine tells you I have been.
I am entirely on board the jamstack, progressive enhancement, browser performance, a11y-first, vanilla-everything pain train, and I've been pretty good at finding jobs for my 17 years as a web dev, but I'm having a terrible time finding jobs that actually do this stuff. I'm convinced I'm not searching the right keywords, but maybe that's not it.
Any suggestions, fediverse?
@cferdinandi
I'd jump on board with both feet and start hollering, but heroku decided to start charging me to run phpdoesnotsuck.com after like 10 years and I didn't agree with that and I have done absolutely nothing to fix my broken website yet so I'm not a greeeeaaaaat person to march at the front of this particular parade, but yes.
I was noodling around on the react.dev homepage today, taking screencaps for a presentation I'm putting together. I had dev tools open and I noticed something odd: every time I would hover over a link, something would get fetched over the network. "That's odd, and quickly adding up to megabytes of bandwidth", I thought.
So I looked at the fetches being fired, and it appears that the website is preloading the content of the page being linked when you hover over the link. Any link, every single time.
Let me say that another way: on react.dev, every onHover over a link costs the user between 5kb and 10kb of bandwidth every single time.
I feel like I'm losing my mind. Forget the fact that this website costs 2mb to download and takes 23 seconds to complete loading, how can charging the user and the app for every hover over a link be sustainable? How is this appropriate?