Yes that's the idea and I think it is stupid. We should be spreading DNA far and wide instead of sending humans. As much as I am curious about evolution, I am more interested in a deep future full of life.
Hello fellow dc user! I use it as my default calculator and even in shell scripts I'm all "sum=$(echo $a $b + p | dc)" (though it is usually a much more complex expression of course)
What are the chances all four of us would find the same thread? It’s so fast, so reliable, so omnipresent. Between that and being able to turn multiplication into addition by working in powers of two, I get answers while my colleagues are still waiting for excel to start.
Ahaha :) Nice on. Its kinda similar to my net docs system written in ruby. I just type blgrep ip=192.168.0.10,15 hosts.txt and get answer, before people start any IPAM :) CLI power... Unfortunately, it does not get right respect these days.
I'm not sure why I started using dc instead of bc, but I think it might have been because at one point in time bc output a bunch of extra noise that made it annoying to use in shell scripts, so I just learned dc is the standard way to calculate stuff in UNIX and kept on using it that way. I noticed some new Linuxes don't have it installed and I'm always stuck for how to calculate things in shell scripts. I guess people just use Bash nowadays. In any case, thanks to the Gavin Howard dc I still use it today, even on the Windows command line. dc is great!
The € penny still exists but here in NL every cash transaction is rounded to the nearest €0.05. I make less than one cash transaction a month, so this whole conversation seems a bit silly.
I'm wondering if the use of wcwdith() will improve my luck with using UTF-8 characters in my caption and hardstatus lines. I'd like to be using nerdfonts in there but it just makes a mess.
The entire wchar_t API is hopelessly broken. It isn't guaranteed to represent Unicode nor is it guaranteed to be UTF-32. Unicode has a large number of codepoints designated as ambiguous width. This is largely due to existing narrow text presentation symbols being gifted a wide emoji representation. Which width is the default is heavily dependent on the font(s) in use and your rendering engine. Gnome VTE has a configuration option to set the default width for ambiguous codepoints.
Any program has to expect wide, narrow, or an inconsistent mixture of both if font substitutions are invoked. With no actual API to reliably discover a codepoint display width, your best option is to print some candidates and check the cursor position as a heuristic.
FWIW, wchar_t is guaranteed to be Unicode if __STDC_ISO_10646__ is defined, which is the case on Linux/glibc. It's too bad that other platforms are lagging behind on this - there's really no good reason to not guarantee this in 2024. Windows at least has the excuse of having wchar_t be 16-bit which they can't change for legacy compat reasons, but that doesn't explain why e.g. FreeBSD isn't there yet.
I used to do training with this. Every student got a private username/password to connect to my laptop where their login shell connected to a specific window (to which only that user had access) in a shared screen session. They each had their own little environment to hack in. Then when we were doing exercises and people got stuck, I would put their screen up on the projector so we could discuss their code together.
I've only noticed Shopify behind one of the online vendors I use and it has the worst recurring order management UX I have ever seen. Is it that this vendor has set it up badly or is Shopify yet another case of worst in class market dominance?
Recurring order functionality is typically delegated to a third party app in Shopify land; the two biggest incumbents in this space have pretty ordinary UX so it’s likely you were looking at one of those.
More recent entrants in the market do a much better job on this front.
Worse. Its like someone shouting "Fire! We are dead in 5 seconds!". People who are still alive after 5 seconds will correctly figure that this is a liar and possibly also assume that there is no fire at all.
Except, they don't say we are dead in 5 seconds. They say stuff like "The trends reveal new all-time climate-related records and deeply concerning patterns of climate-related disasters." The records being set is pretty objectively true. The "deeply concerning" part involves a little perspective taking, but more/stronger storms, heat waves, etc with impacts on insurance, the power grid and public health are reasonable causes for concern.
They don't say we're all gonna die. They don't say anything about such a short time period as 5 seconds. You're accusing them of being alarmist, but the way you're describing their claims is itself a false and hyperbolic caricature.
It could be more appropiate "Fire! Some may die in 5 seconds". Maybe no one died yet in the 5 seconds mark, or maybe someone die but we attribute that to the heat more than the fire, or just don't count them as there was no one important for us.
But that is no reason to calmly stay there doing nothing while the flames keep rising up.
You know whats the right thing to do? Stay with the facts and avoid hyperbole. "There is a fire in Hall B, I'm leaving the building" and people will follow you with no questions asked.
Its a matter of how you communicate.
I'm tempted to rewrite the abstract in a better wording so people can compare realize what an difference that makes.
> ... "so people can compare realize what an difference that makes."
It makes zero difference, because the people who could change the course of all this aren't listening at all to those who speak up, regardless of what is said or how it's said. They're firmly convinced that money is literally more important than any life (even their own), and no words can or will change their minds. Literal decades of inaction despite growing numbers of actual climate scientists speaking up about the issue has proven this.
reply