Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What is your current stack?

news.ycombinator.com

Post reply on HN
Print view View original

21–30 of 48 posts

Re: What is your current stack?

#21

Post by wanderingstan »

bikamonki wrote: post #4

If I do my own REST back-end: node/express or good old php. If I go no-backend: parse.com or firebase.com (different use cases). Front-end: BackboneJS and the usual mix (CSS, HTML5, Bootstrap, Jquery, etc) and I am looking into adding ReactJS to the stack. Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc. Not sure if we can call this approach a "stack" but s…

> Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc.

I'd consider this part of the stack -- it's just not done in-house.

Can you list the services that you'd reccomend for those tasks?

Re: What is your current stack?

#22

Post by iEchoic »

itsbits wrote: post #20
iEchoic wrote: post #18

My current stack: - Server: Node & express - DB: Mongo (using mongoose) - Frontend: Knockout.js using components (introduced in 3.2), Cordova when developing mobile. - Hosting (db, services): Azure Pretty standard with the exception of Knockout.js, which I think is criminally underrated following the introduction of components in 3.2, especially given all the recent hype around component/module based separation of co…

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.

Re: What is your current stack?

#24

Post by lfx »

solomatov wrote: post #10

Java - server side / GWT - client side.

Interesting. We used to use GWT for several projects, but ditched for new ones to simple Java backend and AngularJS. Now when I had to fix some bugs, etc it feels so unpleasant to work and kinda slow (for dev). Project still uses old GWT 2.5 since transition to new version & 3th party component replacement would cost too much.

Do you use modern super dev mode and latest GWT version? How this turned out? Are there 3th party plugins repository?

Re: What is your current stack?

#25

Post by aceperry »

dqdo wrote: post #13
dqdo wrote: post #9

I 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…

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…

Sounds like great advice to me. I'm looking at different stacks and approaches now and coming to the same conclusion about using a single technology to reduce the context switching and simplify everything. The idea of taking time to write software for maintenance sounds great to me.

Re: What is your current stack?

#26

Post by solomatov »

lfx wrote: post #24
solomatov wrote: post #10

Java - server side / GWT - client side.

Interesting. We used to use GWT for several projects, but ditched for new ones to simple Java backend and AngularJS. Now when I had to fix some bugs, etc it feels so unpleasant to work and kinda slow (for dev). Project still uses old GWT 2.5 since transition to new version & 3th party component replacement would cost too much. Do you use modern super dev mode and latest GWT version? How this turned out? Are there 3th…

> Interesting. We used to use GWT for several projects, but ditched for new ones to simple Java backend and AngularJS.

We would love to use lighter-weight technology but project currently is about 300kloc and we share code on the client and the server. It's just not the size of application which JS is good for.

> Do you use modern super dev mode and latest GWT version? How this turned out? Are there 3th party plugins repository?

These are great. In 2.7 you can just refresh page and incremental compilation will do the job. It's almost like writing code in JS.

Re: What is your current stack?

#28

Post by sanmon3186 »

dqdo wrote: post #13
dqdo wrote: post #9

I 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…

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…

Southwest is a great example but lifespan of airliner models and software vary a lot. How about 80/20? Stick with one/two technologies for 80 percent and have 20 percent room to try out new things.

Re: What is your current stack?

#29

Post by akbar501 »

dqdo wrote: post #13
dqdo wrote: post #9

I 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…

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.

Post reply on HN