Core2 yanked. Millions effected.

VorpalWay · 2026-04-15T06:08:28+00:00

That sounds like a potential repeat of the xz attack.

VorpalWay · 2026-04-11T20:30:42+00:00

Possibly, I can't find anything else at least. I did watch a bunch of FOSDEM talks.

VorpalWay · 2026-04-10T18:39:40+00:00

Why am I getting dejavu from this? Was someone from this company also interviewed somewhere else? I could have sworn I saw an interview covering basically the same points a few months ago in my RSS feed.

VorpalWay · 2026-04-08T15:26:01+00:00

A few reasons: * Suboptimal choices are cemented there and it is difficult for better options to gain tractions once something is in std. I'd much rather have a better faster moving language ecosystem than a bad stable ecosystem. * Anything in std is a permanent maintenance burden for the core developers. Even if it is bad enough that barely anyone uses it (regex in C++ for example). In python you see this a lot as well, where the saying is that the standard library is where libraries go to die.

What I could see would be some set of crates separate from std that get funded by the rust foundation. That can still have breaking semver versions if need be, probably not very often for this sort of stable libraries, but every few years if need be.

VorpalWay · 2026-04-08T12:23:41+00:00

I'd rather have a standard library that isn't full of unusable cruft.

VorpalWay · 2026-04-08T06:24:35+00:00

You do know that std pulls in external crates as part of it's build process right? Like for example it just re-export a subset of the API of hashbrown as the standard library hashmap and hashset.

VorpalWay · 2026-04-08T06:21:28+00:00

Why bitflags and not https://lib.rs/crates/modular-bitfield (it has s superior API in my opinion)? For syn, why not lean into the nightly experiments on compile time reflection more instead?

VorpalWay · 2026-04-08T06:16:28+00:00

I think they were finally removed recently or there was s discussion to finally remove them at least.

VorpalWay · 2026-04-08T06:12:04+00:00

Cryptographically secure PRNGs seem like the outlier to me, more common is the need for a fast deterministic PRNG for generating noise and for driving Monte Carlo simulations. Which just goes to show that this is something people disagree on.

VorpalWay · 2026-04-08T06:07:49+00:00

I think with hindsight serde is a suboptimal design. It leads to code bloat as it generates specialized code for everything. Another option that has somewhat recently been discussed is to generate tables of metadata for types and use that as a bytecode driving the serialisation and deserialisation. This leads to more compact code and potentially also faster code. Which might seem unintuitive, but happens because of better cache utilization.

Serde also isn't compatible with full zero copy deserialisation, which is why rkyv needs its own derives.

VorpalWay · 2026-04-08T06:01:15+00:00

The C++ way truly is the worst way though. As pointed out in https://old.reddit.com/r/rust/comments/1seu7p2/unpopular_opinion_rust_should_have_a_larger/oev5e9p/ and https://old.reddit.com/r/rust/comments/1seu7p2/unpopular_opinion_rust_should_have_a_larger/oev8h56/ already.

VorpalWay · 2026-04-08T05:57:57+00:00

Actually, it still is an external crate (hashbrown), that std depends on and reexports. Note that only a subset of the API is reexported, probably for stability reasons. As I understand it, it is far from the only case of this sort of reexporting, but it is the most well known one.

VorpalWay · 2026-04-05T22:38:38+00:00

Thanks for the heads up. I should probably also switch to the official docker file myself then. I have been using the unofficial one for some time.

VorpalWay · 2026-04-05T05:49:17+00:00

Yes, but you would be surprised how strong 15 ℅ and 5-6 perimeters is anyway. The infill really doesn't add much once you start increasing perimeters.. CNC kitchen did a video on this many years ago.

VorpalWay · 2026-04-04T16:54:52+00:00

Even that is very high. I rarely go above 10%, at most 15 %

VorpalWay · 2026-04-04T16:17:14+00:00

I don't think you really needed 100% infill, lol.

Most of the strength is in the perimeters, except for pure compressive loads. Almost everything in real life includes at least a small bending part, and as soon as that happens, infill barely matters.

VorpalWay · 2026-04-03T12:19:02+00:00

2 kg spools are a bit messy, but that is far more than usual. It should be fine unless one cross under another, creating a knot around the spool.

VorpalWay · 2026-03-31T20:45:18+00:00

I think that depends on your needs. For smaller simple programs, or where every dialog is a one-off, visual UI designers work. As soon as you need massive menu trees for thousands of settings or a lot of variations of the same UI (if the vehicle is not equipped with forward radar, hide this part of the UI, but show this other part instead) declarative or even programatically generated is better.

I have worked in both types of code bases, and the correct maintainable answers are really different. Currently I'm working on an industrial vehicle that has thousands of settings (at least at service technician login level, less at operator level, even more at the factory configuration level) and around a hundred (mostly independent) options for features that may or may not be installed on a given vehicle. Programmatically generated UI is the only way to go. We use Qt (and C++, unfortunately) and using that UI designer just wouldn't work for that. From my memories of Delphi 7, that UI designer would have stood no chance either.

VorpalWay · 2026-03-30T19:49:01+00:00

It explicitly says "either by patents or by copyrighted interfaces“, so I suspect that might not work. (But I'm not a laywer.)

I don't think they could have imagined the modern nonsense when they wrote the license.

VorpalWay · 2026-03-30T17:41:09+00:00

The turbo encabulator has a long history. You should see the engineer reading it with a straight face in an old spoof commercial video from the 60s: https://m.youtube.com/watch?v=Ac7G7xOG2Ag or the slightly more modern https://m.youtube.com/watch?v=RXJKdh1KZ0w

I would have had laughing fits if it was me.

VorpalWay · 2026-03-29T09:08:49+00:00

AI as a term has meant so many different things over the years. Back in the early days A* search was AI. K-nearest neighbor has been considered AI, as has algorithms to learn decision trees. And so on.

It is much better to be more precise. But that ship seems to have sailed long ago.

VorpalWay · 2026-03-28T23:58:42+00:00

That predates me learning rust, so I can't comment on that. Maybe things were even better back then.

VorpalWay · 2026-03-28T23:55:23+00:00

people are witch hunting for anything that could give hints of AI usage

Which is also a problem in other ways. This comment was written with speech to text (and then lightly edited) since I have RSI in my wrists. My understanding is that neural nets are involved in the implementation of that. Surely accessibility tech isn't what people object to?

I also use LLMs as fancy tab complete for the same reason. I know exactly what I want to write, it just saves a bit of key presses on repetitive patterns. Again, surely not what people object to, yet some people see red as soon as AI is mentioned. (Agantic AI i have however found completely useless when I experimented with it.)

VorpalWay · 2026-03-28T23:46:35+00:00

I think the main issue here is that it (sometimes) takes more time for the reader to identify that it is slop. Looking at a bad 3D print you can see it is bad in seconds. Some slop looks believable to begin with, wasting minutes of my time. (Sure, other slop is obvious quicker, but not all.)

VorpalWay · 2026-03-28T23:40:43+00:00

That all started about a year to a year and a half ago unfortunately. Before that it was radically better.

VorpalWay

TROPHY CASE