It is a thing of beauty. Crisis averted, until the next time we hit the ceiling.
I just paid my VPS bills with just 4 HKD of miner's fee.
Still, I wanted to do it using batch payment (in Electrum Desktop). That wasn't trivial at all. There's a huge opportunity for UX improvements here.
I would like to be able to just click the bitcoin: link, end up in the wallet, click "queue for payment", click the next link, queue that, and then finally choose to execute pending.
Plans are being made for Chess to come back to both West End and Broadway.
That's a great idea! All of us who listened to the LP when we were 10 are now old enough to fork out a lot of dough to see an ambitious version of childhood nostalgia on stage. :-)
- Why do you care? I don't care about you. That's what we envoys do. We make neat little rows of friends wherever we go, and then line up behind the cannon fodder and watch you die. - We're friends?
Awww, Ava, you're the sweetest character ever conceived.
Are you super smart, love lambdas and probably have a bunch of academic merits under your belt and want to be in a room* with people who would rival that? Like *the* Philip Wadler?
> IOHK is one of the leading cryptocurrency firms. Much of its software is implemented in Haskell. All work is open source and publication is encouraged.
IOHK works on Cardano/ADA and its contract language Plutus.
> When you curry curry your curried curry can have curried any sort of arguments but it can't curry keyword arguments, only positionals, so you need to curry curry in order to curry a keyword that you want to curry onto a non-curry function to produce a curried function.
Apparently you can supply keyword args to a curried function only if you make use of the special case of currying curry, which allows curry to receive the keywords, and apply them to the function.
I don't have these problems myself, but for people who do audio production:
PulseAudio doesn't support low-latency audio like JACK does, and doesn't support the advanced kind of audio routing between applications that JACK can do.
Apparently you are supposed to be able to run mainly JACK, and for the applications that require PA, they can do that on top of JACK, but I've never had the need to play with this.
People don't hate PA because of SD, they hate it on its own merits. If anything, the history of PA made people worried about SD:
1. Solved a problem nobody knew they had. ALSA and OSS already existed for local, esd already existed for networked audio. 2. Claimed compatibility with pre-existing things, broke a whole bunch of stuff. This was other people's fault for not using PA. 3. Difficult to remove, because now everything depends on it.