I brought up that point at the committee meeting. Browsers were clearly not a target for the proposal, and nobody was surprised by my statement.
-
-
Replying to @jfbastien @grafikrobot and
So does the committee want users or not?
1 reply 0 retweets 0 likes -
Replying to @pcwalton @grafikrobot and
A proposal must have interested users, yes. A proposal doesn't need to satisfy users who want something else, which is the case for browsers and 2D graphics.
1 reply 0 retweets 1 like -
Replying to @jfbastien @pcwalton and
I am really curious who the users for this would be. Game devs who don’t want middleware? Application devs who insist on building the UI from scratch?
2 replies 0 retweets 1 like -
Replying to @stephentyrone @jfbastien and
People pushed "teaching" as one of the motivational use cases
1 reply 0 retweets 0 likes -
Replying to @Cor3ntin @stephentyrone and
OK, but the justification for the standard was weird policies around third-party code at big game studios. That’s pretty far removed from the teaching use case.
1 reply 0 retweets 2 likes -
As far as I understood the claimed consumers were - students - people who just want to put things on the screen (say, to do a graph) I don't disagree with helping them. I like things on the screen. That being said, I see flaws with the now-defunct proposal: (...con't)
1 reply 0 retweets 2 likes -
Replying to @jfbastien @pcwalton and
Flaws: - teaches the wrong thing - can't even put text on my axis I'd much rather have something that'll be similar to what high-end graphics are like (batching comes to mind). And I want all the complex stuff like text... understanding that it's complex!
2 replies 0 retweets 2 likes -
Replying to @jfbastien @Cor3ntin and
To me starting at the high level feels like putting the cart before the horse. Start with the basics, like what SDL gives you. See if that gains traction. Then go up the stack.
2 replies 0 retweets 1 like -
Replying to @pcwalton @jfbastien and
One issue is that nothing is simple about graphics or SDL. Probably an order of magnitude more complex than anything the committee worked on so far.
1 reply 0 retweets 0 likes
Yes, that brings me to my next point: There has to be some point at which you draw the line and say “this is no longer the C++ committee’s responsibility, it’s Khronos’”. Otherwise the C++ committee will grow to absorb everything.
-
-
JF Bastien Retweeted JF Bastien
JF Bastien added,
1 reply 0 retweets 0 likes -
Replying to @jfbastien @pcwalton and
More seriously: doesn't have to be Khronos. Diet Graphics said SVG. Deferring to other standards is totally OK. See date / time, regex, Unicode, etc.
1 reply 0 retweets 0 likes - 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.