For information rich applications (ie. B2B-ish), definitely ExtJS. Pretty steep learning curve since, unlike jQuery UI, you sorta have to take all of nothing. We use ExtJS everywhere where using data/information is more…
IANAL but it seems as though a lawsuit would be filed pretty quickly if Apple blocked Adobe's interpreted apps and didn't block Rhomobile/Unity3D/MonoTouch interpreted apps. Seems fair to block possibly harmful…
Agreed that, in some senses, I was trying to force a square peg into a round hole, but the comments on my blog suggest that others share my experience and they're mostly from planet.haskell.org. So I think something is…
plesn, I don't disagree that the reasons are shallow, but it turns out that solving some problems in Haskell is just plain hard. It's precisely because the issues/reasons are basic that it's hard... Also, I'm confused…
For information rich applications (ie. B2B-ish), definitely ExtJS. Pretty steep learning curve since, unlike jQuery UI, you sorta have to take all of nothing. We use ExtJS everywhere where using data/information is more…
IANAL but it seems as though a lawsuit would be filed pretty quickly if Apple blocked Adobe's interpreted apps and didn't block Rhomobile/Unity3D/MonoTouch interpreted apps. Seems fair to block possibly harmful…
Agreed that, in some senses, I was trying to force a square peg into a round hole, but the comments on my blog suggest that others share my experience and they're mostly from planet.haskell.org. So I think something is…
plesn, I don't disagree that the reasons are shallow, but it turns out that solving some problems in Haskell is just plain hard. It's precisely because the issues/reasons are basic that it's hard... Also, I'm confused…