3 ms·
I've been wanting to build a generic version of this type of tool for quite some time. When I'm waiting several minutes for our app server to startup, I often
by nogridbag 10y ago
I've been wanting to build a generic version of this type of tool for quite some time.
When I'm waiting several minutes for our app server to startup, I often ponder what life would be like if we had chosen language X or another stack for our application.
I've primarily worked on JRE-based stacks for some time and once a project reaches a certain size developer happiness begins to decline due to large compilation times, app startup times, etc. Even incremental compiling or hot-reloading of classes seems unreliable at a certain app size (either due to memory or some other reason).
It would be neat if there were a tool to generate large and complex apps with various stacks to get a feeling what the developer experience would be like 1-2 years down the road once the app reaches a critical mass.
- mahyarm 10y agoThat is a good idea for testing out new stacks for that shiny new rewrite. One thing I've realized is most projects are not designed for 100+ developers working on it at +400kloc of code. We adopted https://buckbuild.com/ https://buckbuild.com/ at work for our android builds, and it has sped it up a lot compared to our previous gradle build process.
- RhodesianHunter 10y agoWhy not micro-services?
- Akonkagva 10y agoWhy not OSGi?