Here’s a gift link you can use to read the full article, if the paywall is giving you any trouble: https://nyti.ms/3IXGobM
... and if the side-by-side examples aren’t working for you, try turning off your ad blocker and refreshing. (We’ll try to fix that now, but I’m not 100% sure we’ll be able to.)
Here’s a gift link you can use to read the full article, if the paywall is giving you any trouble: https://nyti.ms/3IXGobM
... and if the side-by-side examples aren’t working for you, try turning off your ad blocker and refreshing. (We’ll try to fix that now, but I’m not 100% sure we’ll be able to.)
My understanding — relayed through one degree of separation from Daniel Griffin, the dendrochronologist who wrote the piece — is that the core samples are very long and thin, and care is taken not to injure the tree and to allow it to heal rapidly.
Working at a still-feels-new-to-me job as Graphics Director for Opinion at The New York Times. Our small team publishes arguments and guest essays supported by visual evidence, like these:
But I'm a believer in asking for help in order to cast a wider net. If you happen to stumble across an obscure-yet-newsworthy dataset, or have a strong feeling about a particular guest essayist that we should be approaching, or can't stop thinking about an argument that's itching you — pitches and tips are always welcome: [my hn username]@nytimes.com
I started reading through these comments expecting a tall wave of negativity, and was surprised to see such a warm wash of mixed and fond memories from the "bad old days" when ES3 and IE ruled the roost.
Full disclosure: I haven’t used it myself much since ~2012 or so, and modern JavaScript now contains many of the most important features that CoffeeScript offered at the time .... Although they did screw some things up (IMHO): null-vs-undefined in default arguments, super as a parent reference instead of a direct function call, optional parens for single-arguments arrow functions (Prettier agrees!), no shared semantics between arrow and normal functions, that class syntax only supports methods and not data as properties, and so on...
When all is done and dusted, I hope that CoffeeScript can be looked back on with affection as a little experiment that showed surprising vigor, one that — with no corporate backing and zero financial support — spread by word of mouth through the web community of the early 2010s, and helped fuel the fire to get JavaScript moving and evolving as a language again.
As a side note — and I write this without bitterness — I do find it a bit strange that extremely well-resourced companies like Dropbox, GitHub, CircleCI, Trello, Airbnb (and many, many more) would write so many hundreds and hundreds of thousands of lines of CoffeeScript without ever attempting to contribute changes or fix the issues that they wanted to fix. It’s open source! They probably would have been able to quickly and cheaply make most of the changes they wanted.
Yeah. Wow indeed. The dataset actually goes all the way back to the end of January, but I'm trimming it to start at the beginning of March, because the early days are pretty much invisible at the current scale.
You can change the value of `startDate` in that notebook if you'd like to look back further in time.
The Italian Department of Civil Protection is now publishing detailed confirmed case statistics on GitHub. I just finished throwing together a little animated map of of how it's been spreading across provinces:
> Is it possible to add a function to output this as PDF or save the result as PNG?
Fortunately, in Observable, every cell that contains SVG or canvas graphics has image export built in. Just click the dotted menu to the left of the cell, and it will offer you downloads in either SVG or PNG flavors.
... and if the side-by-side examples aren’t working for you, try turning off your ad blocker and refreshing. (We’ll try to fix that now, but I’m not 100% sure we’ll be able to.)