2013 C++ [portable] -

JavaScript developers who faint at the sight of && or :: . Or anyone who thinks Python’s GIL is "not that bad." Final note: If you're writing C++ today (C++20/23), thank 2013. That was the year the committee stopped polishing the deck chairs on the Titanic and started rebuilding the ship.

2013 was the year C++ stopped being your dad’s systems language and started flirting with modernity. The ISO standard known as C++11 (published late 2011) had finally trickled down from compiler god-mode to everyday build systems. GCC 4.8.1 was solid. Clang 3.3 was a revelation. Even Visual Studio 2013— yes, Microsoft —started playing catch-up with real move semantics and variadic templates. Let’s start with auto . In 1998, auto was a joke—a keyword that meant "please ignore me." In 2013, auto meant finally, I don't have to type std::vector<std::unique_ptr<Foo>>::const_iterator like a medieval scribe . 2013 c++

Systems programmers who want speed without sacrificing sanity. Game devs tired of manual memory management. Embedded engineers who just discovered constexpr . And nostalgic millennials who remember when std::make_unique finally arrived in 2013 (yes, it was added via a defect report). JavaScript developers who faint at the sight of && or ::