• Parov Stelar (All Night)
• Kavinsky (Nightcall)
• Guetta & Sia (She Wolf)
• Christine and the Queens (Christine)
1] Once you add a setting you're supporting it forever
2] Unintended consequences: settings impact other settings
3] Settings excuse you from making informed product decisions
4] Settings allow complexity/opinions to creep in
It has tons of settings in the form of properties read from several .properties files (with cascading: shipped, on site, per user, etc.).
When we replace an implementation with another, we provide a setting to fall back on the original implementation, in case a catastrophic bug happens in production... Of course, these settings and old implementation remain there for years!
When we change a behavior, we provide a setting to allow users disliking this change to go back to the previous one...
Etc., ad nauseam...
The worst part is that at least half of the settings are not even documented (on even in internal docs) and can be discovered only when reading the code (and of course, they are sprinkled all over the whole code base!).
Later, we introduced a more central location for these settings and they became auto-documented... :-)
In recent products, we try and avoid to add (too much) settings. :-D
git log --stat on one of the archetypes says:
6 files changed, 47 insertions(+), 135 deletions(-)
and more importantly:
• devmode is easier to use (no need to ever run mvn install)
• POMs have (almost) no hacks in them (just configuration of Tomcat and Jetty to make them load the .nocache.js from SDM)
Note however that I removed the ability to run the server with the compiled (prod mode) client. I'll add it back if there's demand.
You can see the exact changes at https://github.com/tbroyer/gwt-maven-archetypes/commit/b3ef2b90f3435323c9aef0a0ba93677a98b0e5b9, to help you migrate existing projects.
Re. moving your gwt.xml file to src/main/module.gwt.xml, it's not required. It gives you a few benefits though: generating the <inherits> from dependencies, and generating the rename-to="".
Credit: James Rignault
Compare the 1½ year-old http://blog.ltgt.net/maven-is-broken-by-design/ with:
• “core extensions will be the path to proper consumer POM support (build time vs dependency resolution time)” — http://takari.io/2015/03/19/core-extensions.html
• “Maven has always had a loosely defined notion of a multi-module project, but we are starting to move toward a more cohesive definition” — http://takari.io/2015/03/20/mmp.html
• you can now pass execution IDs on the command line when invoking goals directly, to select the appropriate configuration — https://jira.codehaus.org/browse/MNG-5768
Don't get me wrong though, I still think Maven is broken by design and unfixable (at least not without breaking backwards-compatibility; maybe the only thing that really cannot be fixed will be the linear lifecycle, but that's still one of Maven's biggest design mistake that really makes many things hard or nearly impossible, or at best totally unoptimized)
Some research and findings on how Maven, Gradle and Buck misuse javac, mostly due to some misunderstanding about how it works I believe.
Feedback about other build tools (Pants?) would be very much appreciated.
Les enfants en colère après la publication de caricatures jugées injurie...
OSLO – La nouvelle n'a pas tardé à faire réagir. À peine publiées par un journal iranien, les caricatures se moquant ouvertement du Père Noë
Testing on the Toilet: Writing Descriptive Test Names
by Andrew Trenk, This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of
One man willingly gave Google his data. See what happened next. - O'Reil...
Despite some misgivings about the company’s product course and service permanence (I was an early and fanatical user of Google Wave), my rel
Bolinfest Changeblog: Hacking on Atom Part I: CoffeeScript
The truth is out: money is just an IOU, and the banks are rolling in it
The Bank of England's dose of honesty throws the theoretical basis for austerity out the window
22 Responses To Buzzfeed's 22 Creationist Messages
Buzzfeed published 22 questions and statements from Creationists; here's some responses from a science reporter.
Troy Hunt: For your convenience, please disable security warnings
Let's just start here: This is an annoying feature of Internet Explorer, and is not indicative of any security. Allow me to provide a techni