jeeyoungk

http://ccr.sigcomm.org/online/files/p83-keshavA.pdf - this paper is actually pretty insightful.

There are some dangerous thoughts in this thread, for example: https://lists.w3.org/Archives/Public/public-whatwg-archive/2...

"These javascript frameworks are all trying to do this, but none of them do it easily and they’re always being redesigned."

Things are being redesigned because there are flaws and limitations. Making something, and stamping it as "HTML6" doesn't automatically make it perfect. It would simply hinder the development further.

This is an interesting categorization - somewhat like adding an axis to the political compass. Thanks.

Thank you everybody for your valuable comment. Like I've said in the post, this was my first attempt to explain my passion. I read every one of your comments, and spent the next few days fully understanding their implications.

This post is a bit biased towards what I've interacted with. I think I do have a good sample of various workflow, but there are obviously large number of databases and use cases that I'm missing, and my view of what is "modern" may not incorporate a lot of bleeding edge theory and technologies.

Operational complexity is definitely my #1 concern. The service I originally maintained is a OLTP system, located at the top of the service & data dependency graph. Availability is the top concern.

The current system I'm writing is metrics database. The operational burden is much lighter. It is almost a leaf node in the service & data dependency graph, and I can take downtime to restart the cluster. A very different workflow, indeed.

Thanks!

I use this all the time, except I don't like some of the syntaxes that it generates. I tend to avoid

    EXPR if COND
    EXPR unless COND

type of code, because the order of execution isn't very clear.