This looks great. I'll have to play around with it.

For once, I'd love to have a nice UI around this so I don't need to search docs, google mongo syntax, check the schema, and edit the code in different spots

Wonder if it can it write data pipelines with unit/regression testing and model the data for decision making. Probably not but one day it might. Generally I see tools like these as potential supplements for what my team does, not replacements.

"not just for electric vehicles, but all cars" -- this is good news for the planet, regardless of what you think of $TESLA.

Perhaps, although my understanding is that the environmental cost of battery production and energy sources does make it less warm-and-fuzzy-feeling. Still a net good, but I've become less convinced over time that EVs will significantly impact climate change.

I honestly think in a lot of ways we’d be better off focusing on all the small engines (lawnmowers, chainsaws, etc). They are extremely dirty since they have no emissions controls what so ever. You can just see the particulates coming out.

(To add on a bit)

I dislike the current dumbing down to carbon and nothing else matters. Particulates are very impactful to health - but maybe that’s just my bias as an asthmatic.

That would be great, yeah. Or even just banning a lot of their use (e.g., leaf blowers).

But in general I think that, especially in the US, failure to invest heavily in public transportation options is the biggest problem.

12.5.1 is the latest, non-beta release. That's still Monterey. Ventura will be 13.x.

You can actually compile ReasonML to native code with dune.

What are some of the things that weird you out about OCaml's syntax?

  > You can actually compile ReasonML to native code with dune.

Yeah but the community doing native ReasonML is small and the maintenance has really petered off.

With OCaml 5 looming you're better off just biting the bullet and writing OCaml if you're going to do it IMO.

  > What are some of the things that weird you out about OCaml's syntax?

For whatever reason, I really dislike the named-argument syntax -- and some of the operators make it hard to read compared to named alternatives IMO.

Below examples showcases some of these:

    let variables = (json_variables :> (string * Graphql_parser.const_value) list)

    ~resolve:(fun info () ->
      Lwt_result.ok (Lwt_unix.sleep duration >|= fun () -> duration)
    )

OK but you can write code golf in any language, OCaml provides every opportunity to write readable code. The second snippet you provided is incomplete, if we were to write it in Python terms it would be something like:

    (resolve=lambda info: ...)

But let's say for the sake of argument that it's an argument to a function `f`:

    f ~resolve:(fun info () -> ...)

One of the simplest ways to improve readability is to use argument name punning:

    let resolve info () =
      let sleep =
        let open Lwt.Syntax in
        let+ () = Lwt_unix.sleep duration in
        duration
      in
      Lwt_result.ok sleep
    in
    f ~resolve

To be fair, it’s hardly code golf. It’s just that Lwt takes a monadic approach to concurrency and that’s always going to look a bit strange to someone unfamiliar with using monads and who doesn’t know that (>|=) is fmap.

I never understood why Lwt chose this aweful operator by the way. That’s a really unfortunate choice. My guess is that they really want people to use their ppx extension. I really hope that eio will solve the current concurrency libraries mess.

It’s the same for the first exemple: if you don’t know (:>) is upcasting, you are going to wonder what you are reading. I have to confess I had to look for it. Despite using Ocaml professionally for a bit a decade ago, I never had to upcast anything.

It’s hardly beautiful code but it’s fairly readable.

Note that this doesn't mean you can start eating chocolate with 30% simple sugars. Just cocoa with hot water, no sugar. Maybe a bit of milk, but not much since it has simple sugars as well.

Argo CD is one of those tools you use that you can't imagine living without.

A fun way I've been thinking about all this is what nanotech/nanobots are actually going to look like. Tiny little protein machines doing what they've been doing since the dawn of life. We now have a library of components, and as we start figuring out what they can do, and how to stack them, we can start building truly complex machinery for whatever crazy tasks we can imagine. The impact goes so far beyond drugs and treatments.

This no longer seems to be the case. I've always found it easy to tell it what format a cell is.

So I had a thermal problem with my 2018 15" i7 MBP that sounds very similar to what you describe. Temps hit 60° and then get heavily throttled. It started happening after a repair to the keyboard. After dealing with that for 6 months I brought it in to Apple and they fixed the issue by replacing the mainboard, I think. Since it's very rare I see throttling for my use cases (compiling, some gaming).

Last year all of my photos and presets had disappeared after updating the Lightroom app. That was 2+ years of edits that are just gone, lost, unrecoverable.

I do photography as a hobby so I never saw a need for backing up photos and I never paid for the subscription (which would include cloud storage) because I didn’t use any of the tools that came along with the subscription.