it would be interesting if instead of making migration tools - one shot - you could do a migration then sync.
Easier said than done, but changing peoples chat app from under them in an org is a stressful thought. If they could run side by side in sync until a critical mass has moved over, then sunset the old one, or not.
Seems fairly useless to me, for a few dollars I can sample the L1 frequency with a dumb device which has no idea of speed or altitude, and do the calcs with FOSS which is in the wild.
Basically a rule which inconveniences the honest and has zero impact on the bad dudes, whoever they are
There is a bit more to it on ARM I'm afraid. The device trees are complex and it feels to me it takes it out of the realm of 'anyone can and should do it'
I just did this at home, and my 9 year old, without my bias or prompting, was pointing out that sea of thieves and MSFS are both microsoft games but run better on Linux
I can't believe what a non-event it was switching the kids over
I feel like we are of a similar age. This is great advice. My small company is growing and i'm thinking this is the path so I don't need an IT helpdesk.
Do you still use vi or were you meaning vi(*) and actually use something else? I've been on vim for a while but happy to go back to vi
Have them make something difficult and time consuming to make, out of a flammable material, then as soon as it get's a pass from a supervisor they have to burn it.
i love HN but also starting to think it's time for us oldies to have our own one: cost of entry, having a distant memory of booting linux from a floppy
Easier said than done, but changing peoples chat app from under them in an org is a stressful thought. If they could run side by side in sync until a critical mass has moved over, then sunset the old one, or not.