That policy is a bit risky. That might diminish the use of other things that reduce significantly the spread of HIV, like condoms. It's still unknown how effective the gel is: maybe 90%, maybe 5%, condoms are 90% effective AFAIK[1].
Sometime shitwork can be a very good way to find new possibilities. A lot of people do shitwork that's immensely useful, like editors on Wikipedia, moderators on reddit and forums, people who enter all the data into imdb. I don't see how those people could be replaced by algorithms with what we know now.
Sometime shitwork needs to be done because you can't simplify. I'm doubtful that Facebook's auto-group feature would work for me. Maybe me doing shitwork on Google+ is what work for me, because I value my freedom to control my information online.
I don't know if I like it or not. If you know SQL well and want to switch to a NoSQL database, what's easier learn? The "proprietary" API of the dababase (like Redis, or MongoDB) or the limitations of unSQL?
I can't speak of other NoSQL databases, but unSQL doesn't seem to expose most Redis' features, like lists & sets.
Husky & HD (another StarCraft caster) both have a healthy revenue stream from their Youtube Channel. There are at least 12 other casters/players in North America/Europe making a living casting StarCraft II games.
Husky wasn't the first to cast. Guys like Day9, Artosis, & Tasteless cast too, and are quite popular. But HD & Husky were the first to focus mostly on "Virtual" tournaments. The other successful casters focused more on "Real life" tournaments. Artosis & Tasteless even went to Korea for a year to comment StarCraft II games on GomTV. Day9 regularly travel to big tournaments.
And yet, none of them make as much money as Husky & HD (supposedly, I don't have hard numbers.)
It shows the power of the web. The old medias are here to stay, but most of the creativity & growth today comes from the web.
I agree that SPDY would be a "quicker" solution. Just modify the browsers and wait a year or two, and 30%+ of the people browsing the web will have it.
SCTP have the nice side effect of improving things like streaming, and games.
As for application-layer changes, I don't think it would be too difficult to do, kind of like ipv6 (I don't have anything to back this up, it's just a hunch).
SCTP deployment will much longer than SPDY, but SCTP seems to be the "right thing to do". Not only for the web, but for other things that use the network. Internet is not only http://.
UPDATE: I just realized that saying that the transition to SCTP will be like IPv6 isn't necessarily a good point for SCTP :-D ... I guess I'm a purist and not a pragmatist.
I don't like SPDY. It's trying to solve a transport problem at the application level. Plus it seems to be quite complex.
I'd love to see Google promote a transport protocol like SCTP[1], and do HTTP over SCTP instead. If Google pushed SCTP a little bit, we might see it pop on Linux and Windows within a few years.
> groff amounts to over 5 MB of source code, most of which is C++ and all of which is GPL. It runs slowly, produces uncertain output, and varies in operation from system to system. mdocml strives to fix this (respectively small, C, ISC-licensed, fast and regular).
Yes, the answers' quality seemed very variable: the most critical answers were the most useful. I'd also be willing to pay a premium to get reviews from the "meanest" soldiers ;-)
You should show more respect to what other people do.
You're not the only one guilty of this, everybody tend to overestimate their contribution to the world. How many times did you hear/read about a business guy / manager saying that programmers are a disposable commodity? Saying that "the entire financial industry is ready to be replaced with a lot of very short shell scripts", you are acting exactly the same way.
Did you forgot about the dot-com bubble when the tech industry was the one guilty of being over-rewarded for what was often was no value (pet.com)?
> I'd be interested to know what the "core developers" disliked about Git too.
I spoke to Brett Cannon --basically the guy who chose Mercurial-- not long after the choice was made. Apparently the most important factor was that Mercurial was the favorite choice in the Python community. That's probably because Mercurial is written in Python, and was used by a lot of Python projects.
Also Git didn't work very well under Windows at the time if I remember correctly.
Companies can always build their own "last mile connection". I have a fiber optic connection here in Vancouver (20/20mbps), it cost $45/mo, which is reasonable.
The thing is that the ISP (Novus) had to lay cables to all the suites in the tower. This cost money, and might only viable in high density areas.
I've been using Redis for 2 months now. It's a real pleasure to use.
I especially like the simple protocol. It's possible to write a simple client without any external libraries within days --maybe hours if you're really good ;). Try to do that with SQL or MongoDB (Javascript parser anyone?).
Which is one of the most tested, most utilized, most known pieces of code used among modern software.
Sounds like Microsoft Windows to me :)
I think that SQLite is a really nice database. But just because SQLite would work in the browser, doesn't mean W3C shouldn't try to do something better.
SQL is certainly a well-known _language_, but I don't think it's very well understood by most.
Also if IndexedDB has a "lifeless" spec, it might be because there's not much to discuss. Something simple and straightforward tends to requires much less discussion and debate, than something complex.
[1] http://www.advocatesforyouth.org/publications/416