Heroku replaces its Erlang-based router with Go

Chat / Discussions
, ,
21

I have raised such concerns in the past in the build and packaging working group.

See build-and-packaging-wg/minutes/2023-11-07.md at 13a4350ad08bca5647208f0ff53fbff5eea41b75 · erlef/build-and-packaging-wg · GitHub for example:

  • Fred mentions that while he still plans to be maintainer, he has cut back his time dedicated to OSS work for work/life balance.
    […]
  • A question asked was “how do we fill the gap?”, which is an issue with a growing portion of the tech industry lately
    […]
  • No good answers but to be a bit concerned.

The EEF does play part of that role for some of us, of being that bridge for keeping in touch and making these calls. I’m also running the working group at the same time so if I want to spend more time on some things, I have to let go of others as well.

The sort of problem is that more or less everyone who participates to these working groups is also doing it out of passion and on the side as their job function rarely (but sometimes) aligns with it. So when a maintainer goes “well, I gotta cut back time and the project is at a greater risk”, nobody in the room actually has bandwidth to do much about it.

Hence why people go to money as an option. The oss work we do is valuable. It could be worth paying for. In many cases the foundation can’t compete on engineering cost with businesses hiring people either.

2 Likes
22

k8s is not only for scaling.

It is just a very convenient replacement for a old plain unix with deb files. It replaces package manager, systemd, etc.

23

Some 20 years ago at the Swedish Social Insurance Agency all back end was developed in C++ using Tuxedo as signalling scalable middleware (BEA Tuxedo, same company that developed WeblogicServer i recall).

In a project there was one architect handing over a project to me where he had decided to switch to Java in the back end because “it is easier and better”. Period. That was his personal view of the matter and well, it happened. It took us 2 years to deliver the project and we developed the same software 3 times before all platform stuff was in place.

Sometime the world is bigger than just the develop-part. Value comes when software is in production and, well, we couldn’t have things in production unless there was a framework for that in place with monitoring etc. The project also introduced WebLogic Server and some bridge between the two to middlewares the game park that needed to be properly setup for production.

Point is, it took one man that didn’t approve on the technology we used a simple “i think this is better” to start introduce new core technology in a rather huge organization…

1 Like