I think a similar thing happened to journalism ethics over the course of the 20th century up through the 1st quarter of the 21st.
The XKCD counterpoint: https://xkcd.com/915/
(I think this shows how arrogant Randall Munroe can be sometimes. He does a lot of great stuff, but when he's wrong, he's egregiously so!)
Does it include water in the mantle? (https://www.bnl.gov/newsroom/news.php?a=111648)
or other non-liquid water for that matter like hydrates (ebsom salts, etc)
https://lightsinthedark.com/wp-content/uploads/2013/06/ceres...
Deleted Comment
Misinformation. The good EVs are selling quite well. It's just that their price has effectively dropped quite a lot. My wife's Model Y which cost us nearly $80k (we bought at peak price: the prior Corolla got totalled) now has the equivalent 2024 model selling for $42k!
The crappy EVs (ie most everyone else's) aren't selling, because they are inferior in efficiency and software implementation. Rivian and Lucid vehicles are pretty good, but those companies are still at risk of never showing a profit. I've been in a Hyundai Ionic 5, and that seemed decent too.
Proof that Tesla demand is up in July 2024: https://www.youtube.com/watch?v=dHiAIZsXT1Q
We frequently break up large systems into chunks like modules, or micro-services, or subsystems. Often, these chunks' relationships are documented using diagrams on a high level (like flowcharts or state transition diagrams etc.), but are not executable.
Fixed it for you.
Fixed it for you.
Dude, if you say the flow in the diagram is not executable, blanket in any fashion, then are you saying all of the programming projects you've been in are either monolithic systems, or have all failed?
This post seems to still focus the former while an earlier HN post on Scoped Propagators https://news.ycombinator.com/item?id=40916193 showed what's possible with the latter. It specifically showed what's possible when programming with graphs.
Bret Victor might argue visualizing a program is still "drawing dead fish".
The power of visual programming is diminished if the programmer aims to produce source-code as the final medium and only use visualization on top of language. It would be much more interesting to investigate "visual first" programming where the programmer aims to author, and more importantly think, primarily in the visual medium.
The power of visual programming is diminished if the programmer aims to produce source-code as the final medium and only use visualization on top of language.
I disagree. We frequently break up large systems into chunks like modules, or micro-services, or subsystems. Often, these chunks' relationships are described using diagrams, like flowcharts or state transition diagrams, etc.
Furthermore, quite often there are zero direct code references between these chunks. Effectively, we are already organizing large systems in exactly the fashion the op is proposing. Inside each chunk, we just have code. But at a higher level viewpoint, we often have the abstraction described by a diagram. (Which is often maintained manually, separate from the repo.)
What exactly are the disadvantages here?
EDIT: Finding more evidence for convergence between scientific fields is also worthy. (Though the delta is very small at this point.)