IssueRaiser

That is an excellent comment.

That is an excellent comment. I wish I could give you a prize, but all I have right now is a banana. Every time somebody mentions the "C++ replacement" aspect, people freak out because you can't use Go to write Unreal Engine 6 in it. There was a talk/video somewhere where Pike/Griesemer explained how it all started. They were waiting for some gigantic C++ project to compile on their compile farm and every compile took hours . So during one of these down times, they started shooting ideas back and forth of how to speed up compilation . Then they figured out it's easier to start a new language with simple parsing rules than to fix the mess that is C++ grammar. That's really it - it started with a pain point about C++ compilation speed, not C++ performance.

Posted by PopsiclePete on Mar 26, 2015, 3:50 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments

reliability (Other)

That is an excellent comment.

PopsiclePeteMar 26, 2015, 3:50 PM

That is an excellent comment. I wish I could give you a prize, but all I have right now is a banana. Every time somebody mentions the "C++ replacement" aspect, people freak out because you can't use Go to write Unreal Engine 6 in it. There was a talk/video somewhere where Pike/Griesemer explained how it all started. They were waiting for some gigantic C++ project to compile on their compile farm and every compile took hours . So during one of these down times, they started shooting ideas back and forth of how to speed up compilation . Then they figured out it's easier to start a new language with simple parsing rules than to fix the mess that is C++ grammar. That's really it - it started with a pain point about C++ compilation speed, not C++ performance.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue