Quote from the talk: I don't want to make it sound like the sky is falling. This was found on one very esoteric processor that is not used in widespread production. I think it's mostly interesting from an academic perspective that we have a tool that is able to find these kinds of things now.
For the uninitiated, consequences include (for instance) not being able to use custom ROMs (such as CyanogenMod), as long as you wish to use any app that utilizes SafetyNet. Banking apps, Snapchat, Pokemon Go etc. (it's getting more and more widespread)
> You are not going to have room size experience with any of those headsets at home at least it's not feasible you are tethered with so much crap that you need a man servant walking after you ensuring that you don't hang yourself on that tether.
Depends on the size of your play area obviously, but looks pretty good from this[0], and this "crap" you're talking about doesn't seem very bothersome.
> If you want a room size experience just hook up 2 OR cameras it will work the same way (but better) as the lighthouse approach that HTC took, and you can hook upto 50 of those cameras currently to track I believe up-to a 100 players.
Better how? I haven't seen a good comparison of them yet. I'm curious tho, how do you intend to scale up to 100 players using USB3 connections? That would be a MASSIVE amount of data flowing through the computer powering all of this(, the reason it requires USB3 is because it needs 60Hz high resolution image to have good tracking). The Vive takes a completly different approach by having the headset (and controllers) catch and interpret the (infrared) light emitted by the (dumb) lighthouses.[1]
> you can't currently track more than 5 people at the time
Do you have a source for this? I can't seem to find anything about this. Is it a limitation of the hardware or the software?
> Vive only supports 2 trackers per space it's also going to have issues with commercial applications that aren't a single open room.
I'd be very surprised if this was true. Everything I've read seems to indicate lighthouse is built to be scalable from the ground up. The whole idea of it being wireless, only requiring a power outlet, makes it infinitely more scalable than any USB3 solution.
Again, would appreciate sources for any of your claims because I can't seem to find any of them...
Really what makes the Vive the superior option (in my eyes) is that you can have both a seated experience and a roomscale experience. A roomscale experience also removes any "VR sickness" because all your movements translate 1:1 with the virtual world, so anyone who struggle with movement while being seated won't have the same issues with the Vive headset (in roomscale VR).
If you have tried VR, you will realize that one of the first thing people do, is try to look at their hands, only to be disappointed as they can't be seen. The Vive makes this possible on day 1. (Obviously not a 1:1 mapping of your hands, you'd need something like the Leap Motion Orion[0] for that.)
Most everyone who has tried the Vive have not found the wires to be a problem. Also what you say about seeing the cord in VR is not true, there is however something Valve calls the Chaperone[1] system which activates the camera when you are too close to the edges of your play area. The picture has a bluish tint, because the resolution of the camera is sub-par, so this is a cool workaround. It also prevents you from going around "worrying" that you will break something outside of VR, because as long as the system doesn't warn you about anything: You are good to do whatever you want in VR.
Hm, I'm curious why this wasn't caught by the HN anti-duplicate. Previously when I've (obliviously) posted an already posted URL, I've been redirected to the comments of the pre-existing URL. The URLs are literally exactly the same.
For me, vertical space IS at a premium. Especially when browsing the web. How many web pages do you see utilizing the full width of the monitor? Very few, which is also the reason I choose to dock my developer console to the right instead of the bottom. This also doubles as an easy way to resize the viewport when testing responsive design/media queries without resizing the entire window.
In the comments so far, there seems to be some confusion on what this is. The Chrome Sidebar API is an API for Chrome extensions, adding a sidebar surface to Chrome.
The proposed API allows Chrome extensions to access and control a sidebar panel - a per-tab split-pane HTML container to the right (to the left in RTL environment) of the main page content with the ability to resize horizontally.[1]
In short, it provides extensions an alternative to using popups or injecting HTML directly into web pages in order to display something to the user.
With it, you could for instance (re-)implement something like the old Side Tabs feature, which was removed from Chrome because the complexity of a tree-style interface in terms of usage is beyond what most users need or want, and in terms of implementation is more than passes the cost/benefit test for building into Chrome natively as an option.[2]
I've been using this service for a while already, mostly for demoing answers on StackOverflow and/or testing out new languages without having to install anything locally. Although the site is very handy, I find some of its design choices a bit peculiar.
1. Saving after editing someone elses snippet (effectively creating a fork/clone)
> I can run the code after I change it, but I can't save it? This is what I miss most from other "pastebins".
2. Save indicator
> I don't see any indicator of whether or not the snippet has been edited/saved.
3. Secret snippets
> Why can only logged in users store "secret" snippets? Secret snippets are still accessible by anyone with the URL, so why shouldn't an anonymous user be able to save them? I'd imagine a concept of "private" snippets would make more sense to restrict for logged in users.
4. Code language versioning
> Currently, there is only one version, "latest" of each language available (except Python, JavaScript and PHP). I assume the version support lists will improve eventually, but it would be nice to know what this "latest" refers to, and a bit more accurate versioning in general.
5. No URL immediately visible after saving a snippet
> OK, I need to grab it from the address bar, but this may not be immediately obvious for everyone.
6. Username
> What is it used for? I can't log in using my username, and in the "Snippets" table, I'm listed with my name instead of my username.
7. E-mail address
> I can't change it?
Other than that, props on creating, providing and maintaining a great service!
Tabs Outliner[1] is great for this. It's lacking sync (an extra top layer in the tree for each device would make sense), but other than that, it is fantastic, and has really reduced my memory usage back to normal levels. It allows you to suspend entire windows, and quickly browse all tabs. Allows for unlimited* levels of named trees/notes/windows/tabs. It does however NOT save the state of the page, only the URL.
When the Chrome Sidebar API[2] is implemented, I'm sure it will only get better, as the need for an extra window should no longer be necessary.
Smart TVs being a good idea, all depends on who you are.
It's good for TV manufacturers, because old TVs get older faster (outdated processor / software and so on).
For consumers however, having a separate box for the "smart" part of your TV is much better, because it makes it easier to upgrade.
Personally, I prefer the dumbest possible TV. Most of the time, I don't need a new panel, all I need is an upgrade of whatever smartbox I'm using at the moment. So far my Chromecast is carrying me quite well. The biggest upgrade of my TV I'll be doing in the near future will be an upgrade to 4K and/or maybe OLED down the line.
