bashcoder

Good article - it's helpful, and for me it adds clarity to the discussion.

Parsing recent industry statements, it's notable how Coinbase and peers have been using a rather loaded term of art, "bad actor", in reference to Mt. Gox, both directly and indirectly.

Yet even after all that has happened, many are still basing their conclusions on Mt. Gox's past public statements.

> The spectre of perl6 stopped bothering us about 2006

From a practical usage standpoint, sure. But wouldn't you agree that an effective major version freeze has had a chilling effect on the progression of the language?

I'd argue it's had a deleterious effect to varying degrees, even since 2006. It's not enough for a community to be not bothered. They need to be energized, and it's tough to make the argument that the perl6 snafu has been helpful to the perl movement.

> CPAN uploads have been up every year since.

CPAN traffic was down over 10% last year, according to Alexa. In fact, many perl popularity metrics were down at least 10% in 2013. [0]

My experience, admittedly anecdotal, is that CPAN packages in general are not maintained with the same vigor as in years past. But why would they be, if people are moving their focus to other languages?

Regarding Moo, thanks - I'll definitely have a look.

[0] http://szabgab.com/the-popularity-of-perl-in-2013.html

Join the ##atom-invitations channel on freenode and ask for an invite there. Plenty of folks sharing.

True on the sales point. And it's getting harder and harder to find coders who want to spend all their time writing perl, as great as it is. That makes it tough for enterprises to maintain perl codebases.

Also, more CPAN libraries seem to be in a state of atrophy these days and I think the long-looming specter of perl 6 has had a depressing effect on that community.

The post talks about Moose, which is a behemoth with huge and varied dependencies and must be be tougher to maintain these days. Every time I've tried to write a project in Moose, I've regretted it in the long run.

However, I've written plenty of big, enterprise-class projects in perl instead of buying them from major vendors. Over the years, we were almost always able to beat the value proposition of Big Software precisely because we had a solid team of perl coders.

Looks great - impressive feature, and congrats! We tested it a bit and you're off to a solid start. We were having a few issues with multiple tabs and such, but we'll post github issues when we have repeatable results.

I agree - it really deserves to be seen.

Wow - I didn't even think node.js was that old. It will be interesting to see its genesis. The first git commit for node appears to have been on Feb 16, 2009:

    commit 9d7895c567e8f38abfff35da1b6d6d6a0a06f9aa
    Author: Ryan <ry@tinyclouds.org>
    Date:   Mon Feb 16 01:02:00 2009 +0100

    add dependencies

Dig the feed URL: https://github.com/atom.atom

I also enjoyed their Indigo workstations, which included a 3D stereo goggle viewport. In 1998 I spent 6 months working on a 64-cpu Origin 2000 supercomputer, which had some serious power for long-running Computational Fluid Dynamics jobs.

Thanks for the useful tip. I also really appreciate the power and utility of tmuxinator. [1]

[1] https://github.com/tmuxinator/tmuxinator

In the second legal battle that Aereo won back in 2012, the lone dissenting judge in the US Court of Appeals in NY had a scathing critique of Aereo's scheme. I'm generally pro-Aereo, but I think HN readers might find this portion of Judge Denny Chin's dissent interesting:

"Aereo’s “technology platform” is, however, a sham. The system employs thousands of individual dime-sized antennas, but there is no technologically sound reason to use a multitude of tiny individual antennas rather than one central antenna; indeed, the system is a Rube Goldberg-like contrivance, over-engineered in an attempt to avoid the reach of the Copyright Act and to take advantage of a perceived loophole in the law. After capturing the broadcast signal, Aereo makes a copy of the selected program for each viewer, whether the user chooses to “Watch” now or “Record” for later. Under Aereo’s theory, by using these individual antennas and copies, it may retransmit, for example, the Super Bowl “live” to 50,000 subscribers and yet, because each subscriber has an individual antenna and a “unique recorded copy” of the broadcast, these are “private” performances. Of course, the argument makes no sense. These are very much public performances." [1]

[1] http://www.ca2.uscourts.gov/decisions/isysquery/620ea2ad-c6c...

Yeah, Phusion oversells their case when they say this is the "right way" to do it. It's one way to do it, and this methodology probably addresses customer support issues they are having. Many of their customers likely misunderstand what's actually going in a container by default.

I'd rather see a more balanced approach that shows a range of options, without opining so much about how Docker containers should or should not be used. Better to fit the solution to a particular use case.

I agree, and I also agree with the OP on this issue. Typically, at the point of a counter offer, a line has already been crossed. We've all seen exceptions, but by the time that meeting takes place, the employee has usually left already in their minds and counter offers are typically too little, too late.

