sandwell
Joined 13 years ago
Joined 13 years ago
73 de G4IYT :)
There are some other apps designed for having QSOs - VBand[1] and Vail Repeater[2].
Finally if you want to learn to use morse code on the air check out Long Island CW Club[3]
[1]: https://hamradio.solutions/vband/ [2]: https://vailmorse.com/ [3]: https://longislandcwclub.org/
So it was the wife's phone that changed the meaning of the message, not his.
Through nix-env it even already has the idea (albeit discouraged) of imperative package management like apt.
Having spent a while with NixOS, running containers for user applications seems like using a cannon to kill a fly. The 'simple' alternative is to drop FHS altogether - which containerization is kind of doing in a roundabout way by isolating the app filesystem from system fhs.
As for it being for developers only... I get that perspective. Debian/Ubuntu packaging is also hard, AUR packaging has its quirks. A lot of this is hidden behind the package manager, wheras with NixOS it is more obvious.
The killer idea for NixOS would be to make package management for Joe Q Public as easy to use as apt while. Tools like MyNixOS[1] are emerging which might bridge that gap.
I've spent a lot of time writing YAML for Ansible, Cloudformation, k8s, Helm, etc. Some of the issues this article mentions are pitfalls but once you get a bit of experience with it, you know what to look out for.
I've also spent and a lot of time writing Nix expressions, which is much more "joyful" IMO. Seemingly simple features like being able to create a function to reuse the same parameterized configuration makes life much easier.
Add in a layer of type safety and some integration with the 'parent' app (think replacements for CloudFormation's !GetAtt or Ansible's handlers), the ability to perform basic unit tests, then configuration becomes more like writing code which I consider a good thing.
They have an incentive to provide easy access to their media, so pirating is always going to be more complex, which will be a barrier to the majority.
Android is pretty darn fragmented though.
I expect that aftermarket firmware would be an issue for content providers. For example, is Netflix going to allow third party firmware developers to create an app to access their content? They will already have contracts with content distributors like Lionsgate that mandate DRM in their own apps to prevent piracy.
If your aftermarket firmware doesn't support Netflix, Prime, HBO, etc then it might have limited appeal. Browser based apps might get around that in a limited way.
As for printers, I think of them as loss leaders to generate ink sales.
Don't know either space particularly well so might be wrong.
One of the most rewarding training experiences was giving my old Haskell textbook to a junior team member and watching his (at the time .NET, w/LINQ) code change over the course of a few weekends.