h4l

SBF lost customer funds by spending them as if they were his own. CZ isn't accused of spending customer funds, he's accused of letting people trade too freely.

A few releases back they replaced the python parser with a more capable PEG parser. At the time nothing really changed, but it was done to enable this kind of improvement and make it practical to evolve the syntax over time.

This change isn't so much done for the sake of being able to next quotes in f-strings, it's done because there was a dedicated extra parser for the python syntax inside f-strings, but with the new parser this can be parsed without this special case extra parser.

It's all to manage technical debt.

Have you come across iiif? https://iiif.io/ It's not exactly that, but it's the sort of thing that its standards and viewing apps aim to enable.

Ah, thanks for correcting that.

The EU are requiring phones to have user-replaceable batteries (no tools) from 2027. Hopefully batteries will stop being a problem soon. https://mashable.com/article/replaceable-batteries-smartphon...

My intuition is that it's not possible to have an open platform like substack where the majority are making enough to live off. Imagine that was currently the case. People would see the platform as easy money and jump in. The quality of the median writer would drop, as would the median income, until the perception that it was easy money reduced enough to stop people joining.

I wonder if this has anything do with how bad his health was? https://en.wikipedia.org/wiki/Health_of_Charles_Darwin

Interesting, I'd not known of this RFC before.

Another example of a content-addressed data store could be OCI registries (more commonly known as container image registries). Using them to store arbitrary artefacts is quite well supported now: https://oras.land/

I love it, thanks!

I think it's relative to our own experiences. If you drive on a perfect road, even a small bump is noticeable. But I don't think that means people's perception of problems is not legitimate. There's always someone worse off, especially if you compare now to historical times.

If there's a sure-fire way to create a mental health problem, it's to tell yourself you don't deserve to have a problem because other people have worse problems.

Maybe take a break if you feel like making toxic comments like this.

I've not used it myself, but https://htmx.org/ combined with a traditional web framework like Django or Rails seems like it should greatly reduce the need to triplicate logic. At least for apps where the UI needs to be good enough rather than as good as possible.

95, using a phone and the old trick of squinting a bit to get a sense of the overall layout.

Maybe it's obvious, but I find resizing the window much smaller helps a lot with the close eye contact thing. Slack's huddles are good for this — their UI seems to be designed to be a small thing in the corner while you're doing other stuff.

I also used to find it disconcerting watching some YouTubers film themselves with their face taking up the entire screen. I must have got used to that though as I've not noticed it in a while.

It is per target, that's how it works when I've used it. For example:

  # Makefile
  SHELL := bash
  .ONESHELL:
  .RECIPEPREFIX = >
  
  thing1:
  > FOO=bar
  > echo "$${FOO:?}"
  .PHONY: thing1
  
  thing2:
  > echo "$${FOO:?}"
  .PHONY: thing2

Results in:

  $ make thing1 thing2
  FOO=bar
  echo "${FOO:?}"
  bar
  echo "${FOO:?}"
  bash: line 1: FOO: parameter null or not set

Note how the bash error for unset FOO is line 1 for the second target.

Edit: Maybe I misinterpreted, do you mean you'd want to choose whether a given target is ONESHELL or not?

I've found these guidelines for Makefiles make for a pretty good experience using make: https://tech.davis-hansson.com/p/make/

The advice on output sentinel files for rules creating multiple files helps keep rebuilding dependencies reliable. Avoiding most of the cryptic make variables also helps Makefiles to remain easily understandable when you're not frequently working on them. And using .ONESHELL to allow multi-line statements (e.g. loops, conditional etc) is great. No need to contort things into one line. or escape line breaks.

Seems like you could even use a more serious programming language instead of sh/bash by setting SHELL to Python or similar. That may be a road to madness though...