I wondered as well and I think they're just used to calling their contributor team members 'staff', like you needed to be voted in as a contributor then you are 'staff', apparently oftc does the same thing
hn is kind of notorious for having most of the people in a thread have pretty similar opinions, reddit is another one if you try criticizing anything about certain companies in the wrong channel there are going to be a bunch of people who will target your account with massive down votes so that the comment is removed
I've always found computer algebra systems a particularly fascinating niche in computing, implementations in accessible languages like Julia are really doing a service to enthusiasts and learners everywhere!
tl;dr Gentoo requires users to build packages locally meaning they are dependent on the build software for a library to have Gentoo support for their architecture. Rust has limited support for some of the architectures Gentoo otherwise supports. Since this is an important crypto library adopting Rust Gentoo may have to drop support for certain currently supported architectures.
I think I saw something about reports that FB has hired a number of individuals to work full-time on the Rust lang, so there are probably lots of companies contributing to Rust in ways that don't get them features on the website.
Despite my aversion to these 'live-coding' environments for compiled languages, I'm actually interested to see what can be managed with Rust. The dynamic linking they are using sort of reminds me of rust-analyzer which quickly re-parses it's tree at every save. I don't code in a way that normally requires interpretative feedback but quality tools like evcxr might contribute to changing my habits.
It's a failing of many licenses where if the binary isn't modified then the rest of the software doesn't need to be similarly licensed. This goes against the spirit and intent of these licenses. Simply wrapping a OSS product in proprietary service layers is antithetical to the spirit of the open source license and not in the best interests of the community.
Unfortunately off-by-one errors can be insidious and non-obvious to debug, having different systems only complicates this. 0-indexing makes sense for systems and computer programming while 1-indexing makes translating math more straightforward. Inter-converting between the two systems is unfortunately non-trivial, even if the cost isn't that high.
realistically what's been upset is ad purchasing behavior which realistically could be seen as the origins of media bias in the first place [i.e. literally appeasing the sponsors]
Julia is simply a _much_ nicer to write lang than Python, it is more functional and it provides the user with far more ways to be expressive. I think the JIT warmup is less of an issue than its overall memory use but I can see that the former is more apparent to the average user sitting at their terminal.
I wish we would see a larger fraction of the energy invested into propagating the 'Pythonic' approach were _properly_ redirected into improving relevant aspects of Julia.
lately (2-3yrs) I've found twitter has generally become completely insufferable, I can't simply enjoyably watch a broad twitter stream, the fediverse manages to bring the joy back into this for whatever reason it is _less_ political and less full of influence(r)s shoveling trash into the shared social spaces
Interesting as I've just recently turned to learning Lua for use precisely as it is described as a "scripting language".
Out of several dozen alternatives (the other scripting languages from a list on Wikipedia), my analysis is that Lua offers a very compelling and attractive technical profile.
I haven't been using it long, but so far I haven't seen evidence otherwise. Prior to Lua I would have used Bash, or maybe Python in a pinch.
It seems like overall this was a long time coming and there had been precedence with MongoDB prior to as well. It's never a good thing to think that open source developers need to divert attention to such seemingly hostile actions though it seems credible enough that is was necessary for that reason.
Overall this seems like a fitting outcome for both projects, it certainly gives what it now Perl7 a sense of momentum and freshness as far as discussions around some of the direction being taken by Raku (nee Perl6). Huge thanks to everyone involved.