henryprecheur

[1] http://www.advocatesforyouth.org/publications/416

8 hours a day * 200 working days = 1600 hours

With 30 people working just a week (5 days), we're already at 1200 hours.

Maybe they got their hours wrong? Or it's not that impressive (I'm a grumpy old man).

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.

The "who" is actually pretty important.

Tax the working man more, and you'll discourage working. Tax the rich, and he might move to another country.

There are many ways to raise money for the state, and none is really "fair". There will always somebody who'll be screwed in some way.

I can't speak of other NoSQL databases, but unSQL doesn't seem to expose most Redis' features, like lists & sets.

It's a lecture from Ed Catmull. I highly recommend it, many gems from a brilliant developer turned brilliant manager.

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.

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'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.

[1]:http://en.wikipedia.org/wiki/Stream_Control_Transmission_Pro...

I don't think that g++ will be removed. Too many things are written in C++. And as long as GCC is present in OpenBSD, there's no reason to remove G++.

1. Groff is buggy

2. Groff is slow to compile & execute

3. Groff is not BSD licensed

mandoc has none of these problems. If you want a "generic" roff system, groff is available as a package.

According to http://mdocml.bsd.lv/

> 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).

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)?

It shouldn't be too long though. I'd bet that in 6 months 1 or 2 projects will already be functional.

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.

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 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?).

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.

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.

Local storage wont go away. I hope Web SQL will be replaced by something "better" and more straightforward, A simple key-value database would be great.

Of course we can run X on top of something like Wayland, but we'll just have added another layer, and X will still sit on top for another 10 years.