Since we are living withing a simulation already this doesn't surprise me.

Work in Java for a few years or on a large Java project then go back to C or switch to Python.

It boils down to what you want to do: use best tool for the job. But I wouldn't be caught dead working on a new project/team who decided to use Java as the primary language.

Lazy? Java is overly verbose, a lot of typing.

protected static transient synchronized const unsigned int m;

It loses points in my book for being too verbose.

Gotta love Jack Handey. ....

"If someone tells you you should 'walk a mile in their shoes' you should take them up on that: you'll be a mile away and have their shoes."

That's a lot of porn...

My ranger used to kite dire-wolves... And my tree-hugging druid too.

If you don't like that you won't like:

> [] + []
""

Hmm, I wonder what [] - [] is?
> [] - []
0

How about adding an element to array?
> [1,2,3] + 4
"1,2,34"
And subtracting?
> [1,2,3] - 1
NaN

Come on, jeeze

Isn't Mac OSX certified as Unix S3 compliant since 10.5'ish? Does this help in any way to port a Linux game to OSX?

I am under the impression it is, albeit lack of full OPEN GL support in their video card drivers.

ooop I need glasses.

I don't know enough about Ruby to say anything positive or negative about it. I was just commenting on Python because that's what I know - it's just funny to hear people moan and whine about similar things, which I've heard re. Python. And the quote "Ruby adds nothing to the existing languages" is harsh, C certainly got slapped around in its early days. Who needs to get slapped around more now and kicked off the bus (or at least charged for taking up two seats) is Java.

Python is a great language aside from the whitespace.

But did you know you can add braces using the future module?

Next major release of Python will include braces, so you can get ready by doing this in your code:

>>> from __future__ import braces

You are more likely to "shoot yourself in the foot" so to speak and code can get unmanageable.

In short given too much flexibility you can make the language so different than the norm. 10 people with 10 different styles writing Ruby code on a 2+ year project...come back after a 6 month break take a look and you got a big mess on your hands :) Style guides help there but still.

Bottom line and not just ruby avoid getting "cute" with the language. I got berated by a college prof. because I thought it was a good idea in C++ to overload the ++, -- operators on a stack class to do push and pop! He asked sarcastically why stop with just ++ and --?

I sense something here... is it possibly sarcasm?

About metaprogramming...

https://www.destroyallsoftware.com/talks/wat

Ha, I feel your pain.

This kills languages, Python took a hit with 3. Yes there is 2to3 and maybe other tools but Ruby may suffer the same fate if they keep mucking with common libs and grammar.

Well 1,270 were made between 2004-2007 and 604 were sold in the U.S.

So just looking at the four people who died in the U.S. (that I know of): 2 in the accident with Paul Walker and 2 in the 2006 crash out of 604 cars that's pretty high. Also not everyone can afford $500k+ car, those who do tend to be known in some fashion.

These cars are temperamental, twitchy, and unsafe maybe one of the reasons Porsche stopped making them. If you want a fast Porsche get the 991 Turbo S, albeit not as pretty.