Actually, those materials can be MUCH more radioactive in the beginning compared to 'conventional' nuclear waste, the half-life is just so short that you can let them sit for a couple of decades and then deal with it.
I sincerely hope Donut really has an ace up their sleeve, we could really use some domestic competition against China here in the EU. I sincerely hope that the next update from them is something solid (pun intended), and not 'what color is the battery'.
> We have libraries like SQLite, which is a single .c file that you drag into your project
You are just swapping a package manager with security by obscurity by copy pasting code into your project. It is arguably a much worse way of handling supply chain security, as now there is no way to audit your dependencies.
> If you get rid of transitive dependencies, you get rid of the need of a package manager
This argument makes no sense. Obviously reducing the amount of transitive dependencies is almost always a good thing, but it doesn't change the fundamental benefits of a package manager.
> There's so many C libraries like this
The language with the most fundamental and dangerous ways of handling memory, the language that is constantly in the news for numerous security problems even in massively popular libraries such as OpenSSL? Yes, definitely copy-paste that code in, surely nothing can go wrong.
> They also bindings for every language under the sun. Rust libraries are very rarely used outside of Rust
This is a WILD assumption, doing C-style bindings is actually quite common. YOu will of course then also be exposing a memory unsafe interface, as that is what you get with C.
What exactly is your argument here? It feels like what you are trying to say is that we should just stop doing JS and instead all make C programs that copy paste massive libraries because that is somhow 'high quality'.
This seems like a massively uninformed, one-sided and frankly ridiculous take.
> You are just swapping a package manager with security by obscurity by copy pasting code into your project
You should try writing code, and not relying on libraries for everything, it may change how you look at programming and actually ground your opinions in reality. I'm staring at company's vendor/ folder. It has ~15 libraries, all but one of which operate on trusted input (game assets).
> fundamental benefits of a package manager.
I literally told you why they don't matter if you write code in a sane way.
> doing C-style bindings is actually quite common
I know bindings for Rust libraries exist. Read the literal words you quoted. "Rust libraries are very rarely used outside of Rust". Got some counterexamples?
Gamedev is its own weird thing, and isn't a model you want to generalize to other industries. It has to optimize for things a lot of software does not, and that skews development.
Vendoring libraries is almost always a terrible idea because it immediately starts to bitrot and become a footgun.
Sometimes it's necessary, but it's not desirable, and you almost always just want to pin your dependencies instead.
> And cancel culture. Highly politically motivated cancel culture.
Most of the people who started on Mastodon are people of the LGBT+ community that were getting constantly harassed on other platforms. This 'cancel culture' is just a healthy attitude to having a zero tolerance policy on abuse, it is how it avoids being the enormous bigoted alt-right techbro mess that is now X.
Since Mastodon is federated, you can choose the instance you want to use, and what you see. Just don't expect other instances to actively want to engage there.
Not true. You cannot federate with tech news and bigoted alt-right techbro (based) instances. That decision is made for you by the janitors of the instances you federate with. Just like reddit, where the janitors of the subreddits decide what you're allowed to see. Your agency is gone.
Compare this to X, where if it's not illegal, you can choose to see or say it with no repercussions beyond an individual blocking you, which solves their problem of not wanting to see what you say. It's the perfect system!
It avoids the overhead of Promises, so I can imagine that this would be quite useful if you know that blocking the thread is fine for a little while (e.g. in a worker).
Servo has a distinct design goal that sets it apart from its predecessor within Mozilla and has already had offsprings that has made its way directly into Firefox.
Its purpose is not to reinvent everything. It’s not a hype project.
Servo's original purpose was to reinvent everything for Firefox to modernize the codebase, and make it secure and more performant (e.g. CSS styling engine, HTML parser, etc.) So it actually fits that purpose pretty well.
Unfortunately licence incompatibility may prevent that. Ladybird is BSD and Servo is MPL. This is also why there is only limited collaboration between Servo and the Rust GUI ecosystem.
I wonder what this means for the EU. We made a new deal under pressure of the tariffs that is actually worse than the deal we had. If we had not bent the knee, we would have had that original deal back, or at least, so it seems? Now we seem to be properly shafted due to weak politicians.
1. The EU would face higher tariffs on their exports to the USA. Now mostly struck down
2. The EU would not retaliate with tariffs of its own. Not really a big deal since the only US export to the EU that's worth worrying about are digital services, and those aren't subject to tariffs anyways.
3. The EU promised to buy lots of LNG and make investments in the USA to the tune of hundreds of billions of dollars. This was a bald-faced lie on the part of the EU negotiators. Even if the EU wanted to actually do this, they have no power or mechanism to make member states and companies within those member states buy more LNG or make more investments in the USA. This was just an empty promise.
___
So if the tariffs are struck down, we're more or less back to where we started.
> The EU promised to buy lots of LNG and make investments in the USA to the tune of hundreds of billions of dollars. This was a bald-faced lie on the part of the EU negotiators. Even if the EU wanted to actually do this, they have no power or mechanism to make member states and companies within those member states buy more LNG or make more investments in the USA. This was just an empty promise.
The amounts named were also, ah, suspiciously similar to the amount of LNG Europe would generally buy, and the amount that would be invested in the US as a matter of course. It was kind of "well, the thing that would ordinarily happen will happen".
It also has an ever-increasing amount of debt and an aging population, e.g. the US is expected to spend more than $1 trillion a year on the interest on the debt itself, or $7,800 per household per year.
reply