Why did we choose Rust to develop TiKV?

Re:Why did we choose Rust to develop TiKV? by blub on Wednesday September 27, 2017 @10:22AM (#15348026)

The issue with C# and Swift is that the Apple and MS dev communities enjoy having a ready made solution that they can pick up and work with immediately. Official support is very important.

C# and to some extent Swift are also two huge platforms, there are very few organisations out there that would be able to steer their development.

Finally, they are not standardised in any way. MS tried something with 2.0 and then gave up.

My impression is that these two live and die by the will of their corporate masters. I'm not saying they will kill them or anything, that would be pretty stupid of them to do.

[ Parent | on HN ]

Re:Why did we choose Rust to develop TiKV? by pjmlp on Wednesday September 27, 2017 @10:46AM (#15348278)

> Finally, they are not standardised in any way. MS tried something with 2.0 and then gave up.

They are standardized, you just need to look at the right place.

https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...

https://docs.microsoft.com/en-us/dotnet/visual-basic/referen...

http://fsharp.org/specs/language-spec/

https://swift.org/documentation/

[ Parent | on HN ]

Re:Why did we choose Rust to develop TiKV? by blub on Wednesday September 27, 2017 @02:12PM (#15350609)

Documentation & specs is not standardisation, not in the C or C++ sense. But you already know that, so why are we having this conversation?

[ Parent | on HN ]

Re:Why did we choose Rust to develop TiKV? by pjmlp on Wednesday September 27, 2017 @02:19PM (#15350684)

I assume you know what a de facto standard is all about.

[ Parent | on HN ]