In addition, he noted that the team then prioritizes containing the damage in the application code instead of the fixed cost of library code.
Finally, if the team is aware that an approach is a dead end, it pivots from investing into such an approach as soon as it is viable to do so to then invest in another approach that makes a lot more sense in theory.
“These are a few fundamental principles I’ve observed in how we work, but I’ve probably missed a bunch of them. I also haven’t touched on the less technical principles around how we roll out APIs, communicate changes, and so on,” Abramov wrote.
Ionic prepares for Angular 9.0
One of the biggest improvements coming in Angular 9 is that Ivy is enabled by default, according to the Ionic development team. Ivy is Angular’s new renderer, which works to make the final output smaller.
Angular will also receive CLI improvements, which include app building automatically using AOT, and differential builds that will first build an ES2015 version of the app and then produce an ES5 build with the necessary polyfills.
The detailed list of updates the Ionic team is looking forward to for Angular 9 can be viewed here.
What to expect in JDK 14 Rampdown Phase Two
OpenJDK announced what to expect in JDK 14 Rampdown Phase Two, which is expected to be released on January 16, 2020.
The full details are available here.
Apache Maven source plugin 3.2.1
Apache Maven announced the 3.2.1 release of the source plugin release, which creates a jar archive of the source files of the current project.
Apache Maven also offers configuring for reproducible builds, which create an independently-verifiable path from the source code to the binary code.
More details on reproducible code are available here.