4 ms·

Also there is a serious problem: It is often not fun at all. Abstracting hardware as an open-source API is definitely a more painful job then other kind of pro

Also there is a serious problem: It is often not fun at all. Abstracting hardware as an open-source API is definitely a more painful job then other kind of projects like a web project. It's because you have absolutely no control over how the hardware works, and each hardware vendors work differently. The worst moment is when the maintainer receives a reaction like this: "Oh it doesn't work on my hardware. Plz fix it". How the hell to fix it when the maintainer doesn't have the hardware? But there are people complain and criticize that the maintainer doesn't do the job for them. You can easily see these kinds of cases in desktop related project like Sway Wayland compositor. (mainly because of Nvidia of course.)

LeonM 6y ago
> It's because you have absolutely no control over how the hardware works, and each hardware vendors work differently. Replace 'hardware' with 'browser' and you are in the same situation. As someone with a degree in embedded systems engineering, I have a lot more sympathy for hardware quirks than browser quirks. Hardware can't easily be updated, browsers can. > It is often not fun at all. I'd rather spend weeks researching a hardware bug than spending hours on SO to find CSS hacks to make some browser render my page properly.
- kbumsik 6y ago
  > I'd rather spend weeks researching a hardware bug I would too, but only if it is my hardware. But for other guy's hardware who want to use your project? I will loose an interest if it is a free job. At least web browsers work in the same way in many cases. Of course there are some cross-browser incompatibilities but workarounds are not as hard as hardware.