mollerhoj

"I think the author is saying" - Wait, are you not the author? This seems dishonest.

This seems like a strange combination of proposals:

1) PUT, PATCH, and DELETE methods: Logical and obvious extension, no extra syntax, but easy to get around today by just using POST for everything.

2) Buttons actions without forms: Just syntax nicety to avoid a single form tag, unconsequential and just adds implementation complexity.

3) Partial page replacement: Would completely revolutionize js-free html capabilities, but the draft is unfinished..

It would seem to me that the author should have just made the thrid proposal, and not wrapped it in a project of two much less consequential proposals?

the execution model of cargo-nextest makes my test suite extremely slow to run - Most of my tests rely on postgres. Since cargo-nextest uses a separate process per test, there is no efficient way to share the connection pool.

"feels like using a 30years old database"

Its a bit confusing to claim that "The things your current stack can't give you because it doesn't own the DAG" and use DataBricks as your example: DataBricks includes jobs and pipelines, so it very much owns the DAG, no?

this is not big news in dk, it will be up again soon - i dont know of any mitid services that are life-or-death enough to have people panicing about an hours downtime

nuts are ultra processed?

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

I prefer the Danish term: Datalogi

single threaded, memory requirements, function coloring

Our long winters + free education sure doesn't hurt either - what better way to spend the yearly 6 months of darkness than working on a new proglang?

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?

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?