dmethvin

> IE for example still does not support Touch Events, even on WP.

Yes they do. However, IE11 doesn't support Touch Events on desktop because there is already too much code out there that makes stupid assumptions about Touch Events implying a tablet or phone without a mouse. http://blogs.msdn.com/b/ie/archive/2014/09/05/making-the-web...

Here are some I'm aware of:

https://github.com/jquery/sizzle/issues/290

https://github.com/jashkenas/underscore/issues/2081

https://github.com/jquery/jquery/issues/2145

Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.

This is why semver is not a silver bullet. It only covers what the project maintainers think are breaking changes. Their unit tests don't consist of all programs that use their code.

When you use undocumented behavior, is it correct to blame the project and take no blame for yourself? That seems to be what happened here.

> Also remember that Google brought us HTTP/2 when Microsoft and Apple were completely ignoring the web.

You only have that half-right, Microsoft hasn't been ignoring the web for several years, but Apple still is. The problem for Microsoft is that it can't move the web anymore. The center of gravity is in mobile and they don't have any market share there. Apple doesn't want to move the web, their walled garden is making much more money for them and there's no need for competition.

Not only expensive to run things underground, it introduces maintenance nightmares. Overhead lines can easily be inspected and even repaired while in service [1]. Underground lines cannot easily be inspected or repaired. Even when there are multiple lines, failures can overload the remaining lines as happened in Auckland [2]. If you want to get an idea of the hassle repairing an underground line is like, read this series of posts [3].

[1] https://www.youtube.com/watch?v=tA9oBEHRLqQ&hd=1

[2] https://en.wikipedia.org/wiki/1998_Auckland_power_crisis

[3] http://www.jwz.org/blog/2002/11/engineering-pornography/

I wonder if malicious plugins are modifying the page and injecting things? I've encountered ones that physically change Google results pages, it looks like the page came from Google but the results are from some scam network.

I don't have any quantitative data, agreed. The Internet certainly provides a lot more visibility for such contemplation, and I can't recall seeing a lot of it.

Stuhlinger's thoughtful reply seems like something very few people would do today. Not just the part about taking time to reply to a random letter, but the part about deeply considering the role of their work and its effect on humanity as a whole. Perhaps he's just rationalizing a greater good because he really likes space exploration, but if that's the case he did an excellent job of it.

> Which, incidentally, here on step two indicates why the NASA standards are from such a different world from the web browser that they don't much matter.

Other than the mention of recursion, everything else is about predictable and visible program flow. If you were to carry this forward to JavaScript you would want to avoid `throw` for application control for example.

You could build a custom jQuery copy that eliminated whatever methods you don't need. Since plugins use unknown parts of jQuery and Closure Compiler can't always detect that, you really need to do some manual labor to pull in what you need.

In the 1.8 time frame the jQuery devs made a call for people who wanted to use Closure Compiler's ADVANCED_OPTIMIZATIONS to participate, but just didn't get any community interest. CCAO style is not typical JavaScript and it doesn't seem that a lot of people use it.

I think the answer to that is "yes", since our technology is advancing all the time. The question this made me wonder about is, "If this new 2015 engine was given to the 1970s engineers, would they be able to understand how it was made and create a similar one?" This is just 40 or so years later. It makes you wonder how advanced an alien civilization would really have to be to impress us.

Contrast the design and price with the electric unicycles like Solowheel, Airwheel, Rockwheel and various knockoffs that have been around a while. I got a Uni-wheel [1] for $300 last month and it's pretty fun to ride. The specs for the weight, top speed, and run time are pretty similar.

[1] https://www.youtube.com/watch?v=sF17hVc_VaM

I think yours is the traditional take on frameworks vs. libraries, so you're not alone. We have a lot of frameworks in JavaScript because we're still expanding and exploring the space where they can work. Eventually I think we'll settle on a smaller number of frameworks, but even so I doubt we'll see the level of consolidation that happened with libraries and jQuery.

