DoubleCluster

Don't use webfonts? Lame but effective.

I've used it to bolt file storage on a REST API for enterprise stuff. It seems to be a good fit. I'm even using the Windows WebDAV implementation... working around its quirks is madness: http://www.greenbytes.de/tech/webdav/webdav-redirector-list.... Note that XP SP3 has the port-handling bug even though it's not on that list.

It's common in engineering. I like it because it makes matching parenthesis much easier.

Exactly, I'd love more interactivity but you can pry my plain text source files from my cold dead hands. The smalltalk environment was way too magical and too easy to mess up when I tried it.

Why the dislike? It's not a bad protocol.

Alright, I was just wondering if you had experienced the origin of pixel art.

Honest question: how old are you?

Scraping a website is absurdly easy. You can have the data before you'd have finished writing the email.

If you're going to use them a lot you're cheaper off using consumer grade computers with the most expensive intel processors available. What I usually do is take the Passmark CPU list, add $500 for the cost of the rest of the system and sort by score/price.

Oh, they really have an API for everything. That's awesome. Now... I wonder if there are companies in China that have an API to order a pallet of stuff?

Ohh... shiny!

Can we also get Elastic tabstops? http://nickgravgaard.com/elastictabstops/

Google hosting stuff on Github and not on Google Code? Is that because of the easier forking? Is this the first sign of Google abandoning its own open source project hosting?

Just found PiHAT - Rasberry Pi Home Automation Transmitter: http://www.skagmo.com/page.php?p=projects/22_pihat

I don't get much mail, but I usually respond to them at once and then leave them in my inbox forever. If I need to take action at a later time I usually still respond, and then write it on my paper todo list. I've got some filters for mailing lists and other spammy things (bug reports etc.).

I actually like old and ancient. That means all bugs have been fixed already. Systems become complex quickly enough and you need to use the most boring bricks imaginable if you want to build something sturdy.

I think we agree?

Well... I would like to disagree on your opinion about cleaning up prostitution. Over here in the Netherlands it seems to work just fine. If person A pays person B for doing intimate stuff that doesn't really harm anyone.

From Wikipedia, uTorrent: > Although originally developed by Ludvig Strigeus, since December 7, 2006, the code is owned and maintained by BitTorrent, Inc.

> Every IM install screen has a decline as well as an accept button

Well, could you provide a screenshot of that screen? Usually users are misled into thinking they are accepting the install of the software they actually downloaded.

> The apps that get installed are "crapware." This one seems a matter of opinion.

Yeah... I don't think very highly of your opinion if you really think like that. Making someones computer slower or less usable by installing "unwanted software" is something that should be forbidden in my opinion. Really, do you have any idea how much hours of my life were lost by removing crapware from computers?

I did check the ycombinator.com website for any indication if the type of company or product was of any concern. I did not find anything about that. This probably means ycombinator is actually just interested in the money and not in making the world a better place. Silly idealistic me...

The Segway... is back! Cool product!

You've got a nice site but I think the product is not useful enough. You've got to install those bulbs and any enterprise I've been in uses fluorescent lights and not the classic fittings. I couldn't even use those in my home.

If you want a mobile device to locate itself indoors, why not use WiFi? Probably the entire place is flooded with access points already.

In my experience it's quite doable (with a good IDE) to refactor the working but messy code into something maintainable. It might take the same amount of time as a rewrite but you'll still have all the features and corner cases covered. Usually refactoring will be much faster though.

That's fine. Did the code become easier to maintain? It's not clear from the article. The "The good" section is relatively weak and the "The not-so-good" has some painful points about memory management and api instability.

It sounds a bit like you guys rewrote it because node.js is hot and you then stuck with the rewrite because of sunk costs. Or am I imagining things?

Thanks for sharing your experiences with us. I'm just asking those questions because I want to learn more about them.

> It terms of performance, we also have seen a significant (about 25%) bump in terms of feeds processed by second per server.

They rewrote the entire codebase and obtained for just a 25% gain? It doesn't sound like they are very happy to be coding in javascript now either.

Everyone: please don't rewrite your code, it's almost never worth it. The one exception is rewriting a core part of an algorithm in C for speed (the last 10x speedup).

It's great that Amazon keeps innovating. Or are they just using the tools from Netflix?

You really can't be a good developer on rules of thumb. The best code just does the minimum it needs to do (YAGNI) but still has the necessary abstractions for for easy extensibility in the future. It's a fine line to walk on.

For a second I was hoping for 18+ features. That might actually get some people on Google+.