erik/kobalt-doc
erik/kobalt-doc
1
0
Fork 0
mirror of https://github.com/ethauvin/kobalt-doc.git synced 2025-04-25 12:07:10 -07:00
Code Releases Activity

Refactoring toc.

Browse source
This commit is contained in:
Cedric Beust 2015-10-08 21:26:02 -07:00
parent 6392d6965c
commit 0a49785494
4 changed files with 30 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

8
home/index.html
View file

@ -119,7 +119,7 @@ Kobalt is complete enough to build three of my personal projects (<a href="https
With this disclaimer, why did I decide to write Kobalt?
<h3 class="section" indent="..">1. Scratching an itch</h3>
<h3 class="section" indent="1">1. Scratching an itch</h3>
<p>
I give a lot of credit to Gradle for having open a brand new avenue in build tools but despite all its power and flexibility and the fact that I've used Gradle for more than five years, I've never really felt comfortable or fluent with it. Even today, I regularly find myself spending a lot of time on StackOverflow whenever I need to do something a bit out of the ordinary with my Gradle builds.
@ -134,19 +134,19 @@ I suspect a part of it is due to Groovy which, even though it started gaining so
<li>Building is slow and hard to diagnose because of Gradle's mixed Java/Groovy code base.
</ul>
<h3 class="section" indent="..">2. An experiment</h3>
<h3 class="section" indent="1">2. An experiment</h3>
<p>
I wanted to see for myself if my discomfort with Gradle was justified or if, by trying to write a build tool myself, I would end up with a very similar tool with similar strengths and weaknesses. I still haven't made up my mind about this but I will certainly by the time Kobalt reaches 1.0.
</p>
<h3 class="section" indent="..">3. A proof of concept</h3>
<h3 class="section" indent="1">3. A proof of concept</h3>
<p>
I have been a fervent believer that there is nothing that dynamically typed languages can do today that statically typed languages can't. Groovy's meta model and features have enabled a lot of clever tricks (DSL and others) for Gradle builds and I was really curious if I could put money where my mouth is by creating a similar project with Kotlin. This experiment is still ongoing but by now, I'm pretty convinced that the answer is a resounding "yes".
</p>
<h3 class="section" indent="..">4. An excuse to write Kotlin</h3>
<h3 class="section" indent="1">4. An excuse to write Kotlin</h3>
<p>
Just a personal thing. After toying with the language for almost four years now, I wanted to take my efforts to the next level and push the language to the limit. So far, the language has held all its promises and then some.