this post was submitted on 25 Feb 2022
-1 points (33.3% liked)

General Programming Discussion

7810 readers
8 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 5 years ago
MODERATORS
Restioson@lemmy.ml
Cloak@lemmy.ml
-1
The "Shoemaker's Children" Problem (personaljournal.ca)
submitted 2 years ago by ttmrichter@lemmy.ml to c/programming@lemmy.ml
13 comments fedilink hide all child comments
 

Software has a problem.

OK, it has many problems. I've already highlighted one of them. But this is another important one.

The problem is that software—all software, with no exceptions—sucks. The reason for this is multifaceted and we could spend years and years arguing about who has the larger list of reasons, but in the end it boils down to the proverbial shoemaker's children: Our development tools are the worst of the worst in software.

you are viewing a single comment's thread
view the rest of the comments
[–] Helix@feddit.de 2 points 2 years ago* (last edited 2 years ago) (1 children)

often it’s just the problem of a very specific problem domain with very few eyes willing to work on it as a hobby.

Why do people always confuse FOSS with hobbyist software? There's lots of commercial FOSS out there, some even with a sane ecosystem.

For example, the PlatformIO IDE is part of a larger, commercial ecosystem. Open Source allows a code and architecture audit before spending a single cent.

[–] ttmrichter@lemmy.ml 0 points 2 years ago

Because a lot of it, even when "commercial" is hobbyist-grade at best.

PlatformIO being one of the ones I'd place there, incidentally. Failed out of the box for me (where "fail" involves "crashing") when I tried it, resulting me in spending more time debugging my tools than my own code. Which is exactly what I rail against in this article. Even this reeks of hobbyist work:

Multi-platform Build System without external dependencies to operating system: 50+ development platforms, 1000+ boards & dev-kits, 20+ frameworks. Arduino and ARM mbed compatible.

That focus on "boards" and "dev-kits" is basically useless for people who, you know, are making their own hardware. (Like my employer.) By the time you navigate through all that (often poorly-written and invariably poorly-documented) crud it's actually cheaper, in terms of development time, to write it from scratch in-house.

I genuinely gave PlatformIO a try for a work project. I had to ditch it and replace it with a hastily-assembled ST HAL-based from-scratch project to get it done in time for the test cycle. It's simply not suited to the use cases I have both because of the crashing issue and the way hardware support enters the picture (which revolve around 100% custom hardware in our shop).

Had the first issue not been there, I might have had more patience for the second one (and vice versa), but the two together made it a show-stopper and added to the long list of shoemaker's children.