We need to start normalizing that software engineering can be a 9-to-5 job. It's ok to not live, eat, and breathe tech 24/7. It's ok to be in tech bc it's a lucrative job that pays the bills. You don't need to be passionate about tech to be in tech.
@mityasmusin@pbakaus Oh god! So much doom and gloom - am I the only one not existentially worried? I have faith in engineers ability to always be in demand and stay relevant as there will inevitably always be new problems to solve.
Recording and minutes from the recent @nodejs Next-10 meeting, good follow on discussion to the Advocacy deep dive last week. Many thanks to @nomadtechie and @shepsheplu for leading that deep dive! - https://t.co/rJvGuw1aNj, https://t.co/KAnzVsWSfh
🚀 #100DaysOfPerf Day 50! This was due yesterday, but left it in draft. Two of my faves were on the @JSPartyFM podcast talking all things #corewebvitals. @anniesullie & @rick_viscomi were busy breaking down LCP, CLS + INP for 90 mins. Enjoy! #webperf
🗣️ https://t.co/yvxygfn5hM
It was so much fun to chat about Core Web Vitals and Interaction to Next Paint with @nomadtechie, @nicknisi, and @rick_viscomi! If you're interested in Core Web Vitals, definitely give it a listen!
The point is that would be a massive breaking change in the ecosystem and entertaining it and giving it’s space isn’t the way forward. Things don’t have to be binary - enabling other pkg managers doesn’t have to come at the cost of removing npm. Stoking useless fires in community is also not productive.
@galstar@t3dotgg That’s pretty hot, tbh! I wish we made more space for control flow via generators. Super underutilized in the world of application development, and more commonly used in libraries.
Corpack works best for yarn and that makes sense the in wider context. Ultimately, the best best path fwd is to A) do nothing since this wasn’t a need being driven from the community. It’s been proven that not being bundled with node has not been a barrier to usage. B) Start bundling yarn, and pnpm bc unbundling npm or enabling it through Corpack isn’t a viable option.
And as for whether or not to enable Corpack by default (which is a separate but related issue) there are many valid technical reasons raised here by @darcy as to how this creates serious integrity issues, which is in turn will be a source of confusion and bugs for end users:
https://t.co/HMKqZDud9s
This code is likely a very good read y’all! I’m sure it’s mountains more streamlined than npm’s legacy codebase. Very eager to dig in! Still not clear on the business model though, is this just a value add for the deno ecosystem, or is there some direct revenue stream?
JSR source code for frontend+backend, all of our cloud configuration, the docs, and everything else is now open source on GitHub:
https://t.co/9ewyPjFJXd
@darcy@lcasdev@syntaxfm Thank you both for the share! And looking forward to the birth of vlt as well! The package management space continues to heat up with big bets - so here for this! 🔥🔥🔥🙏🏾
@brucel I know, that was the most duh and stupid response. Oh really, really??! lol
Jeeez, so glad someone other than an developer called them out on that.