VeeSilverball

Some of my own thoughts, which rebut the article in parts:

1. Godot does have "barbell performance" - you can make it go fast if you drop to C++ and do low-level engine things to add new nodes, resources, etc. You can also make it go fast when you use the premade nodes without a great deal of script in between(and the nodes are, FWIW, pretty flexible and composable). What it doesn't do at present is the thing Unity users are used to, which is "fast scripting". Fast scripting still means working around the garbage collector and the overheads of going between native and a runtime. C# is a kind of flytrap for the needs of high-end games, and Unity has only seemingly surmounted the issues by doing a lot of custom engineering for their use-case. That is, you don't really code standard C# in Unity, you code Unity's C#, which is nearly as bespoken as GDScript.
2. Saying the engine is coded in a naive way is actually not as smart as it seems, because there's a maintenance cost to always doing things in exactly the most optimal way. The target for what is fastest changes every time the platform changes. As a (up until recently) relatively small project, it's overall better that the engine stay relatively easy to build and straightforward to modify, which is what it's done. The path it's taken has helped it stay "lightweight". The price of that is that sometimes it doesn't even take low-hanging fruit that would be a win for 90% of users.
3. The 3D in Godot 4 is capable of good test scenes, but everyone seems to agree that it's not really ready for production for speed reasons. Any specific point on this just backs that up. And that's disappointing in one sense, but pretty okay in others. If you need high-end graphics, Unreal will welcome you for the time being.
4. On that note, developing for console always comes with fussy limitations, at minimum just meeting TRC/TCR/lot check; that's why professional porting is a thing. Engine devs usually end up in the position of maintaining these multiple-API abstractions because it's necessary for porting. It's the same deal with the audio code, the persistent storage, the controllers, the system prompts, it just goes on and on like that. So, rewriting the rendering bindings to do things in the D3D way and not the Vulkan way is actually a bit of a whatever; it's more rendering code. It changes some assumptions about what binds to what. But it accesses the same kind of hardware, running the same kind of shaders. A lot of ports in the not-so-distant past basically had to start over because the graphics hardware lacked such a common denominator.

