Java FX 1.0 è stato rilasciato

Sun ha lanciato JavaFX 1.0, piattafroma software  di cui ci siamo già occupati in tempi non sospetti.
La notizia è stata ripresa da Slashdot.
Purtroppo leggiamo anche che non c’è al momento una versione per Linux o Solaris:
“The lack of a Linux or Solaris release is a notable absence.”
Però la presenza del codec On2  (usato per riprodurre i filmati di youtube) lascia pensare che javafx voglia competere frontalmente con Flash.

Sul sito di JavaFx è possibile guardare gli esempi, mentre aspettiamo di capire la reazione del mercato per questa nuovissima suite, che tenta di sedurre gli sviluppatori sparsi per il pianeta…

Percorso Formativo Completo

This entry is part 1 of 5 in the series Formazione

(Updated on 2014)
Programma suggerito del percorso formativo:

  1. Object Oriented Programming (OOP) & Java
  2. Consulenza
  3. Design Patterns
  4. ToolBox as a plus:
    1. JUnit e HttpUnit Cookbook
    2. Regular Expressions
      Esempio animato
      Editor per esercitarsi
    3. Linux
      Filosofia alla base di Unix, da “The Art of Unix Programming” di Eric Steven Raymond
    4. Linguaggio open a scelta, diverso da Java: Python, Perl o Ruby
      Cosa provare: RubyOnRails, GoogleAPI in python, librerie CPAN del Perl
  5. Approfondimenti

Javascript and Smalltalk

There is a future for SmallTalk? I was a very strong fan of the SmallTalk language, but in the last five years I have seen more and more contraction of its usage in the IT field.

The OLPC project, which uses also Squeak Smalltalk and its done by the core team fo Squeak, is not going very well.

Anyway, Dan Ingalls, one of the father of Smalltalk, is working on a new project called Lively. It is a rewrite of Morphic in Javascript, especially target  for building a Squeak-like interface.

 The interesting part of this work is a paper outlining the limitation of javascript as programming language. I have tried in the past years to look for ajax and or web 2.0 javascript libraries, but I feel very difficult to develop with them.

From the Paper we underline these parts:

Loading multiple JavaScript applications into the same virtual machine is problematic.[…] For instance, if two programs
happen to use the same names for global variables or functions, the overlapping variables or functions of
the first program will be replaced with the corresponding features of the second program, resulting in
unexpected behavior in the subsequent execution of the first program. Since JavaScript will not typically
give any warning messages or errors in such situations, the resulting behavior can sometimes be a total
surprise; in many cases the errors resulting from such situations may not be discovered until much later.


Evolutionary development approach is a necessity. Due to the highly permissive, error-tolerant nature of
JavaScript, JavaScript programming requires an incremental, evolutionary software development
approach. Since errors are reported much later than usual, by the time an error is reported it is often
surprisingly difficult to pinpoint the original location of the error. Error detection is made harder by the
dynamic nature of JavaScript, for instance, by the possibility to change some of the system features on
the fly.


A lot of room is left in optimizing JavaScript performance. Current JavaScript virtual machines are
unnecessarily slow. Even though JavaScript is a significantly more dynamic language than, for instance,
the Java programming language, there is no fundamental reason for JavaScript VMs to run two orders of
magnitude slower than Java virtual machines.


Memory management capabilities of the current JavaScript VMs are poorly suited to large, long-running
applications. Current JavaScript virtual machines have simple, 1970's style garbage collectors

 The reason of these issue are simple:JavaScript was intially a language for web developers, small and easy to use, and very compact.
Absence of errors or warning is a nightmare, if you care of your digitating time.
And Javascript is slow because no one will write  long script with it.

A very compact and clean discussion can be found in 

Fixing these problems is hard. Until the current  implementation will not provide a better way of error detection, writing javascript code will be a very long and time-consuming task.

And using a so old garbage collector, give a chance to a c/64 BasicV2 to beat your code:  you are awared, guys :)

Anyway, there is a good set of javascript libraries out of there (prototype and jquery, for instance but not only), so you should be quite happy 




Site Update: Happy new editor!

(First published on 2007-01-20)

Hi all, ObjectsRoot now has correct story ordering ontags view!

I am happy to announce I have just installed tinymce on my site.

TinyMCE is a very nice javascript editor, also used in Drupal. What makes tinymce very nice in my humble own opinion, is its easy installation. You do not need complex init procedure: you just tell tiny you want to edit well textareas, and it will do all for you. Because django  (my web framework for the site) has a bit complex way for handling administration pages, this is good news for by TinyMCE

TinyMCE is a very professional product, and has all the things I like in a text editor.

I remember,  in the dark ages of the 2002, ajax was not yet born.

So in that dark era, I was stunned with a very poor javascript editor product, with a very big license to pay to use it.
I was complex to configure, and a nitghtmare to use.
So I am happy to have a very easy-to-edit blog now, and I will be able to write more and more throughts in a scattered way.
Keep in touch, babies!