ColdFusion 11: Thank-you Carl, Mary-Jo, many other community members and indeed Rupesh

G'day:
Integers. We "won". Adobe have reversed their position, and they're gonna fix the isValid("integer") bug:

• Rupesh Kumar

  9:18:35 PM GMT+00:00 Mar 4, 2014

  Wow - it is indeed incredible. Thanks Carl for digging this out. We will fix it - we would have a application setting which would bring back the old behavior in case some one needs it. I hope nobody needs to use this flag. 
  
  We will also roll it out in an update for the public beta and we would need your help in verifying and making sure that applications don't break. 
  
  Thank you everyone for raising this and providing this feedback!

Good stuff, Rupesh.

--
Adam

ColdFusion: Of integers and indolence

G'day:

Yes, OK, I'm still banging on about integers and ColdFusion bugs. It's my blog and I can talk about whatever I like! ;-)

You might be aware that I am particularly nonplussed about Adobe's reaction to bug 3712010, which relates to integer validation via isValid(), and how it is broken.

I started by just being mildly annoyed by how ColdFusion can make such a pig's ear of something that should be simply. But the more Adobe (or, hey, let's say it: Rupesh from Adobe) squirms about the place and tries to justify why they shouldn't just bloody fix a fairly obvious bug, the more annoyed I am getting about this. I dislike having my intelligence insulted, and I also dislike the collective intelligence of the ColdFusion community insulted. Especially by someone who very clearly should not be in the business of insulting anyone's intelligence.

It's all getting a bit stupid, but one of the comments posted today on this caught my eye and made my blood boil just that bit more. I've asked Carl if I can reproduce his comment, and he has said it's fine. So here it is. I've dollied it up for formatting, but it's othewise unchanged.

Being loosely typed is often a good thing but...

G'day:
Here's the upshoot from something that bubbled up on Twitter. I'll spare you the replicated timeline this time, and just cut to the chase...