Software engineering is not engineering. No need to pretend that it should be. We dont rebuild a bridge 3 times before we get it right, but in SE thats a pretty good approach
Theoretically correct, but worse is better - consider how many things we could have asked of C or javascript before they become standards.. Practically, a spec is something to prioritise alongside all the other things we wish for
The entire language is single thread. But I/O uses a separate thread pool.
> memory usage
Are you talking about extra 120 bytes per Promise?
> function coloring
How does it manifest in JS? You can `await` non-async function without any issues, anything potentially async is awaited, if it doesn't end up doing async inside there is no problem.
Six months of darkness is a bit hyperbolic, to say the least. The sunshine, temperature and daylight situation in Denmark is on the whole comparable to what you'd find in Germany, the UK, and Northern France.
Also, long winters? You're thinking about Canada. The daily mean temperature in Aarhus, Denmark in January (the coldest month) is 1.3 C (34.3 F). https://en.wikipedia.org/wiki/Aarhus#Climate.
By comparison, Montreal, Canada has a daily mean temperature in January of -9.2 C (15.4 F).
it is not strange that these systems don’t do incremental compiles? Things are literally paged.. Why does newer systems such as typst do full compiles when a single page is edited? I know that all subsequent pages might be affected, but surely, one could workaround this by allowing sloppy but fast compile options for subsequent pages, that sacrifices correct layout for something decent?
But that doesn’t make much sense - by your account Latex would also be a mix of closed and open source, since closed source web apps exists for writing Latex.
What does not make sense? Did you mean to answer to someone else? I only stated that Typst (the typesetting engine) is free to use and modify, and only the web app is closed source. Typst can be used without touching any web apps. I use Typst locally.
I made no claims about any mixes or claims about LaTeX.
This stack appears to be a solid choice for building generic CRUD applications, regardless of immediate ISO certification needs. Would it be feasible to package this as a ready-to-use solution for greenfield projects that may pursue ISO certification in the future? Which components would still require manual setup, and why?
Yes, web apps all need logging, performance dashboard, redundancy, DB backups and such.
This could be a stack that could be parametrised with sound defaults just requiring some terraform provider credentials as well as a path to an executable web app and a choice of database engine.
ISO readiness built-in and abstracted at the OS level rather than programming language level.
If anyone wants to "assetize" what I built, reach out at jk@datapult.dk. I bring a battle-tested setup that has been ISO certified by independent auditors.
You bring clients directly or indirectly with marketing/growth hacking mindset.
I looked at Kamal, Dokku, and CapRover — all great tools if you want to abstract away server management. But for a HIPAA/ISO 27001 certifiable app, I need a higher level of control and auditability across the entire stack.
With Ansible, I can version everything — from server hardening to DB backups — and ensure idempotent, transparent provisioning. I don’t have to reverse-engineer how a PaaS layer configures things under the hood, or worry about opaque defaults that might not meet compliance requirements.
There's nothing wrong with these tools, but once you're in the mood for the ISO certification, and once you start doing these things yourself, they actually seem like a step backwards or add very little value.
I also prefer running my own DB backups rather than relying on magic snapshots — it's easier to integrate with encrypted offsite storage and disaster recovery policies that align with ISO requirements. This lets me lock down the environment exactly as needed, with no surprise moving parts.
Tools like Kamal/Dokku/CapRover shine for fast, developer-friendly deploys, but for regulated workloads, I’ll take boring, explicit, and auditable any day.
Interesting point about db recovery: I guess your db is small enough that you can do multiple full backups without issue? Or do you backup the WAL only?
