11–20 of 444 posts
Is there a case for or against incrementally adopting Rust ?
They are experimenting https://chromium.googlesource.com/chromium/src/+/refs/heads/...
On voices against stripped down C++ (via code style): I find it working great in practice. Makes the codebase manageable, and keeps people away from using unnecessary complex language features (imagine Java code heavy with streams or reflection, or Python code that resolves most of dependencies at runtime, javascript full of eval(), etc.). Switching to a new language is half-baked plan.
Writing Chromium grade C++ seems like a hard job with all these extrinsic rules and regulations to make it work
As expected modules are relegated to some later time ("will be its own experiment")
Damn. May as well have used a language that isn’t released yet like Zig. That’s a ton of problems.
Thus making the once famous clang having an honorable third place in ISO C++ compliancy.
Seeing this from a Google team makes it even more ironic.
Earlier quoted context omitted.
They are experimenting https://chromium.googlesource.com/chromium/src/+/refs/heads/...
Is there any common module that can be shared amongst browser engines? I can feel though it sounds hard to extract these common stuff into .. "browser engine common core"? (e.g. https://github.com/SerenityOS/serenity/tree/master/Userland/... ). That would be nice for next gen browser invention.
I stopped using C++ after lambdas were introduced (10 years ago or so?) Is there anything I can read to get up to date quickly?
Is one release really causing so many problems? I thought C++ treated backwards compatibility as a holy thing.
Edit: There are also quite a few deprecation warnings, which are also not errors per se, but nevertheless you'd want to avoid using deprecated stuff of course.
I stopped using C++ after lambdas were introduced (10 years ago or so?) Is there anything I can read to get up to date quickly?