Re:Why did we choose Rust to develop TiKV?
by zerr on Wednesday September 27, 2017 @06:25AM
(#15346375)
I don't think ARC is an issue here - it's just a deterministic reference counting - a la implicit using of smart pointers. Besides, Swift also has some unsafe pointer types as well.
[ Parent
| on HN ]
Re:Why did we choose Rust to develop TiKV?
by cyber1 on Wednesday September 27, 2017 @06:37AM
(#15346425)
Yes, you right according to "deterministic" but you forget about overhead. Rust gives you more safe control on memory management and in most cases, you can always write the fast and efficient safe program without the overhead. Rust give different smart pointers and even sometimes when you 100% understand what are you doing you can use unsafe raw ptr.
Re:Why did we choose Rust to develop TiKV?
by zerr on Wednesday September 27, 2017 @06:50AM
(#15346476)
Yes, there is a trade-off of course. I think Swift is in the middle on Usability - Safety axis (C++ being on the left and Rust on the right extremes).
Re:Why did we choose Rust to develop TiKV?
by imtringued on Wednesday September 27, 2017 @11:39AM
(#15348877)
For certain programs a GC can basically make a programming language completely useless (no shared libraries with C abi, no realtime audio, videogames with stutter) regardless how fast the programming language is. This is not the case for swift. It's merely slower than rust.