It turns out that as The New York Times says, Google is not building a phone. They’ve built (bought, really) a phone platform called Android. It’s Java on Linux, and it’s open source, but notably it is not J2ME based. Reportedly it will run J2ME apps, but the SDK makes the Android API look more like the BlackBerry’s Java API than J2ME. It’s a full featured API that isn’t a least common denominator of all possible mobile devices.
Continue reading “Google Gives J2ME the Finger, but Still Needs a Carrier Partner”
Evaluating Future Web Application Technologies
Technical Architecture is a Form of Investing. I’m reminded of this sort of thinking because of recent news from RubyConf 2007.
Continue reading “Evaluating Future Web Application Technologies”
Technical Architecture is a Form of Investing
Technical architecture (the act of researching and specifying a set of technologies to address a particular need) is a form of investing. Sadly, like stock market investors, many technical architects are blinded by hype, hero worship, tribalism, and short-sightedness, and make poor decisions as a result. A comparison between current web application development issues and the stock market may help you to avoid these tendencies in yourself or your team.
Continue reading “Technical Architecture is a Form of Investing”
ActiveRecord: the Visual Basic of Object Relational Mappers
I’ve been working with Ruby on Rails intensively for several months, and I’ve finally found a place where Rails can’t readily be extended to do what I want. It’s ActiveRecord, which is probably the most controversial part of Rails.
I’m reminded of a James Gosling quote disparaging Microsoft tools, particularly Visual Basic: “The easy stuff is easy, but the hard stuff is impossible.” There’s a parallel between VB and Rails in this instance, in that if you only let yourself use the high level tools, the hard stuff is impossible, but the designers specifically tell you to do the hard stuff using a lower level toolset. The controversy that surrounds “X can’t do everything, therefore it sucks” should really be focusing on the feasibility of going through that trapdoor to do things “the hard way”. This is what Delphi did, which is why so many folks chose it over VB; it made the hard stuff easier.
Continue reading “ActiveRecord: the Visual Basic of Object Relational Mappers”
Immature developer attitudes revealed in flames regarding CDBaby
Derek Sivers of CDBaby kicks ass. He got a sophisticated and very very user-friendly, efficient, straightforward e-commerce system (including the back-end systems) written in PHP. Based on what I’ve read, he’s up there with Phil Greenspun in my opinion; that is, he’s among those who understand strategy and customer service and low-level technology and are able to build systems that don’t suck, resisting the temptation to be distracted by technological panaceas and fads. I may disagree with their individual technology decisions, but their higher-level thinking is excellent, so they’re definitely in the class of people who I’ll give the benefit of the doubt.
So when I read 7 reasons I switched back to PHP after 2 years on Rails I was a bit surprised, but not much. He’s experienced with PHP (he says he’s written 90,000 lines of code for CDBaby!), and has a huge installed base of code he wrote and understands intimately. He tried Rails, it didn’t work the way he wanted, and he went back to PHP. It was immediately obvious to him that this was what he should continue using.
The most shrill and arrogant among the Rails community have been rather unkind, partly due to this rather poorly written Slashdot headline that misrepresents what Derek says in his article.
Continue reading “Immature developer attitudes revealed in flames regarding CDBaby”