Hacker Newsnew | comments | show | ask | jobs | submit | jashkenas's comments login

The New York Times — Onsite | New York, NY

We’re hiring visual journalists to join The Upshot and the graphics department of The New York Times.


As frequently seen on HN...

3D Yield Curve: http://www.nytimes.com/interactive/2015/03/19/upshot/3d-yiel...

You Draw It — Family Income vs. College Chances: http://www.nytimes.com/interactive/2015/05/28/upshot/you-dra...

Is It Better to Rent or Buy? http://www.nytimes.com/interactive/2014/upshot/buy-rent-calc...


Yo progg'n books — I'm really happy for you, I'll let you finish, but The Poignant Guide is one of the best books on programming of all time. One of the best of all time!



Got some Julia plans or hopes?


Sure – with a first-class LLVM backend for WebAssembly, we could absolutely compile to it, which would mean running fully in the browser, which is something Emscripten can't quite manage at this point. That would certainly be very cool (and useful too). See https://github.com/JuliaLang/julia/issues/9430.


You're in luck. Those comments certainly are within the source file:



That's fantastic! I guess the website was auto-generated then, how nice.


If you liked that, here are some links to sister projects:

Docco Source: http://jashkenas.github.io/docco/

Backbone Source: http://backbonejs.org/docs/backbone.html

CoffeeScript Source: http://coffeescript.org/documentation/docs/grammar.html


The resulting "optimal" path sure doesn't look it. For example, Phoenix:


Surely it would be more optimal to cut straight across from Casa Grande to Gila Bend, and then hit the next station on the way north. No?

It would be fun to throw these same markers into the Google Maps Directions TSP engine, and see how it does... https://developers.google.com/optimization/routing/tsp#solvi...


I can answer that ;)

ES6 is groovy. Many features are in the runtime and not the syntax, and just work as-is. As other syntaxful features start to come into existence and then universal implementation in most active browsers, CoffeeScript should begin offering them -- at least the ones that align with the mission statement.

Some will be troublesome because of intentional syntax conflicts, like "for of" and perhaps classes. It'll just take a bit of design work to make things copacetic.

That said, in the long run, the future is going to be JavaScript (if it continues to evolve) and languages that are much more radical than CoffeeScript. For more thoughts on that, see: https://www.youtube.com/watch?v=DspYurD75Ns&t=36m57s


Nice talk. Given how you end the talk, have you looked at Elm? If so, what are your thoughts and do you think it satisfies unifying HTML, CSS and JS? (Putting aside the uphill battle of gaining adoption as a static typed, FRP language)


Personal favorite quote: https://www.youtube.com/watch?v=DspYurD75Ns&t=39m07s

How do you envision the future ? Everything expressed as a js descendant ? no more syntactic distinctions ?


I can speak a little bit to that question.

We do, indeed, hope to keep interactive articles working and available over the long term. But you can't always predict the technical choices of the future web.

For example, there are plenty of past Times graphics done with Flash, which may not be easily viewable within the next 5 years.

On the other hand -- one of the biggest culprits is simply using external APIs as part of a graphic. APIs shut down, change their terms of use (Google Maps), or have data updated in ways that break the graphic. For example, as we just noticed the other day, this 2011 graphic used to show Joplin, Missouri before and after the tornado hit:


Now, the "before" panoramas are actually "way after" shots. We'll need to go back and fix it somehow.

But it's not all Sisyphean. The standard operating procedure for any interactive article page is to live somewhat inside and somewhat outside of the CMS -- with the page's own baked-out HTML base, and individual copies of any JS libraries and CSS it needs (apart from the super common ones). With a little foresight, this should be resistant to breakage from future site redesigns, even if the page continues to look a little "old" ten years from now.

As long as browsers in 2025 understand JavaScript from 2015 (likely), I'm optimistic.


Thanks for your comment, that's exactly the kind of answer I was looking for :)


"Always bet on Javascript" - Brendan Eich


Very nice approach. I didn't know that Google had that auto-redirect feature.

But it's not working reliably for me. Frequently, when I click the bookmarklet, it gets stuck on a blank page. Does it work every time for you?


> I didn't know that Google had that auto-redirect feature.

It uses the functionality of the "I feel lucky" button. It will only work if the site has been indexed by Google, but that's usually the case with news pages that show such fake paywall messages.

Btw. please Google fix your frontpage, you serve an unformatted text message (IE9-11): http://s7.postimg.org/52fu9wbdn/google_bug.png


Is it Google or IE that's broken? Other browsers seem to be coping with it - I know these big sites tend to serve really mangled markup/code however.


As you can see it's still loading. Let it load.



As @frik noted, it uses "I'm feeling lucky" feature of Google. It requires the page to be indexed to work. If the page isn't indexed then it won't work. But since the pages you'd like to see are indexed almost always, it shouldn't be a problem.


No, that's not what I mean. I mean that the bookmarklet is working intermittently for me on any page. I'll click it, and sometimes get redirected through, and sometimes end up on a blank white page. That doesn't happen to you?


I see a blank page for a second than I get redirected to the actual page. Could you also hit me on twitter @umurkontaci to help me diagnose?


FYI: The test link[1] doesn't work for me. It either reloads a white page, or reloads the page but it is still firewalled.

[1] https://go.umur.io/wsj/


That's interesting, I see a white page for a second or two and I get redirected. If something else is happening for you, would you mind sending me a DM on twitter @umurkontaci? I might be able to fix it.


That's not quite correct. Both Backbone.js and Underscore.js were extracted from DocumentCloud — a nonprofit organization.

But I am currently a Graphics Editor at the NYT...


Not for much longer, I bet...


Ha ha... We'll find out soon, won't we.



Applications are open for YC Winter 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact