Even the most developed countries are very much quilty of the same. Just a week ago we had a thread about deforestation of the Pacific temperate rainforests.
If you're interested in how this could be automated, check out Polly[1]. There is also similar framework in GCC[2], but as can be seen from the blog post, there is room for improvement.
In Finland, there hasn't yet been a vote about a petition in Parliament. The first petition with enough signatures was submitted in October, and the signatures will first have to be verified.
Roger that. I got into trouble with Hot and Cold Observables and wanted a model that fits my needs a bit better. Hence Reactive Bacon (https://github.com/raimohanska/reactive-bacon). Then I realised I cannot run Haskell in some of the contemporary browsers and translated it into Javascript :)
We're pragmatic about FRP and also rely heavily on Backbone. For some cases, the MVC approach seems better, for others Bacon is a better fit.
In Flowdock, there is a form that automatically validates parts of the data in JS while needs to confirm other parts with server. During server-side validation, a loading indicator is shown and success enables the submit button. Using Bacon, it has been easier to focus on the logic instead of handling state. But the logic is quickly quite hairy, indeed.
Japsu pointed out that there is a TodoMVC implementation with Bacon and Backbone, but it'd certainly be interesting to see/do a pure-FRP implementation.
I'm interested to see if using FRP principles in conjunction with Backbone makes sense. I love Backbone, but I feel like there are times I'm worrying too much about the DOM because I don't feel like abstracting out yet another subset of data into a model. If it was as quick and simple as calling a few functions (binding callbacks to existing view functions), then I feel like it would really clean up my code.
Bacon.js[1] is another functional reactive programming library for JavaScript. Many similar concepts to RX.js, but the library is much smaller. While Bacon.js might not be the most mature library around, I've used it successfully on (almost) daily basis for few months.
There are libraries to handle stemming and Unicode equivalence which are easy to add into this kind of boolean search. If ranking documents would definitely mean that some other approach, e.g. vector space model, should be used.
As a user, i've been occasionally fristrated with the decentralized nature of Maven. The isn't any single repository which would contain all packages (especially rc/beta versions). And in my experience repos and which repos are used to distributed a package tend to change fairly often. More often than not, I have to hunt for new repos when building from scratch.
Maven is also very slow when your project has ~10 repos and you need to download multiple dependencies. Having your own repo might be a necessity.
https://news.ycombinator.com/item?id=20546288