When I was looking for my next language after Perl, I first went to Java and then C#. Neither worked out for me, personally.
There's just so much extra complexity and boilerplate you have to deal with. Is this class going to be abstract, static, sealed or partial? What about this method, should it be public or not? How about making it void? No wait, let's make it virtual instead! Maybe we should do the whole thing using interfaces to everything? I get why all those options and restrictions exist, so you can architect very locked down object models and APIs so that you can enforce the way components are used. I suppose it enables some optimizations and efficiencies in the way the code is executed. It's just that for me, all that gets in between me and solving the problems I want to solve.
Honestly, I don't have the patience. I'd rather just build stuff (see sig below). Python lets me do that.
There are other options. Ruby looks really cool. One of these days Perl 6 or perhaps even Python 3.x might be an option (that's a joke. If you choose Python go with version 2.7 - seriously). If you really have to run stuff in the browser, Javascript is your boy. But I went with Python back in around 2002 and never looked back. It's slowly been taking over the world ever since.
Cards on the table, if you really want to do web programming there's a good chance javascript is going to take over that whole industry, server side and all. Node.js is apparently awesome and the future, which I have no reason to doubt. It's just that JS gives me headaches. I've tried the tutorials and it's all just mumbo jumbo. I guess you really can't teach an old dog new tricks and I'm a bit past my prime on the learning whole new concepts from scratch front. If I want to whip up a web service I use the Python Flask library and if it absolutely has to present a web front end I randomly mess with the CSS until it's not too badly broken.
Simon Hibbs
There's just so much extra complexity and boilerplate you have to deal with. Is this class going to be abstract, static, sealed or partial? What about this method, should it be public or not? How about making it void? No wait, let's make it virtual instead! Maybe we should do the whole thing using interfaces to everything? I get why all those options and restrictions exist, so you can architect very locked down object models and APIs so that you can enforce the way components are used. I suppose it enables some optimizations and efficiencies in the way the code is executed. It's just that for me, all that gets in between me and solving the problems I want to solve.
Honestly, I don't have the patience. I'd rather just build stuff (see sig below). Python lets me do that.
There are other options. Ruby looks really cool. One of these days Perl 6 or perhaps even Python 3.x might be an option (that's a joke. If you choose Python go with version 2.7 - seriously). If you really have to run stuff in the browser, Javascript is your boy. But I went with Python back in around 2002 and never looked back. It's slowly been taking over the world ever since.
Cards on the table, if you really want to do web programming there's a good chance javascript is going to take over that whole industry, server side and all. Node.js is apparently awesome and the future, which I have no reason to doubt. It's just that JS gives me headaches. I've tried the tutorials and it's all just mumbo jumbo. I guess you really can't teach an old dog new tricks and I'm a bit past my prime on the learning whole new concepts from scratch front. If I want to whip up a web service I use the Python Flask library and if it absolutely has to present a web front end I randomly mess with the CSS until it's not too badly broken.
Simon Hibbs
Last edited: