An interview with Yukihiro "Matz" Matsumoto

Riporto da HN:

Ciao :-),

2012/11/27 Marcello B. [email protected]

Riporto da HN:

http://fredwu.me/post/36493181321/an-interview-with-

yukihiro-matz-matsumotohttp://fredwu.me/post/36493181321/an-interview-with-yukihiro-matz-matsumoto

Ciao :slight_smile:

Grazie !
:slight_smile:

Fra l’altro guardando MRuby ho colto questa cosa che mi era sfuggita

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=59579

““ISO/IEC 30170:2012 specifies the syntax and semantics of the computer
programming language Ruby, and the requirements for conforming Ruby
processors, strictly conforming Ruby programs, and conforming Ruby
programs””

Quindi, al di l della ml con post in giapponese (e della difficolt di
leggere sorgenti in C di ruby MRI) quali sono i grandi problemi di cui
parlava Brian F. a RubyConf Denver 2012 ?

Il fatto che Matz faccia un po’ come vuole senza ascoltare troppo i “big
player” dell’industria che hanno investito milioni di dollari in codice
ruby, rails ?

Che non esista un committee board pi o meno formale tipo java jcp,
python
pep dove discutere l’evoluzione del linguaggio ?
Fra l’altro il java jcp non che funzioni cos bene (in quanto ad
evoluzione del linguaggio :slight_smile:

Matz non ha certo bisogno di me per difenderlo (ci mancherebbe)
Per mi piace (molto) il suo approccio “mi piacciono tutti i linguaggi,
prendo idee da tutto e tutti”
http://www.youtube.com/watch?v=hgs_fVfsduA&feature=relmfu

E finora, negli anni, non mi pare abbia fatto danni “rilevanti” :wink: con
modifiche evolutive “di testa sua” tali da rompere tutto e causare
problemi, perdite di milioni di dollari (alle inc che hanno investito
tanto
in ruby, rails).

Ciao,
Sergio

Il giorno 27 novembre 2012 17:10, Sergio B.
[email protected]ha scritto:

Grazie !
:slight_smile:

""High performance computing.

In University of Tokyo a research student is working on an academic
research project that compiles Ruby code to C code before compiling the
binary code. The process involves techniques such as type inference, and
in
optimal scenarios the speed could reach up to 90% of typical
hand-written C
code.""

In effetti potrebbe essere una buona idea (pseudo-compilatore in C)
Poi tutto avviene nell’ombra, chiusi in universit, laboratori nipponici
(molto giapponese :slight_smile:

""I believe the most effective way is to rewrite the architecture, and
this
is exactly what Twitters been doing. During the rewriting process the
Twitter engineers wanted to take on more challenges so they picked
Scala.
Because Scala is a compiled language it has great performance, so it is
a
fine choice for the new architecture.

My opinion is that when your system is still in its growing stage, it is
far more important to have the ability to react quickly to changes, and
thats what a highly flexible language such as Ruby offers. Once your
system reaches to a point of maturity, stability and success, then to
have
a new architecture that saves on resources makes sense.
Twitter only chose to use Scala for its core components, the web
front-end
and many of their internal tools are still using Ruby. As a matter of
fact,
I paid Twitter a visit last month and talked to many of their engineers
there - Ruby is still in great use.""

+1
Uomo saggio :slight_smile:

““I think in China there might also be languages that emerge from the
right
time that will eventually be a global success.””

Con la crescita di progetti open source fatti da cinesi.
+1
Lo penso anch’io.

S.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs