gtjrossi

7 ms·

1.
by gtjrossi 10y ago
As an engineer that worked on IE, I can totally sympathize. Your story is one repeated throughout almost every enterprise of sufficient size. That said, there's a middle-ground we should strike here. At some point, being out of date (s
2.
by gtjrossi 10y ago
Remember that this is, in large part, a restructuring of existing orgs and investments. I wouldn't interpret this as the starting gun for AI/deep-learning investments at Microsoft. There's been heavy R&D investment for ye
3.
Using Edge instead of Chrome will add hours of extra battery life(arstechnica.com)
3 points by gtjrossi 10y ago|0 comments
4.
by gtjrossi 10y ago
Microsoft engineer here. I would assert we want people upgraded more than anybody else on the planet. Our extended support contracts were designed to be cost prohibitive to encourage this point and were nowhere near a money-making venture.
5.
by gtjrossi 10y ago
Browser engineer here (Microsoft Edge). We read HN too. ;-)
6.
by gtjrossi 11y ago
The version of IE with Touch Events (Windows Phone 8.1 Update) is no longer in preview. You can buy retail devices with it on it today, actually. For the desktop version, see my recent blog post: http://blogs.msdn.com/b&#x2F
7.
by gtjrossi 11y ago
yep, we imagined this would be surfaced as a new event.pointerType value, allowing code to specifically target the device if desired.
8.
by gtjrossi 11y ago
I can see value in finding a way to expose individual touch points from their new touchpad to JavaScript. We looked at doing something similar in IE, actually, but didn't get around to it in time. If they want to do that, then they&#x2
9.
by gtjrossi 12y ago
In Seattle, overnight parking does not cost. They actually have stickers on the parking meters reminding drivers of this in the case that they're planning to drink.
10.
by gtjrossi 12y ago
It was most often not the case that (a) vendor prefixed APIs matched a particular "version" of a spec nor (b) were interoperable across browsers at any point (e.g. -moz-foo didn't necessarily have the same behavior as -webkit
11.
by gtjrossi 12y ago
Actually, our approach is effectively yielding the results you're looking for. Removal of old IE legacy cruft is slimming Spartan's disk and memory footprint when compared with IE. Advances in the Chakra engine are pushing perform
12.
by gtjrossi 12y ago
We're implementing ORTC (which actually gets its origins from outside Microsoft: http://ortc.org/history/ ). ORTC is essentially WebRTC "1.1" and there's active standardization work going on (in both
13.
by gtjrossi 12y ago
Yep! We're committed to interoperability and compatibility for sure, and that includes implementing Touch Events. But, we don't see that as a blocker for moving the web forward with better models. Table layout was terrible. For e
14.
by gtjrossi 12y ago
Pointer Events is a Candidate Recommendation at the W3C http://www.w3.org/TR/pointerevents/ It has 2 implementations (Firefox has implemented in a special branch and is working to port it to their main codebase) a
15.
by gtjrossi 12y ago
On the contrary! I work on the IE team and we're playing along nicely. Google just joined us on the ORTC spec, which Chrome considers to be essentially Web RTC 1.1. http://www.cnet.com/news/reconciliation-draws-clo
16.
by gtjrossi 16y ago
I just tested it in 3.6.8 on Win 7). No crash for me. Though Firefox has a hard time rendering it (~30FPS, or about 1/2 the frame rate of Chrome, IE9 Platform Preview 4, Safari, or Opera!). Try another browser perhaps ;-) Also, if you have
17.
by gtjrossi 16y ago
Nice! It's a bit fast, but fun. Coincidentally, I just finished my version about a week or two ago. I used SVG, HTML5, CSS3-Fonts, etc. Check it out: http://www.jacobrossi.com/tech/helicopter/index.xhtml