If, as in your three cases, the employer has clearly failed, then the employee is in a position of strength. They probably don't even want a counter offer, as they are already resolved to leave. If the employer is surprised, it simply further illustrates the problem and validates the decision to leave.

From the employer's perspective, if the employee is just trying to leverage better comp opportunistically instead of through merit, it's also unwise to match or beat the offer. In my experience, this only tends to happen with younger, inexperienced people who don't have a long view of their career.

Either way, my policy is that when a person leaves, that meeting marks the end of their tenure at the company. Pay them for the two weeks notice they are always willing to give, just as if they were still working, and make all honorable accommodations. But once someone has resolved to leave, it's just better for everyone if they weren't around for an extended farewell tour.

This is often very difficult policy for managers, because they fear that a person is indispensable and will require the full notice period to train up replacements. They worry about the disruption to the business that it would cause. But if that's the case, it simply highlights another management failure. I'd rather take the business disruption, which gives my team an opportunity to shine, instead of the cultural disruption of having someone there-but-not-there, anxious to move on.

Understood - thanks for the feedback.

Of course the old model is upended - that's fine. Adapt and rebuild. Not telling myself anything. Just making the point that maybe this wasn't a genius move on the grand scale.

OK, so I get downvoting a joke that someone doesn't think is helpful to the argument. No problem. But why would someone downvote a legitimate music industry opinion that they disagree with? As someone with over 35 albums to my credit, I just happen to think this isn't a good strategy.

Is the groupthink so strong on HN that someone can't express an opinion supporting the commercial value of professional artists and their work?

I'm not a bitcoin culture expert, but I agree that it is a very interesting experiment and exercise. I too am watching all of this with great interest and wonder what kind of culture will emerge.

On the other hand, I have known more than my fair share of drug dealers. Almost without exception, they are just as likely to steal as deal. And every dealer I know has gotten robbed on the street at some point, if not regularly. The drug supply chain is lawless and rough, and not much of a community model. So to see some of these same dynamics playing out online isn't actually that surprising to me.

Seriously though, I hate to see these kinds of unforced errors. Especially from guys who should understand that the only reason people know who they are is because of a business model that is under siege.

Now is a time when the music industry desperately needs to make the case for value. These kind of gags don't help anybody.

Not a good enough offer - they would have to pay me to download these.

You don't see the hypocrisy of the "they broke the law and stole our money" outcry?

I guess it's just people stealing money then, so they should get over that. Not everyone agrees with allowing people to keep their stuff.

Well said. It's like demanding that someone love you, instead of working to be more loveable.

> Thank you, our customers, for believing in us. It’s because of you that we’re able to move on, to rise to a new challenge, and to make a real difference.

I'm always happy when a company does well. But when a company's success isn't in the best interest of their customers, there's a fundamental disconnect. It is, after all, possible to advocate for existing customers during M&A negotiations.

In this case, their believing customers are now rewarded by having their software assets freshly encumbered by technical debt. What was sold as a solution is now a problem. So maybe it's just me, but it seems that the proper disposition should be one of apology, not celebration.

Yes - there is a middle ground for self insured companies called a stop-loss provision. Companies can still get lower premiums through being self insured, but are also covered against huge losses over a specified amount.

In addition to the horrible way this was handled by management, this is clearly the failure of the AOL benefits team, who exposed AOL to more risk than it was actually prepared for.

Excellent - thanks for the info. I am more than ready to relieve Mr. Jenkins of his duties.

I'm glad to see more options becoming available for CI, especially ones that are easy to maintain and deploy. Basing Drone on Docker with few external dependencies is a plus. I'm also glad to see support for Cassandra and all the other databases.

However, I do see a lot of CI systems depend on Github as the repository, as Drone appears to do, and I would appreciate a more generic, flexible approach to that issue.

Thanks for continuing to make Github safer for all, @homakov. Someday I might even host a private repo there again, but I haven't done that since your first mass assignment exploit. You continue to prove that my decision was a good one.

Yes, love the soundtrack - EDM producer here - great job!

Typo - try http://www.dozeo.com

It's illegal operate an unlicensed currency exchange, and it's illegal for a licensed exchange to knowingly facilitate illicit transactions.

If a licensed exchange even suspects illicit activity, it must report it. Using financial transactions such as these in order to obfuscate and conceal illegal activity is money laundering.

In this case, the guy whose job it was to report the activity as Chief Compliance Officer was materially involved in the illicit activity itself. According to the complaint, he was even a SR drug customer, so there's no way he can feign ignorance as to what was going on at SR.

Huh? Are you even remotely aware of what's going on?

http://www.cnn.com/2013/11/19/health/veterans-dying-health-c...