. (yes = 2*scala + lift)
.Hi all,I attended the talk on Scala and the talk on Lift.Both excellent talks![ I did not attend the talk on Actors(I was cycling on the other side of the Golden Gate Bridge (Mt Tamalpais)) ]...Those talks act as 'teasers' to make developers'eager to know more about Scala'.This is great!But, sometimes, I also have the impression that those talks'preach for those that are already converted'.The point I want to make is the following:when talking to developers about Scala,I am almost always confronted with the fact that theystill think it has a 'steep learning curve'.I tell them that 'once you have climbed the mountain,you can enjoy the view over the landscape' (cfr Mt Tamalpais).So, I really think there is this need for hands on training.Maybe some of you folks should try to convince Sun (or Oracle) Educationto invest in training courses. Not a simple task indeed, but, worth the effort(helps Scala becoming mainstream).ps: I agree that I'm partially saying this out of pure opportunism(I'm delivering Java courses for Sun Education, and, of course,I would be the first one to deliver Scala courses).
Luc
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--
__~O
-\ <,
(*)/ (*)
reality goes far beyond imagination
Awesome idea.
Would be great to establish some kind of curriculum with joint teaching material to be able to offer courses worldwide.
Heiko
here are some thoughts:- agreeing upon the what is probably easier than agreeing upon the howfor example: which IDE to use (if any) during the labs [ Eclipse, Netbeans, ... ] .My experience is that the description of how to do labs should be independentof any tools (it does not make sense to explicitely state things like: in Netbeansgo to this submenu and select that choice and ... ).- I think we should go for 'extreme course development' in the sense thatchanges can be incorporated quickly (any text based format thatcan (in a moderated way) be edited by many people is good(e.g. LaTeX, assuming the existence of templates))[ maybe git would be a perfect candidate for doing version management ]Another advantage of using text based development is that consistencycan be automated: for example, code excerpts in slides can be extractedprogrammatically from the code proper so that all changes to that codeare automatically propagated [ and also propagated in the embedded slidesof student guides ]. I have some LateX templates (and Scala code) to automate all this.[ I have to agree that there is much room for improvement of the look-and-feel(it has been some time since I played around with LaTeX, and I'm not a specialistof LaTeX's beamer package) ]- About the financial model: if it is joint work, then I do not think it makesmuch sense to ask companies like Sun (or Oracle) money for the developmentof the material. If they are willing to make the material part of their curriculum(which implies: visibility via their catalogs),then we can make money by delivering the material.Whether or not the material itself should be freely downoadable by anyonein the world is yet another matter. Again, maybe there should be somemoderated group of people having access to the material.
...Luc
Luc
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
--
__~O
-\ <,
(*)/ (*)
reality goes far beyond imagination
--
Viktor Klang
Rockstar Developer
--
__~O
-\ <,
(*)/ (*)
reality goes far beyond imagination
Cheers,
Alexy
Sent from my iPhone
On Jun 9, 2009, at 4:56 PM, Alexy Khrabrov <deliv...@gmail.com>
wrote: