The Mamdani plan is to put in stores where no stores exist. That's just a city ran store. Something that used to be pretty common in the US.
It wasn’t just Ev - I can confirm that many of us were typography nuts ;)
Marcin for example - did some really crazy stuff.
https://medium.design/crafting-link-underlines-on-medium-7c0...
“Can you read? And by that I don’t just mean interpreting Logotype…” “No one uses that any more,” said Quin. “You’re talking about the symbols on your underwear that tell you not to use bleach. That sort of thing.”
(The last level 9 robot that hasn't killed itself is now the Dean of NYU, and in the 25th century it hires the first man who has learned to read in 400 years – to translate the title cards in silent films. Hilarity ensues. Well, no, but there is kind of a happy ending.)
WARNING: Claude Code running in Bypass Permissions mode │ │ │ │ In Bypass Permissions mode, Claude Code will not ask for your approval before running potentially dangerous commands. │ │ This mode should only be used in a sandboxed container/VM that has restricted internet access and can easily be restored if damaged.
Perl is straight up better. You need to remember one word: pie - for it's command line options, and now you can do:
```
echo "John Doe" > name.txt
perl -p -i -e 's/(?<first>\w+)\s+(?<last>\w+)/"$+{last}, $+{first}"/e' name.txt
# name.txt after the command: `Doe, John`
```
First of all, it woks the same way across platforms.Second, you get all sorts of goodies: named capture groups, lookahead and lookbehind matching, unicode, you can write multiline regexes using extended syntax if you do something complicated.
And finally, if your shell script needs some logic: functions, ifs, or loops, Perl is straight up better than Bash. Some of you will say "I'll do it in Python", and I agree. But if your script is mostly calling other tools like git, find, make, etc, then Perl like Bash can just call them in backticks instead of wrapping things into arrays and strings. It just reads better.
BTW Ruby can do it, too, so it's another good option.
perl -pi -e '...' file.txtI don't have much call for most of the camera system, and my battery life on my Pro is just fine. I have plenty of chargers typically, and for emergencies or times I know I'm going to be out I could potentially get the battery pack.
I basically never use cases on my iPhone, and at most will maybe use an ultra-thin one or some sort of structure adhered to the plateau just to make it flat across so as to not rock on a table.
I tend to lean towards them being snake oil. A lot of process and ritual around using them, but for what?
I don't think the models themselves are a good fit for the way these frameworks are being used. It probably goes against their training.
Now we try to poison the context with lots of (for my actual task at hand) useless information so that the model can conform to my superficial song-and-dance process? This seems backwards.
I would argue that we need less context poisoning with useless information. Give the model the most precise information for the actual work to be done and iterate upon that. The song and dance process should happen outside of the context constrained agent.