- It would be a non-trivial amount of work but syscall user dispatch lets you intercept syscalls on modern linux if you really want to.
https://docs.kernel.org/admin-guide/syscall-user-dispatch.ht...
- > firmware
Yes, lots of firmware runs on hardware where a GC doesn't make sense. Because of limited memory and performance constraints. Sometimes having predictable timings (i.e. not a GC with pauses) is nice. I believe compiler and library support is also just better for many embedded platforms in rust.
> networking type software
Rust is a much more aggressively optimizing compiler, and thus will typically be faster, in the places where that matters. GC pauses might also be a point against golang in some places here. Rust's idioms provide slightly less opportunity for bugs in places where reliability matters (e.g. having a type system that requires you check for errors instead of just patterns that encourage it).
So there's a difference, but generally go is a good enough language for networking software and it would be rare that I wouldn't suggest that "use what you know" is more important than the differences between the languages for non-firmware network software.
- They didn't. They forked an old unmaintained thing already written in rust to add new features...
- For me it either worked great or not at all. Extracting footsteps, the air conditioner noise, voices, one particular persons voice (identified by gender), all worked great (across multiple clips for most of those).
A few prompts failed almost entirely though, "train noises", "background noise" and "clatter"... so definitely sensitive to either prompting or the kind of noise being extracted.
- Footsteps worked pretty well when I tried that on the other hand. I wonder if lot of it has to do with how well the model understands what the english description of the sound should sound like...
- That didn't actually happen. The governor threatened to prosecute, and ordered the police to produce a report on their investigation into the matter. The police complied producing a report saying the person the governor wanted to prosecute did nothing wrong.
- > in its dependency tree.
Ultimately every program depends on things beyond any compilers ability to verify, for example the calls to code not written in that language being correct, or even more fundamentally if you're writing some embedded program that literally has interfaces to foreign code at all the silicon (both that handles IO and that which does the computation) being correct.
The promise of rust isn't that it can make this fundamentally non-compiler-verifiable (i.e. unsafe) dependency go away, it's that you can wrap the dependency in abstractions that make it safe for users of the dependency if the dependency is written correctly.
In most domains rust don't necessitate writing new unsafe code, you rely on the existing unsafe code in your dependencies that is shared, battle tested, and reasonably scoped. This is all rust, or any programming langauge, can promise. The demand that the dependency tree has no unsafe isn't the same as the domain necessitating no unsafe, it's the impossible demand that the domain of writing the low level abstractions that every domain relies on doesn't need unsafe.
- The rest of the world doesn't consider 'gotten' a proper word?
- https://jj-for-everyone.github.io is the most approachable jj tutorial I've seen. I wouldn't say it focuses on workflows, but it does take a "learn by doing" approach a bit more than the "data model first" approach it sounds like you might prefer.
It's still a young tool, it's not surprising that tutorials are a bit lacking (honestly there are surprisingly many for its age). Maybe be the change you want to see in the world and make one? (Which would be an... interesting... way to learn the tool for sure).
- I get that, I'm just disagreeing that we should be looking forwards to storage becoming that cheap. Particularly when our cheap energy sources (solar, wind) have a lot of location specific variability over time.
With some exceptions for sufficiently remote (or sufficiently always-sunny and not too dense) places that local grids themselves are no longer worth it
- I think long range transmission remains a thing anywhere having a local grid remains a thing (which will be most places for other reasons).
Load-balancing the area having a cloudy few days and the area having a sunny days and the area having a windy few days and so on will remain extremely valuable. It lets you install a lot less batteries and isn't that much infrastructure given that the last mile problems are dealt with already.
- > it peaked in June at 10500 GWh
And 8280 GWh the previous June for those wondering roughly how much of this was due to more solar panels being deployed.
- Just build more solar. You generate excess electricity in summer and enough in winter. This isn't a problem.
- And LFP is also cheaper per unit energy and less of a fire hazard. Hard to imagine why you would use a different lithium-chemistry in a UPS.
- If demand stays high existing firms will increase capacity to make more money, and then will compete against eachother on price to sell their new extra capacity. They'll do the same to prevent new firms (in other counties or not) from having an opportunity to come into the market and undercut them.
An illegal price fixing cartel could defeat the first pressure on prices (though is unlikely to). The second pressure would exist regardless.
GPU prices have primarily stayed so high because there's kept being new surprising sources of excess demand that the market didn't anticipate. I.e. it has yet to reach "eventually". Also to some extent Nvidia's government enforced monopoly on CUDA (via copyright) has meant they don't have any competitors with equivalent products. And software creates a so called "natural monopoly" because it has zero marginal cost while hardware generally doesn't.
- Eh, here it's more of a simplification than a myth as used in my comment. There are two effects:
1. We've reduced infant (and childhood) mortality. My comment isn't talking about this effect but it did drag down average life expectancy substantially. Including this effect life expectancy at birth in the stone age might have been as low as 20... but as you say the bimodality means this is a deceptive statistic when used this way.
2. We've made it so you on average live longer even if you survive childhood, my comment is really just about this part of the effect. It's still a simplification because saying "on average if you survive childhood you die at 40" isn't the same as "everyone dies at 40" but closer to "adults die at all ages in a reasonable smooth monotonic curve and 40 is about the average age they live to but some get lucky and live to 80 or whatever". But then "don't use ultrasonic dehumidifiers" is like this too, using one won't kill you at some specific age, it will just slightly increase your chance of death every year for the rest of your life however long that ends up being.
The number 40 was picked out of a hat, too. It should be right for some areas at some times just by coincidence though and since I was non-specific that makes me right ;)
- We didn't have access to modern technology... like ultrasonic speakers?
Also we died at a young age. Everyone dying at 40 isn't incompatible with the species surviving but it's what advice like that is usually trying to avoid (and even less extreme outcomes).
- Logs need to go somewhere to be collected, viewed, etc. You might outsource that, but if you don't it's a service of it's own (probably actually a collection of microservices, ingestion, a web server to view them, etc)
(Not that it really matters since I don't buy for a second that anywhere near 40% of people/people-driving are high at any given time. I also don't put much faith in numbers in the abstract of a a yet-to-be-published study...)