I like to understand things. I like to make things. The meaning of life — first survive, then reproduce 🌞
Don't let the (impractical, even impossible) perfect be the enemy of the (practical) good (enough).
I suspect TypeScript has become the new jQuery.
More than a decade ago, when someone asked a JavaScript question — it was very common many of the responses to be in jQuery, rather then JavaScript.
Which, of course, isn't what was asked for.
Nowadays, I see something similar with TypeScript.
Someone asks about the technical details of a protocol — such as an HTTP-based API, and rather than (many of) the responses talking about the HTTP-based API, they just provide TypeScript code (which hides the details of the HTTP-based API).
Which, again, isn't what was asked for.
It seems so common now (with TypeScript) — just like it was more than a decade ago (with jQuery).
Locked-up in a validator node and locked-up due to (an investment via) a SAFT are are two different types of "locked-up" in crypto.
What investors want in crypto is liquidity.
To investors, lock-ups are a problem.
(Lock-ups are often part of the terms of their investment.)
In Solidity, sub-classing is often used to do what other programming-languages would do using 'imports'.
With the Solidity programming-language —
The lack of methods for structs, and functions outside of contracts — makes you do some unintuitive work-arounds, to get something sort similar.
For some — new chains are a way of gaining market-share.
Sometimes even more-or-less capturing the market within that new chain.
Apparently, Figment is the largest validator in the world.
Their strategy — go after new networks.
It is difficult to get used to the line-terminating semicolon in the Solidity programming-language — when I've been programming in the Go (i.e., Golang) for so long (which doesn't have them).