No word wrap, horizontal scroll is hijacked and the content goes off screen (Chrome on Android) the topic sounds interesting but the post is unreadable
Lindybeige is a fantastic explainer when it comes to that sort of thing - it also highlights how quickly a person can go from knowing nothing to practically hobbyist levels of knowledge in 20 minutes post internet
Scott Adams - creator of Dilbert - was recently ridiculed for suggesting that someone could become an expert on a topic after an hour of talking with the brightest minds in that field. While "expert" needs to be defined, I don't think it's far fetched.
How many times have we had that conversation with someone who knows their topic backwards and forwards and after minutes, we have a deeper understanding of it than almost anyone around. Expand that out to an hour with a few key/relevant questions to frame the conversation and it is totally believable.
I recently attended a lecture by Hadley Wickham on his latest tools built for R. It was both edifying and deeply saddening. I learned a great deal about R in a short time from (IMHO) one of the masters, and I realized that if Haldey is typical of a Rice University professor I should have challenged myself to get a better education than I did.
Chrome has had more than one JavaScript engine. They're all still Chrome to the user, and that's all that really matters. If they decide to rewrite the UI in Lisp and use Servo, it will still be Chrome in the ways that count, just like nobody cares if a game has DirectX and OpenGL versions.
Different HMDs are arguably more similar than different GPUs, and they manage to support the same software, but in the early days there were plenty of Glide-only games. That didn't work out so well. Most people will probably just use tools that optimize for any popular HMD with little enough effort that only contracts will make exclusives make sense.
There's a lot of features that Chrome on Android supports but that can't be added to Chrome on iOS because of Apple's policies. Important features, like fully offline-capable webapps.
I can see your point, but every platform has its own restrictions. Desktop Chrome can do a lot that Android Chrome can't. There are real security benefits to not allowing downloaded code to run on a device without passing through Apple's JavaScript engine. Of course security and features are often at odds. Outside of tech forums, I've never heard anyone complain about missing features in iOS Chrome, so I'm just saying that to most people, the interface, bookmark sync, etc. is what makes it Chrome, not the JavaScript engine, and the tech it's built on will continue to change over time, bringing new features and new restrictions.
Yes, because it shows Google's dedication to not leaving people out. Apple doesn't allow Google to use the real chrome rendering engine, and instead requires that every webview be webkit-based. Google would absolutely use their own if they were allowed.
Yeah, I had to leave a few meetings to 'get a drink of water' when we were discussing this. I wasn't the only person in the room who did. We got a lot of odd looks from seniors in that meeting. Perhaps it's only a millennial thing to find SIEM INASS funny?
