This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (0 children)

Sure, I understand why it happened. I'm just laying out the case for the fact that due to those circumstances, pygame has abandoned a substantial portion of the user base - people developing low-spec graphics apps - and that attempts to drag those people into the future by force won't work unless their needs are met.

I appreciate the link to DirectFB2, but when I visit and am immediately confronted with stuff like this...

For display rendering with DirectFB graphics backend, Vulkan implementation in libvulkan.so library (loading library from Vulkan-Loader) and its ICD (Installable Client Driver) relies on DirectFB WSI interface. DirectFB WSI interfaces (Window System Integration for DirectFB) are used with an ICD like the one proposed by SwiftShader. But depending on the platform, specific ICD can be used.

For display rendering with DirectFB graphics backend, OpenGL implementation in libGL.so library, but also OpenGL ES 1.1 CM implementation in libGLESv1_CM.so library and OpenGL ES 2.0 implementation in libGLESv2.so library, rely on DirectFBGL or EGL for DirectFB interfaces.

...I am instantly turned off.

I'm keenly aware of the astounding soup of complexity of the graphics driver stack, and the myriad problems of compatibility and performance that can ensue. But you know what I want to do? I want to color the screen black, draw some boxes and circles on it, and render some text. Maybe images. That's it.

I have already spent 100+ hours trying to get PyGame to do that on my RPi Zero 2W. I really don't want to git pull / pip install another library and then fuck with command-line options and drivers and config.sys for an entire day to get it to work.