yeah, i’m gaming on 1080 and mostly playing minecraft and factorio though, so im not exactly gunning for FPS there. I will keep this card until it dies dead properly, and then it will become wall art.
yeah, i’m gaming on 1080 and mostly playing minecraft and factorio though, so im not exactly gunning for FPS there. I will keep this card until it dies dead properly, and then it will become wall art.
welp, time to go buy intel… wait.
you and me both my friend, you and me both… except for the fact that im still vibing with them. EVGA 1070, i don’t want to give it up F
the only losers in this situation are people that are squatting on my rightfully pirated domain names!
because there’s also a lot of good stuff on the internet. There was very little on the internet in 2002, and yet people still used it because it was cool. There is a shit ton of information on the internet now, most of which is garbage, and the rest is somewhere between mediocre, or decent, and some of it being genuinely good.
If you hate living, why even bother living? It’s a question of the ages. What’s the point of living if there is no grander purpose? Surely it means nothing, right?
yeah, it also helps knowing how to use the thing, but i consider that to be “basic documentation” personally.
Knowing how to set something up is nice, but knowing how to use it properly after setting it up is even nicer.
2002 called*
and yes, they do want their opinion back, because the internet fucking sucks.
as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior. Write it like you’re coming back to the project in 5 years after having done nothing and you want to be able to skip right to using it. When we build something ourselves, we often hold a bit of internal knowledge from the design process that never quite goes away, so it’s almost always a lot easier for us to reverse engineer something we’ve made, than it is for someone else with zero fore-knowledge to do it themselves.
Generally this can be a bit of a nightmare, but if you minimize the user facing segment it’s not all that bad, because it’s usually pretty minimal, and what would otherwise be a handful of pages, turns into 10 or maybe 15.
as for existing documentation, the i3wm user guide is really good, it’s pretty minimalist but it leaves you enough to be able to manage.
this is just because it’s webhosted, anything that does anything on the web sucks and is terrible, everything else is actually so much better it’s fucking baffling to me.
web 2.0 is dead to me. web 3.0 won’t get off of the ground, we need web 2 electric boogaloo
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
i don’t know if i really like that definition. Going by the definition of a laboratory, it doesn’t really make much sense. I mean sure they’re a sterile environment, but it’s incredibly unlikely that a lab is wiped clean and built from scratch, unless you get millions of dollars, and a lot of free time, i guess.
A lab is merely a place to do work with regard to studying, learning, or improving something.
People often refer to their “homelab” as an entire server rack, you want me to believe that people are willing to wheel out their entire server rack and discard the entire fucking thing? I doubt it. A homelab is just a collection of gear, (usually commercial networking gear) intended for providing an environment for you to mess around with things and learn about stuff.
In some capacity a homelab has to be semi permanent, if not for anything other than actually testing reliability and functionality of services and hardware, for the actual services themselves, because a part of the lab, is the service itself.
Removed by mod
as long as we’re buying 12th gen, we’re ok.