930 karma · joined March 5, 2024
Sounds like an improvement - having beta builds for people to catch those before they arrive in a stable GNU distribution seems the ideal workflow at glance.
Stability (in the "it doesn't change" sense) is underrated.
IMO it's hard to justify creating Option<T>/Result<T,E> wrappers when T|null and T|E will work well enough for the majority of use cases.
effect specifically feels like a different programming language altogether. And maybe going that path and compiling down to TS/JS could've been a better path for them. I'm not on the ecosystem though, so it's an uninformed thought.
- Performance on game servers
- Thoughts on concurrency in general, including whether you'd use the same primitives to achieve what you did back then
- Areas where you felt the tooling was lacking, or if the language could have constructs that would make that problem easier
That's it on a surface level! Your experience seems really interesting, and I'd love to read more and learn from it.
Isn't that always true for thread pool-backed parallelism? If only one core is available for whatever reason, then you may have concurrency, but not parallelism.
> and thus ad-supported
What a sad view of the web. Advertisement is a net-negative for society.
I agree, although if someone isn't the kind of person who would calculate that, they're probably not the person who will become the CEO of a company that size in the first place. I don't think organizations have the right incentives in place to push people with those values to the top.
This can be just my lack of familiarity with the ecosystem though.
Gleam looks lovely and IMO is the most readable language that runs on the BEAM VM. Good job!
One thing that could be improved is that the author could break down some of the commands, and explain what their arguments mean. For example:
> mknod rootfs/dev/console c 5 1
Depending on the reader's background, the args 'c', '5', and '1' can look arbitrary and not mean much. Of course, we can just look those up, and it doesn't make the article worse.
Immigrants can request a CPF (the 'national ID'). I don't think being in the country 'legally' is a requirement, that isn't enforced the way it is in the US.
> people living in Favela who essentially don't even recognize the state
Most people get assigned an ID at birth. And people who live in a favela often have to work outside it, and they interact with most companies/state services that aren't utilities as usual.
Utilities OTOH often get MITM'd by militia/narcos these days though.
> I assume it's something like the US where 10 illegals work under one social security number or a tax ID
No need for anything fancy like that. The poorest people are willing to work based on verbal agreements, as the alternative is either starving, or hoping the public social security network has your back. And in case your employer requires one, that's a non-issue because, except for rare circumstances, everyone has one.
Digital banking, install payments and general smartphone usage is widely popular, including favelas.
Basically all web shops in Brazil require you to give a government ID to buy anything (usually your CPF number).
25k/month? Most people will never come close to earn that much. Most developers in the third world don't make that in a full year, but are affected by raises in PC parts' prices.
I agree with the general principle of having savings for emergencies. For a Software Engineer, that should probably include buying a good enough computer for them, in case they need a new one. But the figures themselves seem skewed towards the reality of very well-paid SV engineers.
Why? Genuine question, sorry if it was said/implied in your original message and I missed it.
Debian also has something 'in the middle' with additional repositories that aren't part of the main distribution and/or contain proprietary software.
Personally my biggest complain from Rust is that I wish it was more readable. I've seen function signatures that seemed straight out of C++.
Out of curiosity, what would you recommend? And what would be needed to make them work automatically?
I don't follow. JavaScript is a dynamic general purpose programming language. It is certainly not limited to displaying websites, nor it's a requirement for that. The improvements I mentioned in the previous post aren't things you'd get the benefit of inside a web browser.
Are we talking about the language, or the wider ecosystem?
If the latter, I think a lot of people would disagree. Bun is about three years old.
Other significant changes are Node.js being able to run TypeScript files without any optional flags, or being able to use require on ES Modules. I see positive changes in the ecosystem in recent years.
It's a shame some ecosystems move waaay too fast, or don't have a good story for having distro-specific packages. For example, I don't think there are Node.js libraries packaged for Debian that allow you to install them from apt and use it in projects. I might be wrong.
I'd say yes, my reasoning being:
1. DDR5 got more expensive;
2. 16 cores AM4 CPUs are cheaper, partially due to the release of the 5900XT (16C/32T CPU, basically a rebranded 5950X with 100mhz lower single-core boost clock);
3. Lots of gamers selling their used AM4 kits for good prices as they migrate to the 9800X3D.
> What you actually want is low latency
High frame rates directly contribute to lowering latency.
I guess I'm the polar opposite of you here, I heavily prefer low latency/high refresh rates over low CPU/GPU usage, as long as the machine is plugged in to a power source.
Though they aren't really competing on anything as far as I can tell, so maybe calling it a "similar project" is more fitting.