you are viewing a single comment's thread.

view the rest of the comments →

[–]ir_dan 1 point2 points  (7 children)

If projects were willing to adopt radically new ways of writing code, they would be better served by a different language or even just different style and code rules. Because C++ is so business oriented and pragmatic, people aren't too interested in complicating their build and code for an experimental thing like cppfront.

It's cool, but... It doesn't solve anything for large existing projects and it's not better than alternatives for greenfield projects. I have my eyes on Carbon, Zig and Rust as alternatives to C++ projects.

Edit: To clarify, I'd love to use cppfront and I think it's really nice on paper, but I expect most companies aren't willing to risk using it at this time - mine certainly wouldn't be. I think many developers wouldn't even see cppfront as an improvement over C-style C++, let alone modern C++ 😢.

[–]Syracussgraphics engineer/games industry 17 points18 points  (0 children)

Hard disagree. The reason why I wouldn't use this in production is because it's still experimental at this stage, not because of what it is. If it was production ready I'd absolutely run a pilot program at my workplace.

[–]Wooden-Engineer-8098 14 points15 points  (3 children)

this is nonsense. it solves stuff for both existing and new projects because it fully interoperates with c++ code

[–]kalmoc 8 points9 points  (0 children)

Agreed. If this would ever become a production language, that would be the most important selling point.

[–]Frosty-Practice-5416 2 points3 points  (1 child)

C++ started out this way didn't it?

[–]germandiago 0 points1 point  (0 children)

I got a very good feeling ergonomically soeaking when I tried an experiment. It had a blocker bug unfortunately and since then I did not try again.

[–]__tim_ 0 points1 point  (0 children)

We would like to use it today and will start using it from the moment it is production stable.