2,213 karma · joined December 30, 2012
I use SystemD extensively and it's pretty neat, you just: - Define default Environment variables in your unit file - Customize a service by adding an overrides.conf file in foo.service.d/ folder This makes it easy to define exactly the environment for a service.
.env files are helpful in dev mode to customise machines where I don't want to pollute the system env, but they aren't the 'config format' and it makes sense that they are specific to the OS/shell they need to run in.
As for cross posting - re posting and re-mixing other people's content has been pretty much the basis of the internet since forever. Again, if this is something you're not happy with you should better create private forums for just your friends, that's a totally fine thing to do. Much like if you want an intimate house party you only invite your friends and eject any gatecrashers who try to sneak in.
Perhaps the clue is in the 'anarchism' bit - in anarchist circles when you have a smallish and relatively close group you can manage a very positive and supportive atmosphere without rules and protocols. But as things grow you lose that, inevitably, as having more people means needing more formalized ways of handling issues. I can see how it feels like losing something but on the other hand you have to question the wisdom of an approach that is basically guaranteed to fall apart as soon as it becomes a bit popular.
Classic big workstations are way more capable than people think - but at the same time it's hard to justify buying one machine per user unless your department is swimming in money. Also, academic budgets tend to come in fixed chunks, and university IT departments may not have your particular group as a priority - so often it's just better to invest once in a standalone server tower that you can set up to do exactly what you need it to than try to get IT to support your needs or the accounting department to pay recurring AWS bills.
One of the huge advantages of GDScript is how deeply in integrates with the engine and handles high level concepts, coupled with the node system you don't need to write that much code. Plus its a simple language (there's no need for 'javascript - the good parts' for gdscript).
The godot approach with GDScript and C++ is very much like Python and C++ - write in the high level scripting language and build C++ components when you need more complexity and performance. The scripting language becomes the user interface of the low level parts.
What is infuriating is that there is so much great work done by great people on building strong resilient and affordable towns which are a pleasure to live and work in, but the easy VC money flows to the wierdo charlatans instead.
If you have more significant compute needs a dedicated server can start to make sense. Linux admin is becoming a bit of a lost art in this container-everything world but actually it's not that hard. I run a hardware server for a lab and once it's running there's very little work, super reliable, and very cost effective.
That said, looking up what the hell is 'Decentraland' and how it works is to dive into a dystopian nightmare. Cutesy illustrations tell you: 'Decentraland: it's like a second rate RPG, except instead of in game currency you have to use your actual cash to participate in a tech-bro pyramid scheme where each coin has the climate impact equivalent to burning down a substantial area of rainforest'.
Blender foundation should insist on getting cash up front ;)