3 ms·

OT: Circle CI looks really impressive. May I ask if you used a library like Meteor to build the app?

pbiggar 14y ago
We have a clojure backend, the front-end uses Sammy.js for routing and history, and Knockout.js for data-binding, written in CoffeeScript and HamlCoffee, delivered using dieter (which is sprockets for Clojure). (PS: like the sound of hacking on dev tools in clojure? We're hiring!)
- Gigablah 14y ago
  The downside of building sites that are exclusively client-side rendered is that it stops working if the user has Javascript turned off. That's why I personally use the strategy of rendering server-side only upon initial load, then hooking in client-side routing/templating libraries afterwards. This solves the issue of search engine visibility and client JS support in one fell swoop. (Mustache templates are great in this regard since there's libraries supplied for most languages.) By the way, just a nitpick: your site seems to have a empty margin to the right, which creates a horizontal scrollbar. I'm using Chrome Version 21.0.1180.89 on OSX.
  - pbiggar 14y ago
    We made an explicit choice not to support non-JS users with our product. For simplicity, we don't support non-JS users in our marketing material/web site. We do intend to do something better there, for example by having a no-script pitch for why you should enable JS on our site. We have a very pragmatic attitude. When people complain, we start to prioritize it (thanks for the bug report/nitpick!). If no-one complains, it can't be important. We haven't heard any complaints from non-JS users yet :)
  - bgilroy26 14y ago
    > the strategy of rendering server-side only upon initial load, then hooking in client-side routing/templating libraries afterwards Is there a name for this strategy? How can I read more about it?
- mattdeboard 14y ago
  Hmm... interesting. Do you have a write-up on your tech stack?
  - pbiggar 14y ago
    No. We have it planned but not written yet. Follow http://blog.circleci.com http://blog.circleci.com or http://twitter.com/circleci http://twitter.com/circleci if you're interested, or if we're very lucky you might find it on HN too :)

We have a clojure backend, the front-end uses Sammy.js for routing and history, and Knockout.js for data-binding, written in CoffeeScript and HamlCoffee, delivered using dieter (which is sprockets for Clojure). (PS: like the sound of hacking on dev tools in clojure? We're hiring!)

Gigablah 14y ago
The downside of building sites that are exclusively client-side rendered is that it stops working if the user has Javascript turned off. That's why I personally use the strategy of rendering server-side only upon initial load, then hooking in client-side routing/templating libraries afterwards. This solves the issue of search engine visibility and client JS support in one fell swoop. (Mustache templates are great in this regard since there's libraries supplied for most languages.) By the way, just a nitpick: your site seems to have a empty margin to the right, which creates a horizontal scrollbar. I'm using Chrome Version 21.0.1180.89 on OSX.
- pbiggar 14y ago
  We made an explicit choice not to support non-JS users with our product. For simplicity, we don't support non-JS users in our marketing material/web site. We do intend to do something better there, for example by having a no-script pitch for why you should enable JS on our site. We have a very pragmatic attitude. When people complain, we start to prioritize it (thanks for the bug report/nitpick!). If no-one complains, it can't be important. We haven't heard any complaints from non-JS users yet :)
- bgilroy26 14y ago
  > the strategy of rendering server-side only upon initial load, then hooking in client-side routing/templating libraries afterwards Is there a name for this strategy? How can I read more about it?
mattdeboard 14y ago
Hmm... interesting. Do you have a write-up on your tech stack?
- pbiggar 14y ago
  No. We have it planned but not written yet. Follow http://blog.circleci.com http://blog.circleci.com or http://twitter.com/circleci http://twitter.com/circleci if you're interested, or if we're very lucky you might find it on HN too :)