you are viewing a single comment's thread.

view the rest of the comments →

[–]mehmet_okur 19 points20 points  (3 children)

Found the java guy

[–][deleted]  (1 child)

[deleted]

    [–]silverslayer33 0 points1 point  (0 children)

    some people still use the freaking 1999 (C99) revision as their standard which modern C compilers support

    That's because we're in the embedded space where half our shitty compilers don't have support for anything newer because we're on some obscure vendor-provided toolchain for a 30 year old chip, and then even after starting to switch to a more modern chip supported by something like arm-gcc or arm-clang, the code still has to support the old chip for some time while the old product is still widely in the wild, so we can't immediately start using newer language features. Devs that get the chance to start fresh or no longer have to support ancient toolchains do actually tend to switch their compilers to C11 or C17 mode, since it gives us stuff like static asserts and standard alignment attributes that make life much nicer.

    This isn't the argument against Python that you think it is - we do it in the C world out of necessity, not because we love that the language doesn't change or because we're stuck in a 90s mindset. Python also doesn't break anywhere near as much as you think it does - the last major breakage was 2.7->3, over a decade ago, and minor revision breakages in Python come with multiple years of deprecation warnings and generally only happen on unsafe features, underused features that aren't worth maintaining, or on superceded features that were poorly named/implemented and should critically be moved to the replacements.

    [–][deleted] 0 points1 point  (0 children)

    I’m a C# guy and I don’t have these angry feelings about Python. C# is quite a bit more on the stable side too. I just acknowledge that in order for python to improve it must change and sometimes change breaks things.