Wes

@jonchurch.bsky.social I though I remembered you doing this for @expressjs.bsky.social, but maybe I am wrong.

This is the thing I keep coming back to. Yes the AI can reproduce that library 100x. Now you have 100x slightly different reproductions of the behavior to fix.

The basic design of software libraries, and the value prop, has not changed at all.

omg, they just started talking about something (wrong) they attributed to Netflix engineering culture. I should have just stayed home today. It is hard to maintain empathy for my fellow humans some days.

People next to me at the coffee shop this morning are fascinating. While talking about using AI in their dev workflows one guy says "I never leave my house"...

...and it all made sense.

Being a truly democratic platform on which to rebuild the hellscape which is current social media would be the goal. Part of the reason it is a hellscape is that addictive algo driven bit.

So pardon me if I am *glad* to be on a platform that is not taking your advice.

This is exactly what I love about #OSS

You pick up an issue, learn, iterate, share, exchange, ship something useful, and make it better for everyone.

💖 npmx

//Happy coding

We deserve a better streams API for JavaScript The Web streams API has become ubiquitous in JavaScript runtimes but was designed for a different era. Here's what a modern streaming API could (should?) look like.

After implementing web streams in multiple runtimes, supporting them for years, talking with other implementers, dealing with issues... I think it's well past time we talked about something better blog.cloudflare.com/a-better-web...

Sir I edited code on a live production servers with vi this week.

Ruby - Advanced 5 Position 14130/106.3k language score: 19 top 20% of all ranked profiles this month change: down 14

You mean my "advanced 5" score in Ruby is meaningless???? how will I ever cope 😭 🤣

for folks who are active on x, threads, etc and feel bad about it bc of its stewards but have a hard time letting go: sometimes your behaviors overpower your values online because tech companies hire psychologists & sociologists to come up with ways to put you in that position

Yep, that's what I was missing. Thanks!

Am I missing context on this post? Connect requests have been supported in Node.js for a long time.

This is 100% how I feel about many of the changes I am choosing not to take part in, but I think is an interpretation of "left behind" that is for those without agency (or at least less).

bsky.app/profile/notw...

Our entire teenage cohort right now has no jobs AFAICT. The remaining retail businesses that survived being “left behind” don’t hire teens anymore. Not sure if this is what you mean, but it’s seems to me that “getting a later start on adulting” is a from of “individuals being left behind”.

Cups! No GPU based replacement because this industry has already been disrupted a hundred times over. 🤣 🏺

bsky.app/profile/notw...

SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflow... An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.

🚨 Active supply chain attack

New Shai-Hulud–like npm worm (19+ packages, 2 aliases) stealing dev/CI secrets, injecting GitHub workflows, poisoning AI toolchains, and harvesting LLM API keys.

Details → socket.dev/blog/sandwor... #NodeJS #JavaScript

thanks for the clarification.

Definition of LUDDITE one of a group of early 19th century English workmen destroying laborsaving machinery as a protest; broadly : one who is opposed to especially technological change… See the full definition

Maybe I should not have used the proper noun there. I meant the popular use as an adjective, not the historical one.

> broadly : one who is opposed to especially technological change

www.merriam-webster.com/dictionary/L...

That said, I will read up on the history, thanks for the suggestion!

Socket Joins the OpenJS Foundation - Socket Socket is proud to join the OpenJS Foundation as a Silver Member, deepening our commitment to the long-term health and security of the JavaScript ecos...

We're excited to announce that Socket is joining the @openjsf.org! Proud to support the #JavaScript ecosystem alongside so many great projects and contributors.

socket.dev/blog/socket-...

Like I am opposed to many technologies that I see as harmful to human lives. But I have struggled to really call myself a Luddite because it implies finding none of that joy in tech even when it improves lives. Maybe I’m being too narrow in my definition?

Is this a “Luddite” view? I don’t know the right labels, so this is me asking to clarify my language of something I agree with.

I see this as some form of human centered techno optimism. As in the optimism is not for the tech sake, but for the way it has/can improve humans lives.

Couldn't read all of it right now, but thanks I will keep the tab for later.

This is the way.

Do you have a link to that? Is it (as your comment implies) on the semver spec?

With the goal of convergence, but I am almost positive that will mean some areas of said potential spec would be loose to accommodate the current implementations (as @steveklabnik.com says above).

Include SemVer in Node.js · Issue #146 · nodejs/tooling It would (imo) be valid to say that SemVer a fundamental and essential part of the ecosystem. All modules rely on it, Node.js itself uses it for versioning, and it's currently sitting at 193m downl...

Very much a fan of this plan. It would be especially nice if this was something that could be done before `semver` in the Node.js ecosystem moves into core. github.com/nodejs/tooli...

Yep, agreed with all above. If you are still in that experimentation phase, then you can have consumers use ~ ranges instead of ^. That said, either way I would consider your choice in the original question is really down to personal preference imo.

To say it in another way, you get very little benefit from staying pre-1.0 any longer than necessary.

So I guess my point was more that the default behavior of using `^` makes pre-1.0 versioning difficult for end users if you *do* decide to treat it as unstable (per spec) so instead of staying pre-1.0 it is easier to just go 1.0 as soon as you are stable.

GitHub - npm/node-semver: The semver parser for node (the one npm uses) The semver parser for node (the one npm uses). Contribute to npm/node-semver development by creating an account on GitHub.

The semver spec does not cover ranges. So that is where most discrepancies happen with how these questions play out. The `^` is behavior defined by the `semver` package (used by npm). github.com/npm/node-sem...