Skip to main content

in reply to daniel:// stenberg://

I love this part:

> Just very recently I decided to stop fighting those methods and instead go with them.

This entry was edited (8 months ago)
in reply to daniel:// stenberg://

Indeed. It's also difficult to realize / accept that a process that's served you well for many years is no longer the best fit for the future. So realizing, accepting, and adhering to that is worthy of recognition!
This entry was edited (8 months ago)
in reply to daniel:// stenberg://

I wish more projects did the same instead of keeping their elite, deserted mailing lists. On one hand it's not something I've ever got to experience, on the other hand I don't feel like going through them so 🤷‍♂️
in reply to daniel:// stenberg://

it is indeed worth reflecting over what other old habits or practices we stubbornly stick to that we should rather change and embrace the modern ways... I appreciate that a project can only stay alive and agile if it manages to keep with the times.
in reply to daniel:// stenberg://

I must appreciate the way you have been dealing with this project and we are having the benefit of hard-toiled work yours and others.

Kudos.

But ..but .... subtracting should be the norm. Although, the inclination to opt for something "modern and flashy" is upheaval.

My 2 cents, Daniel.

in reply to daniel:// stenberg://

darn skippy, the tools are born of the community or as I usually say “the process comes from the team”. The community changes over time and so does the process and tools.
in reply to daniel:// stenberg://

i love to hear this. I'm a 1900 guy (so not very young) but I really never got the mailing lists/patches thing, it seems complex even for me who consider myself a tech-savvy (I write code day to day, devops, etc).

I hope to contribute there soon.