Tracking change and innovation in the enterprise software development community
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Recorded at:
Posted by Guy Steele on Jan 16, 2008 12:23 AM
Rainmaking - IBM's software virtualization strategy (Jerry Cuomo CTO blog)
WebSphere Virtual Enterprise 3 minute demo
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Software Quality Survival Guide
Introducing application infrastructure virtualization and WebSphere Virtual Enterprise
Your speach looks quite academic. From the purely supercomputing viewpoint you are probaly right. But it mentioned industry and it seems to me that you miss the point if you address industry. Did you know that nowdays fortran is already dead and the schientific computing is not restricted any more to Computer Science Department in the university? Mechanical/Aerospace/Chemical engineers do scientific computing both in the university and in the industry very extensively. There are several million people in this area and almost all of them are using MATLAB+SIMULINK. I can speak for the german academics + automotive/aerospace industry. Actually MATLAB+SIMULINK is a standard in the industry since many years and it already replaced fortran almost everywhere. So you better had to invent a replacement for MATLAB. From your speach I have not seen any advantage of fortress over MATLAB. It looks like you are inventing the same things again. For example a BMW car (I work for BMW) has 20 thousand parameters in its microcontroller and its overall structure has to be simulated and all these parameters have to be numerically optimized. Such new language as standalone makes little sense from the industry standpoint - in order to begin with number crunching you have to get your data from somewhere - read some measurement files in some weird format, show a gui dialog and let the user (yourself) drag a line with mouse to chose another operating point, ecc. So for the industry such new language where interesting only if it were better then MATLAB and would compile to java.
client for Windows that can be used to communicate, share, play or work with others on IRC networks around the world, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists Sohbet branda çadır tente travesti travesti travesti travesti geciktirici seks chat kozmetik file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. mIRC also has a powerful scripting language that can be used both to automate mIRC and to create applications that perform a wide range of functions from network communications to playing games. mIRC has been in development for over a decade and is constantly being improved and updated with new technologies. The latest news about mIRC can be found on the latest news page.
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
2 comments
Reply