I miss from the home page a link to github and/or a description of it's license and/or some code of an actual capsule app (what backend language is used? -- I have no clue and cannot find out) and/or does this bundle Node?

While I wish your project success and like the simplicity of Sqlite; I prefer to start with Postgres. PG has many of the benefits (x-platform, free, embeddable, etc) that sqlite has, but also provides an industrial strength db in case you need to scale at some point, or want to use more complicated constructs.

One of the more prolific opensource projects, but apart from the JEP process not very open access (which is a fair choice the contributor('s employer) can make).

I'd read it.

Ubuntu is free. But Canonical is for profit. In these cases "if you are not paying for the product, you are the product" applies.

Ubuntu users will test this. Once the problems are ironed out, other distros will follow.

They certainly have design issues. For such a big brand, I dont get it... Why not make 'm look nice?

There’s a high chance that whoever is in charge thinks they look nice.

After all, someone somewhere thought the PT Cruiser was worth manufacturing.

I've never been able to get over their children's shoes branding. As a kid I felt the tv was flooded with light up sketchers ads and I can't shake that impression that they are only made for kids.

Actually you reply to a comment that makes a lot of sense.

Look into https://en.wikipedia.org/wiki/Worker_cooperative

And in Russian I believe such a company is called a "Soviet". They idea that the main part of the economy is run by this kind of organizations is one of the best parts of the USSR's attempt at communism.

Except A) he said none of that B) it's not actually relevant to what he did say.

There is a vast range of ways you can regulate a corporation and only some of them qualify as communism.

Germany has worker councils, it's still not communist.

Several European countries have much stricter regulations on how companies behave that moves them from the absolute power fiefdom internal model, guess what, still not communism.

In my last project (Kotlin; web app) I've decided against async (coroutines).

I just want to keep it simple.

Async "infects" you code: for it to bring benefits your whole codebase needs to be doing it (ingesting requests, db calls, web API calls).

Due to this we see "split" stacks in programming languages: one lib stack for synchronous, and one for async.

I did not think the benefits of better performance under load is worth the mental overhead of doing async everywhere. So i went with blocking calls and virtual threads. No regrets.

> for it to bring benefits your whole codebase needs to be doing it (ingesting requests, db calls, web API calls).

not really - the core of apps (usually no outside dependencies), and additions which solely rely onthe core, usually can be implemented without async entirely; async only comes into play once you add dependencies to file system, network and ui, but you don't need to make the core async for that. You might not call some functions in async code at all, because the function is used only for heavy computation which is best handled by dedicated threads to avoid stalling your io handling.

Whether you use async or blocking calls you’ll still want to keep IO at your edges otherwise you end up with tightly coupled spaghetti.

I thought Logo was interesting because it translated the syntax (and errors) to the language of the programmer. Thereby it removed "learning English" as a prerequisite for learning programming.

https://apps.kde.org/nl/kturtle/ (in pretty much every linux distro) also brings that benefit (though the language is not exactly a LOGO clone).

I'm sure AI corps have violated some IP laws here 'n there. Did not one guy die while he was trying to blow the whistle on this?

https://en.wikipedia.org/wiki/Suchir_Balaji

(sorry for the thinfoil hat remark)