Plain ol' LAMP stack here (with some extra goodies thrown in - memcache, varnish, redis). You should use what you're most productive with, not the new, shiny thing of the day.
What is your current stack?
41–48 of 48 posts
Re: What is your current stack?
#42Earlier quoted context omitted.
knockoutjs is something i loved to code. Althgh its long time now when I had a look. Does that still fire all bindings together?
If it's been a long time, you should definitely take a look again at components, which really feel like the thing knockout has always been missing. All bindings are still fired upon applyBindings, but I haven't encountered issues here - it's still once on page load, and I can't imagine that it's much different than building the DOM initially using handlebars or react.
I would surely make time for KnockoutJS. But currently I have been following flux which is quite easy to implement althgh I am still not sure how it works with routing, 3rd party libs like some charts etc.
Re: What is your current stack?
#43Python / Django / Postgres / jQuery
Currently trying to learn iOS development with Swift.
Re: What is your current stack?
#44Earlier quoted context omitted.
In my opinion, web technology has become so advanced that the technology for the most part should not matter as much. Unless you are doing something on the scale of Facebook or Google, your technology usually does not matter. Just choose the stack that you are most productive with. And some are more productive than others. When choosing a technology stack I look to Southwest Airlines for inspiration. I might sound st…
I have recently been going the other direction from the "Southwest model". It's on a case by case basis, but if it takes less time to learn and use a technology that is purpose built then I'll invest the time to learn / use something new. I find for some situations it's less time and effort to use the right tool for the job vs. trying to make one tool do everything.
One place where I am often tempted to break the Southwest model is using Rails for an app server and Python for machine learning. I really believe Rails is a better choice for quickly building and adapting web applications, but Python beats Ruby hands down for ML work, both exploratory and in production. If I knew I was building an ML-heavy application right from the start I'd probably use Python for everything, but more often I find places where an existing Rails project could benefit by adding an ML component. Webdev and ML are easy to segregate, architecturally and personnel-wise, so I don't think the impact of using both is too bad, but I'm curious what others think about this. Does anyone else use both languages together? If so, what is the size of your staff?
Re: What is your current stack?
#45Re: What is your current stack?
#46I worked at 2 start-ups so here are the technology stacks: The first company was started 3 years ago and our technology included: (1) Python-Flask (2) Postgresql (3) SQL Alchemy (4) JQuery for web (5) Objective C for IOS (6) Bootstrap In my second company we wanted to take advantage of the growing ecosystem around Node. We also did not want to have to manage a DB, migrations, and server scripts. Our rationale is that…
I see a trend here, I'm also solving most cases with no-backend solutions. In your opinion, what would be the downside of Firebase? Did you have to work-around any limitation? Also, did you try Backbonejs as well? Can you compare it to Angularjs? I am thinking about giving Angularjs a go but would like an opinion from someone who's already using it in prod.
There are two downsides to Firebase. The first one being price. For certain applications (e.g., photo sharing app) it does not make sense to use Firebase due to the high cost of storage. I would just use AWS in this case. The second downside is that it takes longer to run SQL-like search queries on the data. Depending upon your application, this might be important and Firebase does not do this well. What Firebase is good at is make the development process very quick and for real-time applications the set-up is much simpler than web-sockets.
I have tried both Backbone JS and Angular JS and in my opinion, I like Angular's separation between the front-end html and the model. Reading through Angular is much faster than reading through Backbone code because Angular is very opinionated. I like opinionated frameworks and languages (e.g., Python) because if there is only one right way to do something, it simplifies the code greatly. Some people don't like Angular due this structured approach and opt for Backbone. As for performance, there really hasn't been any problems with Angular and Firebase. I am not sure where the complaints about performance comes from.
And just one last comment. I augment AngularJS with Jquery and Lodash. For some functionalities, I like to work directly in Jquery or Javascript rather than use the Angular method. I find this much simpler than stick 100% with Angular and in order to keep this logic clean, I keep the Angular and Jquery code separate.
Re: What is your current stack?
#47I am using openresty,couchdb and jquery.
Openresty because it so much fun :) It uses lua which is a very pleasant language to work with (I love the idea of multiple return values from functions) and it built on top of nginx which is a big win for me since I always use nginx in front of my app server.
With openresty I can use nginx both as an app server and as a proxy. I think that if anyone is already using nginx they should look into openresty because it opens up so many possibilities.
couchdb because of it's ease of use. It has a simple http api that works well with openresty's `location.capture/capture_multi` capabilities. It has a server side javascript environment which can be used to validate data/render templates etc,the common js module system is very capable. It also gives me an excuse to have erlang in my stack, ready just in case.
jquery because it is reliable. The other javascript framework that I like is knockout js but I use it only when I need to have a complex client side logic and knockout js works well with jquery.
Re: What is your current stack?
#48Python, Django, Postgres, Jquery