Disappointing to see it with tires this big, translating into lower efficiency and less usable interior space

> I’m going to skip the drama and just use htmx for the client-side. Render Django templates server-side, include a single JS script, thrown in some HTML attributes, distinguish between full page requests vs. requests for a partial with updated data, and call it a day.

More of a side comment, but I'm skeptical of the way HTMX encourages partial renders like this. It feels like a premature optimization that adds more complexity on the back end. `hx-select` takes care of it, but to me it feels like it should be the default (it's what Unpoly does).

There is a package, https://github.com/carltongibson/django-template-partials, that is basically like server-side hx-select, when there is some performance concern. Overall, I agree with you though, hx-select is going to be fine most the time.

Thanks for sharing that! I also just finished watching Carlton’s talk from DjangoCon EU (linked in the repo) and it is gold: https://youtu.be/_3oGI4RC52s

There is a header that htmx injects to indicate you want a partial render, and it’s really not that hard to add an if on the server-side to check for it. A larger codebase would probably break templates up anyway for maintainability, so it’s just a tiny amount of extra work if you want to reduce the amount of HTML being sent over the wire and swapped in.

> Do you think on average Latin American Spanish is spoken at the same speed as Spain?

Faster in the Caribbean, slower in the Andes

As I understand it, the server is being switched over to Erlang https://github.com/sonic-pi-net/sonic-pi/tree/dev/app/server...

Unpoly (https://unpoly.com/) should be mentioned as well. Much like htmx but with more features.

Are you aware of any ecommerce sites currently using unpoly?

I wrote my own unpoly (so to speak) to transition from React, for a pretty big ecommerce marketplace: https://solovyov.net/blog/2020/a-tale-of-webpage-speed-or-th...

I wish OCaml had something like F#'s lightweight syntax: https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...

It's been tried https://people.csail.mit.edu/mikelin/ocaml+twt/

Note that The Whitespace Thing actually preceded F#. (Mike and I were in the same fraternity, I remember talking to him about TWT, and we haven't talked much since our college days, which pre-date F#.)

IIRC, Mike was also doing a bunch of stuff with a Jabber client in OCaml around that time.

I'd never seen the verbose syntax for f#, I thought you had to write it the whitespace dependent way. Huh.

Lightweight syntax is a pain to use for blind people. Glad OCaml hasn't fallen for that fad.

Do blind people use special code editors? If so, they should probably have a whitespace sensitive mode to make this easier.

ReasonML or ReScript not your cup of tea? They are different syntactical front-ends for OCaml.

OCaml syntax is whitespace-insensitive. You don't need to worry about indentation, copy-pasting code snippets, etc. I think that makes for a better experience especially for beginners when the parser is more forgiving.

This so-called lightweight syntax gives me anxiety just scrolling through these examples.

Thank you. Too many commenters here, years removed from being a beginner, aren't getting it.

Vos, not vosotros

For those interested, I believe you're referring to Fable.Remoting https://zaid-ajaj.github.io/Fable.Remoting/src/basics.html

What? NYT regularly publishes information unfavorable to the US government. WikiLeaks on the other hand participates directly in advancing Russian state aims.

"The New York Times had held the story at the request of the government."

https://www.npr.org/templates/transcript/transcript.php?stor...

One of the most incredible things about that is that the New York Times only published the story when the journalist who had uncovered it threatened to publish it outside the paper. They were willing to sit on one of the biggest stories in their history, at the request of the government, until they were faced with the prospect of getting scooped. Wikileaks would have published right away, informing the US electorate (I mean, "interfering in the 2004 election by providing truthful information to the public").