72 karma · joined October 20, 2015
The first is the consideration of running this on current hardware. Obviously Neo is meant to be run on hardware designed for these interactions (as shown with the voice key on the keyboard and the gaze tracking camera) but I'd like more detail on how this could run on systems that do not have this hardware.
The second is in professional applications. I did not see any screenshots that deal with Photoshop or Final Cut Pro or After Effects or Solidworks or really any of the crucially important applications for the desktop. These are exactly what keep the desktop around, and what keep people from accepting Metro.
It'd be great if we could solve these two issues, or at least discuss them. I think these ideas are really great and the presentation was amazing. I'm seriously impressed, but it's a little held back from widespread adoption until we can figure a few things out.
P.S. Also I'd like to be able to split my terminal windows horizontally please :)
I'd love to see a screencast or some screenshots.
1. Press `Escape` key
2. ":q!"
Jokes aside, text files are a wonderful medium. Not everything can be expressed easily as text, but I highly recommend using it to everybody for whatever can. Emacs may not be the best tool for less technologically literate individuals (for this Atom or Sublime Text are very good), but the format is certainly very useful. I think people should look into using the command line more, as it can be much more productive after a period of learning.React Native just keeps getting bigger and bigger. I can't believe what has been accomplished with this tool, and it's amazing to think what the future of it might be.
Will definitely use this as soon as they open their doors to me.
I think what you've got here for an OS X implementation is pretty good, but I can still tell that it isn't really native, and if an OS update changes anything in regard to the standard UI components forget about it.
Why not design and develop your own UI? That way you can control how it is supposed to work given the drawbacks and advantages of web technologies and not have to ask the user for forgiveness of minor quirks in your reimplementation.
Furthermore I can't stand when I have to setup all of my accounts across the multitude of devices that I own. Way too many settings to configure regarding ports, domain names, encryption techniques, folder mappings, etc.
Don't get me wrong, I'm super impressed that email has managed to continue to be an essential tool in many people's day to day workflow despite being old enough to be found in a museum. But it's time for a change, and for us to put all we've learned about encryption, data serialization, and user workflow out on the table to design a better future for the universal method of digital asynchronous threaded communication.
And if we've learned anything from Google Wave and friends, these changes have to make sense, and not stray too far from what we're already familiar with and know that works.
Anyone want to weigh in?