pquki4
Joined 2 years ago
Joined 2 years ago
For a notebook/repl environment, you can create any number of intermediate steps, rerun the previous step with minor modifications and check if the results are better, rinse and repeat. For jupyter notebook specifically, you can visualize data and add markdown inline which are very useful.
You won't understand it unless you are already familiar with the workflow.
Most code in jupyter notebook is bad, but that's fine, because nobody should waste time doing that unless they must reproduce the results or they are sharing the notebook with others.
Notable example of high quality notebook: https://youtu.be/zduSFxRajkE
[0]https://www.macrumors.com/2024/04/23/apple-cuts-vision-pro-s... [1] https://www.macrumors.com/2024/04/22/apple-vision-pro-custom...
Maybe it is more about the business model. ChromeOS runs efficiently on low-cost hardware for a small license fee (?), and get almost guaranteed updates. In exchange, customers sell their souls (actually, data) to Google. Won't happrn with Linux. But undeniably it sells and works well enough for ChromeOS.
This is the real "developer" issue we are talking about.
Just to put it out there.
https://www.zdnet.com/article/log4j-chinese-regulators-suspe...
It's for the same set of reasons, and people aren't dumb.