Got a web idea ,cant code weblangs: How to pick 'em up
Hey Folks,
I had been programming for quite some time, but I have coded most of the parts on C,C++ and Assembly(yes, assembly for ARM for coding crypto algos) So as you can understand, I dont have much experience in web based technologies.
So lets say, I want to be self reliant and start coding on my own. How do I start? :)
9 comments
[ 3.0 ms ] story [ 28.2 ms ] threadI would recommend against going with PHP (especially) since you say you already have coding experience. As such the usual "PHP is easier to learn" argument hardly holds and I think the more consistent style of libraries is more pleasant for experienced programmers.
To be frank,I never did start with PHP, but yes I did flirt with Perl. I know a bit of Perl,(though embarrassed to admit,I lost my patience with Perl midway)
As for Ruby, I strangely had the impression, that I can't attempt at it, without knowing PHP and others.
So anyway for RoR or Django, do I need to learn Ruby and Python respctively to start over, or can I jump straight to it. I have coded in C# and did some personal db work in MySQL . If that helps.
(Also, the #python IRC channel on FreeNode.net is a truly excellent community!)
Java has some excellent web frameworks. My personal favorite is Wicket, but there are many others.
Yes, I did hear many good things about Java as a programming language, right from my grad days. C++ is not a pure oops, java is a pure oops, and some other cool stuff.
As I understand, going to Java will be "grammatically" approach but Django and RoR will be a quick and dirty way. Am I right?
http://en.wikipedia.org/wiki/Duck_typing
Also, Java is not pure OOP in any real sense of the word. It still has primitives, and plenty of other reasons.
All I was saying that if you're accustomed to statically-typed languages with pointer/reference passing semantics and limited FP usage, the manner in which you think is likely to mesh better with Java. And in that sense, you'd probably be more productive out of the gate with it than with Ruby.
Or maybe not - learning about servlet containers and how Wicket overlays it, and Wicket's own component-oriented stateful approach could be fairly steep.
This is not an easy question to answer, and is almost entirely dependent on your experience and disposition.