Explore >> Select a destination
|
You are here 
|
shpota.com | ||
| | | | |
nguyenhuythanh.com
|
|
| | | | | I named this post "Good" Practices, not "Best", since I believe that there is hardly a silver bullet that can be used to solve everything, technology oriented or not. The practices are good since they fit my case, and I hope that it would give you (or my future self) some useful insights. Monorepo Development Style Normally, we are used to Angular CLI's new command: ng new The style is normal for a "multi-repo" development style, where we split our projects into multiple repositories (Git repository to be precise). | |
| | | | |
www.carloscaballero.io
|
|
| | | | | Thoughts, stories and ideas. | |
| | | | |
humberto.io
|
|
| | | | | Discover how to separate your stacks to get autonomy between frontend and backend using Angular 6 and Django 2 | |
| | | | |
in.relation.to
|
|
| | | Java 9 comes with a new feature very useful to library authors: multi-release JARs (JEP 238). A multi-release JAR (MR JAR) may contain multiple variants of one and the same class, each targeting a specific Java version. At runtime, the right variant of the class will be loaded automatically, depending on the Java version being used. This allows library authors to take advantage of new Java versions early on, while keeping compatibility with older versions at the same time. If for instance your library pe... | ||
