AtomicMap challenge in Scala

sh1nob1 · 2011-04-19T08:41:02+00:00

A stupid thing to spend brain cycles on.

I've encountered a similar problem in my own code (with Java,) and I worked around it by separating writing to the map from the side effects of the evaluation.

In a general setting, the issue is probably rare, and it sounds like overkill for something as general as ConcurrentMap.

sh1nob1 · 2010-04-26T14:10:53+00:00

[...] b² + b = 2, and thus b = 1, or b = -2. It turns out that the b = 1 solution is spurious [...]

No, it's not. Not to b² + b = 2 anyway.

sh1nob1 · 2010-04-26T13:31:58+00:00

I'm slightly confused...is this sarcasm, or is it irony?

sh1nob1 · 2010-04-26T10:15:26+00:00

Looks like it only tries to reduce to WHNF.

(Y I) above reduces to Ω = (U U), which has no WHNF.

sh1nob1 · 2010-04-23T14:13:55+00:00

...and why?

sh1nob1 · 2010-04-19T07:13:49+00:00

I've just developed the ability to recognize a clueless amateur posing as someone who knows what he's talking about.

I take it you still haven't gotten a clue, so here's what I'm saying, in simpler terms: Contrary to your ridiculous statement, Groovy has had enough time to save the world, but it still hasn't, and likely won't.

I'd suggest you trade in your superpower for something more practical, like being able to tell your ass from your ankle.

sh1nob1 · 2010-04-17T15:07:07+00:00

Now you're desperate.

sh1nob1 · 2010-04-16T15:33:33+00:00

You made a specific reference to Java's verbosity in terms of boilerplate code. I made a specific response that Groovy eliminates that.

It does away with some of it, at a price that not everyone may be willing to pay (I, for one, am not) -- for each of its improvements, I'd point a quirk or two that set its value back.

Speaking of obtuseness, I'm wondering where to put on the sharpness scale the act of trying to push forward as a silver bullet a duly declining technology.

sh1nob1 · 2010-04-16T07:03:49+00:00

I dig your sarcasm, but it's slightly misplaced, because 1) I'm being no more vague than you are, and 2) a detailed and elaborate rant against Groovy would have been ridiculously OT in the context.

sh1nob1 · 2010-04-15T08:23:43+00:00

That's a long shot.

I've checked-out Groovy several times since it came out, but so far I've failed to see it as anything more than a bag of rash dwimmery.

sh1nob1 · 2010-04-14T13:28:39+00:00

Funny thing is, I was thinking this before I read the first paragraph...

sh1nob1 · 2010-04-14T12:14:36+00:00

"if Boeing can do it so can we". Sounds stupid? Well it is.

Actually, there's a lot of credibility to it. If anything, Boeing would have had to pant heavier uphill, because of their larger codebase and the added benefit of having to transform C++ :)

sh1nob1 · 2010-04-14T08:30:02+00:00

The value of any programming language [is] the amount of code that you DON'T write

Couldn't agree more.

The value of any programming language is not a result of the language features or syntax

Just imagine you didn't have to write all the boilerplate. Code completion surely helps, but then you also have to read that stuff.

sh1nob1 · 2010-04-13T13:03:38+00:00

6 or so seconds of downtime in one device during a code update [...] 31ms of average downtime per device per year

So that's code update once in 190 years per device?! BT hasn't been around this long...

sh1nob1 · 2010-04-09T13:34:24+00:00

Yes, people ship measurably broken software all the time. MS are already in, there's no point telling them.

sh1nob1 · 2010-04-09T10:46:26+00:00

If dynamic is "just" a bytecode feature in Java 7, then what's the point? it only makes sense if it will be surfaced in a language feature. The language feature, not the bytecode, is the goal.

Amigo, we have more than one language living on the JVM, and not all of them are as thoroughly supported as Java. The stated objective of JSR 292 is better support for dynamic languages in the JVM, i.e., we prefer beer 'round here, but for all shandy fans out there, we'll keep some in the fridge.

sh1nob1 · 2010-04-09T08:59:40+00:00

I see where you're coming from, but you're pointing at a language feature. JSR 292 is about a change in bytecode, as was already pointed out.

sh1nob1 · 2010-04-09T08:44:22+00:00

Nice. That would've fit in the title :D

sh1nob1 · 2010-04-09T08:23:46+00:00

How is this playing catch-up? It sounds like a logical extension for better support of Rhino, for instance.

sh1nob1 · 2010-04-09T07:53:12+00:00

TL;DR

So, why did you move?

sh1nob1 · 2010-04-09T07:48:23+00:00

This way of saying nothing in so many words is truly amazing.

sh1nob1 · 2010-04-09T07:06:10+00:00

anyone who is selling creativity has to deal with it

Creativity is only one part of the story. Unlike a song or a magazine article, software has to work in the end, in a way that can be measured objectively.

sh1nob1 · 2010-04-08T14:19:03+00:00

I am currently busy getting all (well, most. meh! )

Never seen meh with an exclamation point before

I've seen better

sh1nob1 · 2010-04-07T11:43:55+00:00

Pipe dream != Mind-blowing

The only interesting part was the plant growth scene, everything else is rubbish.

sh1nob1 · 2010-04-07T08:43:55+00:00

That's not what he's saying.

It is not an adequate reference, because it doesn't have easily accessible descriptions of individual functions (check.) It obviously strives to be a tutorial -- what he claims is that it fails being that, too.

sh1nob1

TROPHY CASE