> Time passes and your application becomes multi-threaded.

Is it realistic to think that any app starting with a bunch of assumptions about being single-threaded can ever just "become multi-threaded" without bloodshed?

You're aware of jQuery custom builds? Leave out what you don't use. It's in the README file.

That won't work on Android 2.x, which doesn't support `.classList`. Performance isn't even an issue here since changing classes will cause a reapply-styles and layout.

Just in case you'd like to look at their financials before donating, they are at faqs.org [1]. I couldn't find the official IRS Form 990 online.

[1] http://www.faqs.org/tax-exempt/CA/Internet-Archive.html#anal...

> Ben does have a JD from Harvard law that I forgot about

A major omission when attacking someone's legal qualifications.

> When he's not writing antitrust papers, he's busy writing scare papers about click fraud, or online ad deals

Yes, and they're scary because they are true. The insidious thing about click fraud is that consumers are the mules who do the work but generally are only indirectly harmed. Advertisers and merchants really get screwed. Ben has been exposing those situations for a decade.

> You only have to look at his testimony list to see where his views lie, and have since 2006.

Actually I worked with him in 2005 and his views were consistent then as well. If he works on behalf of people who share his views, that's not a bad thing is it? It's fully disclosed, which is more than I can say for many of his attackers.

That's not true. If you look at http://kangax.github.io/compat-table/es6/ you'll see IE11 preview (their "canary") has more green than any other browser including Chrome or Firefox. Yes, even more than Firefox nightly or Chrome canary.

I think that's a key point, the earlier you can catch the problem the less frustrating for both sides. There is https://www.npmjs.org/package/commitplease for commit hooks but it's still handy to have something audit pull requests.

At the moment, they provide two very different views of email. Actually I guess you could say the old GMail client offers two different views itself, since it has both standard and priority inbox.

It's not clear that Inbox is the right way to look at email for the majority of users, and I'm saying that as a user/tester. I've had to drop back to the regular GMail app do do things a couple of times and Inbox has crashed twice on me.

Note that the GMail client did take on some of the look and feel such as the (+) widget on the bottom right.

TypeScript compiles out all the overhead, AtScript will need to leave at least some overhead so that it can support RTTI. The AtScript design acknowledges and borrows from TypeScript, ideally I would prefer it to be a superset so we don't end up with a lot of divergent dialects.

Google and Microsoft do this too when you enable real-time searching via the address bar, but both are pretty good at letting you know it happens. Doesn't Safari have some kind of first-run experience where the user gets some notice on this?

The other problem is what little vetting the ad platforms do is easy to circumvent when they allow advertisers to host their own content. A few years ago the New York Times was serving out malware because they approved an ad and later the advertiser swapped it for an exploit.

http://bits.blogs.nytimes.com/2009/09/14/times-site-was-vict...

Even better, they can bid based on the IP address range and only pay for the suckers they target. Why go to the trouble of making a harmless ad when you'll never need to show it?

IE12 isn't released so I doubt the feature set is fully established. The status.modern.ie site has been mentioned on HN a few times though, and it does have some info. https://status.modern.ie/?term=hsts

It's a question of who gets the last word, though. Originally I thought that web devs should have the last word about IE document mode, because darn it, they own their site. After seeing so many sites that seem to be unmaintained (or maintained by uninformed devs) I am also leaning towards the user having the ultimate say.

I use Google's voice dictation frequently for text and email, because my fat fingers don't like onscreen keyboards. It often gets the dictation of an entire paragraph totally right. It's impressive.

My wife and I work from home most of the time. I just checked our last bill and our use is 108 gallons per day. Toilets, showers, laundry, cooking, dishwasher. We don't wash our cars and just water some house plants. It adds up.

Um, "haven't bothered"? Think about all the Linux/Unix-based devices that could be affected here, it's in the millions. Do you run a local server on your box? How about your Linux-based router? Has it been patched yet? Why not, it's been more than 24 hours now.