Gradle: "Gradle combines the power and flexibility of Ant with the dependency management and conventions of Maven into a more effective way to build."

That is like making headcheese and than coding it with anthrax.

Ah yes, the battle cry of the agile apologist. "If it didn't work, you are doing it wrong"

Any one size fits all process is a failure.

The combination of enforced white space, and not making everything an expression has significantly weakened Python.

The workarounds for Python's gimped lambdas for instance(they suck because of the above two issues) are truly bloated and horrifying.

Tacked on scoping(self isn't required because 'explicit is better than implicit', that is just spin. It is required because once upon a time, Python had no scoping) and OO just add to the Python suck-fest.

If explicit is truly better than implicit the language wouldn't be filled with implicit elements. Don't believe Guido's spin.

Ruby 1.8 and earlier has a AST interpreter written in C.

All, or nearly all of the standard library for Ruby(regardless of version) is written in C.

To say Ruby is written in C is not wrong in the slightest.

Wrong.

The Linux version crashes often, like 10 times a minute. It does run and render poorly on Linux, while the FF version palemoon is at does not, so there is definitely something wrong with the Palemoon devs

Google is a spyware company. That makes them evil, by default.

The fact that they are shoving themselves everywhere, shows that they want to be evil overlords.

Violence is the only way to stop these sanctimonious pricks.

You see some fucktard wearing one, walk up to him and smash his face in. After you do that, stab him or her in their genitals because they do not deserve to procreate.

It's the only way to be sure.

Name calling != ad hominem

HTML5 & XML have nothing to do with client-server.

Javascript can be client, server, or both.

REST is just the obvious consequence of HTTP and doesn't need annoying acronyms and meaningless buzzwords like RESTful.

Sockets implement the client and server. HTTP sits on top of that and shuffles the crap you mentioned back and forth.

I actually remember when /. had mostly good technical discussions.

Proving that your unit tests are complete and correct is as difficult as proving the actual program being tested is correct.

Yup, I kept my master thesis(written in Latex) in mercurial.

Liberal Republicans are no longer welcome.

glibc is LGPL, so you can dynamically link to it if you don't want your app to be GPL'd.

Swing is a little verbose and unwieldy, but people tend to forget(or maybe they just don't know) that it is a very low level GUI library that is great for creating custom, reusable widgets(assuming you don't use crap like anonymous inner classes). It is not meant to be a high level GUI library. For a layout manager use Miglayout, seriously, how did this not get included into the standard library?

JavaFX 2 is much easier to manage and layout as long as your requirements don't call for seriously complex GUI elements. It ditched that crappy language that plagued JavaFX 1 and uses a simple functional approach.

File choosers - again Swing is meant to be a low level GUI library.

Java doesn't integrate well with underlying system so why are you using java for command line apps?

Unsigned types? I would prefer that they add in integer overflow protection instead.

They should deprecate interfaces and add in mixins over multiple inheritance. It has all the advantages of both, without the boilerplate of interfaces and potential mess of MI. Could you imagine the mess that the typical over-engineering of Java would make of MI? The horror!

The point is that lambdas don't have to be tied to the class and can easily change on the fly.

I never understood the draw of anonymous inner classes, or plain old inner classes, especially for GUI code. I never used it, because I hate repeating myself and that is what this clunky mess causes, and it also makes it difficult to reuse the code with different behaviors. I always just had a method in the GUI widget class that accepted listeners dynamically so behaviors could easily change in my Swing library I built up.

Following Java conventions leads to a bloated, un-DRY and ultimately difficult to maintain code base.