pablobaz

I'd be interested to see how a Genetic algorithm with carefully chosen mutation/recombination operators would suit this problem.

Mutations could be flips and random swaps. Recombination would be combining chunks of already partially optimised solutions (breeding).

Genetic algorithms do suffer a cost of having to keep a population of solutions in memory so it would be interesting to see how the end results compares in performance to annealing.

Comparing their Finance demo [1] to the HighStocks equivalent [2]. It comes in at nearly twice the lines of code for significantly less functionality. Obviously there's a difference in approach here - HighStocks comes with lots of sensible default options where as Plottable.js seems to require more explicit configuration. And Highcharts is a commercial product whereas Plottable is free.

For me though Highcharts/Highstocks is still easily worth its license fees. In my experience >90% of charts I require are very simple to implement in Highcharts and the sensible defaults make your life easy. For the other <10% use D3/a custom solution.

[1] http://plottablejs.org/examples/finance/ [2] http://www.highcharts.com/stock/demo/compare

For something simpler and less time consuming for users I'd recommend https://heelhook.github.io/chardin.js/

If you like namedtuples, you'll love attrs. https://pypi.python.org/pypi/attrs/16.0.0

Yes I thought the same. See: http://devmag.org.za/2009/05/03/poisson-disk-sampling/

and for a D3 animated example: https://bl.ocks.org/mbostock/dbb02448b0f93e4c82c3

This is untrue. Good investments are often capacity constrained. In this scenario it makes sense for managers to charge high fees to investors to allow them access the best products.

Here is another one also from 2013 by Kohsuke of Jenkins/Hudson fame: http://kohsuke.org/2013/08/13/lego-earth-project/

This article doesn't mention one of the most interesting aspects of snowmaking - the addition of bacteria to the water to increase the productivity.http://web.mst.edu/~microbio/BIO221_2010/P_syringae.html

While I agree with all the points listed in the article, it highlights for me a major problem of a lot of code reviews.

Most code reviews seem to focus on:

1. Examining what the change does 2. Finding ways to make the change in a nicer way. E.g. Refactoring etc.

This leaves out the key step 0 - what is actually trying to be achieved, does it need to be done and is there a better (maybe completely different) way to do it.

This leads to a focus on relatively trivial matters such as naming conventions and method lengths.

I think that the underlying reason for this is laziness. Talking about clever refactoring is an easier/faster process than understanding the 'why'.

This rapid evolutionary change is one reason why much of the reasoning for "Paleo" diets is flawed. Humans have changed since Paleo times.

Here's a proof of concept built around 620AD. Obviously a bit different but this type of technology has been around a long time. http://www.archaeology.co.uk/articles/features/harnessing-th...

A key feature for me would be that it remains runnable in the browser.

Gauss (https://github.com/wayoutmind/gauss) has some nice features in this space. But only has vectors at the moment.

Just a quick plug for my angular directive for highcharts https://github.com/pablojim/highcharts-ng

Although it appears there's a diverse ecosystem of competing systems. The worst scenario would have be a total domination by a single player.

Here's my plugin to integrate Hichcharts with AngularJS:

https://github.com/pablojim/highcharts-ng/

> A huge, naked pile of nuclear waste has sat beneath Oklo for billions of years; why not put a bit more under the Nevada desert, in shielded canisters no less?

I think this is a bad case of survivorship bias.

Firebug has a $ built in just for debugging.

One thing that struck me is how uncluttered the streets look. There is very little street furniture.

Interesting that this is being returned to now.

Easy to be snarky about this. But I admire their persistence.

In the face of the extensive criticism they could have just given up.

Instead they have acknowledged making mistakes, didn't give up, learnt from the mistake and changed their subsequent behavior. This is admirable.

As you dive deeper into Angular it becomes clear a lot of it is unpolished. For example $resource seems very half baked. It has lots of quirks e.g. trailing slashes and its promises support seems to be a bolt-on.

It's not just about efficiency though. From carbonfootprint.com - "Emissions from planes at high altitudes impact climate change more than if the emissions were released at ground level. To take account of this you have the option to factor up the CO2 emissions released by aviation Radiative Forcing Factor of 1.9"

I like the concept but like not having my laptop on my vacations more.

Something similar for highcharts here: https://github.com/pablojim/highcharts-ng

Demo: http://jsfiddle.net/pablojim/Cp73s/

u.getA() and u.getB() will still be evaluated. However I believe the conversion of A and B to strings will not be carried out if debug is disabled.

Often it is the conversion to string that is an expensive operation.

Incidentally with lots of lazy loading (Hibernate I'm looking at you...) this can lead to errors only appearing when debug is turned off - not a nice situation to be in.

What are you using for the help arrow overlay?

What are you using for the help array overlay?