[note: I do cherish unix, kernels and userspaces; AND lisp. Oh and C...]
364 karma · joined May 22, 2019
Also: embedded linux / C++ development
Contact: hn -at- ayaken.net
Previously: type safety x unit safety
Previously: semantic mediation in production networks
Previously: embedded linux development for industrial automation
History: - Tcl -> Scheme -> C -> C++ -> C -> Common Lisp -> C -> Clojure -> Tcl -> C/++ & wanting zig (unimportant deadends like e.g. ruby, icon, python, perl elided)
- DOS 4.11 -> Win 3.11 -> Win95 -> Linux -> NetBSD -> Linux -> FreeBSD -> Linux (those damn hardware drivers)
[note: I do cherish unix, kernels and userspaces; AND lisp. Oh and C...]
I believe andrew and loris have been with zig for long enough to have their own bias and no longer be aware of it, thus I believe it's the newcomers' job to hold up the simplicity design premise now...
Does asdf come with a plugin for asdf & quicklisp? would've preferred for the new guy on the block pay respect to the old guy on the block and used a different name..
In case you're worried about sound quality - don't be; a) most consumers won't notice anyways, b) check out dave rat on youtube, he was dissecting Midas vs. Behringer X32 and you'll likely be surprised by the results.
Also love that the XAir Edit application is available under a lot of platforms, including x86 and ARM32 linux. The only thorn on the software side is the lack of an iPhone application (but there are iPad and Android ones). If you know about a OSC iPhone management SW for the iPhone, I'm all ears :)
I kept my subscription for ardour, though, because I think the project is awesome.
Sadly now I've grown used to another set of quirks (reaper's), so switching back seems quite unlikely. Still gonna keep that subscription running...
Also s/sensisble/sensible/?
Speaking of the "desire[s] for [of] C++", it's a matter of design-by-committee and we all know what sort of results this brings. Consultants love each new standard. I am happy about this, that or that other library improvement but I'd wish they'd stop fucking about with the language. Come on guys, you aren't ever going to catch up to ML or lisp or ever return to C's "dirty elegance". Just stop breaking the mental model users have of C++ with every update please?
Sorry that comment went nowhere, I'm massively frustrated with C++, its direction, and I can't wait to leave it behind for good.
But "could this ever happen?" the committee agrees on the wildest stuff, so, sure, why not.
I program in more languages that I care to enumerate and some are just so in-grained in me that I don't make mistakes with 'close' naming. I'd be more efficient in a single language if I only programmed in that, true, but I think I'm more efficient overall because I bring a wide variety of solution sketches with me that can be applied depending on scope and primary, secondary, tertiary (and more) concerns. Once you have the first half-dozen to dozen languages under your belt, ideally with different paradigma (OO, FP, logic, old-school structural/procedural, bare-metal, VM/script) the next dozen dozen will be a piece of cake and your biggest problem is the warm-up of the language keyword and stdlib name cache. Hence b), above.
As bandcamp user, the "others who bought this also checked out that" might be helpful, but I seldomly follow them.
As a music consumer (niche metal) I follow the set of bands and naturally uncover close relatives by supporting acts on live shows etc.
Given my time is very limited, I don't feel a big need to discover even more music. Most of my time already is taken by me practicing, recording, mixing and keeping up with publishing next to $DAYJOB and $FAMILY.
As someone who uploads music (videos) of my own creation, youtube (still) works fine to connect with an audience that I would have no chance of reaching otherwise.
I'm far from being flagged to monetize, so I don't have any incentive to put out something that I do for the money and not because I want to put it up.
As a niche musician (didgeridoo), I'm glad that I have access to a global community and a non-zero chance of someone searching for e.g. 'didgeridoo music' finding me.
Shorts may annoy people but I see it as an interesting challenge to make great 60s didgeridoo solos. Maybe my view will change if I'm ever sniffing the chance of being monetarily successful on this platform but until then, I'm doing whatever the hell I want and it's great.
And this is the political dimension of systemd. One they keep using to shape the ecosystem to their preference.
> If I'm to design some piece of software that requires something,
See that's the point. It doesn't _require_ a merged /usr to work. The benefit of the merged /usr here is that this guarantees to potentially overwrite/extend "all" binaries, not "only" those in a split-/usr. The latter doesn't mean it doesn't work. It just means that they only overwrite one place, not all potential places something exists.
It's not an _assumed_ limitation. It's an _enforced_ limitation based on a limited world-view that also uses the gravity of the project to enforce the world-view on any user.
I'm not arguing pro or against split /usr. Reality though is that for various reasons there are legitimate use-cases for a non-unified directory tree, e.g. embedded ramdisks that contain only the barest of /bin in a crunchgen'd binary that don't want to duplicate stuff that's later used in /usr/bin. Linux is not only desktop and server.
systemd is being adopted because it solves problems well the distributors have, but THEN the distributor ALSO has to bend their distribution to the single enforced world-view the systemd folks have if they want it to integrate. They, the distributors, software integrators per se, are just forced to hack out limitations that are imposed by systemd folks for no benefit of either; systemd dev or user. No unified-/usr-user will benefit from this enforced restriction. A split-/usr-user will have to patch systemd and maintain their tree to use this feature if they have a good use-case for it because .. "systemd says so" (if you prefer that over the "B"DFL lennart).
Lastly, you are correct in that systemd is a pool of like-minded developers - not only lennart; and this is where I add: - who like to shape the reality out there instead of allowing distributors and users to easily take on their own responsibility easily. Sure, I can fork systemd (it's free software after all), but it's unnecessarily "opinionated" for its broad area of application. And that's where the "politic" dimension of systemd development comes into play ...
> Oh, and in case you wonder, all of this only works with distributions that have completed the /usr/ merge. On legacy distributions that didn't do that and still place parts of /usr/ all over the hierarchy the above won't work, since merging /usr/ trees via overlayfs is pretty pointess if the OS is not hermetic in /usr/.)
IOW, if I build a system with yocto for an embedded system, which is also a very useful candidate for a read-only system image installation, I cannot use this feature for this use-case because ... yeah because what. Because lennart says so. This got old so fast.
Given the music I/we make fits the trippy trance pattern quite well, this ought to work quite well. If I capture someone else also fiddling with the patterns, all the better. Perfect now it would be to integrate a lua bridge so I can remote control the pattern from a side-chain on the master bus in reaper ... if any of you has something like that figured out already, please point it out to me, thanks in advance!
(if any of y'all are in for some home-grown manual psychedelic trance, feel free to check out our music at https://www.youtube.com/channel/UCGDW9hicaeV9Z15gFpXcANw )
Both are very rare nowadays, and have been for quite a while, where "responsive" means "one of X configurations, and _we_ choose which" and scaling text often has the effect of breaking the visual appearance, and thus, in a visual-first mindset, the UX, and more often than not also the functionality in general.