News for hackers. Stuff that matters.
Re:The C++14 Standard: What You Need to Know by pjmlp on Wednesday September 17, 2014 @01:52PM (#8331323)
- Not able to use the OS vendor tooling which only support the official languages

- Another layer to debug (FFI)

- Possible loss of performance when crossing the FFI barrier

- Loss of productivity, because that cool API isn't available and so one has to write it

- Writing drivers, daemons/services, OS plugins, ...

One of the reasons I moved from Turbo Pascal to C++, when I started coding on Windows 3.0, was being fed up to write binding libraries by myself. Although I really enjoyed Turbo Pascal back then.

Re:The C++14 Standard: What You Need to Know by mwcampbell on Wednesday September 17, 2014 @02:26PM (#8331539)
I can confirm that writing bindings is a big time sink. One of the biggest projects I've worked on is a Win32 application that's primarily written in Lua. I chose Lua because of the small interpreter and minimal standard library; a project requirement was to keep the download size small. But I spent a lot of time writing my own Lua bindings for Win32 APIs. Maybe that just means I should have used a more mainstream alternative language like Python, but even in Python-based Windows projects, I've sometimes had to drop down to ctypes, Cython, or the like. In recent years I've wondered if I would have been better off using C++ in a modern style, with smart pointers, string and container classes, etc. Then I would have had direct access to all Windows APIs, plus access to all of Microsoft's tools.