News for hackers. Stuff that matters.

A comment on Neither GCC nor Clang are compliant with standard C++. Parent comment

Re:Neither GCC nor Clang are compliant with standard C++ by t0mpr1c3 on Sunday July 19, 2026 @04:53PM (#48971579)
It seems like the history of programming languages since the 1980s has mostly been people trying to avoid C++.

First languages with run-times and dynamic types, and more recently lower levels of abstraction (Go, Rust).

[ Parent | on HN ]
Re:Neither GCC nor Clang are compliant with standard C++ by pjmlp on Monday July 20, 2026 @05:04AM (#48976116)
I was there, and C++ was all over the place on Windows, OS/2, Mac OS, UNIX/CORBA.

It was FOSS with its set of coding guidelines, that gave C a new wind.

Languages with runtimes and dynamic types go all the way back to Lisp and Smalltalk.

[ Parent | on HN ]
Re:Neither GCC nor Clang are compliant with standard C++ by t0mpr1c3 on Monday July 20, 2026 @10:29AM (#48979368)
> Languages with runtimes and dynamic types go all the way back to Lisp and Smalltalk.

Java was the 800lb gorilla though, wasn't it? Because it promised portability.

Why did Smalltalk not take off?

[ Parent | on HN ]
Re:Neither GCC nor Clang are compliant with standard C++ by pjmlp on Monday July 20, 2026 @11:01AM (#48979839)
Java was the 800lb gorilla thanks to Sun's marketing.

Write Once Runs Everyone has been the promise of several bytecode formats since UNCOL in 1958, with UCSD Pascal being the most famous one until Java came to be.

Smalltalk was already taking off when Java came to be, it had a role similar to .NET on Windows, on OS/2, with SOM (OS/2's version of COM), doing C, C++ and Smalltalk.

All IBM Visual Age IDEs were written in Smalltalk, however it was exactly IBM alongside Oracle that were the very first to jump onboard to the Java ship.

Thus one day of the other, Smalltalk was out, and Java in.

Eclipse started as a rewrite from Visual Age into Java, and many of the Java early frameworks were ports from Smalltalk.

Also note that while Java has a C++ like syntax, its execution model is closer to Smalltalk and Objective-C, thus why it was such a great fit for Sun, acquiring StrongTalk and re-purposing the JIT compiler into Hotspot.

[ Parent | on HN ]
Re:Neither GCC nor Clang are compliant with standard C++ by igouy on Monday July 20, 2026 @01:09PM (#48981641)
== Long-ago, Smalltalk systems could be file-copied from say win to mac to unices and would just work.

== Not standardized. Language vendors used proprietary code to lock-in customers and that fragmented the skills base. Skilled Smalltalk-A programmers were not-so-skilled with Smalltalk-B.

== Not free as in beer.

[ Parent | on HN ]