Choosing a Web Framework/Language Combo for the Next Decade
jacquesmattheij.com
Choosing a Web Framework/Language Combo for the Next Decade
1–10 of 228 posts
Re: Choosing a Web Framework/Language Combo for the Next Decade
#2Re: Choosing a Web Framework/Language Combo for the Next Decade
#3Re: Choosing a Web Framework/Language Combo for the Next Decade
#4So Xamarin is Microsoft now? Better tell them, because they don't know it yet. Clojure is a .NET language as well by the way.
Re: Choosing a Web Framework/Language Combo for the Next Decade
#5Re: Choosing a Web Framework/Language Combo for the Next Decade
#6Judging by how fast technology is evolving nowadays I can't even imagine what is going to happen in 10 years from now... We might not even have the Web... I don't think nowadays you can choose something for the next decade. Maybe for the next 2 years Maximum!
Re: Choosing a Web Framework/Language Combo for the Next Decade
#7Re: why there were so many "PLAY!" results in Google, that would likely depend on the query you use. Something like "play framework" would probably match for any page where someone said "I will play with this framework".
...which is another reason why "Go" was such a bad idea for a language name, BTW.
Re: Choosing a Web Framework/Language Combo for the Next Decade
#8"I still haven’t forgiven Microsoft for their countless misdeeds so Asp/C#/F# are all right out." So Xamarin is Microsoft now? Better tell them, because they don't know it yet. Clojure is a .NET language as well by the way.
Re: Choosing a Web Framework/Language Combo for the Next Decade
#9I love Kohana (for a PHP framework) ... too bad it's no longer being developed.
So you are absolutely right. Will drop it from the list to try and will update the article.
Re: Choosing a Web Framework/Language Combo for the Next Decade
#10The lead developer, Qiang, is literally the second most active developer on github[0], so it's not like they're not trying - the guy is currently on a 370+ day streak - it has taken a huge amount of effort for them to get to this stage.
I would personally build on the beta at this point because I have a lot of faith in the core team and they've had a lot of time to iron out any major problems, at this stage any changes are likely to be quite minor or fixes, so the real release will probably ship before your new project does.
Kohana seems dead and CakePHP has historically been rather slow and ungainly.
The lack of library support for Lua is a bit annoying, but it's getting better and can possibly be mitigated by using Lua's FFI to talk to C. If the eco-system was a bit more mature OpenResty[1] would be pretty compelling.
0. https://gist.github.com/paulmillr/2657075 1. http://openresty.org/