dralley

It was messy. A number of agencies of the German government, including a handful of intelligence agencies, used Wirecard for banking.

Or the amount of energy required to produce a large gas turbine. Which, between the refining and advanced metallurgy and the casting and machining of such a large piece of metal, is a lot.

Compared to gas generators? Probably. And unlike gas there's no ongoing cost.

This matters less in Alaska than nearly any other state, given their ranked choice system.

Personally, after having watched Rs put up fake Dem candidates in my state and pull the same games with candidate names in other states, it's hard to get too upset about this. Either make it illegal, make a bilateral pact of de-escalation and stop doing it, or quit whining.

The people that got fucked over by Wedgewood were the party-preferred candidates. Wedgewood artificially inflated the polling of progressive candidates that were running against the party to a degree.

On top of that it's not election fraud, though it is potentially some kind of fraud if they were involved in betting markets.

It has improved significantly since the early days of 3.0. Not back to 1.1.1 levels of performance, but enough that it's probably not a dealbreaker for most people.

Still a shame that it went backwards.

I don't think it's necessarily that difficult to monetize, they just ignored a lot of the needs of enterprise users (rootless, not punching holes in the firewall, not fighting with systemd, private registries) for long enough that other projects (e.g. Podman, Quay) filled the void.

You have a point but it's just hyperbole in the other direction. Yes, Rust is only a small fraction of the code in use every day, but it has nonetheless achieved deep penetration into critical infrastructure.

Cloudflare's network routing code is predominantly Rust. Massive parts of AWS and Azure are Rust (including crown jewels like S3 and Lambda). Multiple car manufacturers have shipping Rust code in their production cars for years, albeit yes it's a slow process intoroducing it into regulated industries. Airbus and Boeing are putting up job openings for Rust development. As mentioned critical pieces of Windows and Android are now written in Rust. If you use Discord - that's Rust. If you use Amazon Prime Video or Disney+, that's Rust. I could go on.

When like 40% of internet traffic and 75% of end user devices are using Rust in some capacity, to say that it's "not production" is just ignorant, arrogant nonsense.

I've never seen an LLM write unsafe Rust unless I explicitly asked it to, or the thing I asked it to do fundamentally required it.

Well, that will certainly be an issue for nuclear power capacity in the future.

It's just a Lotus body, though I agree that Lotus cars are pretty

Why does Russia whitewash Stalin in 2024/5/6?

Correct. e.g. RHEL 9 has Python 3.14 available

https://access.redhat.com/support/policy/updates/rhel-app-st...

The support lifecycles are divergent from the rest of the OS though. Only the base Python version gets full lifecycle support, the newer versions get refreshed occasionally and eventually fall out of support.

They're not that far apart anymore. Wild is still faster on average but they trade blows occasionally. Both are well ahead of the next best.

It's unlikely that many people are using Rust without using Option<T> or Result<T, U> a fair bit. Idiomatic Rust fundamentally uses a lot of generics. And a basic for loop expands into quite a lot of intermediate representation due to Iterator.

This is not actually the main reason, most of the time.

Generics/monomorphization and how iterators work results in a lot of compiler bytecode that has to be churned through. More bytecode = longer compilation. It increases the size of the (debug) binaries, the debuginfo in general, causes performance issues with debug binaries in some situations unless you bump the optimization level, causes more IO, etc.

The project was started long before LLMs existed.

There is a rustc_codegen_clr which transpiles to .NET

https://github.com/fractalfir/rustc_codegen_clr

>overhaul Firefox to be all our Rust as Quantum was aiming towards

That was not in fact the purpose of project Quantum

It has supposedly dropped to below 10% (but higher on average in rural areas than in cities, and of course that's just smoking, not the use of other nicotine products)

https://hsph.harvard.edu/news/u-s-smoking-rate-hits-an-all-t...

The article suggests that 18%+ are using some kind of nicotine product in general (zyn, chewing tobacco, vape, smoking)

In any case it has been mostly successfully purged from public spaces.

They've mostly switched to vapes now. It's still annoying, but at least it doesn't leave trash all over the streets.

Seeing the sidewalks / parks outside of the main train station in Prague covered in cigarette butts as an American tourist in 2019 was certainly something.

DRM = Direct Rendering Manager. GPU scheduling.

The latency isn't that bad, it's reasonable for a compatibility shim.

>and intentionally stifled improvement on xorg

Open source developers are not required to spend their time prioritizing your priorities. You just have to look to Xlibre to see that a lot of contributions are quite bad quality, and in a C codebase of Xorg's complexity and security profile it's not a small job to review things.

Xorg's security (and X11 in general) is objectively terrible - this is not even a debatable question.

Xorg isn't neglected for "ideological reasons", it's neglected because development is work - and most of the people with knowledge of the problem domain decided they didn't want to work on Xorg anymore, and most of the companies that were paying for it decided they didn't want to pay for it anymore (apart from baseline maintenance, Xwayland and security fixes). And the people who want Xorg support maintained in perpetuity rarely seem interested in maintaining Xorg themselves, at least not properly (see this history of Xlibre introducing bugs and LLM slop).

You are free to spend your own time and resources doing the work, but you don't get to dictate how other people spend theirs.

Wayland is not a "display server", it's a display protocol.

A lot of the "existing functionality" that it broke has nothing to do with displays, it's stuff that got crammed into Xorg at some point whether it made sense or not.

I find it quite funny that many of the same people that rag on systemd and say it does too many things, are big fans of Xorg doing a bunch of things that "display server" probably should not be handling.

Even if Wayland was a "display server", it would still "remove existing functionality" if it meant that in any principled sense, because "display server" is only half of what Xorg does.

But sure, the transition was difficult and took a long time.

Well for years HN was complaining that Mozilla was trying to fix that, because it broke XUL extensions.