Omitting the human history of a field does not automatically make it easier.

I'd also recommend getting used to serialisation/deserialisation. Serde for Rust makes this remarkably easy. Writing every setting to a file is simple if the compiler can do it for you, rather than you walking the long way around.

Isn't that literally the link above?

Instead of just cutting out the middle bit of getting a PhD, becoming a professor, setting up a research lab, and mentoring students for decades, and leaping straight to "make a startup from an idea that works", every single person decided to go the hard road because it seems proper?

Your cargo cult idea works - he's arranged all the trappings of being an influential theorist - funding and research labs and media coverage - except perhaps for the one thing that lets him fly: a worthwhile idea.

If I go to a meeting I take notes with pen and paper and transfer them in elaborated form when I return. Good note taking is a skill, though!

I dabbled with an ultra quick template (F12 to write a single line in a mega list with a date stamp at the front of each item, no options, no slowdown). I found the discipline of taking slow notes at the end of every task or day much better than effectively tweeting my day to my future self.

One thing that I've found difficult is having task/project journals that work easily into this flow. Tags help but I found I was duplicating everything in changelogs.

There's also a trickier problem in your simple binary flag: papers can have incorrect proofs of correct statements.

I'd love to see a Semantic Web approach where you don't cite papers but results in papers. So while a result in a paper might be wrong, you don't have to throw out all the results in all the papers citing this paper.

Many other companies are mature enough to show their cards but Apple keeps declaring victory. Apple writes its own narrative instead of participating.

There are mature ways for this to shake out and they don't include your strawman dichotomy.

You can't set an expiry date on a password. You can't change a password if it's compromised. You don't know when a master password was created so you can change it. If you change your master password you have to change every password you care about. You can't introduce new entropy. You have to manually specify a keyword scheme (and presumably store it yourself). You can't store metadata in case the website decides it's changed from usernames to email addresses and you've forgotten which one you used for what. You can't change the master password independently of the individual passwords.

In actual password management, this program makes you specify, store and organize it all yourself. And without significantly more security than a traditional password manager like Keepass.

It seems a bit cocky to call it "Visionary".

For example, org-babel allows you easy access to any language you have support for in emacs. Same syntax highlighting, same behaviour, same utilities. Improve any of that and org-mode takes advantage of it for basically zero cost.

Except that it is. This is not a discussion about self-driving cars because they don't work that way and are a long way off potentially working this way.

This is the age-old trolley problem (http://en.wikipedia.org/wiki/Trolley_problem), which was never really satisfying as a philosophical problem. You create contrived examples and try to transport that situation to a wider world.

The trolley problem seems to be popular for self-driving cars because it's easy to create horrible situations without engaging with the way the technology actually works. Moreover, you can make the decisions for the computer to fit the situation without having to think about how that'd apply generally.

Or at least, if you're going to do it, go the whole hog: http://www.mindspring.com/~mfpatton/Tissues.htm