tantalic

If they win, the US government collected taxes they shouldn't and those would be returned. Saying the "US taxpayer will pay for it" is equivalent to saying the US taxpayer pays for your tax refund. (And also, Nintendo is a "US taxpayer.")

Twenty years ago, I was strongly anti IDE and pro text editor. In the last ~10 years or so text editors have gained features previously only found in IDEs and IDEs have improved their performance and brought in features from text editors. I would argue the distinction between text editors and IDEs at this point is academic.

There's an old saying in Tennessee - I know it's in Texas, probably in Tennessee...

They had me at "4 months of work just to make a stupid pun."

I have been a happy Base user since 2011. I don't use it all that often, but anytime I need to explore a database file or take a CSV and turn it into a database for some investigation it is the first tool I turn to. Happy to be able to be able to pay for an upgrade after this long!

FINALLY

Being cool and getting a lot of views/clicks should not be confused.

I am a bit surprised the proposal doesn't suggest using a hash (such as SHA-2) rather than directly passing the email address.

As someone who almost always has a text editor open, I have paid for many over the years. In particular multiple versions of TextMate and multiple versions of Sublime Text. I have also been responsible for getting licenses for my team(s) at work.

I now find that the editor I am happiest with is VS Code, not because it's free but because of the extensibility and community support it brings. I'd happily pay for it - but I think the nature of it being free is what has brought so much community support to it.

While that is true, it requires a very specific understanding of both intellectual property law and the inner workings of development tooling that is pretty rare in practice. As such, companies are generally conservative in such decisions. Most organizations have a single list of licenses allowed for use rather than getting into specific use cases for specific licenses. These types of environments will generally limit uptake of copyleft tools.

All that said, I'm not convinced the licensing is the issue here (although I wish them the best). We are in a world that has grown accustom to free development tools and building a commercially viable business in tooling is incredibly difficult. I'm always amazed by how many developers I know who make a living by creating software yet are unwilling to pay for software themselves.

Is there any way to trial the self hosted version? I'm rather interested, partially as someone who doesn't like the idea of putting such data "in the cloud." (For products with less sensitive data I would try the monthly subscription first.) I'm assuming not, and that the self hosted is probably a small percentage of your customer base. But worth asking!

This is problem of misaligned incentives: if you are making a security scanner the last thing you want to do is miss a vulnerability. The result is many false positives.