From b2df1af880fe7fcc83f1cb896115ad9865d2cf62 Mon Sep 17 00:00:00 2001 From: Nikita Tchayka Date: Sat, 16 Sep 2023 23:19:03 +0100 Subject: Statements to the top --- docs/intro.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/intro.md b/docs/intro.md index 7465215..09dc18a 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -6,7 +6,18 @@ sidebar_position: 1 > A Dogma is not bad if it is aligned with the principles of the individual, and flexible enough for the moments it isn't. -## The Complexity Generation +## The NeoHaskell Statements + +* Beautiful is better than ugly +* Simple is better than complex +* Duplicate and easy is better than concise and complex +* Mathematics are good when not seen +* The 80% of type-safety should be done with 20-or-less% of the effort +* Instead of investing effort in the other 20%, better release to prod +* If it takes more than 5 minutes to understand, it's a bug +* The functional way is better, unless the imperative one is easier + +## The Beginning: Complexity Generation Once upon a time, there was a developer who embarked on a project written in Haskell—a language known for its expressive power and strong type system. Consumed by the allure of purely functional programming, this developer started off with enthusiasm and hope. Yet as time passed, the Haskell codebase, once a work of intellectual beauty, turned increasingly cumbersome and enigmatic, as the team kept adding on newer and fancier features. @@ -37,17 +48,6 @@ Inspired by CQRS and Event Sourcing, NeoHaskell promotes a clean architecture wh NeoHaskell is not merely a tool; it is a craft. It aspires to make coding not just functional but also pleasurable. The language aims to trigger a flow state, making each moment of development a joyful experience. -## The NeoHaskell Statements - -* Beautiful is better than ugly -* Simple is better than complex -* Duplicate and easy is better than concise and complex -* Mathematics are good when not seen -* The 80% of type-safety should be done with 20-or-less% of the effort -* Instead of investing effort in the other 20%, better release to prod -* If it takes more than 5 minutes to understand, it's a bug -* The functional way is better, unless the imperative one is easier - ## The NeoHaskell Promise As it continues to evolve, NeoHaskell aspires to be a nexus of balance: simple yet potent, utilitarian yet principled, designed to cut through complexity while offering a pleasurable user experience. It doesn't just aim to be another programming language; it hopes to be a landmark in the landscape of software development—a testament to the hard-won lessons from a history rife with complexities. -- cgit