@d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df@alex@strongerthanyou Yeah, this is an artifact of journalists having no idea what they are talking about when they talk about technology. They don't understand that Poast is not Soapbox, and that Truth Social has a similar relationship to Soapbox as it has with Mastodon. Yet guilt-by-association only goes in one direction. If they are going to slander us by associating us with Trump, they should at least have the courtesy to do the same to Gargron and the mastogroomers.
@ahmad@alex This might be a hot take, but we should have forked mastodon instead of pleroma. We would have had the ability to start with a saner database design, too.
Nationalism is a very simple ideology at its core. We share a group identity and we believe that the interests of that group identity are more important than the interests of any of our individual identities. This is the framework that we use to judge policy: who it benefits, not whether the policy itself adheres to ideological principals. This is also not a statement that the individual doesn't exist: we also believe that you can't really have a strong individual identity without also being a part of a strong collective to back you up. And lastly, we believe that our state should be organized to advance our nation's interests.
@n3f_X@RahowasaurusRex1979@nozaki@bot@animeirl@unabomber But even with all of this information, the most important part of this is that the overwhelming super-majority of White people did NOT own slaves and had NOTHING to do with slavery. In fact, slavery HURT normal White people by hurting the power of labor. The civil war was fought on both sides by financial interests that wanted to use nigger labor to suppress White workers.
@alex I generally don't even look at SO because its full of bad takes.
Making it possible to do turn an async operation into a sync operation would become a really easy way for developers to do the wrong thing, and potentially block the main thread with a long running operation. The web specs are designed defensively for an environment where there are lots of 3rd party scripts on most pages, each with the ability to theoretically break things. It may suck for some things, but giving developers an easy way to do the wrong thing guarantees that people will do the wrong thing. We want more things to be async, not less.
We can't just make every function asynchronous and get rid of async/await all together because we still need to have a Promise primitive to get any benefits from it. You couldn't do something like this if everything were automatically await'ed:
var taskA = heavyTask1(); // starts A var taskB = heavyTask2(); // starts B in parallel with A
var resultA = await taskA; var resultB = await taskB; // OR var [resultA, resultB] = await Promise.all([taskA, taskB])
If taskA encounters a network request, it can run taskB while it waits for the result and then switch back to taskA.
@alex According to this article, WebCrypto heavily uses async operations because they can be slow (out of necessity), and they don't want to block rendering or input.