Hacker News new | comments | show | ask | jobs | submit login

Just use what you enjoy.

I recently had a similar experience - on a whim I decided I would learn python by taking a asp.net mvc app I built and have maintained for the last 3 years and port it. So I just needed to choose a python web framework right? omg. So many, micro, mini, full stack, no stack, template engines, wsgi, uwsgi, whoa! My head was spinning

You can be completely overwhelmed just trying to make a decision, I haven't even looked at storage yet but I'll probably just use sqlite (the old .net one used db4o, which ended up being a huge mistake, great tool, pitfa to do maint on)

on a side note, loving python, and I settled on bottle, but I wrote my own template framework called canvas, inspired by the seaside component/tag/canvas classes.. essentially it's all just python code, no html.. example usage is https://gist.github.com/3087622 (i'll push it to github once I'm happy with it, hah!)




That looks pretty neat: the use of context managers seems very nice.

But is "canvas" (and "HtmlCanvas") meant to refer to the HTML5 <canvas> element? If not, I can see that being a point of huge confusion.


no it isn't, and you raise a good point, I'll change it

canvas.canvas() would definitely look weird


I've been writing Python code since 2003 and I still have that problem of having way too many frameworks. I still remember back in the old days where you had to write CGI manually.

I for one am glad for the existence of frameworks, but this can lead to pretty schizophrenic programming. For example, one of my latest projects has 3 front-facing ends. I somehow made a wrong judgment call and ended up with Flask, Bottle and Web.py on each end (the web.py end has been culled just today).


> Just use what you enjoy.

One has to use what the customer or project requires.

If it is something that we can enjoy, great, if not it is a job and the customer should always be an happy customer.


I think the customers in quite a lot of markets don't care about what language you use to implement your software--they only care about what it does.

The same is true for projects: there are relatively few projects that force you to use some particular language.

As people like to endlessly repeat, you should choose the best tool for the job. And, unless there are strong reasons against it, the best tool is one you like.

On a more cynical note: the job market is great right now. If you don't like the technology you're using, it's a prime time to look at new opportunities. Apply to some cool startups doing cool things with cool technologies--at the very least, it'll be exciting :P.


> The same is true for projects: there are relatively few projects that force you to use some particular language.

On the corporation consulting world I work, the technology is always part of the RFP sent by the customer to the consulting companies.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: