4 ms·
My policy is to stick to a couple of stacks for projects I will have to maintain 5 years down the road: currently Python/PostgreSQL for server side code, and An
by Xixi 13y ago
My policy is to stick to a couple of stacks for projects I will have to maintain 5 years down the road: currently Python/PostgreSQL for server side code, and AngularJS or Unity for client side code (depending on the nature of the project, but really there's not much overlap there). It will definitely evolve whenever I find something warranting the switch, but the bar is set pretty high. At the end of the day it's what you ship that matters, much more than how it's built.
On the other hand, when I get to do a short-lived project I tried to use a new technology: that's still the best way to learn, plus it's loads of fun. If it's great then I start using it for longer term projects: that's how I found (and so far sticked to) AngularJS.
In 2013 I shipped small projects built on top of nodejs, chicago-boss (erlang), meteor, but also RethinkDB and coffeescript. RethinkDB genuinely seems like a great document store: I will probably give it a second shot when it's more production ready.
- rdtsc 13y ago> My policy is to stick to a couple of stacks for projects I will have to maintain 5 years down the road: > On the other hand, when I get to do a short-lived project I tried to use a new technology: Hey, that's a pretty good idea, I like it. So what are your impressions so far on Chicago Boss, and what do you like about RethinkDB? I have been following those as well but haven't got a chance to try them yet.
- Xixi 13y agoTo put things in perspective my goto stack is Django/Celery/RabbitMQ/PostgreSQL. Chicago Boss is quite impressive in that it replaces all of that (except PostgreSQL, though for an adequate project you could use mnesia instead) in just one piece of software, thanks largely to Erlang/OTP. With boss_mq you get your websocket/comet stuff for free, while with Django the best I found so far is to use the RabbitMQ-WebStomp plugin. The less impressive part is the general lack of polish: for instance the Django templating system is quite forgiving when it comes to types and data you feed it with. Chicago Boss not at all, which can be frustrating. The lack of community around Chicago Boss is probably the biggest downside though. Anyway I got a working demo product, which was good enough to land a bigger project. For that one I moved back to my usual stack, to avoid codebase fragmentation. I'll probably give Elixir and Dynamo a try if I get an adequate project...
- rdtsc 13y agoThanks for replying. That makes sense. The number of included features is what I liked about Chicago Boss as well and I can see how a small community would make it harder to get started.