C++ and the Culture of Complexity (2013)

Re:C++ and the Culture of Complexity (2013) by pjmlp on Wednesday January 31, 2018 @09:32AM (#16274074)

> Win32 or the interfacing is not seamless

Well then Rust, D, Swift, Go, Rust, Haskell, OCaml are not native by that measure.

C# integration with Win32, COM and UWP (aka COM reborned) is painless comparing with any of them.

[ Parent | on HN ]

Re:C++ and the Culture of Complexity (2013) by gpderetta on Wednesday January 31, 2018 @09:46AM (#16274188)

I think Rust and D have seamless integration with C style ABIs. Swift is native on iOS. Haskel and OCaml have, as far as I understand, painful FFIs and a relatively heavy runtime so I wouldn't call them native.

edit: to be clear, using 'compiles to object code' as the definition of Native, is both a misuse of the word, and meaningless as it is a implementation detail that can change easily and bound to be obsolete quickly.

[ Parent | on HN ]

Re:C++ and the Culture of Complexity (2013) by pjmlp on Wednesday January 31, 2018 @10:29AM (#16274566)

Try to write a GUI WIndows app, COM server, or service daemon in Rust and C#, then let me know which one is more native.

Bonus points if it is a UWP one.

[ Parent | on HN ]

Re:C++ and the Culture of Complexity (2013) by gpderetta on Wednesday January 31, 2018 @10:56AM (#16274784)

I wouldn't want to be caught dead writing a GUI Windows app (I might do Qt if forced at gunpoint though), so I'm probably not the best person to test this :)

[ Parent | on HN ]