I guess I look at those examples and think they are exceptional and dubious, respectively. Maybe that's just a cultural difference across the pond. If you head down to London and catch a show and don't want to walk home, I think that's about you, and maybe you catch a cab home.
Your other examples all seem like things that would likely be done before 10pm. As someone who lives in a college town and who also lived on campus at the U of Lancaster for a school year, it seems like 10pm would cover the vast majority of the use cases.
Maybe I should talk to the town council about dimming the lights.
What time is 'late', I wonder?
I'd be very happy if the (small) city I live in only kept street lights on from dusk until 10pm, for example.
Everyone has their reasons. In my case I had no real interest in ad blockers until dice.com's ad partners started serving exploits.
Agree 100%. I installed adblock plus when slashdot started throwing URL blocks from the ad rotator. How do I know the next ad rotation won't be a driveby? The industry provides zero guarantees and relies too much on upstream ad providers to vouch for safety.
Slashdot has notoriously always had a comically unfunny April 1st, and at this point I have to think the complete lameness of it all is the real meta-joke.
The whole "HTTP/2 stink" thing seems to be a bit of a meme, but it's remarkable how the people who state it vaguely wave their hands around and make unsupported claims.
1. HTTP/2 is *fantastic* for higher latency connections. If you're a small site and you can't afford to have geolocated servers around the globe, HTTP/2 offers a much better experience for those high latency connections. I've been using SPDY for a couple of years to service clients in Singapore from a server in the US (which for a variety of legislative and technical reasons I can't replicate there). It is absolutely better.
2. HTTP Pipelining is when you know that someone is just doing the "I oppose" thing and searching around for objections. HTTP pipelining is not supported by default in a *single* major browser because it has critical, deadly faults that render it useless. When people bring it up to oppose HTTP/2, their position is rendered irrelevant.
3. HTTP/2 removes the need to do script and resource coalescing. It removes the need to deal with difficult to manage image sprites. All of those are bullshit that are particularly onerous and expensive to little sites.
4. HTTP/2 makes SSL much cheaper to the experience. This is very good.
HTTP/2 is a *huge* benefit especially to the little guy. Google can do every manner of optimization, they can deploy across legions and armies of servers around the globe. This can be expensive and logistically difficult for little sites, especially if you want SSL. HTTP/2 levels the playing field to some degree.
It isn't about "a chip". It's about a system that is designed for a specific thermal and electrical load. nvidia probably got flak from notebook makers who were facing dissatisfied customers.
You only have to look at a lot of the nonsense comments throughout, such as yours -- people just contriving how "easy" everything is, and how simple it is. Yeah, and I'll bet all of you design notebooks. No? Then shut up.
To the best of my knowledge "head starts" in letters and numbers make no difference in long-term outcomes. I'm disappointed to hear Gates pushing for this sort of thing. Solid educational resources at the right developmental stages are critical for long-term success, not some sort of fast-track to the ABCs.
Investors don't care about 20% revenue growth y-o-y if EPS has tanked.
GOOG Earnings Per Share:
Research is to see what everybody else has seen, and think what nobody else has thought.