Re:Systems Past: The software innovations we actually use
by pdonis on Friday March 14, 2014 @11:56PM
(#7403430)
If this writer is so convinced that we need a new way of interacting with computers, why isn't he building it, instead of just writing about it?
[ Parent
| on HN ]
Re:Systems Past: The software innovations we actually use
by TheZenPsycho on Saturday March 15, 2014 @12:04AM
(#7403451)
Because software actually is kind of hard, and to get anywhere you need to convince a somewhat larger group than one to all work towards the same goal.
And how do you know he is not?
Re:Systems Past: The software innovations we actually use
by davidad_ on Saturday March 15, 2014 @12:39AM
(#7403546)
Yes. I am working on it, but it is "kind of hard" to do by oneself. Also, writing about it is a good step, regardless of who might be convinced or not, simply because it forces me to get my ideas more straightened out.
Re:Systems Past: The software innovations we actually use
by andrewflnr on Saturday March 15, 2014 @02:05AM
(#7403772)
I'm quite curious where you intend to go with the "mesh" project on Github. "An operating system with the heart of a database" sounds like some of my ideas, as does your doc/index.md, but it seems to stop there.
Re:Systems Past: The software innovations we actually use
by pdonis on Saturday March 15, 2014 @12:13PM
(#7404996)
I am working on it
I don't see that mentioned in the article; a mention or a least a link to your own work would be helpful.
Re:Systems Past: The software innovations we actually use
by pdonis on Saturday March 15, 2014 @12:15PM
(#7405003)
to get anywhere you need to convince a somewhat larger group than one to all work towards the same goal
I don't think this is true. For example, Linus Torvalds didn't convince a larger group to work on Linux first, and then build it; he built Linux first and then the larger group came to it because they saw that it was worth working on.
Granted, Linux was not as ambitious as the kind of thing the article is talking about; but that doesn't mean the method has to be different. Working code, even if it's for a very small subset of what you eventually want to build, is a great convincer.