https://thephd.dev/_vendor/future_cxx/technical%20specificat...

Discussion:

https://thephd.dev/_vendor/future_cxx/papers/C%20-%20Improve...

This is how it worked:

They had a documentation-writing branch. And you (developer) knew that if you don't write documentation, they will. And then if will cost you _more_ time and frustration to review and correct what they wrote than to write it yourself and give to them.

So you did write it (and they proofread it, corrected grammar etc.).

Such a shame susam.net still has not adopted IPv6 in 2025 :-Q

   $ cat /etc/apt/preferences.d/firefox-ppa-pin-400 
   Package: \*
   Pin: release o=LP-PPA-mozillateam
   Pin-Priority: 900

Kepping DNS registry, CA, and hosting in different jurisdictions could be a noticeable improvement...

I take an issue though with this assertion:

> The order [...] is quite different to english but very similar to functional programming.

The most widely accepted (imo) order of function composition is right to left:

  send(makeUrl("http://..."))

(*) In quintessentially functional Haskell, you can compose functions both ways, but right-to-left is more traditional:

  {-
   - Find numeric value of the first figure of the decimal representation
   - of a number:
   - 1. convert it to a string of decimal characters (show)
   - 2. take the first character of the string (head)
   - 3. convert the character to a string containing one charcter (:[])
   - 4. convert the string of one decimal character into an integer (read :: Int)
   -}
  
  main = do
    let
      firstfigure1 :: Int
      firstfigure1 = read . (:[]) . head . show $ 413
    print firstfigure1
  
    {-
     - Reverse the order of composition. Define "right-pointing" versions for
     - (.) and ($)
     -}
  
    let
      (.>) = flip (.)  -- it will become infixl 9 by default
      ($>) = flip ($)
      infixr 0 $>      -- We need value lower than the above. Use the same as $
  
      firstfigure2 :: Int
      firstfigure2 = 413 $> show .> head .> (:[]) .> read :: Int
    print firstfigure2

People are mostly motivated by gratification. You've written _functioning_ code - you can instantly see how it solves the problem at hand. You've written _beautiful_ code - you can stare in satisfaction at the negative total in `git diff --stat`.

You've written secure code - you reward comes in the form of nobody talking about your code for the next twenty years ;)

I've recently stumbled upon an article on the same topic, but containing competent and accurate information, I have a link because I recommended it to a friend: https://thevaluable.dev/guide-terminal-shell-console/

Ability to trade for fiat currency proved to be a mixed blessing at best, and a downfall at worst, of this approach. When a system is so lucrative as a vehicle for ponzi schemes, it inevitably gets hijacked, and becomes unable to serve its declared purpose.

But the results are not even promising, let alone useful, which is very sad.

(I tried "haskell gloss terminate animation normally". That was my real search a couple of days ago.)

- on each platform, include your pgp key id in the "bio"/"about" of your profile

- in your pgp key, include your profile URLs on each platform as an identity.

(In DNS, CERT RR exists for this purpose already.)

That is why my bet is on Musk. With lots of low orbit transmitters each covering a small area you have "space division" like in a cellular network. I.e. less endpoints competing for the bandwidth to the same transmitter.