Archive for May 1st, 2009
Google business cards
What could be a better sign of the times than a business card that simply suggests one Google your name for contact information? Google is doing just that, in fact giving away 10,000 sets of 25 cards free to the first people who request them. It’s part of their effort to promote Google Profiles, which incidentally is a great way to get your name, profile, and whatever links you desire into the very top search results for your name.
Mine are ordered…
The ecomony killed the SOAsaurus?!
I’ve seen a bunch of “SOA is dead” articles floating around, but you’ve gotta love the helpful diagram on this one!
However, I do agree that it would be great to never have another “what’s the best ESB?” or “WS-* vs. REST” debate again; they’re right up there with vi vs. emacs, where to put my curly braces, where we should go for lunch, and should-I-listen-to-you-or-just-shoot-myself-now?
Seriously though, why do people see things in such absolutes? There is always a new thought advancement just around the corner, and in this case I think it’s absolutely SaaS, cloud computing, and in general leveraging “the grid” to get powerful, aggregate functionality from a bunch of different (and cheaper) sources instead of building it all on one mega-architecture somewhere. Big changes in software thinking don’t come out of geek think tanks, they evolve organically out of lots of lots of little pieces. A component of this will always be Big Coporation’s IT strategy, but add to that today’s tight budgets and the abundance (and acceptance) of using the internet for “everything” and you get a clear trend towards life in the cloud.
Instead of worrying about whether [insert your favorite acronym here] is deprecated you might as well get used to change, because it isn’t going anywhere.
GXT 2.0-M1 dynamic sizing issue
Recently I commented on a rather severe change in GXT 2.0-M1 with regard to dynamic sizing via percentages not being converted to final HTML as expected with some components. For anyone else experiencing this issue, here’s my support thread which also includes a very simple example app illustrating the problem.
So far our workarounds have been:
- Explicit fixed sizes, ugly but easiest in some tricky spots (not resize-proof)
- Fixed sizes derived from parent, e.g. parent passes in its height/width minus any margins and borders (resize-proof only if parent size changes are manually propagated down)
- Add additional wrappers/children so that the problematic components delegate to, or inherit from, one that works (resize-proof only if parent size changes are manually propagated down)
- Implement “smart” post-render sizing based on actual height/width of parent (resize-proof as long as sizing methods are called on resize, most robust, probably the most invasive)
Java performance basics
A good reminder of some little things in Java that can make a big performance difference, but are easy to forget:
Java Performance: The Return of the Usual Suspects (Updated)
Recent Comments