grout

Rule of thumb: If any part of your pitch sounds like Microsoft marketing, you're not ready.

"Satisfactory."

Fuck Diablo. My interview will be in Alpha Centauri.

Perl has this: https://metacpan.org/module/Getopt::Declare

AVR-targeted gcc has an __int24 type. Not a power of two.

The readability arguments need to include such modules as Method::Signatures::Simple, which replaces the old manual method (no pun intended) with:

   method foo ($a, $b) {
      $self->blargh($a + $b);
   }

"using rhetorical force to invalidate contrary views"

Thank you for epitomizing what makes Linus worth emulating.

Rhetorical force. Coooool.

http://topsy.com/ yeah. we do that.

A lot. Ignore comments to the contrary.

Based on that picture, I pity the employees.

Doesn't build with the gold linker. Feh.

Forth's necessity of carrying the stack in short-term memory while coding and debugging has seemed to me its deepest flaw as a tool for mortals.

Mythical Man Month and Silver Bullet essay ought to be mandatory. K&R as well, and Stroustrup (both C++PL and Design and Evolution of C++).

Programmers don't stand on each others' shoulders, but each others' feet.

Beware the naked man who offers you his shirt.

OpenSSL's command line tools are so antequated and annoying that I can't help thinking that they're being held back by the Powers That Be so as to discourage casual crypto.

It is fun watching kids rediscover the wheel.

sigh Scientists stand on the shoulders of giants; programmers stand on each others' feet.

The only valid reasons to "leave" Perl apply equally to Python. Sorry, but it's true.

Compilers are good enough for type systems to be advantages, now.

Microsoft wants to kill C. I don't know why.

You're funny. If this really pushed you over the edge, you were born -on- the edge, and didn't give Perl a fair shake.

"They laughed at Columbus, they laughed at Fulton, they laughed at the Wright Brothers. But they also laughed at Bozo the Clown." -- Saint Carl Sagan

Whenever anybody complains about hate, I usually find that what they mean is "don't get mad just because we deserve it."

Usually.

The best system involves keeping end pointers, not lengths. Remaining length changes. End pointer never changes. At previous job we converted our whole code base to this system, and it worked great.

I hope Feinstein gets primaried. Her support for PIPA is sick.

"The advantage of abstraction" is not always an advantage, which is the whole point of this whole thread.

This is what happens when people with the kind of crazy that broke HP and Palm and Compaq decide to play with open source projects.

Clue: Dealmaking is not codemaking.

You're not idiots, and neither are Amazon. But using a Dynamo style design safely requires overprovisioning and performance loss. W=1 speed is your bait; reality is the switch.

Node failure is not the failure case in question. As long as the node is up, hinted handoff can't play any part.

You use argument from authority ("It's based on Dynamo, which is made by Amazon, so you know it's good!") while accusing me of a strawman for reporting my own personal experiences.

Good thing there is no god, or you should have to watch out for lightning.

sigh And here your PR guy wanted to fly me to New York to talk to you. Obviously the effort would have been wasted.

Replication events are too important to be designed to fall on the floor. I want at any given time to know approximately how far behind replication is; I want primary write events to block until replication is at least durably scheduled; and if I pause or slow operation and wait for replication to catch up, I want to know that it _is_ caught up without holes. Cassandra fails utterly to meet these minimal requirements.

Master/slave queue is not the only way to meet these needs, but unless a replacement can fulfill the requirements, I can't responsibly switch.