2 ms·
Why are people trying to turn C++ into python, complete with it's legacy useless cross platform UI library (ktinker). We know from experience that this is a ba
by shadowmint 11y ago
Why are people trying to turn C++ into python, complete with it's legacy useless cross platform UI library (ktinker).
We know from experience that this is a bad idea, and a waste of everyones time.
Build your application layer logic onto of a robust module ecosystem, don't try to bake it into the standard library.
...but even if you were to say, want to do this, this is a horrible legacy api before it even exists!
Hard coded color constants? (antique_white? alice_blue? Are you kidding me?)
Font support, including (presumably) true type font parsing?
Brushes and gradients?
No mention in the whole document are programmable graphics pipeline? (ie. shaders)
No mention of device independent output scaling?
Maybe we can just fork inkscape and put it into the standard library?
I know this sounds harsh, but have the authors of this proposal actually built anything using a 2D graphics api recently?
This is a high level 2D vector graphics day dream.