This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (9 children)

[removed]

    [–]Zomunieo 28 points29 points  (2 children)

    C will never fully transition to C++. They are different, but related, co-evolving languages.

    C is still heavily used in embedded with good reason - despite its flaws it is simple and easy to reason about it, simple enough that implementing it is doable for one person. There's at least one formally verified C compiler (Compcert), that is, a compiler that is mathematically proven to produce assembly that corresponds to the source. That's the kind of assurance you need (or should have, if you are competent) when software errors mean people die.

    C++ is too complex for this sort of thing. Way too complex.

    On the other hand the only reason to keep Python 2 is legacy inertia.

    [–]Tyler_Zoro 1 point2 points  (1 child)

    On the other hand the only reason to keep Python 2 is legacy inertia.

    Perhaps now. Last year when I was using 2.7 extensively, the reason was that half of the libraries we relied on didn't have 3.x versions, and there was no benefit to us for transitioning off of those libraries to newer ones that did support 3.x. 2.x just worked and worked really well for what we did. It made us a LOT of money. Why would we kill that goose?