AJAX via XMLAsynchronousMessage
It seems to me that much of the interactions that take place over a relatively synchronousAJAX XMLHttpRequest could just as easily have been modelled as asynchronous messages.
It seems to me that much of the interactions that take place over a relatively synchronousAJAX XMLHttpRequest could just as easily have been modelled as asynchronous messages.
If Spring is going to stop putting out maintenance releases to the community at large after either three months or when the next release is out, do we simply need another organization to look at the maintenance branch and bundle up the work for us?
posted at 9:42 AM Labels: open source, spring, spring framework
When looking at systems furniture or other corporate furniture, are some better-suited to agile techniques than others, including pairing and pair-swapping? I was just looking at the Kimball Hum desk, which is appealing in some ways, although it still doesn't match the truly mobile solutions where you could have a workspace but move it around easily (Herman Miller used to have a desk I really liked in that respect, although I haven't seen it recently).
I also have fond memories of using a Huddleboard.
I'm curious if some of you have recommendations with respect to furniture that's worked well for you.
Last time I looked at Scala, I quickly stumbled over the nascent support for Scala in Eclipse and found that I didn't have the energy to work with a JVM language that didn't have good IDE support. It's been a while since then, so it seemed like a good time to look at Scala again and see how support for Scala in Eclipse has improved.
posted at 1:14 PM Labels: development, eclipse, ide, scala
If you think about it, Google should have no problem funding Chrome. With Firefox's small but growing share of the search engine referrals, they're already paying them $55M a year. If Google were able to take over some segment of that market share, they wouldn't need to pay themselves referral fees.
Now, I'm not saying that this is a move on Google's part to take away Mozilla's market share and funding -- I doubt that's a huge factor in their mind. It's not like they can't afford to pay for these kinds of projects in other ways, and there are lots of good reasons for them to pursue the browser as an application delivery platform.
That said, it's interesting to realize that this can, to a certain extent, pay for itself, if it's successful enough.