Cairo 2D Graphics May Become Part of ISO C++

An anonymous reader sends this news from Phoronix: "The C++ standards committee is looking at adopting a Cairo C++ interface as part of a future revision to the ISO C++ standard to provide 2D drawing. Herb Sutter, the chair of the ISO C++ standards committee, sent out a message to the Cairo developers this week about their pursuit to potentially standardize a basic 2D drawing library for ISO C++. The committee right now is looking at using a C++-ified version of Cairo. Sutter wrote, 'we are currently investigating the direction of proposing a mechanically C++-ified version of Cairo. Specifically, "mechanically C++-ified" means taking Cairo as-is and transforming it with a one-page list of mechanical changes such as turning _create functions into constructors, (mystruct*, int length) function parameters to vector<struct>& parameters, that sort of thing — the design and abstractions and functions are unchanged.'"

Re:Sure, why not

[Anonymous Coward]

C++ stopped being a fully-humanly comprehensible language a long time ago. Might as well just add more crap to it like it's going out of style.

Competent programmers stopped being formed a good 10-12 years ago. The JAVA/.NET generation is a fucking disaster.

standard c++

[mevets]

Is there anything it cannot do?
The old C++ looks better and better as they nail every bit of crap they can find to her wretched offspring.

Re:Sure, why not

[rubycodez]

don't have to, you could mark everything inline and define in the header without typing each function declaration twice.

not recommended for general practice 8D

Re:standard c++

[StripedCow]

Is there anything it cannot do?

Garbage collection.

Re:But... why?

[Anonymous Coward]

So, my question really is why they are doing this? I'm betting the answer is not one where they have actual usecases in mind.

Firstly, I take issue with your premise that Cairo is no more than a toy and useless in actual work.

Secondly, One very important usecase for a simple drawing library in the standard is to provide an easy route for novices to write cool, interactive and meaningful programs, without needing to write several hundred lines of scaffolding code and be well-versed in 6 different layers of abstraction from OSes to frameworks and graphics API.

I don't know how other people learned programming, but in my case, the most engaging things I wrote all those years back in BASIC and Pascal (under DOS) were graphical programs in nature (extremely simple games, GUI-like apps that didn't really need the GUI, function plotting and other graphical toys, etc.) I'm guessing that I'm not unique in the fact that having access to simple, straightforward, inefficient, well-documented, built-in 2D graphics API led me to all sorts of cool experiences in programming and (majorly) determined my pursuit for the rest of the two decades since.

Now, it is obvious that there will always be more novice programmers than experienced ones, so, I don't see the problem with the ISO C++ committee to explore standardizing such a library. Do you, really? Who is this going to hurt?! For most of us, this is pretty much out of our way, since we either write more serious graphical applications and need platform-specific, performance-oriented APIs that offer much more control and features, or we haven't written anything that needed a 2D immediate-mode graphics API in years. So, I ask the Slashdot readership again, what's wrong with standardizing a simple, straightforward 2D drawing API to help the novices and the occasional non-performance-sensitive drawing needs of the community?

Re:huh?

[Behrooz Amoozad]

Do you develop for windows? I suspect yes, because in linux we've had this library for years and everyone knows it's a freakin' cross-platform library with very good documentation, coding style, naming convensions, specs, ...
Stop ranting already.

Re:But... why?

[Gavagai80]

Qt doesn't get out much beyond Win/Lin/Mac.

Qt isn't available for enough platforms because it only runs on Windows, Mac, Linux, Android, iOS, Blackberry, Kindle, vXWorks, BSD, Solaris, Haiku, WebOS, OS/2, Tizen and AmigaOS? Anything that passes the "does it run on Amiga?" test is good enough for me.

Re:Sure, why not

[celle]

"The JAVA/.NET generation is a fucking disaster."

      Fucking disasters is more like it and all the coupling is creating a whole new generation of mega disasters.

Re:Sure, why not

[rsilvergun]

News flash, the vast majority of _all_ people are like that. Very few people are capable of being the sort of 'Rockstar' programmer you're pining for. And what's wrong with that? Is it just me, or do we as a society just have unrealistic expectations of people? If you can't work 70 hours a week banging out amazing code non-stop you're worthless as a human being just because somewhere out there is someone who can. We hold up what are essentially freaks of nature that don't need sleep as the norm and wonder why the rat race is getting so awful...

Re:Sure, why not

[Anonymous Coward]

Wrong. I turn away 95% of the people who send in resumes because they don't understand what they're doing. They don't understand the logic behind anything, or what's happening in the background. I personally interview everyone, and I can attest to this fact. Self-taught people typically have drive, intelligence, and interest, and those things combined enable them to be competent.

Your expectations are either a) unrealistic

They're unrealistic in the sense that most people don't meet them. That's fine by me, as I don't accept garbage. But the fact is, some people do meet or exceed my expectations, and I'm quite happy even though there aren't many who do.

Re:That's unfortunate

[Anonymous Coward]

Really?

glVertex2d
glVertex2f
glVertex2i
glVertex2s
glVertex3d
glVertex3f
glVertex3i
glVertex3s
glVertex4d
glVertex4f
glVertex4i
glVertex4s
glVertex2dv
glVertex2fv
glVertex2iv
glVertex2sv
glVertex3dv
glVertex3fv
glVertex3iv
glVertex3sv
glVertex4dv
glVertex4fv
glVertex4iv
glVertex4sv