The Trello Tech Stack • Hacker News Board

Re: The Trello Tech Stack

#81

Post by bigiain » Fri, Jan 20, 2012, 6:52 AM UTC

davesims wrote: post #65

Not to pick on him, because I think the overall received wisdom on new tech has shifted and morphed a great deal over the last few years, no doubt including Joel's...but I can't resist pointing out that, my how times have changed... http://www.joelonsoftware.com/items/2006/09/01.html In other words, it's nice to see Joel greenlight something like this, I'd say it's kind of a sign of the times in terms of the industry…

To Joel's credit, that was over 5 years ago - which is, like, 35 dog-years ago (which are even shorter than tech-years).

Re: The Trello Tech Stack

#82

Post by sandwiches » Fri, Jan 20, 2012, 7:24 AM UTC

Pretty cool; any insight as to how they deploy code to production servers?

Re: The Trello Tech Stack

#83

Post by strictfp » Fri, Jan 20, 2012, 7:49 AM UTC

" sending changes to Models down to browser clients". _Down_ to the client? He draws the stack with the client on top and the storage at the bottom, and then says 'down to the client'? I have a collegue who also does this. I never figured out why. Can anyone explain possoble reasoning behind this wording?

Re: The Trello Tech Stack

#84

Post by crescentfresh » Fri, Jan 20, 2012, 10:13 AM UTC

Does it just go without saying these days that jQuery is required? Trello uses it, as well as jQuery UI, date.js, and highcharts.js far as I can tell.

I mention it because they mention other parts of the client stack (Backbone.js for ex), but not said libs.

Re: The Trello Tech Stack

#85

Post by wuher » Fri, Jan 20, 2012, 10:46 AM UTC

Great writeup, I wish more companies did this: be open about their tech stack and experiences.

This inspired me to write about how I think, they could've gone even further: http://wuher-random.blogspot.com/2012/01/single-page-web-app...

Re: The Trello Tech Stack

#86

Post by lrobb » Fri, Jan 20, 2012, 1:18 PM UTC

davesims wrote: post #65

Not to pick on him, because I think the overall received wisdom on new tech has shifted and morphed a great deal over the last few years, no doubt including Joel's...but I can't resist pointing out that, my how times have changed... http://www.joelonsoftware.com/items/2006/09/01.html In other words, it's nice to see Joel greenlight something like this, I'd say it's kind of a sign of the times in terms of the industry…

It's also weird to see fc have a "get big, then figure out how to make money" mentality.

Re: The Trello Tech Stack

#87

Post by yesbabyyes » Fri, Jan 20, 2012, 1:55 PM UTC

josephg wrote: post #69

yesbabyyes wrote: post #23

Earlier quoted context omitted.

Socket.io is a great library. When it comes to a contender, I see Server-side Events [1] as a contender to WebSockets. I feel it's a simpler architecture which fits HTTP/REST better than WebSockets in the general case. I built a couple of small experiments/examples using CoffeeScript and Redis [2]; the middleware.coffee in particular is designed to be used together with REST, where if you send "Accept: text/event-str…

Unfortunately, eventsource isn't supported by any current version of IE. It'll be awhile before ES can replace your AJAX/websocket libraries. http://caniuse.com/#search=eventsource

On the plus side, it's supported by Opera Mini and iOS.

For IE and others (Android, I'm looking at you!), I have yet to try it and so can't vouch for it, but there exists a polyfill: https://github.com/Yaffle/EventSource

Re: The Trello Tech Stack

#88

Post by dodger » Fri, Jan 20, 2012, 2:28 PM UTC

wuher wrote: post #85

Great writeup, I wish more companies did this: be open about their tech stack and experiences. This inspired me to write about how I think, they could've gone even further: http://wuher-random.blogspot.com/2012/01/single-page-web-app...

Yep! We intend to use our shiny, well-organized REST API for future development and probably port existing functionality to it, too!

Re: The Trello Tech Stack

#89

Post by Haul4ss » Fri, Jan 20, 2012, 2:31 PM UTC

jcromartie wrote: post #51

edw519 wrote: post #32

Use things that are going to work great in two years. This is one of those remarks that is obvious to someone who knows what it means but mysterious to someone who doesn't. So what does it really mean? - Don't use a technology that, no matter how good, is just too niche for widespread adoption? - Don't use a technology that we'll have trouble finding programmers to support? - Look for stuff that will take better adva…

It might also include things that don't work so great now, but show promise, and will work great in 2 years at their current rate of development.

This is how I read it. He was saying it's alright to go with bleeding-edge technologies, even if they're a little shaky now. As long as they have a good dev community behind them, they'll get better.

Re: The Trello Tech Stack

#90

Post by Flenser » Fri, Jan 20, 2012, 3:24 PM UTC

strictfp wrote: post #83

" sending changes to Models down to browser clients". _Down_ to the client? He draws the stack with the client on top and the storage at the bottom, and then says 'down to the client'? I have a collegue who also does this. I never figured out why. Can anyone explain possoble reasoning behind this wording?

Because from the client downloads assets and we are more used to thinking about what happens from the client's pov.

Alternatively, it could be for the same reason people usually say they're going "up" to a big city, regardless of the direction of travel. The server is the hub and all the clients are down from it. This possibly dates back to when towns/fortifications were usually located on hills.