As software developers we measure technical debt as lines of code, or "LOC". The more LOC we've got, the more technical debt we've got. Technical debt again, is a bad thing, because it makes it more expensive to maintain your project in the future. So reducing technical debt should be our first priority when architecting our software.
Below is 11 lines of Hyperlambda code encapsulating an HTTP endpoint returning Artist records from the chinook database. If you were to create the same solution in C#, you would end up with 197 lines of code. The Hyperlambda code is small enough to read the entire code in one page, while the C# equivalent needed 5 screenshots to show the equivalent.
Hyperlambda
C# 1
C# 2
C# 3
C# 4
C# 5
Imperative versus Declarative Programming
Hyperlambda is a declarative programming language, while C# is imperative. I have done the same exercise with Python, GoLang, Java, PHP, and all other programming languages out there - And the numbers are always around 1 to 20. Implying ...
Hyperlambda produces 5% of the technical debt other languages produces!
Since we have science that proves you will produce about 3 bugs per 1,000 lines of code, regardless of language - This also implies you'll produce 20 times as much bugs if you use anything but Hyperlambda simply because your LOC count becomes 20 times larger.
If you're interested in exploring Hyperlambda more, you can find it here. You can check out my company here.
Top comments (0)