undershirt

I'd be interested in hearing what you think about the article I linked then. Jade is so close to Hiccup, except you can use it alongside your code.

Jade/Handlebars don't map to React components.

Or use a language that makes it trivial to mix data with logic, so you end up with something like Jade/Haml but with the power of macros.

   [:div
     (for [p ctrl.pages]
       [:a {:href p.url} p.title])
     [:button {:onclick ctrl.rotate} "Rotate links"]]

Is the only difference really that Mithril has replaced "React.createComponent" with "m"?

The limitations of creating the view in JS seem invisible, yet visceral to us. I think the reason it is jarring is a fundamental expressivity problem of JS not being able to match templating logic of Handlebars like for-loops and conditionals, despite JS having these statement constructs.

An elegant templating solution is a result of Lisp's mixing of data and logic, something called Hiccup in the ClojureScript community, which I've written about here [1].

[1]: https://github.com/shaunlebron/jumping-from-html-to-clojures...

looks like the annotations on genius have this interpretation as well: http://genius.com/46404

I'm not saying this makes sense, but the perception of an employee wanting to leave a company goes from "terminable flight risk" to "an asset worth fighting to keep" as soon as you get an offer from another company. This is why employees never share that they're looking for work until they've received an offer, which allows negotiation. It's a strange reality I think.

My condolences that you're going through this. You did good demanding what you're worth. contact any tech headhunter in your area, and you'll find work in no time.

If JS developers want a concrete example of Lisp's benefits, you only need to look at React's JSX syntax-- it lacks conditional logic and loops. To see why, you kinda have to see how React components are created in ClojureScript's lisp syntax, it's really elegant: https://github.com/shaunlebron/jumping-from-html-to-clojures...

we essentially peel the globe like an orange and stretch to fill the empty space. The poles have the most empty space: http://i.imgur.com/JnRijN9.png

you might want to look at clojure again. that comment reads like babble

Oh, and I left out one of the biggest benefits. We will have a simple option to ship the compiler inside your application, to allow things like the ability to "eval". Just think of interactively inspecting and modifying a running application after it is shipped.

some background: the ClojureScript compiler has recently been bootstrapped, effectively giving us two different versions of the compiler, "ClojureScript JS" which only relies on a JS runtime, and the original "ClojureScript JVM" which will continue to be the default choice, partly because the benefits afforded by the Google Closure compiler (written in Java) are huge and irreplaceable.

The "ClojureScript JS" compiler cannot replace the original compiler fully, but is already finding some great use-cases, such as this new insanely fast Planck REPL, targeting new platforms like iOS (see Replete, Ambly, React Native), an in-browser try-it-out REPL for our upcoming website, the ability to try out new libraries from a webpage, and possibly adding ClojureScript support to CodePen.

Lot of great stuff coming.

interactive version: http://pacman.shaunew.com/play/index.htm#learn

how does that url work with asterisks?

amazing, thanks!

I watched the NBA playoffs on Sling TV, which had ESPN and TNT. But I couldn't watch the Finals because it was on NBC.

I wish I could watch local broadcast TV from my computer. But when broadcast TV went digital, it made it harder to get a decent signal. Partial signals on digital are a lot worse than it was with analog.

Om has extra constructor syntax and functions for dealing with cursors; that's it. I get the initial perception that Om is "over-engineered" but it just isn't.

Yeah, I'm just happy people are learning about this awesome thing named after him, however spelled.

Thanks! it was years ago I made these. The interactive ones are made in just straight Raphael.js (in js/1dscreen.coffee). The cube animations are just plain canvas (in js/iso3d.js)

Thanks, I'm glad it changed your view of the game. My goal was to show this beautiful isomorphism between the two representations.

This is awesome. I used SimpleCV in Python to detect the walls, much like you did. But I used it to transform the screen to make the platforms fall vertically:

https://github.com/shaunlebron/super-hexagon-unwrapper

not just any blackholes-- supermassive ones. Some are bigger than our solar system.

recorded a video of my experience (1h40m with level bookmarks in description):

http://youtu.be/vtuZlufpfag

truly great idea. thanks for the game!

Really well put, thanks for sharing.

It's interesting to me that the dolphin and octopus seem to be separated from us by some missing feature. The Dolphin is social and intelligent, but lacks graspers (for tools). The Octopus is intelligent, has capable graspers, but is not social and doesn't live long. I wonder if having those missing features would cause critical tipping points toward civilization.

Clojurescript might be more of a magnet than a filter in finding developers. I think any developer would be excited to learn the language that influenced React and the immutable js libraries... as long as they had some guidance and employment to do it!

In my experience, I joined a company specifically to learn/use clojurescript and others joined the same time, and we were committing code after 2 weeks.

Om has a steep learning curve. I'd recommend quiescent if you want the bare minimum for interfacing with React in cljs.

ClojureScript auto-compiler is really fast (under a second) after the first compile if you don't use advanced optimizations.

Thanks for the comparison. And good catch with the cursor equality relying on both value and path. That is something that was recently fixed in Om.

Give ankha a try. It's still in early development: https://github.com/noprompt/ankha

In Om, you can't create Cursors to primitive values. Rather, you can only create Cursors to indexable collections, like a Map or Vector. Looks like React-Cursor allows this, so I'll take another look to see what's preventing this in Om.

Don't forget about Tetris, the Soviet original released in 1984.

I used advanced optimizations, and the problem went away.