The author's bio says that they have been doing this as a professional for about 5 years, which, face value, actually means that they haven't seen the kinds of transitions that have taken place in the past and how widely game scope can vary. The way Godot does things has some wisdom-of-age in it, and even in its years as a proprietary engine(which you can learn something of by looking at Juan's Mobygames credits the games it was shipping were aiming for the bottom of the market in scope and hardware spec: a PSP game, a Wii game, an Android game. The luxury of small scope is that you never end up in a place where optimization is some broad problem that needs to be solved globally; it's always one specific thing that needs to be fast. Optimizing for something bigger needs production scenes to provide profiling data. It's not something you want to approach by saying "I know what the best practice is" and immediately architecting for based on a shot in the dark. Being in a space where your engine just does the simple thing every time instead means it's easy to make the changes needed to ship.

The game has already consumed over 40 hours of my time, and I've got plenty more campaign to go. It does just about all the stuff I wanted JA2 to have to make it play faster - combat is faster, looting is faster, inventory is faster. It has a few things that look like X-COM, but it still mostly plays like JA. The early game is the roughest part but things definitely shaped up once I had a team with size, experience and gear.

And the campaign is detailed with a few surprises and plenty of side quests - it does some things to pull the rug on you, which is rude, but rewarding if you play along and accept a few losses(or carefully savescum and go out of your way to avoid triggering timed quests).

Arch is always "latest and greatest" for every package, including the kernel. It lets you tinker, and it's always up to date. However, a rolling release introduces more ways to break your system - things start conflicting under the hood in ways that you weren't aware of, configurations that worked don't any longer, etc.

This is in contrast to everything built on Debian, which Mint is one example of - Mint adds a bunch of conveniences on top, but the underlying "how it all fits together" is still Debian. What Debian does is to set a target for stable releases and ship a complete set of known-stable packages. This makes it great for set and forget uses, servers that you want to just work and such. And it was very important back in the 90's when it was hard to get Internet connectivity. But it also means that it stays behind the curve with application software releases, by periods of months to a year+. And the original workaround to that is "just add this other package repository" which, like Arch, can eventually break your system by accident.

But neither disadvantage is as much of a problem now as it used to be. More of the software is relatively stable, and the stuff you need to have the absolute latest for, you can often find as a flatpak, snap, or appimage - formats that are more self-contained and don't rely on the dependencies that you have installed, just "download and run."

Most popular distros now are Arch or Debian flavored - same system, different veneer. Debian itself has become a better option for desktop in recent years just because of improvements to the installer.

I've been using Solus 4.4 lately, which has its own rolling-release package system. Less software, but the experience is tightly designed for desktop, and doesn't push me to open terminals to do things like the more classical Unix designs that guide Arch and Debian. The problem both of those face as desktops is that they assume up-front that you may only have a terminal, so the "correct way" of doing everything tends to start and end with the terminal, and the desktop is kind of glued on and works for some things but not others.

My principle of "blockchain's fundamental value" is simply this: A blockchain that secures valuable information is valuable.

To break that down further:

• "Valuable information" isn't data - it's something that you can interpret, that has meaning and power to affect your actions. So, price speculation taking place on a chain isn't that valuable in a broad, utilitarian sense, but something like encyclopedic knowledge, historical records, and the like might be. The sense of "this is real" vs "this is Monopoly money" is related to the information quality.
• "Secures" means that we have some idea of where the information came from, who can access it, and whether it's been altered or tampered. Most blockchains follow the Bitcoin model and are fully public ledgers, storing everything - and just within that model(leaving aside Monero etc.) there are positive applications, but "automatically secure" is all dependent on what application you're aiming for.

You don't need to include tokens, trading, finance, or the specific method of security, to arrive at this idea of what a blockchain does, but having them involved addresses - though maybe without concretely solving - the question of paying upkeep costs, a problem that has always dogged open, distributed projects in the past. If the whole chain becomes more valuable because one person contributes something to it, then you have a positive feedback loop in which a culture of remixing and tipping is good. It tends to get undercut by "what if I made scam tokens and bribed an exchange to list them", the maxi- "we will rule the world" cultures of Bitcoin and Ethereum, or the cynical "VC-backed corporate blockchains", but the public alt chains that are a bit out of the spotlight with longer histories, stuff like Tezos and NEM/Symbol, tend to have a more visible sense of purpose in this direction - they need to make a myth about themselves, and the myth turns into information by chance and persistence.

What tends to break people's brains - both the maxis, and people who are rabidly anti-crypto - is that securing on-chain value in this way also isn't a case of "public" vs "private" goods. It's more akin to "commons" vs "enclosed" spaces, which is an older notion that hasn't been felt in our political lives in centuries, because the partnership of nation-states and capital has been so strong as a societal coordinating force - the state says where the capital should go, the people that follow that lead and build out an empire get rewarded. The commons is, in essence, the voice in the back of your mind asking, "Why are you in the rat race? Do you really need an empire?" And this technology is stating that, clearly and patiently: making a common space better is another way to live.

And so there is a huge amount of spam around "ownership", but ownership itself isn't really a factor. That's just another kind of information that the technology is geared towards storing. The social contract is more along the lines that if you are doing good for a chain and taking few risks, a modest, livable amount of credit is likely to flow to you in time. Everyone making "plays" and getting burned is trying to gamble with it, or to advance empire-building goals in a basically hostile environment that will patch you out of the flow of information.

To me, a big difference is in the lengthy prelude, which follows the model of TOS, just with an updated production. First the synths layered with strings, which are very 80's wonder-music(it could be right out of the score for Flight of the Navigator or The Goonies) and then the french horns come in playing a round, which adds a Wagnerian element.

The percussive "march music" elements quoting TMP are subdued in TNG's arrangement - it's a less compressed, "punchy" sound, and I believe the mic has been set farther back or they've EQ'd out some higher frequencies. Those decisions, plus a few choices of instrumentation like the harp glissandos, tone down the bombastic energy and add a gliding, romantic quality. Again, more like TOS, but updated.

My favorite example of "weird camera" is Journey to the Planets. It's an Atari 800 game with graphics that are more 2600-esque. It's mostly side view, but the proportions are abstract, like a child's drawing: the spaceship is about 1/3rd the size of the player sprite, but then as you lift off it shows zoomed out terrain and the sprite is the same size. The game is based around solving adventure game puzzles with objects that are mostly just glowing rectangles, but your way of interacting with the puzzles involves a lot of shooting. Even though there's so little detail, every room feels "hand-crafted".

I'm pretty sure the game permanently altered my sense of aesthetics.

I've become comfortable with saying, "it's not worth it being normal", and thus am ok with the normie tag, even if I don't want to turn it into a slur. Normal is a form of social construct that tends to be imposed on us: it's when the teacher enters the classroom and the class sits down and shuts up, not because they explicitly agreed to, but because it was normalized. There isn't anything in particular suggesting that normal = good.

And that does have an elitist ring to it, which does upset the goal of equitable outcomes in some ways. There are certain philosophies in which a premise of elitism is assumed, as in, some people just won't be able to access the necessary understanding to participate, so it's better to have a gate than to let anyone wander through. This is the view of Leo Strauss and followers - for a really detailed explanation try Arthur Melzer's book Philosophy Between the Lines.

Even if you don't read that book(it's a good book), I would make the case in this way: it's the difference between online gaming that uses automatic matchmaking, versus a martial arts dojo. Online gaming and toxicity correlate because there is no lower bar on who can play, so all sessions are pushed to the lowest common denominator of cheating, griefing, etc. But someone who participates in martial arts like a gamer gets kicked out of the gym, if the standards are high: an instructor who values students does not let them attempt to eyegouge each other or slam their head on the mat.

