tedjdziuba

Put bylines on your articles. You are not The Economist.

In a federal prison somewhere, Andy Fastow mutters "...amateurs".

Good lord, thank you. As a math guy, numerology drives me apeshit.

No.

C-x k

Series C? Wow, you guys must be hurting. That's got to be some serious dilution.

And nothing of value was lost.

Ahem.

tail -n 1000

Holy balls, talk about going out of your way to avoid syslog.

He mad.

> Enter Cy Khormaee, a Harvard Business School student, and his team at Lifelens.

I believe you mean "HBS Student Takes Credit for People who Created an App to Detect Malaria".

The false dichotomy between MySQL and NoSQL is really irritating. Just because MySQL isn't solving the problem, doesn't mean that you have to completely change the database structure.

There are more grown-up SQL servers out there that can handle way more than MySQL, and not one of these "NewSQL" things that the author talks about.

Sure, let's bet the whole site on a really new database. Worked really well for Digg!

I know of a company, made up of scientists from academia, that develops software by writing the code (or "codes" as they call it) in Microsoft Word documents and e-mailing them to eachother.

Some how, they are still in business.

True story.

I suspect that using this product will be a punishment for not knowing Emacs or Vim.

What problem does this solve?

As far as radio stations I can receive at my home, I consider my physical radio to be the single point of truth, not a database.

tl;dr

Protip: if it floats, flies, or fucks, rent it.

Hm, defense contractors were attacked, and it's taken so long for RSA to acknowledge the compromise to the rest of the world? It's was most definitely perpetrated by a government, and it's taken so long for them to respond because our government has been assessing the damage.

FWIW this is why the rest of us chuckle at MySQL.

u mad

Watch a production log file for 5 minutes and tell me if you can get anything meaningful out of it.

OP's ignorance makes him a threat to himself and others. It's this absolute refusal to learn the existing toolset that's pervading modern software development, putting projects in jeopardy. What's odd to me is that not only is the HN community complacent in this, you actually applaud it.

FWIW, this is why your sysadmin is pithy. He has seen software developers pull stunts like this for far too long, unwilling to listen to reason, unwilling to be technically cuckolded by a software package that's existed for thirty years.

Ignorance doesn't listen to reason.

I said that OP had reimplemented something that already existed, but with fewer features and tests. Or did you get something else out of those six words?

Raw logs generally aren't a useful source of information for humans.

There's value in brevity.

Yeah that would be cool. Even better if it could be done over UDP, so the log messages are fire-and-forget from the client side. Even BETTER if there was a standardized way for all programs regardless of implementation language to write to said socket/log.

Yeah, they thought that up 30 years ago. It's called syslog.

Cool, you just reinvented syslog, poorly.

> As for DHH's opinions, they are his own. I may or may not share them, but we're both grown ups and we respect each other no matter what.

I've got some bad news for you, friend.

Alright, Fred. We all agree with you here, the people you need to convince are the ones writing the laws. You're a wealthy and powerful person, who is good friends with other wealthy and powerful people, so why not leverage that? Hire a lobbying firm, get actively involved in the cause.

Whatever you do, don't count on Reddit and Hacker News to do it for you, that's just slacktivism.

Re-arranging the deck chairs on the Titanic.

This sounds like something that's been painfully over-engineered.

One of the main problems they solve is "distributed RPC", from TFA: "There are a lot of queries that are both hard to precompute and too intense to compute on the fly on a single machine."

That's generally a sign that you've made a mistake somewhere in your application design. Pain is a response that tells you "stop doing that".

Oh cool, so now I can host my app in one data center and have it make DB calls across the open internet to another DB server! But wait, there's more! It's over a stateless protocol: HTTP, with really poor multiplexing/pipelining support.

Latency is a feature, right? Like "slow your roll, cowboy, let's not have a heart attack here".