I am guilty of that as well.

I somehow value my time more than the money. I think that I have some kind of stake/interest in things I dedicated my time to.

Though I am always thankful (as Eric is in this post) for the people and the income. I can't help but feel regretful as the product of my time and dedication is discarded.

If you would like to put that advice to practice, this book will help.

(The Art of impossible) https://www.amazon.com/Art-Impossible-Peak-Performance-Prime...

It guides you through discovering your mix of passions and strengths to land on what you might make you uniquely extraordinary.

What works for me is "accepting myself".

Accepting myself meant accepting the universe. Even the parts I hated. The suffering. I didn't have to love it all, I just had to accept the balance.

This has helped me be at peace. Once I am at peace, I can be creative.

During a global chip shortage?

I believe 2025 deadline would be the best timing for this push because PC sales will decrease because many people/companies already bought PC in 2020-2022.

They are: https://github.com/tailscale/tailscale

A fair bit of the client code is also on the repo. Things like role based access control that require a backing store on tailscale side aren't open.

No, that's only the client.

Good stuff. Thanks for sharing.

Wow! This product is making my day. Great job.

I am still hacking around on it. I would like to sign-up as a team, though I only have need for 3 seats.

Thanks! If you send me an email (in my profile), happy to make that work for you

I too "cultivate my own garden".

Like the "Turk" in Vaoltaire's Candide, working on my product (garden) insulates me from the wants and worries projected by todays internet.

Here is my garden: https://www.gorelo.io/

Publish your apps without .net core (--no-self-contained) and install/manage runtimes as you usually would.

If you have thousand apps, you probably also have a CI/CD system and you can gain fine grained control on your runtime management needs with .net build/publish.

MS does quite a few things poorly but they have done a solid job of operating in large enterprises.

"Publish your apps" isn't the issue: I support a lot of applications I don't build or have the source code for. And they may be on my network for over ten years.

The problem is if developers are publishing self-contained apps with .NET Core, IT staff will be up a creek on vulnerability mitigation. While being able to pin specific .NET Core versions is nice for developers, being able to require the most current .NET Core version be used is important for IT staff who have to support these applications.

I'm expecting as this issue plays out, there will be a way to inject an updated framework to an existing app with a utility tool. Probably first party but definitely third party.

> you probably also have a CI/CD system

Or more realistically, dozens of CI/CD systems, covering less than a third of the applications.

You are trying to something slightly complex. I don't see how one could make it any easier from a language design perspective and staying idiomatic to the language.

Go: Goroutines make you wire the "stop" scenario on your own (channel close). Rust: Hold on to your future and drop() it. C#: Pass a cancellation token and call Cancel()

All seem reasonable and stay within what they think their developers will be able to pick up and run with.