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?
Fair point. Databricks owns a scheduling DAG (Workflows, DLT). What I meant by "owns the DAG" is the semantic DAG: model-to-model dependencies with column-level types that the compiler builds.
Workflows knows task A runs before task B. Rocky knows `dim_customer.email` flows from `raw_users.email_address` through three CTEs in `stg_customers`. Different layer, same word.
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
This is a tech site, not a news site. Threads posted here are rarely if ever "big news" nor is that the point.
The topic is an opener to discuss MitID, electronic ID's in general, the protocols behind them, what happens when they fail, privacy, societies reliance on them or something similar.
Really FAANG can stop a solar-storm? A war on infrastructure?
Remember that your website not just needs running computers but energy too, and a net that brings that information to the peoples, and those peoples devices need power too.
Just look at the Berlin outage where people had to go to hotpots with generators to load the phone:
nah, i generally agree with you on single points of failure, i just don't agree that it would go on as long as 2 weeks. 24-48 hours i can believe, but at the absolute worst case I'd also expect anyone with minimal competence to have a plan to spin things up from the latest offsite backup somewhere else. (minimal competence is a big statement though). Even redundant setups can go down altogether from a fatfinger or automation gone wrong (see almost any outage from FAANG)
> stop a solar-storm
never heard of those taking out a data center, but i'm not highly educated on that one.
> A war on infrastructure
government datacenter will be first in line for fuel, generators, etc. A destroyed gov. datacenter would be the start of much more serious things to worry about.
> Just look at the Berlin outage where people had to go to hotpots
yeah, this one _is_ a little embarassing, but people who have to go to hotspots != datacenters
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?
