Linked by Thom Holwerda on Sun 30th Sep 2012 20:15 UTC, submitted by MOS6510
Thread beginning with comment 537141
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
dikatlon,
"So whats the language I should use then?"
If you don't have your own server at your disposal, then there's no denying that the widespread availability of a language is a compelling reason to use it. For better or worse, network effects have driven me to hypocritically use PHP simply because it's popular with clients.
My own personal projects are more geared towards system programming. But if I were to choose a new web language to learn today it'd be Opa. It seems to be a very welcome radical shift away from the multi-tier approach of SQL/PHP/HTML/CSS/JAVSCRIPT/DOM into a new more convergent paradigm. Not that I can recommend something I have zero experience with it, but I'm never the less extremely interested in what it potentially offers.
My interest in Opa was sparked here on OSNews, actually:
http://www.osnews.com/story/25564/Programming_Opa_Web_Development_R...