Are you seriously asking me in the 21st century about people getting fired for what they say publicly? Did you just wake up from a 20 year coma? There is a very good reason why people value anonymity on the internet.

Have you ever seen javascript?

Gamespy was the worst service ever. Client integratio was always atrocious, latency was horrific and any game that used a third party service like gamespy didn't have a large enough playebase to support online multiplayer.

Freedom of speech does not protect you from private entities except in very specific cases, like labor laws. Suggesting that Eich's stepping down due to his actions creating bad press for Mozilla is somehow a violation of his free speech rights is farcical. It amounts to "You can't be mean to me for saying bigoted things cuz free speech." And no I wouldn't be juvenile enough to suggest that churches boycotting services run by pro gay rights organizations would be a free speech violation.

Breaking news: actions have consequences.

You seem to think that freedom of speech means "My words and actions shouldn't have any consequences."

If your developers didn't write shitty code you wouldn't need the comments. Comments are extremely useful for explaining edge cases that aren't apparent just by looking at the code so some other developer doesn't remove your changes thinking they are incorrect or explaining a configuration of an object or external service that other developers might not be familiar with. If every single line of code is unintelligible or it isn't obvious what it's doing you have way bigger problems.

Most organizations see PCI compliance as a huge annoyance. It's generally too technical for an executive to have eyes on so it falls to a technical person to enforce it. Once you get big enough merchants tend to go easier on you because it's a huge cost to be PCI compliant and they really want your business. Then shit like this happens.

If your code needs a lot of comments, then your code is not easy to read by definition. Code should be written to be easily read with small functions with names that are self explanatory as to what the code is doing. Comments are great for those little exceptions and cases where the code looks daft but has a legitimate purpose that you don't want someone else to remove, but if your code is 20% or more comments, then they are either completely unnecessary or your code is not well written.

• Self explanatory method names.
• Low cyclomatic complexity
• Good test coverage

Good code should be easy to follow with no function taking more than a minute to read and understand with meaningful names that can be trusted to do what they imply they do. Each function should ideally have 4 or less paths through the code with greater complexity being shoved into another method. Test Coverage is sexy. There is nothing that will make me hate a codebase more than when I have to dig deep down into a code base and find that one little variable that's getting set to null in some peripheral object instead of what it's supposed to be after hours of debugging.

You don't think banks have the money or the interest to support a linux distro that will be a core component of all of their ATM's. Next you'll tell me they pay taxes.

Even if you aren't a vegan and don't care about the environment it makes great economic sense. Animal protein is expensive and wasteful to produce. If a vegan option can mimic what is a fairly plain tasting foodstuff, then the cost savings on a lot of dishes and processed foods would be huge.

If a more declarative/rule based model appeals to you, you should check out Drools.

It is taking away exactly the key features that languages like Java have that make them ideal for business logic. It takes away the generalist properties and ties each line of code into a database process, removing the separation of logic from implementation. It encapsulates functionality without giving access to it by tying procedural code to relationship statements rather than to actual calls, making it extremely vulnerable to the law of leaky algorithms, making it more difficult to both debug and optimize. There's no way this could actually produce scalable, stable codebase that you could use to provide a large scale solution to any business problem.

• Infrastructure ceases to function and an upgrade is the cheapest long term solution.
• The cost of upgrading is less than the savings in productivity, which is frequently true because manpower tends to be significantly more expensive than hardware.