Group items matching

in title, tags, annotations or url

4. Availability (or Reliability) How long the system is up and running and the Mean Time Between Failure (MTBF) is known as the availability of a program

5. Extensibility Are there points in the system where changes can be made with (or without) program changes?

6. Security I shouldn’t need to go into this one but to be thorough I like this definition of security: the measure of system’s ability to resist unauthorized attempts at usage or behavior modification, while still providing service to legitimate users.

7. Portability Portability is the ability for your application to run on numerous platforms.

We need to get rid of these gratuitous dependencies.  Merely papering over them with a transaction—making them “safe”—doesn’t do anything to improve the natural parallelism that a program contains.  It just ensures it doesn’t crash.  Sure, that’s plenty important, but providing programming models and patterns to eliminate the gratuitous dependencies also achieves the goal of not crashing but with the added benefit of actually improving scalability too.  Transactions have worked so well in enabling automatic parallelism in databases because the basic model itself (without transactions) already implies natural isolation among queries.  Transactions break down and scalability suffers for programs that aren’t architected in this way.  We should learn from the experience of the database community in this regard

There will always be hidden mutation of shared state inside lower level system components.  These are often called “benevolent side-effects,” thanks to Hoare, and apply to things like lazy initialization and memorization caches.  These will be done by concurrency ninjas who understand locks.  And their effects will be isolated by convention.

Even with all of this support, we’d be left with an ecosystem of libraries like the .NET Framework itself which have been built atop a fundamentally mutable and imperative system.  The path forward here is less clear to me, although having the ability to retain a mutable model within pockets of guaranteed isolation certainly makes me think the libraries are salvageable.  Thankfully, the shift will likely be very gradual, and the pieces that pose substantial problems can be rewritten in place incrementally over time.  But we need the fundamental language and type system support first.

On the Desktop - Dolphin creates 500k exe’s with ease - its a 1 button click (you just have to follow some of their easy put things in packages rules).

Remember LAN MAN? OS2? Both were heavily endorsed by Gartner.

I laugh when people say poor performance on older hardware was a mjor Smalltalk weakness. We routinely delivered applications that ran on 386 and 68020 processors with 8MB RAM. And yes, they were quite snappy. No, the reason Smalltalk didn’t catch on is because Sun spent more money on Java marketing than was spent on all computer languages combined, since the dawn of time.

I’ve listened personally to whiny ROR programmers groan and whine about PHP devs LEARNING ROR and undercutting them.

I didn’t fall for it for the marketing. I fell for WORA, for the language/runtime separation, for the multi-vendor approach (Sun never wanted to be the single provider for any Java centric product niche, and in fact was never the leader), for the comprehensive set of vendor-neutral APIs for all sorts of execution environments/applications,

For now I would like to see more use of Smalltalk like constructs in Java (Groovy).

Smalltalk must have sofisticated CASE tools, business process simulation tools, large development environments etc. etc. etc.

I stayed to teach Smalltalk since 1993 and am very happy about this information. Each academic year, we produce a small group of new Smalltalkers in the Czech Republic.

Joe Barnhart // Apr 4, 2009 at 2:48 pm At the company where I work, we have used Smalltalk for 19 years. Our tiny team of programmers has beat the pants off of competitors who employ teams 100 times our size.