IANAL, but wouldn't Jeremy's 50% be relative to the time he left the company? No reasonable person would assume a co-founder leaving a startup would retain 50% equity.
I also use a tiling window manager on Linux, but I think Google's decision here is based on the general public - who probably aren't ready to learn a new window management scheme. For window management, overlapping floating and resizable windows are the norm, and I think will be for some time.
That's true, but for smaller screens and only one or two apps per screen (in split screen view). I think the goal of multi-window might be to support larger display extensions (e.g. plugging a 24" display into a phone)?
Thing is that i think most are already running everything maximized (unless they are OSX users). The only things left floating are calculator and IM clients. This because the content will more often than not require the use of the majority of the screen, and they switch windows via a taskbar or similar.
BTW, i seem to recall that the original GUI design at Xerox had things tiled upon opening (they could be moved afterwards though).
Maybe people run most things maximized because window management on Windows is so limited? With 8.1 and now 10 you can arrange up to four windows on the screen without using the mouse, but even that is too basic to be useful compared to tiling window managers.
I think Google could actually pull this off by "forcing" users to use a tiling concept (like a couple of different layouts to choose from and letting you launch/drag apps into the screen areas).
I run most things maximised because, even on a Macbook retina display, I only get 1280x800 effective pixels, and that's just not enough to run more than one window at once. If I had a 5K desktop, it might be a different story. The only things I ever tile are side-by-side Finder / Terminal windows. Never see my wallpaper.
I think part of it is due to the fact that Google has greater access to a broader audience. Not everyone will search Twitter for "Donald Trump" but they will certainly search Google - so Google is providing a way for the candidates to take advantage of what is already happening probably millions of times every day.
I'd argue further that Twitter has done close to nothing to make their search a useful feature in the first place, which is why people aren't searching Twitter with "Donald Trump". If I was Twitter, this would be very worrying. All they've managed to do so far is "firehose search", which is only useful for realtime events unfolding. They probably should have been thinking about "topic search" and "person search" for a while now...
Yeah, the inability to search your Twitter feed is simply infuriating. This is an embarrassingly parallel problem, so the issue isn't scale slowing the development of Search down. Twitter just doesn't give a shit.
I think the main argument against this is the risk of running out of battery while you are using the computer. Forcing the user to stop using the mouse to charge is not very great.
That being said, I think Apple's (or Ive's) justification for the port on the bottom would come from the design issues with a front-facing port (asymmetry), and I guess for them the trade-off is worth it. It probably is for me, too.
Stool is just a benchmarking utility for comparing JavaScript snippets. For each test case you enter a name and the code you want to run.
You can definitely code in your own editor, and copy/paste the JS into the text box.
Note however the tool is not meant for large amounts of JavaScript (e.g. not for comparing entire files), but rather for comparing specific atomic implementations (comparing sort algorithms, methods of query DOM elements, etc).
https://twitter.com/awscloud/status/836656664635846656