vampirechicken

This will be lobbied into oblivion. Content providers won't go for it, because they currently use their popular programming to force their new ventures onto cable providers. You can't force a cable provider to put your crappy home and garden channel on their line-up, if nobody orders it. You can't argue with real sales metrics.

Further, cable providers can't make a living when all of their customers downgrade to the three basic-cable channels they actually watch, plus HBO. Because the idea of a la cart cable is to lower the bills by not paying for what you don't want.

Huge amounts of money will, from both sides of the cable programming negotiating table will align against this pro-consumer measure, because it will force a radical rethinking of an industry that has never really had to be pro consumer.

Maybe those are the premium features...

If you want startup time boost, check out the zeus gem.

Try to keep your environments as consistent as possible, whenever it is reasonable to do so. In the long run, it's better for your peace of mind.

Because businesses want to cut corners and ignore the good practices and disciplines of software. Then they complain that it's the software engineers' fault.

why would anybody do that?

Right. I thought we were only supposed to hate Perl and PHP.

I can't keep up with the dogma...

I think you're missing segiotapia's point.

The story about the middle managers not approving ideas that they team was later excoriated for not having implemented is classic Corporate America.

Dear customer, we have a Hippa/PCI/confidential-in-some-other-way message for you in our in-app message center. Please log in to view it. Yours, The Management.

There, that was easy. Otherwise, just send me the message.

Open Source is not a methodology. It is a neologism coined to make the concepts behind Free Software palatable to businesses who would not touch "Free" with a ten foot pole. This is analogous to the rebranding of Punk Rock into New Wave to give it an inoffensive name so they could play it on the radio.

Git is a journey, not a destination.

#9 is missing, and the Peter Principle is not, strictly speaking, from Computing.

Why would you insist on creating and destroying a db connection on each request? We stopped doing that decades ago.

Tim Pope has a potty mouth.

Hey Balanced, many of your competitors have rolling payouts and/or reserve requirements due to the risk of refunds and chargebacks.

How and why are you willing to float that risk?

That's about what you can expect from that guy.

When RapGenius didn't get the answers they thought they deserved, they went to the court of public opinion, and put Heroku on the defensive. All Heroku can do now is damage control, and we recently saw an example of that which didn't work out very well for Elon Musk.

So they give interviews to Venture Beat (a C-level exec publication) with the COO who talks about trust and community, and the C-level execs feel a little better.

You and I are left to wonder why a random routing dispatcher is better than a deterministic routing dispatcher regardless, of single-thread, multi-thread, evented, non-evented listeners.

You would expect this answer from the COO or CEO, you get technical answers from the CTO, but when you have a PR problem you trot out the CEO/COO.

It's the age old set of trade-offs between buy and build.

Build it all yourself and it takes forever, but you understand it all.

Buy it from somebody else, and you get it quickly, but you're at their mercy for efficient understandable code.

No language or framework is immune. Enjoy your java.

But with a quick perusal of the man page, you learn how the software works, and you don't have to make assumption based on interpretations of natural languages.

ln, as well as, cp and mv are all 'command source destination'

There's a lot of data to pick through

How much of this happening do you think can be attributed to how young the Ruby user base tends to skew? How often does it occur on the Python or Perl IRC channels?

If you want to compete with craigslist, build a better product and convince people that there is value for them to enter their data. That's what craigslist did.

Semantics is the study of meaning. Open Source does not mean the same thing as free software. You're saying that the author should get a pass for being egregiously wrong. Stallman being Stallman is part of what drove ESR to coin open soource.

One does not avoid being called out for being wrong about a thing simply by saying "calling me out for being wrong is one of the problems I'm discussing."

They Come With Cheese is my semi-ironic blog about cheese. http://www.theycomewithcheese.com

One more time, with feeling: Free Software != Open Source Software.

Open Source is a marketing term, coined by ESR because "Free Software" is scary to businesses, much the same way that record labels coined 'New Wave' to make Punk Rock palatable to the record buying public.

and yet, we have no way to positively identify anybody here as an Hacker, we must put up with secret infiltrations by non-hackers who upvote non-hackish stories.

A Law Enforcement Officer, provided the IDENTITY of the suspect. There fore IDENTIFIED by law enforcement is semantically and connotatively correct. An identification was made, and it was made by a member of law enforcement.

People on the other end of the TV do not ponder whether the identification was a legally-important one or not. They only know, via both of your examples, that a cop said that I guy named John Doe is a suspect.

The divide between intent and reality is in important concept to grasp, especially when you finally put your web application in the hands of soccer mom's and office administrators.

How did J2EE become a night mare. It was pretty clear to me that you put your business logic in session beans, and they manipulated entity beans along the way.