That might have been me! There were one or two M stations there. I heard a couple of stations calling CQ. Very difficult to pick out signals without any filtering.
Very cool. It does get a bit chaotic when there are a number of people keying. If there was the ability to add a narrow filter then it could be usable for a QSO (radio contact)!
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]
> The problem was that Emine's cell phone was not localized properly for Turkish and did not have the letter <ı>; when it displayed Ramazan's message, it replaced the <ı>s with <i>s.
So it was the wife's phone that changed the meaning of the message, not his.
Also a Nix/NixOS user/contributer. I feel like Nix+nixpkgs could become the universal packaging solution adapted to build deb, rpm, etc packages.
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.
Agree with the final part of this article that "programmable" configuration languages like Nix and Dhall are the way forward.
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.
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.
I wonder if it is possible to generate a ROT8000 quine, that is a phrase like "hello world" which yields a semantically matching phrase in some other language?
I love that effect. My JS changed a lot once I grokked LISP, and I finally understood why there was a Haskell course on my degree track.
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.
I've seen a lot of embedded Forth stuff recently but I don't get the appeal. Clearly there is some benefit over writing assembly, but why is it preferred over portable C, or even higher level languages such as Python on more powerful mcus?
FWIW I felt the same way about LISP for a long time until I fell in love with it via Emacs. So please educate me!
Especially since they are publicly funded, so UK citizens are paying to have their data transmitted to unknown parties and advertised at. Oh, and if you don't pay it? Fuck you. The government will send bailiffs to seize your property to pay the bill, or imprison you for up to 3 months.
Strange hobbies indeed. The latter part of your comment is reminiscent of the goal of the MAME project:
> MAME's purpose is to preserve decades of software history. As electronic technology continues to rush forward, MAME prevents this important "vintage" software from being lost and forgotten. This is achieved by documenting the hardware and how it functions. The source code to MAME serves as this documentation. The fact that the software is usable serves primarily to validate the accuracy of the documentation (how else can you prove that you have recreated the hardware faithfully?).
Those guys are doing a very good job of "documenting" a specialist subset of systems, even without support from vendors.