Vittorio Romeo
vittorioromeo.info · Personal blog · on HN since 2016
Vittorio Romeo is a C++ developer who writes about modern C++, compile-time techniques, game development and language design.
What HN saysHN links his proposal to fix C++ with Rust-style epochs, and his book on modern C++, which commenters criticize for splitting the language into dialects.
15HN people shared it
5linked it in comments
22stories submitted
603story points
2 years agolast shared
2016people per year2026
Most-shared posts
- 1Fixing C++ with Epochs7 people · 8 points · first shared 2019 · discussion on HN
- 2Vrsfml: My Emscripten-ready fork of SFML3 people · 3 points · first shared 2024 · discussion on HN
- 3Wordlexpr: Compile-Time Wordle in C++202 people · 107 points · first shared 2022 · 8 comments on HN
- 4Compile-time iteration with C++20 lambdas2 people · 3 points · first shared 2018 · discussion on HN
- 5Why choose sum types over exceptions?2 people · 3 points · first shared 2017 · discussion on HN
- 6Modern C++ gamedev: thoughts and misconceptions1 people · 221 points · first shared 2020 · 217 comments on HN
- 7The Sad State of Debug Performance in C++1 people · 146 points · first shared 2022 · 108 comments on HN
- 8Implementing secure leaderboards for my game1 people · 96 points · first shared 2021 · 17 comments on HN
- 9Show HN: Quake VR – Quake (1996) as a first-class PCVR experience1 people · 6 points · first shared 2022 · discussion on HN
- 10On the recent 'lambda vs. iterator' paper1 people · 4 points · first shared 2016 · discussion on HN
- 11Zero-allocation continuations in C++171 people · 4 points · first shared 2017 · discussion on HN
- 122018 Jacksonville ISO C++ meeting report1 people · 1 points · first shared 2018 · discussion on HN
- 13My CppCon 2016 trip report (thoughts on my favorite talks and my sessions)1 people · 1 points · first shared 2016 · discussion on HN
- 14Emcpps1 people · first shared 2023
What HN people wrote when they linked it
SuperV1234 · 2024-09-30
I'm working on a Emscripten-ready fork of SFML that brings several key improvements:
- Modern OpenGL and first-class support for Emscripten4 - Easy to use drawable batching system - Enhanced API safety at compile-time - Flexible design approach over strict OOP principles - New audio API supporting multiple simultaneous devices - Built-in SFML::ImGui module - Remarkably fast compilation time & small run-time debug mode overhead
More info: https://vittorioromeo.info/index/blog/vrsfml.html
tkhattra · 2023-07-27
yep, the authors of "Embracing Modern C++ Safely" [1] are Bloomberg folks
[1] https://vittorioromeo.info/emcpps.html
tialaramex · 2022-05-30
Sure, the effect of such guidelines, including the "Core Guidelines" is to further shatter the language into effectively incompatible dialects while not really solving anything.
One of the book's authors actually proposed work to get C++ to a place where C++ 20 could begin actually abolishing the things everybody agrees you shouldn't do, Vittorio's "Epochs" proposal. https://vittorioromeo.info/index/blog/fixing_cpp_with_epochs.html
But the preference for C++ 20 was to add yet further stuff. I believe that, unwittingly, the C++ 20 process sealed the fate of the language in choosing to land features like Concepts but not attempt Epochs, I'm not sure it was actually possible, but if it wasn't possible in 2020 it's not going to be any easier in 2026 and it's only going to be more necessary.
wscott · 2020-05-22
C++ needs to just steal the idea of Epochs from Rust
https://vittorioromeo.info/index/blog/fixing_cpp_with_epochs.html
By default, everything is backward compatible, but to use new features you need to declare this compilation unit as being part of C++23 (or 26, 29). Then code that uses the new stuff also ignores the old and can have different rules. But it can still be combined with legacy code and libraries. You know at compile and linking time when crossing boundaries and can do the right thing. This actually combines nicely with modules since we already need a new build infrastructure to take advantage of modules.
steveklabnik · 2020-01-03
This is the idea for the 'epochs' proposal https://vittorioromeo.info/index/blog/fixing_cpp_with_epochs.html