Consider a video of an office worker smashing their keyboard in frustration and an interview about the server being constantly down. If the article and comments section focused on the clear inferiority of Logitech peripherals you would probably wonder if brand prejudice was playing a role.
Surface is getting all the heat in the article, but in the linked interview [1] he blames pretty much every part of the infrastructure other than the interface:
> The other communication systems involve the press box to the coaches on the field, and then the coach on the field, the signal caller, or the coach-to-quarterback, coach-to-signal caller system. Those fail on a regular basis.
> And again, there's a lot of equipment involved, too. There are headsets in the helmets, there's the belt pack, that communication, there's a hookup or connection to internet service or that process and so forth with the coaches and the press box. So, there are a number of pieces of equipment, there is a number of connections that are on different frequencies.
> And then during the game sometimes something happens and it has to be fixed, and first of all, you have to figure out what the problem is. Is it a battery? Is it the helmet? Is it the coaches' pack? Is it the battery on the coaches' pack? I mean you know, again, it could be one of 15 different things.
I think they're saying it's not the best way to go about asking someone for a gift of money. It's not all that cynical to be skeptical of vaguely defined goals.
If you use crouton [1] to manage chroots, you can easily run Sublime and everything else in Linux land. You should be aware of what developer mode is on Chrome OS, though, and all of the negatives that comes with it. The xiwi crouton target allows you to connect to the chroot in a popup window. You can also now launch individual applications giving an integrated experience, including copy/paste.
I ordered the LS pixel, and it was by far the nicest computer I've ever used. I used IntelliJ IDEA in a popup window with zero lag for Java development. After enabling a kernel flag, VirtualBox worked too (with several networking caveats), and thereby Docker.
Ultimately I returned it and got the entry level MBP retina for the same price. Relying on crouton for functionality, meant small stuff would break here or there, much like running Arch Linux. For example, the home, end, page up/page down shortcuts broke in xiwi windows after an update. VirtualBox would cold cut the power to the machine if I enabled bridged networking. 64 GB is exactly half the minimum hd space I need. Developer mode is not a first class citizen within the OS, so I was constantly fighting the machine to get a stable work environment. Etc.
I really really miss it though. Especially the touch screen. It felt like using my future computer today. I needed a dev machine that I could rely on, and my current situation could not justify a $1300 toy. The ecosystem is rapidly evolving, and I am certain I will eventually be using something very much like the Pixel within a couple years. Hope that helps.
You are right to not do so. Describing what is not impossible is hardly advocacy, however. There are a few uses for allowing mouse in terminal emulated emacs of varying utility. Same with the GUI version, but just to get basic mouse/wheel functionality is not one of them.