There is a professor Jiri Demel in Prague with Czech Technical University with a book "Graphs and their applications". Is this in any way a tribute to him? He is very wholesome guy that tought me graphs :).
Isn't this upriver/downriver/elevation terminology just a fancy/ignorant way of saying "topological ordering"?
show comments
0xbadcafebee
Every time somebody tries to make a super-simplistic ASCII file format to make raw data "easy for humans", it either ends up sucking for humans, or sucking for computers, or both. I get it, the programmer is lazy, so the programmer finds a way to do something they find easier. But that's what gave us YAML and Markdown - the former setting us back in both data serialization and configuration formats, the latter setting us back in document formatting and layout.
It's 2025. Enough with the ASCII. As a human, if I want to map out and display a DAG, I don't want to do it in a text file. Give me a UI or give me death.
There is a professor Jiri Demel in Prague with Czech Technical University with a book "Graphs and their applications". Is this in any way a tribute to him? He is very wholesome guy that tought me graphs :).
edit: link https://kix.fsv.cvut.cz/~demel/grafy/
Isn't this upriver/downriver/elevation terminology just a fancy/ignorant way of saying "topological ordering"?
Every time somebody tries to make a super-simplistic ASCII file format to make raw data "easy for humans", it either ends up sucking for humans, or sucking for computers, or both. I get it, the programmer is lazy, so the programmer finds a way to do something they find easier. But that's what gave us YAML and Markdown - the former setting us back in both data serialization and configuration formats, the latter setting us back in document formatting and layout.
It's 2025. Enough with the ASCII. As a human, if I want to map out and display a DAG, I don't want to do it in a text file. Give me a UI or give me death.