From: Arved Sandstrom on
ClassCastException wrote:
> On Fri, 04 Jun 2010 14:16:27 -0700, Nebulous wrote:
>
[ SNIP ]

>> None of the nasty things that you have said or implied about me are at
>> all true.
>
> Ah, the more things change, the more they stay the same.
>
[ SNIP ]

Yeah, that turn of phrase I remember. As a constant mantra it's somewhat
creepy...I'd hate to work with the guy because I'd always be wondering
when he's going to completely unwrap.

AHS
--
Real programmers don't comment their code. If it was hard to write, it
should be hard to understand.
-- unknown
From: Arne Vajhøj on
On 27-05-2010 21:32, ClassCastException wrote:
> On Wed, 26 May 2010 09:35:13 +0000, Arved Sandstrom wrote:
>
>> ClassCastException wrote:
>>> Oh, lovely, so it will be another six months to six years in coming
>>> and, when (if) it finally does show up, it will have "designed by
>>> committee" written all over it?
>>>
>>> Maybe it's best to just stick with JDK 6 then. :)
>>
>> Even better, continue working with JDK 6, and if you're a
>> dyed-in-the-wool JVM person, expand your programming horizons with Scala
>> or Clojure.
>
> (defn drop-bombshell []
> (.println System/out "I already know Clojure, actually."))
>
> Yeah, I was a scout once, and still stick to that whole "be prepared"
> thing. :)
>
> Clojure comes in handy when you don't need seriously blazing speed and
> the problem lends itself to a functional style.

Scala is more Java like.

> Actually what Java really needs for speed these days is an API that lets
> you do arbitrary SIMD math on the machine's GPU. That seems to be where
> all the really sneaky optimizations are in rendering/number crunching
> these days, ones that JIT won't get you, and pretty much everything else
> you want to do is I/O bound.

For true number crunching: yes.

But true number crunching is not a primary area for Java.

> Actually, the other thing we really need is OS/JVM integration so the JVM
> heap plays nicer with paging and multitasking.

I believe that both work fine with current JVM's.

> I foresee a day when
> there's a small kernel written in C that bootstraps and provides the main
> API services for a JVM or similar VM, and all user-mode applications run
> in the VM. If the VM is stable enough, they can't crash it, just catch
> unhandled exceptions. The JVM's security features make it almost ideal
> for something like this, combined with its maturity and JIT.

Microsoft did something similar with C# in this research project:
http://research.microsoft.com/en-us/projects/singularity/

Arne
From: Arne Vajhøj on
On 04-06-2010 21:59, Mike Schilling wrote:
> "Nebulous" <nebulous99(a)gmail.com> wrote in message
>> Macros.
>
> He was an SOB. It was a great day for the Philippines when Corazon
> Aquino replaced him. I didn't know he was a LISP programmer too.

Marcos??

Arne

From: Arne Vajhøj on
On 03-06-2010 06:16, Alessio Stalla wrote:
> On May 26, 11:35 am, Arved Sandstrom<dces...(a)hotmail.com> wrote:
>> ClassCastException wrote:
>>> On Tue, 25 May 2010 19:36:47 -0400, Arne Vajh�j wrote:
>>
>>>> On 25-05-2010 18:57, ClassCastException wrote:
>>>>> Is JDK 7 really on the way, or is it just another Duke Nukem Forever or
>>>>> Half-Life 3 -- that is to say, vaporware?
>>
>>>>> Because I swear it's been like *years* since I first heard mention of
>>>>> it and JDK 6 still seems to be current.
>>>> It has been a long time underway.
>>
>>>> But people are working on it.
>>
>>>> And eventually it will come out.
>>
>>>> Lot of people are unhappy with the speed, but ...
>>
>>>> Anyway - Java is so mature so there are very few must haves missing and
>>>> for each nice to have there are 7 different opinions on how to
>>>> implement.
>>
>>> Oh, lovely, so it will be another six months to six years in coming and,
>>> when (if) it finally does show up, it will have "designed by committee"
>>> written all over it?
>>
>>> Maybe it's best to just stick with JDK 6 then. :)
>>
>> Even better, continue working with JDK 6, and if you're a
>> dyed-in-the-wool JVM person, expand your programming horizons with Scala
>> or Clojure. For example, if you're working with J2EE on Weblogic, but
>> see a problem that is really better addressed using functional code,
>> write that portion using Scala, for example.
>
> JDK 7, among other things, is supposed to provide features that should
> benefit functional and dynamic languages, so Scala and Clojure could
> theoretically take advantage of JDK 7, too.
>
> With the JDK open sourced, nothing stops you from downloading it and
> trying the new features, and complain with the committee who's
> designing them ;)

Even before being open sourced SUN put out beta versions of the binaries
for people to try.

Arne
From: Arne Vajhøj on
On 04-06-2010 17:16, Nebulous wrote:
> On Jun 2, 4:22 pm, ClassCastException<zjkg3d9g...(a)gmail.invalid>
>> Well, speak of the [insult deleted] and look who appears.
>
> No, you're the devil.
>
> None of the nasty things that you have said or implied about me are at
> all true.

Nobody missed you around here, so ...

Arne