In the article they call out that MARKETING can be date based

We could make it so profit wasn’t the prime motivator, instead it’s main motive would be to provide a public good. We would call it a public utility.

Or Fedora.

I feel like Fedora has the same pragmatic approach (allows non-free drivers, packages, etc.) and is just as easy to use.

JubHub

You can always fork it if you don’t like the choices they make

That’s the point the OP is trying to make about the advantage of open source

That's happened like three times to the extent that the forks are more widely installed than the original

And people did but it is hard against Redhat that has actively made harder and harder to use Gtk+ outside GNOME.

What changes have been implemented in GTK that make it harder to use outside of a GNOME environment?

practically everything in GTK 4. It removed menu bars ffs

As far as I can tell, every major version of GTK should be thought of as an entirely separate project, and nothing in GTK 4 made GTK 3 or GTK 2 harder to use.

Please link me to the python3 gtk2 library so that I can migrate all my python2 gtk2 software to python3 without rewriting the entire UI. Thanks in advance!

what does make GTK2 harder to use is that it is not supported anymore. you can't build or run GKT2 based apps on new systems without building the GTK2 libraries yourself.

Haha I was thinking the same when I read he hand filed it

As it is with any box, there is only so much material you can remove from the corners before it disintegrates into disconnected surfaces.

Filing vs. CNC doesn't make one bit of difference.

With a CNC you can make sure you'll get a uniform curvature.

You can get uniform curvature when filing. Ever hear of filing buttons? Or checking your work with a radius tool until you are in compliance? Stop talking about what filing can't do if you don't know anything about filing.

That only goes one level deep so it’s not much of a guarantee

That’s because it uses the WebKit renderer built in to iOS

This

Rebase only makes sense if you making huge PRs where you need to break it down into smaller commits to have them make sense.

If you keep your PRs small, squashing it works well enough, and is far less work and more consistent in teams.

Expecting your team to carefully group their commits and have good commit messages for each is a lot of unnecessary extra work.

You could still support a subset of the most common features like bold, italic, strike, bullets, links, etc.

Isn’t the beauty of MD supposed to be that if you can’t render it it should still look fine as plaintext?

Even these basics are not consistent. See my Markdown Monster:

https://git.sr.ht/~xigoi/markdown-monster/blob/master/monste...

There should be only one correct interpretation of that according to CommonMark. Software is faulty for sure and a lot of the these "markdown converters" are pre-AI slop code but at least there is a carefully written spec now.

(That dude who coined the name Markdown is being a dick about other people finishing his abandoned idea is another issue and not the fault of CommonMark.)

The problem for web browsers is that markdown is technically a superset of HTML.

Why is this a problem? To me it sounds like a it would be an advantage because you have everything you need to render it already built into the software.

Rendering is trivial. The issue is standards, and the DOM. No-one can write a Markdown implementation for the core of any major web browser in a form that is simultaneously acceptable to both their technical and political governance.

Best you’ll get is a plugin. Strictly arm’s reach. Translation only.

I'm not quite sure I understand what you are saying. Is the essence of what you are saying that it is hard to agree on a spec for the Markdown (and how it is translated to HTML or directly to DOM?) Or that this represents a technical challenge I don't understand?

I think you mean that any markdown byte sequence will also parse with some results using an HTML5 parser?

Content-Type should fix that.

Easy enough to associate *.md with one on most static servers too.

In what ways is it a superset? What can you express in markdown that can't be expressed in HTML?

Why is it a problem for web browsers?