News for hackers. Stuff that matters.
Re:Reasons to avoid static type checking by jongjong on Sunday January 28, 2024 @03:02AM (#39163448)
If you saw how little code my projects require, you would realize that this is incorrect.

I've built a decentralized cryptocurrency exchange that can work with most blockchains in just 5000 lines of code. Has been running for 4 years with zero bugs.

I've written a cryptocurrency from scratch with only about 4000 lines of code and have not had any bug reported after 3 years of continuous operation. On the other hand, projects like Bitcoin and Ethereum are hundreds of thousands of lines.

I've also written a no-code platform in less than 4k lines of code which supports complex views with real time updates, pagination, indexing, access control, multi-tenancy and has been bug-free since it launched. I built the whole thing in about 3 months part time.

All of these built with plain JavaScript/Node.js. I can support all of these projects in parallel because I rarely need to update them.

Re:Reasons to avoid static type checking by j-pb on Sunday January 28, 2024 @03:32AM (#39163587)
> I rarely need to update them.

Not really a good project to measure ossification on then.

Re:Reasons to avoid static type checking by ssijak on Sunday January 28, 2024 @04:31AM (#39163947)
your lines must be long then or those projects featureless
Re:Reasons to avoid static type checking by jongjong on Sunday January 28, 2024 @06:17AM (#39164553)
Not so, they're quite short and feature-rich. When I read the code of most other people's projects, I'm often shocked at how over-engineered they are. A lot of code merely wraps some other logic or there are unnecessary abstractions which add unnecessary layers of indirection.