The BSDs are definitely not for everyone, and they come with their own set of tradeoffs. However, it is safe to say that all BSDs are better today than 10 years ago. Small and steady improvements over time.
286 karma · joined June 26, 2021
The BSDs are definitely not for everyone, and they come with their own set of tradeoffs. However, it is safe to say that all BSDs are better today than 10 years ago. Small and steady improvements over time.
We're using this Philips Labs module at $dayjob. It's a great piece of work!
For scripting, it's better to resort to a simpler solution that doesn't even need complexities like parsing or data types. In a Unix environment all you need is the ability to compose commands together. This is what execline is for:
We do meandering sync calls[1] for 1 hour, four times a week. Plus a weekly demo call.
It's a matter of how much your management cares about developer experience and efficiency. Get another job :)
[1]: https://www.honeycomb.io/blog/standup-meetings-are-dead/
A classless CSS framework that makes content look like it would have in the very first web browser – the Nexus browser.
Because yeah, trying to change Alpine's init system, mdev, or other coreutils is indeed not easy/feasible at the moment.
On a side note, I know that skarnet is working towards declarative service files as a possible interface in the next major versions of s6 and s6-rc:
https://skarnet.com/projects/service-manager.html#plan
>> Declarative service files. The model of unit files, where users can just write key=value lines instead of scripts, has been a resounding success for systemd — and it is also good end-user design (provided the parser correctly validates the files). And it can be done as a separate user interface layer, running on top of the more minimalistic engine.
I think this is a key part of the problem and is not unique to Pine64 devices, but the ARM ecosystem as a whole.
There needs to be more funding and focus drawn towards standards compliant firmware. U-Boot is great, but it tends to lead to lots of unique distribution-specific problems as Drew points out here.
We have the SBBR and UEFI standards for ARM, but it needs to be more widely built out for consumer devices and not just servers.
Here is one key piece of work that NetBSD maintainers are working on: https://github.com/jaredmcneill/quartz64_uefi
This is one of the reasons why Google Android, and probably many others, are using Toybox for their userland. Because it's distributed under a BSD license.