awesomegoat_com

This reminds me the blog one would write around 2006. Not the text content, but the pixelated font and pictures of winamp wibe like that.

Myself, I am rather happily using mplayer - without any gui. Initially it was practicality of not leaking memory - like many gtk+ apps would do. Now, it is pure utility.

I have seen this so many times. You almost made me weep.

It's tragedy of commons. To stop this we need software engineers to own their own code legally.

Nod.

I would love to hear more about these rewrites.

Today, I woke up feeling that elixir/phoenix is the best platform for rewrites.

I mean, when you know the problem domain well, you can build a master piece in elixir/phoenix. I still feel that putting together the first prototype has to be faster in ruby on rails.

> I date in my age group.

Sometimes changing the proposition can drastically change the outcomes.

Haven't sandboxed programs in a privileged context been the root cause of me seeing BSOD so often in the late 90ties?

More spiritual society is the less stuff it needs to amass.

One of the theories goes that ancient civilizations made progress in non material domains. How else would you explain these thousands years long periods in the history when a table or a spoon looked the same. And nothing visible happened?

Yes.

IIRC, Patternfly started many years ago, because many open source project (of Red Hat interest), had inconsistent ui. The idea was to develop a common guideline that other open source projects could use and be somewhat consistent with each other. To have a framework, artwork and guidelines that would be available on permissive terms forever.

Are we surely going in the right direction?

Shows power of market forces. And price sensitivity of the buyers.

> it requires devoting time and effort towards its upkeep, and that is not our core business, nor should it be.

I would try to argue that this in fact may be subjective.

For me, updating all the dependencies in my stack every morning is a productivity routine that gets me started. If I spend a 30 minutes studying changelog of a dependency and linked github issues, I don't see that time as wasted even though it often does not contribute to the business. I think it has three benefits.

- easy morning start routine to get going

- developer education, expanding horizons

- code climate; having warn feeling in the gut of not falling behind, wanting to avoid dirty plugs and monkey patches, ability to work on the HEAD, should an issue arise.