The article says this uses only 30% of the concrete you’d otherwise use. Presumably prefab would use more.

In Denmark it’s usually bricks (very common and traditional) or other stone like materials or concrete. Never understood why there is this difference across the world in how houses are usually built, but wood seems a very… Temporary material for something like a house? I’ve lived in buildings from the 1910s, I can’t imagine anything made of wood lasting that long.

What do you mean switching? Think this is more about using less concrete than stopping to use it entirely. That also helps, but yea it’s a problem.

Not sure about speed but I imagine it could be pretty speedy, if for no other reason than the fact that it can run with much fewer workers and probably also running during the night. I mean even if it was half as slow as manual labour, if it ran for 24 hours, it would still be faster overall.

But another point is that it uses much less material, 70% less according to the article. I suppose that helps with costs and CO2 emissions.

Surprisingly political. Not often that happens, not that I mind.

How much did it cost to get all the parts?

On that I agree. It’d be nice with a more universal platform.

I feel like that’s an unnecessarily narrow view of what the fediverse can be. The fediverse is not only for any single particular social networking use case, like micro-blogging (Mastodon) or forums (Lemmy, Pyfed etc). It can be much more than that, and all of it at the same time. There’s no reason why the fediverse should restrict itself to only certain social media use cases.

Not sure I understand - you think some of those things don’t belong on the fediverse? What do you mean “one or the other”?

I know we love to hate on LinkedIn, but honestly there are plenty of reasons to want social features about employers and jobs. Reviews, salary discussions, union organization and all such stuff that employees could leverage against employers, for instance.

Of course that’s not what LinkedIn is largely used for because it’s full of employers trying to brand themselves or influencers trying to make an image for themselves. But it could be different, I think.

but i assume the sheer amount of images/video takes up a lot of space

You can adjust settings in Lemmy to not store other instances media like this, so this shouldn’t be a big problem with the right config.

Already posted, duplicate post

Super cool! Hopefully that can resolve some of the long standing issues with the borrow checker.

I’m not really sure what you’re asking. Or I guess I mean, it’s a very broad question. Just start a project and get learning.

If you have any more specific questions, feel free to ask!

Isn’t it pretty obvious? Fastrand is not cryptographically secure, urandom provides that option.

Scenarios in gambling are rarely “purely random”. I.e. the likelyhood of winning in poker depends on what you already got dealt and what other cards got dealt and so on. What does “purely random” even mean? Like a lottery with equal chance of winning for all participants? Yea that’s gambling but just one kind of gambling.

working on a project where memory safety isn’t that important

I can’t really imagine anything where this is not the case, unless you’re doing like… I dunno, small scripts for personal use or something? But why would you use Zig or C or even Rust for that, just do Python or even bash at that point? Python is memory safe and perfectly suitable for very small programs where static analysis gives little benefit.

ReleaseSafe which have runtime checks to prevent illegal behavior

To prevent some illegal behaviour. Again, I’m not an expert on Zig, but as far as I understand, even Release"Safe" is not actually memory safe.

Saying that “memory safety is checked by tests” is basically saying “memory safety is not checked”. Yes, you can write tests. How do you know the tests cover all cases? How do you know the tests aren’t buggy?

Also, what about memory safety across threads? Are you testing multi-threaded scenarios? Are you ensuring you have no data races?

I also don’t understand how this is an argument for Zig over C. You can also test memory safety of your C code via various means, but it’s never a guarantee. Zig is the same. So again, it seems a bit more pointless to go from C to Zig. Going from C to Rust brings actual tangible guarantees of memory safety (outside of any unsafe usage, obviously).

rust does a great job, however there are some inconsistentcies where a lot of memory allocations can throw out of memory errors that will crash the app

That is not an “inconsistency”. Crashing the application when you run out of memory is honestly in almost all cases the correct call and crashing is memory safe. Most applications can do absolutely nothing when running out of memory. “Handling” OOM is extremely complicated and most applications simply cannot handle it in any way.

Of course low level stuff needs to sometimes actually handle this, but it’s mostly an operating system thing. And Rust still allows you that control, it’s just not the default behavior of the collections and such in the standard library, because again, it almost never makes sense to try to handle OOM. But if you really need that behavior, you can have it.