If you mean this "Tezos: the self-amending cryptographic ledger" ( https://tezos.com/ ), this look like something done from 4 amateurs in their spare time.
I don't know if it has "$200 million+" warchest, but if it does I pity the fools that gave it that.
I don't have a lot of faith in Tezos, and it's spent most of the time since its (well-known, but apparently not to you) over-funded ICO spent in legal fights over the money, instead of engineering. However, it's only fair to observe that a lot more thought and work did go into Tezos than most of the other Blockchain crap we see every day. Glancing at the marketing splash is hardly enough to assess that.
I'm not so sure. Besides there are lots of way more well known cryptocurrencies that are amateur hour themselves. It comes with the territory.
>well-known, but apparently not to you
Yeah, it's world famous among the people who follow these things...
Where does $200 million+ come into it? What is the history there?
At this point, if a language doesn't have first class support for multithreading and static typing, I wouldn't start a new project in it. Nullability support is pretty high up there too, but that is a far more tractable problem.
Out of curiosity, what is it about smart contracts that makes multithreading so important? Why isn't multiprocessing enough? [edit: sorry, I mis-read your comment. You said that multithreading probably isn't a big deal for this problem.]
https://discuss.ocaml.org/t/ocaml-multicore-report-on-a-june...
It's been a couple of years away for the last 10 years.
https://discuss.ocaml.org/t/ocaml-multicore-report-on-a-june...
Nullability? As in null references? The "billion-dollar mistake" (Tony Hoare, referring to Algol), also frequently called the "worst mistake in computer science"?
https://www.tutorialspoint.com/swift/swift_optionals.htm
It's also called nullability support, you can see it in use in this article:
http://journal.stuffwithstuff.com/2011/10/29/a-proposal-for-...
Option type on wikipedia, cant paste the link somehow.
On any case, as someone else pointed out, OCaml had supper for option types built in, through sum types.
I agree that sum types are indispensable in a modern programming language.
Well, it's not yet ready, but it's incoming
https://discuss.ocaml.org/t/ocaml-multicore-report-on-a-june...