Skip to content

Instantly share code, notes, and snippets.

@sigmaray

sigmaray/no_c.txt

Created February 9, 2017 19:12
Show Gist options
  • Save sigmaray/5d98b8b9faea2aea35730498ecb605af to your computer and use it in GitHub Desktop.
Save sigmaray/5d98b8b9faea2aea35730498ecb605af to your computer and use it in GitHub Desktop.
Download ZIP
Blog post about C that was deleted
Raw
no_c.txt
Web archive link: http://web.archive.org/web/20160304122737/http://blog.dottedmag.net/post/105014442549/no-c
=======================
No C
The more I deal with C (or C++ for that matter) the less I want to continue doing it in future.
It is insanely useful to have enough C knowledge to be able to debug problems all the way down to the hardware, but doing it on a daily basis and outside of confines of tight loops is a huge waste of time.
Next time I’m writing something I’d like to avoid to care about macros inadvertently modifying names in unrelated namespaces (awesome for mixing C and C++), unsynchronized declarations in system-provided header files due to order of includes (e.g. _FILE_OFFSET_BITS=64), non-portable serialization of basic data types ("%" PRId64 anyone?), lack of standard data types (uint64_t? unsigned long long?) and other nuances which ought to be handled by the language.
Languages should provide at least sound type system, proper modules and decent standard library. FFI for time-critical code is useful too.
Life is too short.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment