We need lots of cosmetic stuff we're probably not gonna get.

I usually do, but sometimes, it just doesn't feel feasible. Not if you're going for "pretty" factories, like we're trying to, this time around.

Like, this build will be able to accommodate me upgrading the one miner that powers it to a Mk3 at 250% clock, without needing a clock higher than 250% on any machine. And no belt will need more than 1,200 items/min. But, for example, my first attempt to plan for this factory was to use all of the mine-able Quartz in this cave, not just a single Pure node, and that would have required me to have 40 constructors. It just didn't seem worth it to me, when this facility will already produce over 500/min of each item, when it's fully-upgraded. If that does turn out to not be enough, I'll add another miner, and figure out how to either expand this facility, or build a second one right next to it.

Yeah, "lack of vision", that's definitely the problem.

The "vision" of the Israeli government has been clear for quite a while, now: Israeli ownership and settlement of the entire region, achieved by killing off or convincing to leave everyone that's already there.

For sure, it's just unfinished, so I didn't bother yet. The maun facilitiy is pretty much complete, from the outside, except for painting and lighting.

So how much cocaine was he using?

My brother in Christ, this is a social media platform. Idiotic posts is what we live on.

Me personally, I'd do a combined factory.

I also have to make an effort to suppress the design paralysis urge. Like, sure, thinking about how stuff bow will fit with future ideas is good, but it's not worth agonizing over. Figuring out how to connect systems that weren't necessarily made to work with each other is part of the challenge/fun, and usually produces a more interesting result than something fully-planned-out.

Also related to reddit, since that's where I was always inundated with this shit, before moving here: the constant stream of Genshin Impact leaks that come out, that the whole obnoxious subculture is built around, are just released by Mihoyo, intentionally, under the guise of all the anonymous leakers that constantly come and go. Seems to me like the only explanation for how CONSTANTLY leaks come out, and how they're basically never actually damaging to the game or the company, while being REALLY effective at stirring up obsession in the fanbase, and driving people to invest more time and money into the game to be prepped to get the next new character immediately on release.

Also how so many of the leakers would release extremely accurate stats and numbers, but then drop statements like "if I release any more than this, I'd be risking my safety" or "since everyone's been asking about it, I'll go ahead and confirm X, but after this I'm gonna have to go on hiatus for a while, until things cool down". Seems like nonsense meant to either inflate the leaker's ego, or rile up the fanbase.

First game I ever played where I was like "yo, I actively WANT to do the speedrun achievement, and the deathless achievement." So, first game where I ever did those things. Maybe I'm just crazy, but I found them way easier than I expected.

Also, a prime example of storytelling through music.

I appreciate the "carrot with a bit out of it" icon.

Red.

Naaaaaaaaaahhhhh......

I'm guessing Vance said something insulting about Appalachia.

It's the capability of a program to "reflect" upon itself, I.E. to inspect and understand its own code.

As an example, In C# you can write a class...

public class MyClass
{
    public void MyMethod()
    {
        ...
    }
}

...and you can create an instance of it, and use it, like this...

var myClass = new MyClass();
myClass.MyMethod();

Simple enough, nothing we haven't all seen before.

But you can do the same thing with reflection, as such...

var type = System.Reflection.Assembly.GetExecutingAssembly()
    .GetType("MyClass");

var constructor = type.GetConstructor(Array.Empty<Type>());

var instance = constructor.Invoke(Array.Empty<Object>());

var method = type.GetMethod("MyMethod");

var delegate = method.CreateDelegate(typeof(Action), instance);

delegate.DynamicInvoke(Array.Empty<object>());

Obnoxious and verbose and tossing basically all type safety out the window, but it does enable some pretty crazy interesting things. Like self-discovery and dynamic loading of plugins, or self-configuration of apps. Also often useful when messing with generics. I could dig up some practical use-cases, if you're curious.

It's known, recently, as the "pig butchering" scam, and this is the telltale opener. The idea is that you respond with "hey, you've got the wrong number" and they can then open a dialog of "oh, sorry about that" and then spend weeks or months just conversing with you casually to build a "heh, what a crazy way to meet a new friend" sorta relationship. Eventually, they spring some kinda ask for money or malware on you, because they earned your trust.

Give it a google, it's pretty fucked up, and completely counter-intuitive how effective and profitable it is.

Goddamn, I completely missed that.

I think they're a decent chance that's what they mean, anyway. "What, no, what the hell would we want with your shitty social media software? Just give us the domain name."

Me, it's not the size of the blueprint, particularly since they added 5x5 and 6x6 blueprints in 1.0, it's the fact that blueprint placement is horrendous for seemingly everything except perfectly-rectangular structures. And non-rectangular structures are basically the ENTIRETY of thing the things that are difficult to build, and thus worth blueprinting.

My wife and I have been putzing with coal power and blueprints and experimenting with architecture for 3 days now. Haven't really done anything productive in that time. Have completed Tier 3, and part of Tier 4.

I'm on the verge of declaring blueprints to be more trouble than they're worth. Anyone else?

If you're interested in detail, I can recommend this book: https://play.google.com/store/books/details?id=ncGVPtoZPHcC.