News for hackers. Stuff that matters.
Re:Modern C++ Won't Save Us by geezerjay on Wednesday April 24, 2019 @02:01AM (#19735923)
> So instead of trying to figure out which one of the dozens of GUI frameworks to use in making a window and have it change colour, you just write it using the standard library.

Congrats, now you're stuck with something like Xwindows or MFC or AWT.

Re:Modern C++ Won't Save Us by daemin on Wednesday April 24, 2019 @05:45AM (#19736860)
They're standard for the OS but not a standard for the programming language library.

Granted AWT wasn't great but you could still make a GUI with it straight out of the box. It allowed you to make windows and buttons and start exploring the programming language.

Like I said having a standard library option won't eliminate third party libraries, it will just provide something in the box for people to start using straight away.

Re:Modern C++ Won't Save Us by pjmlp on Wednesday April 24, 2019 @04:01AM (#19736435)
Which while not ideal, are guaranteed to be present, contrary to third party libs.
Re:Modern C++ Won't Save Us by geezerjay on Wednesday April 24, 2019 @10:47AM (#19738860)
That assertion is disingenuous at best.

That guarantee is only achievable at the expense of forcing compiler developers to maintain a GUI toolkig for all platforms. Who in their right mind believes that's reasonable or desirable?

Re:Modern C++ Won't Save Us by pjmlp on Wednesday April 24, 2019 @12:15PM (#19739901)
Everyone that wants a language to thrive instead of dealing with thousand incompatible implementations.

Many C++ targets don't support IO or networking, so lets not burden embedded compiler developers with standard library bloat.

Re:Modern C++ Won't Save Us by daemin on Wednesday April 24, 2019 @12:05PM (#19739795)
So instead of a GUI library what about a HTTP or a network library as part of the standard? Surely handling TCP and UDP connections is an order of magnitude easier to implement and maintain.