RustyNova

I'm going to burst your bubble but GitHub doesn't allow non open source licenses on public repositories.

Just ask winamp lol

Michelin guy

I hope it's not needed to be connected to the internet. It's not like there's 62937 vulnerability that are network based without user interactions on old windows versions, right?

Oh hey. We'll probably have something new in the BCachefs saga soon!

But anyway, that wait for cleaned sub volumes ioctl seems great

I feel like it's more analogous to enum pattern. Your belt is just a array, and your items are enums that may be part of that enum

So to go back to gleba, nutrient belts are just Vec<Result<Nutriment, Spoilage>>

I was actually making my own legendary grinder! But it has some of the problems I personally think is a deal breaker

• No easy replacement for the assembler. You need to move everything if you want to put an electromagnetic lab
• not modular. Low quality assembly often get clogged while high quality is waiting for stuff, so you need to be able to add more low quality assemblies than high quality.
• No easy way to set the buffer. 4 stacks is way too generous, and you way want to lower the buffer for low qualities

It's been at least 20 hours since I said "let's get there". But preparing for it was supply issues after supply issue

A few things to note:

• spoilage inserters should always be placed on the same belt as the last inserter that needs it. It prevents situations where the spoilage inserters still have fresh items while the machine inserter has spoilage
• heating towers are better at egg disposal. You can even get some electricity back!
• it's better to have centralised nutriment production for your factory block. A bioflux to nutriment biolab could easily power both sides with less wastes

Technically yes, but a newbie doesn't need that. I doubt it's an application that performance is so critical either.

Too much premature optimisation IMO

It's quite simple. Just remove the permalink field! If you are calculating it then no need to store it in the struct.

If you do need the field to be there (ex you serialise it with serde), then create a method called new that takes everything but the permalink, construct your permalink there, then return a new object.

Your permalink method can now just be self.permalink.to_string()

P.S. in the second case I'd recommend to change the return type of self.permalink() to &str. It avoids unnecessary cloning of the string.

You guys need FNEI? Factoriopedia is great!

For a second I thought it was the Linux comunity