Occasionally someone like that will sign up for a tournament, commit an illegal move in the first round, and get themselves disqualified. But they can leave their opponent seriously injured in the process, and maybe end a career. So the standards tend to condition a degree of gatekeeping, respect for others, etc. Not every gym does well at this, and some styles like boxing have a norm of "hard sparring" where full-contact is trained and damage is expected. But predominantly the focus is on getting the techniques and training without destroying yourself or others.

And I do liken the idea of complete access to, essentially, allowing dirty street brawls to be the only kind of sparring, the only way in which you can interact online with strangers.

Martial artists also sometimes use the normie term. They will say it outright: you have to be a weirdo to spend so much time getting beat up and choked out. We can have a gate and still be tough on ourselves to do better.

Eugen is not the person I would trust for good judgment on this because his agenda has always been user growth-centric, so a Fediverse that resembles Facebook would just be a "yay" moment for him - either way he can still end up with a career by leveraging his role with ActivityPub.

That said, I don't believe EEE works here, because AP evolved in an environment that already had to compete like-for-like with corporate options. You'll still log in for the rest of the fediverse if it brings you better content than Threads...

...and it has an edge on that, because these spaces are not designed around herding around industrial quantities of users. They have a natural size at which moderators shrug and close the gates if a big instance is too troublesome, because it hurts the quality of the experience for their own users. This peeves instance admins who want the power fantasy of "owning" a lot of low-quality users, but it also basically guarantees defederation with corporate social, because it's never been able to handle its own moderation problem other than in a "pass-the-buck" way.

The Market street tram line runs a variety of vintage cars from various different places and eras. It's a kind of "living museum" piece that complements the better-known cable cars.

I have no plans to support p92 precisely because it's going to "push" users together as a commodity. What Meta has jurisdiction over is not its communities but rows of data - in the same way that Reddit's admins have conflicted with its mods, it is inherently not organized in such a way that it can properly represent any specific community or their actions.

So the cost-benefit from the side of extant fedi is very poor: it won't operate in a standard way, because it can't, and the quality of each additional user won't be particularly worth the pain - most of them will just be confused by being presented with a new space, and if the nature of it is hidden from them it will become an endless misunderstanding.

If a community using a siloed platform wants to federate, that should be a self-determined thing and they should front the effort to remain on a similar footing to other federated communities. The idea that either side here inherently wants to connect and just "needs a helping hand" is just wrong.

I believe there is a healthy relationship between instances and magazines, actually: the way in which topical forums tend to be "hive-mindy" fits well with Fediverse instance culture. The difference is that instead of Reddit-scaling leading in the direction of "locking down" topical discussion to be a bureaucratic game of dancing around every rule, because all users are homogenous - just a name, a score, and a post history - you can have "this board is primarily about this" but then allow in a dose of chaos, affording some privilege to the instance users who already have a set of norms and values in mind and pushing federated comments out of view as needed, where you know the userbases are destined to get into unproductive fights.

This also combats common influencer strategies applying bots and sockpuppeting, because you've already built in the premise of an elite space.

There's work needed on the moderation technology of #threadiverse software to achieve this kind of vision, but it's something that will definitely be learned as we go along.

I find that what is needed depends on the task. Mostly, it's about whether you need to switch views on information frequently. If you're working in a maximally focused way you already have the right info, so you don't have to make the view more diverse.

Two monitors can be really helpful if you're in a situation where you need one view to always stay the same(e.g. reading one document while editing another) and the editing app is some fussy internal thing that always wants to be on the first window when started, but I also haven't had that setup in quite a few years. Tiling can get you 80% of that if the screen is sufficiently large and the software cooperates.

When in Windows I stick to using the Win + arrow keys shortcuts to tile; in Linux I've used a few different WMs over the years but lately have been using Ubuntu defaults and basically working with it like Windows.

There is a lot of utility from not relying on screens and using a small gridded or ruled notebook with a spiral binding as the second screen. Mark it up with color multipens and sticky notes, and take it around in your jacket pocket or a belt bag.