The splash screen is a condition for using JUCE for free under the AGPLv3 license, particularly when distributing open-source projects or plugins without purchasing a commercial license.
I don't think anyone is suggesting that the generated Rust is nicer than the original C.
It is auto-generated with the purpose of maintaining the exact same semantics as the C code, with no regard to safety, best practices, etc.—of course it is messier than actual, handwritten Rust.
As c2rust says in its documentation [1], it's meant to be the first step in an otherwise manual and incremental port of a codebase from C to Rust, and the author recognizes this in their closing remarks:
> The next goal is to convert the codebase to safe Rust.
Stubborn complaint (and maybe a hot take): I dislike CLIs that try to be overly pretty. I don't receive any tangible benefit as the user from the "fancy" (their words) help output. I'd much rather simple plain text output that looks like all the other tools I already use.
Alignment (and maybe bold text for some things) is all you need in >95% of cases, IMHO.
One of the downsides of a lot of these tools is that's exactly what they don't do well: many things don't align or wrap nicely.
For example, here's a comparison of this fang library vs one where I just raw-dogged the usage text: https://imgur.com/a/QWh9TLD – the nice alignment does a lot more than colours. Especially for larger programs with a bunch of flags it can be such a pain. For example from an otherwise quite nice tool: https://imgur.com/a/RELL9Gk – you just completely lose any "overview".
I did spend some time on some better tooling to improve all of this, because manually writing these isn't super-fun either, but not so straight-forward to do well (or at least: not in a way that I like).
> One of the downsides of a lot of these tools is that's exactly what they don't do well: many things don't align or wrap nicely.
Bling is easy. Unsexy usability details are hard.
Z$ time ./example/run
You ran the root command. Now try --help.
./example/run 0.13s user 0.27s system 177% cpu 0.228 total
Why would an example program take 228ms?
Z$ ./example/run --name='abc def'
Unknown command "def" for "example".
Try --help for usage.
Huh? 'abc def' is one shell word. --name=abc works fine.
Z$ ./example/run --name ''
ERROR
Flag needs an argument: --name.
Try --help for usage.
But I did give it an argument: the empty string.
And why is the output indented two columns from the left margin anyway?
Z$ ./example/run ''
You ran the root command. Now try --help.
Z$ ./example/run 'x'
ERROR
Unknown command "x" for "example".
Try --help for usage.
Should have produced an error using '' for the subcommand name.
Z$ ./example/run sub "multi-word quoted string" --flag "another quoted string"
Ran the sub command!
Z$ ./example/run --help
A little example program!
It doesn’t really do anything, but that’s the point.™
USAGE
example [command] [args] [--flags]
EXAMPLES
# Run it:
example
# Run it with some arguments:
example --name=Carlos -a -s Becker -a
# Run a subcommand with an argument:
example sub --async --foo=xyz --async arguments
# Run with a quoted string:
example sub "quoted string"
# Mix and match:
example sub "multi-word quoted string" --flag "another quoted string"
COMMANDS
help [command] Help about any command
sub [command] [args] [--flags] An example subcommand
throw Throws an error
FLAGS
-a --async Run async
-h --help Help for example
--name Your name (jane)
-s --surname Your surname (doe)
-v --version Version for example
Z$ ./example/run sub "multi-word quoted string" --flag "another quoted string"
zsh: command not found: example sub multi-word quoted string --flag another quoted string
Huh? Why did the command work when I typed it myself but not when I pasted from the help output?
Oh. Because the help output is using nbsp, not regular spaces.
Anyway, command line interfaces have a surprising number of hairy corner cases. I'd rather have boring monochrome that gets them right than an all-colorful theme auto-shell-completion-generating system that doesn't.
I could explain the single-quote argument quoting error if you were running it on Windows. The Go runtime library does not provide single-quoting on Windows. At all. (This is historically the behaviour of C runtime libraries on Windows, too.) It should be using a proper argument vector and not doing its own command-line parsing on other platforms, though.
As a counter argument, not putting color in help usage text leaves a large amount on the table for readability. The reasonable compromise for those that disagree with this is to set the NO_COLOR environment variable. This should be respected by most things which do use color (and if it's not, that's a bug).
"bling" is the word you're looking for. It's just a fashion. Fashion is famously cyclic, and we're just in a high-ornamentation part of the cycle. Eventually, restraint will become fashionable again.
A lot of the fancy CLIs I use have a `--json` option that gives the user the chance to pipe output to eg jq and process it there. I find that a good alternative to running stuff through cut, sed or awk before processing.
My best guess, and I've thought about this a lot, is that chronic illness drives billions of dollars of direct economic activity.
Of course, illness has an even larger cost to society and to overall happiness, but that's much less measurable, and therefore has less effect on public policy.
At least with cigarettes there was a public nuisance argument because of the smell and also the secondhand effect. I dont find general public health a compelling argument for restricting sugar.
That's semi-reasonable in America, but less so in any country with single-payer health care. Like smoking, there are serious effects later in life that cost money to treat; this makes for a compelling case for a sin tax IMO, like we have for tobacco and liquor here in Canada.
It’s the root of the toxic nature of American culture. We worship the “freedom” to have bad outcomes shoved in our faces, but castigate and actively harm anyone who falls afoul as a result.
From my limited travels in Europe, I see countries with problems, but with people who appear to be happier and healthier.
Is it? You'll either have higher health insurance costs to cover the people destroying their bodies, or you'll have to prove to your insurance provider that you live a healthy lifestyle somehow. Both seem like a bad thing.
I agree with you, and I think the sin tax up here in the Great White North is great. There are more externalities than just the healthcare system having more, expensive, patients. To lead with a strong argument that's less likely to be nit-picked apart though, I avoided getting into that discussion for the USA
So if we vote for a single payer healthcare system, we get a back door for government tyranny over every little aspect of our lives that they decide is bad for us, including as the science shifts? Don’t eat eggs or you lose your coverage, no wait, eat 3 eggs a week or you lose your coverage, no wait.. Sounds like a bad deal, and most Americans will take freedom over free health care if that’s the cost.
Yes, having billions poured into creating foods that are as addictive as possible and manipulation campaigns to get people hooked is a much better system.
This system also affects your freedoms in many ways. If a large portion of the population gets fat, you have a smaller pool of people that are able to do physical work, making it more expensive for you. You have a lot more demand for healthcare, making it more expensive for you. You have people demanding car-centric infrastructure because they can't walk, and that will affect you. Etc.
In a single payer system, the government is mandated to provide you with health care, since you are paying for it with your taxes (or would be if your income was high enough), no exceptions.
Typical tools of such governments include:
- taxes on products which are deemed of danger to public health, for example taxes on cigarettes in the EU. The government is then mandated to invest these taxes into the health care system
- public health campaigns (ads etc.)
- age restrictions, as they exist on alcohol in the US.
Legislation shifts to represent newest advances in science, yes. That's not per se a bad thing.
Not every country with a single-payer system is an authoritarian communist hellscape, you know.
That sound very reasonable and I'm inclined to agree, but empirically US health care system is the worst I know of. You're only free if you're rich and if you're rich you're not free, cause you've got so much to lose.
And from a more theoretical viewpoint the societal cost of unhealthy people is still there at the least in loss of productivity, so the argument for prohibition is still there and the US is only really liberal in things that are backed by wealthy corporations/people that have subverted the government.
This not only doesn’t happen, but those "tyrannical" systems also usually have lower minimum age requirements for alcohol consumption than the US, and healthcare is cheaper while people are healthier on average.
It is sad how so many people in the US were persuaded to be so afraid of supposed "communism" that they are actively voting against their interests.
No. This is a myth, and while it does force you to enter your password instead of using biometrics on the next unlock, it is not the same as returning to BFU.
They have a long history of encrypting firmware. iBoot just stopped being decrypted recently with the launch of PCC, and prior to iOS 10 the kernel was encrypted too.
The operating theory is that higher management at Apple sees this as a layer of protection. However, word on the street is that members of actual security teams at Apple want it to be unencrypted for the sake of research/openness.
As a user of Monodraw in an airgapped environment: thank you!