@166877d9 Hah, great! Any package manager comes with it's own merits, I guess. Fun fact: I did only two re-installs in the whole time, one when I couldn't swap the hdd because of IDE vs. SATA, and one to switch over to 64 Bit, which was a lot easier when starting afresh. Everything else was rolling updated, which is a real thing in #Gentoo. I didn't say it's always easy, though.
Happy 24th Birthday, Gentoo Linux!
When I started using it in 2004, it was not for performance tuning reasons, but to be able to install exactly the software I want and with exactly the versions I want. All my laptops (ThinkPads) and various servers ran on it since then, which makes me a #Gentoo #Linux user for almost 20 years.
I wonder if every #Kotlin user is really happy with using #Gradle? It's currently to only option to get in the comfort of fast compilation. Outside of this vender-provided ecosystem, compiling #Koltin is really slow. Much slower than my #Scala toolchain.
@Jonathan Lamothe Yeah, me too. I wouldn't have the time to scan all these site manually. I never used any online-reader though.
Nowadays, using RSS means, opening the source code of an iteresting article or video and search for some rss links. Those links are visually pretty good hidden.
@371fbbae There are so many reasons why there exist so many different tools. Different requirements, personal preferences, and so on. Creating an uber-tool isn't the right solution IMHO. To the contrary.
But by sharing and re-using the same building blocks in your build-tools, we can improve. To give an example, most build tools don't re-invent the compiler, but if it comes to license management of dependencies, you will find many different solutions or none at all.
Most #BuildTool plugins should be developed as an library or CLI app first. Then, you can feed everything from your build tool into it. This makes reusing it in other build tools much easier. Also testing is easier that way.
When looking at the current tooling landscape in #Scala or #Java, most tools are exclusive to one build tool. They use the API of that tools and can therefore not easily reused by others.
Notes by Tobias Roeser | export