Open source, standards and ... iron

This morning I had the chance to look at such acquaintances as a developer, things like open-source and standards from a different perspective. And the reason for this was an ordinary iron.

The background is as follows. I had an iron (application) from a well-known company Tefal. It worked quite stably, was easy to use and slightly demanding of resources. Like any other application, occasionally there were glitches - at a certain inclination water dripped from the evaporator. But in general, he was fine with me.

And there was a nuisance - the iron fell from the ironing board. It's okay, but one corner broke off. Part fell out, the other inside. Small household breakdown, a little glue and ten minutes of work. If it were not for one “but” ...
')
Taking out the glue, a set of tools, spreading a rag on the table and putting the iron on top, I found that the case is twisted with one single bolt, which is unscrewed with a hexagonal star screwdriver, not to be confused with the hexagon, with a hole in the middle (the application was developed without observing generally accepted standards). I have never seen such bolts (in a broad sense). I think the right screwdriver is not in every store, if at all. Thus, the use of non-standard technologies makes the iron (application code) closed and inaccessible for change (not open source). As a result, I have to either use a broken iron or go to the Tefal service center so that they can repair the iron with their special screwdriver (contact the developer for paid support).

Because of such a simple thing as a single bolt, I have to lose time (half a day on the road, and still wait for it), spend money (road + repair) and nerves (what the fuck do I have to go somewhere and pay something ?!)

But I could solve the problem simply and quickly if the bolt were standard, and the iron itself, as a result, open and available for change ...