internet_points

Also, 1.6k < 6k, and I highly doubt this model is anywhere near as good as it is on EU languages for most of them.

[0] I think most people just end up post-rationalizing whatever choice they have already invested in, I know I do :) With that in mind, maybe I as a mainly-Haskell dev should instead list some things I miss from OCaml: faster compile times, non-recursive `let` by default, polymorphic variants, labeled arguments

> Contrast what society says rehabilitation is versus what it actually feels like. How much of it depends on luck, personality, or privilege?

> people want linear redemption stories, but real self-improvement is messy, nonlinear, and impossible to A/B test.

> There's a certain freedom in owning your story publicly. People can't weaponize what you've already made peace with.

(though https://www.youtube.com/@emacsrocks has newer stuff by the same person, seems like game dev in clojure and emacs)

I do sometimes work on files that are 300k lines (don't ask), and while it's mostly fine, once in a while I'll try to use some less common operation that's not very optimized and have to abort it (e.g. don't try to magit-blame that file). But stuff like searching, scrolling, editing, syntax highlighting are all fast.

If I have to open files >100M I sometimes open them in `fundamental-mode`, which turns off syntax highlighting.

For truly large files (gigabytes), there is the `vlf` (Very Large File) package, which doesn't load it all into memory at once, but still lets you search, scroll and even M-x occur (sort of like grep, but more integrated and editable).

Note that this is on Emacs 31 (there have been some major perf improvements in the last three or so releases, and more is coming with the new garbage collector)

In earlier days there were issues with very long lines; these have partly been mitigated in later releases; on the one hand by faster internals, but also a new builtin package `so-long` that can notice very long lines, default 10k bytes, where Emacs probably should give up syntax highlighting etc. to remain snappy.

you would add a special "typeball" into your IBM Selectric Typewriter. Some pics:

https://www.duxburysystems.org/downloads/library/texas/apple...

https://pierce.smugmug.com/Misc/APL-Typeball/i-pjq6hWC

and I do like `#define _(e...) ({e;})` – that's one where I feel the short macro name is OK. But I'd like it better if that were just how C worked from the get-go.

Very nice discussion at the end of the article. There are good things to be learnt from this code and its discussions even if you disagree with some or even most of the style.

But getLine doesn't seem to be implemented, so there is output but not yet input :)

Isn't this a strawman? Even Haskell has unsafePerformIO and Debug.Trace etc. It just also provides enough ergonomics that you don't need them so often, and they "light up" when you see them, which is what we want: to know when we're mutating.

Anyone tried just taking a picture of a messy Ticket to Ride-board with ChatGPT?

> An inadvertent tenant configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting both Microsoft services and customer applications dependent on AFD for global content delivery. The change introduced an invalid or inconsistent configuration state that caused a significant number of AFD nodes to fail to load properly, leading to increased latencies, timeouts, and connection errors for downstream services.

> As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy. We immediately blocked all further configuration changes to prevent additional propagation of the faulty state and began deploying a ‘last known good’ configuration across the global fleet. Recovery required reloading configurations across a large number of nodes and rebalancing traffic gradually to avoid overload conditions as nodes returned to service. This deliberate, phased recovery was necessary to stabilize the system while restoring scale and ensuring no recurrence of the issue.

> The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations. Safeguards have since been reviewed and additional validation and rollback controls have been immediately implemented to prevent similar issues in the future.

So, so far they're saying it's a combination of bad config + their config-validator had a bug. Would love more details.

Also re: alphabet

    $ echo {a..z}
    a b c d e f g h i j k l m n o p q r s t u v w x y z

    # High level examples
    run_some_command | clip
    clip > file_from_my_clipboard.txt
    
    # Copy a file's contents
    clip < file.txt

    # indent for markdown:
    $ clip|sed 's/^/    /'|clip

    $ jo details[author]=Dickens details[age]=dead books="$(jo -a 'Oliver Twist' 'Great Expectations')"
    {"details":{"author":"Dickens","age":"dead"},"books":["Oliver Twist","Great Expectations"]}