Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TSC
-
Bringing Forward the End-of-Life Date for Node.js 16
The dates were known in advance - however, the Node team expected OpenSSL 3 to be out before the release of Node 16, but it didn't happen - so they had to release with OpenSSL 1.1.1. Between the lines, I think that there was some minor hope of maybe upgrading, but obviously it was to difficult.
https://github.com/nodejs/TSC/issues/1222
-
In response to the moderation team resignation (Rust)
>After the Node incident, it's highly likely Ashley Williams is involved again due to her propensity for racism and sexism.
I didn't know what this was referring to so I looked it up.
Here's a Reddit thread which seems to be the genesis of the complaint (an archive link because the actual post was removed):
https://archive.md/VEtHu
Link to original Reddit thread:
https://old.reddit.com/r/node/comments/6whs2e/multiple_coc_v...
NodeJS GitHub issue thread
https://github.com/nodejs/TSC/issues/324
HN threads:
https://news.ycombinator.com/item?id=16085545
https://news.ycombinator.com/item?id=15115989
https://news.ycombinator.com/item?id=16073017
- Rust mod team resignation
-
What you need to know about ES modules in Node.js
If Node.js 12.x and 14.x releases have full support for ES modules, what gives? I was wondering the same, so I asked Matteo Collina on Twitter (he's a member of the Node.js TSC). Myles Borins (also a member of the TSC) chimed in on the thread to explain the rationale behind ES modules being marked as 'Experimental' in the 12.x and 14.x release lines:
- Running Homebridge Server On M1 Mac
team
-
Non-code contributions are the secret to open source success
It's just as true today, though. When the Rust mod team resigned en masse in 2021, it was announced by a programmer (the author of ripgrep) [0], and the conflict was with the core team (also programmers). A supermajority of their contributors to open source projects are programmers, so most famous meltdowns are going to be conflicts between programmers, not between programmers and the tiny minority of non-technical contributors.
I'm still waiting for anyone to give an example of an open source project meltdown that was triggered by non-technical contributors.
[0] https://github.com/rust-lang/team/pull/671
- Remove my name from the [Rust] project
- Batten Down Fix Later
-
Graydon Hoare: Batten Down Fix Later
the mods publicly outlined the governance issue, while keeping the moderation issue private (https://github.com/rust-lang/team/pull/671)
-
On the RustConf keynote | Rust Blog
Here's another list: https://github.com/rust-lang/team//blob/d4c071b86c33683845919cf27eabf33e15fb6784/teams/interim-leadership-chat.toml
-
On the RustConf Keynote
they linked their (user)names:
https://github.com/rust-lang/team/blob/2cea9916903fffafbfae6...
-
Let's thank who have helped us in the Rust Community together!
You can also check rust-lang/team repo, where shows more than 400+ people have worked on the Rust Project as official members. And on thanks.rust-lang.org, it shows that 300+ people have been involved in each recent release. I believe the number of active contributors may be more than 100+.
-
JT: Why I left Rust
Right, but this type of drama isn't new in the community. A while back the whole mod team resigned because they were not able to hold the core team accountable. In fact I remember it being said that the Core Team placing themselves unaccountable to anyone but themselves. So I don't think I'm being dramatic at all here.
-
Can someone explain to me what's happening with the Rust foundation?
If that's too onerous, you can also look at the list of directors and observe that there are people titled "Project Director" who you can look up on https://github.com/rust-lang/team and observe that they have in fact been selected from the project teams.
-
Safety and Soundness in Rust
You're more than welcome to set the narrative straight. The infighting among Rust maintainers is based partially on your resignation note where you said the Core Team was "unaccountable" https://github.com/rust-lang/team/pull/671 and implied that they were untrustworthy. The same people that once went around starting language wars, like calling Zig a "massive step backward" for the industry https://news.ycombinator.com/item?id=32783244.
I'm just an outsider observer, who's been watching the sparks fly. It's been interesting as well to watch how quickly memories changes when positions are dangled. If there's ever an investigative report on the tribulations of Rust, they can also dig into the allegations of nepotism around one maintainer and his girlfriend on the project, vis-a-vis Amazon. https://news.ycombinator.com/item?id=28633113.
What are some alternatives?
Sinon.JS - Test spies, stubs and mocks for JavaScript.
go - The Go programming language
ah-theyre-here-esm-nodejs - Code accompanying my talk "Aaaaaaaaaaaaaah, They’re Here! ES Modules in Node.JS"
Elm - Compiler for Elm, a functional language for reliable webapps.
awesome-npm - Awesome npm resources and tips
byteorder - Rust library for reading/writing numbers in big-endian and little-endian.
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
xgb - The X Go Binding is a low-level API to communicate with the X server. It is modeled on XCB and supports many X extensions.
build - Better build and test infra for Node.
rfcs - RFCs for changes to Rust
pack - CLI for building apps using Cloud Native Buildpacks
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]