Earlier quoted context omitted.
portmaster is a freebsd "package manager" for managing installation and uninstallation of ports. Sort of analogous to the "formula" function of brew where it's compiled in-situ... with your local march! https://man.freebsd.org/cgi/man.cgi?portmaster https://github.com/freebsd/portmaster
Oh, wow. Glad I asked. I thought you mean port but while they are related it is something I’ve never heard of. Brew has transitioned into primarily bottled (pre-compiled binary). Compiling with the local march sounds great and it is quite difficult to find one consistently do that. On top of that, I’m trying to look for one that can be installed on arbitrary prefix too and recently I’ve been eyeing on pkgsrc, gentoo…
Apple. Apple Please
61–64 of 64 posts
Re: Apple. Apple Please
#62Earlier quoted context omitted.
I could make a car with wooden wheels too but since we have synthetic rubber it makes sense to use the best tool for the job. Basic functionality that users expect from social media needs JavaScript. Endless scrolling is a simple example. Adding a comment reply or liking a post without reloading the page is another one.
A car with wooden wheels - as in the type used by Babylonians, not even the iron-rimmed wheels used by the Romans - would be suboptimal and not at all comparable to one running on rubber tyres. A site which does not depend on Javascript is not suboptimal, it is a local optimum which works best for many applications. Endless scrolling is a good example of how adding Javascript to a page can push it away from the local…
HN is a wonderful place but it’s a niche industry-only forum. The barebones nature of it works fine for the people here but products like Mastodon are attempting to be a much more broadly adopted general purpose product.
Re: Apple. Apple Please
#63Re: Apple. Apple Please
#64Earlier quoted context omitted.
How would a shell interrogate the valid parameters from a complied binary? I know that approaches like Powershell which has understanding of all the Microsoft commands and the ability to define a structure that defines the options ... but how would bash figure out the structure of the arguments for dd or tar or that a.out that I just compiled?
By accompanying the binary with a formal description of the possible arguments, either as a separate file or embedded in the executable. But the latter is not really sustainable the more metadata you add, so more likely a separate file. Applications already come with lots of metadata: man pages, icon, readable name, ... adding formal shell-completion information is just another one. Besides that, the built-in command…