Weaving WebSphere: An Internet Christmas

[MCWebsite.Staff]

** This thread discusses the article: Weaving WebSphere: An Internet Christmas **
** This thread discusses the Content article: Weaving WebSphere: An Internet Christmas **
0

[Guest.Visitor]

Weaving WebSphere: An Internet Christmas

** This thread discusses the article: Weaving WebSphere: An Internet Christmas **
Platform independence means code that is not optimized for the platform. If code is not optimized for the platform, then every machine is fundamentally equal. If every machine is equal, you go for the cheapest CPU cycles available. iSeries CPU cycles are not cheap. Thus, platform independence implies not using the iSeries. Is this too tough to follow? Joe: A somewhat flawed analysis but still a reasonable conclusion. Why take a "platform independent" approach? One reason is that, as you point out, iSeries CPU cycles are not cheap and you might want a more cost-effective solution. Another is that platform independence is often a nice side effect of using high-productivity tools like Perl. Twenty years ago, computers were expensive and programmers were cheap. But face it Joe, things are different now. COmputers are now cheap and programmers are expensive. In the past it made sense to worry about every byte and every machine cycle. Now it's more important to optimize the programmers time. Writing apps in high productivity languages like Perl makes more sense since you can deploy your apps much faster. Who cares if the code is not as fast and efficient as code compiled in some propriteary programming language. Most of the time the performance bottlenecks are elsewhere anyways and if necessary you can always slap another cheap blade in the rack. No, as pointed out by someone else in another thread, the only reason to go with OS/400 (or i5/OS) on the Power platform is if you still have legacy OS/400 code. q