eYrKEC2

> Today, someone can post a Telegram group message and make thousands of people rally to a town square. I see the dangers, and I see why governments think they are doing this to protect the people.

Yes. Previously this capability was reserved for the CIA.

You know what I think is better than a push of the CPU stack pointer and a jump to a library?

A network call. Because nothing could be better for your code than putting the INTERNET into the middle of your application.

--

The "micro" of microservices has always been ridiculous.

If it can run on one machine then do it. Otherwise you have to deal with networking. Only do networking when you have to. Not as a hobby, unless your program really is a hobby.

Has anyone used ArgoCD as a CI pipeline?

You just described my samsung fridge.

Absolutely agree, but most know nothing other than the almighty BTC.

I want 3 things from crypto:

    * throughput that _could_ scale to something like visa. 50k/second christmas.

    * privacy by default for everyone - "public ledger" for a currency replacement is INSANE

    * reasonable transaction completion time ( < 1 minute)

Fiat does better than 7 transactions per second.

You're on that site right now!

Much as Lisp'ers say,

    Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

If one says, "we don't use an ORM", you will incrementally create helper functions for pulling the data into your language to tweak the data or to build optional filters and thus will have an ad hoc, informally-specified, bug-ridden, slow implementation of half of an ORM.

There is a time and place for direct SQL code and there is a time and place for an ORM. Normally I use an ORM that has a great escape hatch for raw SQL as needed.

Why do you need a common websocket bus when h2 interleaves all the HTTP requests over the same SSL tunnel?

For C, once I learned that types are best read right-to-left, they became much more scrutable.

        int[] foo
        |   |  |
        |   |  foo 
        |   is an array  
        of ints

I still prefer Rust types though..

I use a simple bash script:

    #!/bin/bash -x

    TOK="my-jwt-tok"

    case "$1" in
        get-foo)
            curl -H "header: bearer $TOK" "http://www.example.com/foo" | jq .
            ;;

        post-bar)
            curl \
              -H "header: bearer $TOK" "http://www.example.com/bar" \
              -H "content-type: application/json" \
              --data-raw '{"baz":"bap"}'

            ;;  
        *)
            ;;  

    esac

used like:

    ./example.bash get-foo

I know it doesn't have the functionality of postman, but this is how I build up interactions with a new API.

First they ignore you. Then they laugh at you. Then they attack you. Then you win.

J/k, but I still love Linux and as a family it admin, people in my sphere get pushed there.

My son almost died in the first 24 hours of life. I said, "There's something wrong. There's something wrong." multiple times and the nurses finally told me, "YOU NEED TO CHILL OUT." I did chill out....

Next morning the pediatrician did his rounds, checked on my son, and immediately started speaking Latin, to go over our heads while rushing around and getting equipment to clear his lungs of amniotic fluid.

Reminds me of what my first engineering boss told me -- "When the people on the line say there is a problem. There is a problem."

I'm not a doctor, but I am an engineer --- so I am _SUPER_ used to being wrong -- my systems don't spontaneously heal themselves.

I'm not sure Willy Jeeps were "allowed" in Germany in 1945, but it happened.

Some dyes _have_ been found to be carcinogenic and outlawed in the USA, even prior to this administration.

From there, you then apply the "precautionary principle" - https://en.wikipedia.org/wiki/Precautionary_principle .

Who, whom?

In law, isn't the process the punishment frequently? What if they're just expecting Disney to drain their coffers with frivolous legal work? Isn't that a reasonable response then?

Or if you use its predecessor, bitkeeper.

Have you considered joining the cult known as crossfit? They have fantastic community. Church as well.

oops. You're right.

Running tests and then fusing off broken cores or shared caches helps to recover lots of yield for bigger chips. Certain parts of the silicon is not redundant, but Intel's designs have redundancy for core pieces and chunks that are very large and hence probabilistically more prone to a manufacturing error.

Intel has always pursued agglomeration into the main CPU. They sucked up the math co-processor. They sucked up the frontside bus logic. They sucked up the DDR controllers more and more. They have sucked in integrated graphics.

Everything on-die, and with chiplets in-package, is the Intel way.

Default, average integrated graphics will continue to "statisfice" for a greater and greater portion of the market with integrated graphics continuing to grow in power.

React, _combined with its ecosystem_, feels like a local maxima. System D may be better than C++, but it wasn't better _enough_. We needed massive improvements offered by Rust to move the C++ community (not everyone, I know).

Then I guess you become a monarchist, like Curtis Yarvin.

But of all things Charlie Kirk was not, first among them: He was not "a threat to democracy".

A guy who gathers large groups of people to talk with them and persuade them on political topics is the _essence_ of democracy.

Someone who calls for violence or does violence against people wishing to have open debate is the essence of fascism.

They may not be disabling them maliciously -- they may be "binning" them -- running tests on the parts and then fusing off/disabling broken pieces of the silicon in order to avoid throwing away a chip that mostly works.

I've only ever used Tan's React-Query and I absolutely love it inside of a React codebase.

https://tanstack.com/query/v5/docs/framework/react/overview

Yeah. Risky compared to Intel. Intel manufactures chips _right now_. They have lost their process edge, but if I have to put chips into a drone tomorrow, I'm betting on Intel rather than any bag of scrappy kids. The risk that they _can't_ produce chips is the same risk as that of Hillsboro Oregon getting carpet bombed -- which is of course not 0%.

Trading view charting_library is a nightmare. D3 is a pain to learn, but unmatched.