leonkenneth

Very excited to see these kind of improvements. Coming from Rails to Django I've been a bit disappointed in the amount of things provided out of the box for a SaaS app (the main exception being of course the admin). Even in the ecosystem, I find packages to be a bit more messy and less production-ready than in Rails. Granted I'm fairly new to it, and the design philosophies are different

If your target browsers support it, you can use the `sandbox` attribute and avoid supplying the `allow-top-navigation` flag to prevent this behaviour.

Granted, this won't prevent other framebusting techniques such as checking the parent before rendering.

I am not a maintainer and I just tried it briefly so I am not 100% sure of the allegations they make on their front-page, but it seems like http://gridstylesheets.org are using Workers to run their layout algorithm (Cassowary Constraint Solver) and absolute-position elements (using 3D transforms).

EDIT: Searching for "Worker" right now didn't bring any mention, but it seems it is a very recent edit (cf https://github.com/gss/gss.github.io/commit/d6a931e3629d4b5d...).

Our stack is Angular on the frontend and Node.js + MongoDB on the backend for now.

The main issue are our servers being on AWS Europe, will move some closer to the US soon :)

Also, picking one or two of these skills makes you stand out a bit more for potential employers looking for these particular skills.

A bit like picking a vertical in a market.

Actually it already has, see http://www.facebook.com/note.php?note_id=10150172618258920.