Even then, wasn't it usually the opposite case, where you would get the "console undefined" error when the developer console was closed? I can't think of a single case where an error only occurs (or is observed) when the console is closed. Having said that, this project definitely still has its practical uses.
Wow, is the snarkiness really necessary? At least by proposing a possible solution here, we increase the chances that a bona fide geologist will come by and tell us why it wouldn't work.
John Muir, for teaching people how to appreciate and preserve the few precious natural wonders we have left, and how to discover our own spirituality within them.
I can't seem to be able to get to that page, even when I'm signed into my Heroku account. When I try to go to the above link, I'm instantly redirected to https://www.heroku.com/home. Anyone else observing the same thing?
Something about this study feels contrived. The size of the project makes a big difference, and it seems that the study focused primarily on making the code less linear and more abstract (adding polymorphism, etc.) in cases where the overwhelming benefit is seen in huge projects involving many developers. I don't feel that was even close to being the case here.
Perhaps the incentive here is to educate coders as to what patterns to avoid which will have an inclination toward "evil" AI. This won't stop others for whom this is the goal.
For a simple scatterplot with many points I would probably simply use Canvas directly, and perhaps borrow elements from D3 like d3.scale to plot the axis labels. It is possible to use Canvas underneath to plot the 100,000 points, and SVG on top for other stuff like tooltips and brush selecting.
Using D3 for simple charts is not necessarily a waste of time -- I have a small collection of code for D3 charts I've made that I keep around and reuse as needed. Although they are simple they are tailored to the way I like simple charts to look like.
The article mentions that databases can be up to 140TB in size, and yet it also mentions that it may not be a good choice for very large datasets - does this mean that approaching the upper limit is not recommended, or are we talking about something even larger?
Seems pretty obvious to me, since the above description could also apply to your typical declarative languages such as SQL, where you also rely on the database to do optimizations based on a description of the result you're looking for, rather than procedures for calculating it.