Select all always appears if you have no text selected and never appears if you have some text selected. Insane UI decision by apple but that's how it is.
Which means you can't select all on text which isn't editable - insane!
Readit Newsthehappyfellow commented on Fix the iOS keyboard before the timer hits zero or I'm switching back to Android ios-countdown.win/... · Posted by u/ozzyphantom
My blog is at https://blog.happyfellow.dev if you'd like to read it.
I'm also the Head of The Institute for Type-Safe Memetic Research which website is https://typememetics.institute/
A million times this. I wonder how to make them accountable though.
Author here.
I wonder about that as well!
thehappyfellow commented on Programming Language Theory has a public relations problem happyfellow.bearblog.dev/... · Posted by u/Bogdanp
Unconvincing article. PLT is a theory subject, as it says right in its name. If you're a practitioner and don't get off on theory, you're not going to be designing bleeding edge languages or compilers anyway, so you can stay pretty hip by just using the theory-adjacent stuff that comes out of the research places (example: Haskell). Just like if you're an electrical engineer, you might want to keep up with new kinds of semiconductors, but you don't need to study bleeding edge physics.
If you want to get started on PLT, Harper's PFPL is pretty accessible (https://www.cs.cmu.edu/~rwh/pfpl/). Even Martin-Löf's article on intuitionistic type theory (the one that introduced dependent types) is fairly readable for a PL geek.
I'm unfamiliar with Barendregt's article but it sounds too mathematical by comparison. I.e. by the title I'd classify it as mathematical logic rather than PL. Remeember there were no computers when Alonzo Church invented lambda calculus in the 1920's.
Of course practitioners shouldn't expect to understand the bleeding edge without investing a lot in learning the subject.
However providing people with software engineering background an easier on ramp for understanding PLT would be nice, wouldn't it?
thehappyfellow commented on Being too ambitious is a clever form of self-sabotage maalvika.substack.com/p/b... · Posted by u/alihm
It's closely related to another truth:
Unconstrained curiosity is a vice, not virtue.
Allegedly. And if you read anything about the case its clearly in a very gray area.
Their actions are what you'd expect any firm to do to hedge their exposure. Its just that they were so large and the Indian stock market is relatively so small that they're hedging moved the market.
So the question is, was their market moving hedging actual market manipulation or was it just the same thing every other quant firm would do in the same situation to hedge out their option exposure?
https://libgen.li/edition.php?id=151275376
Here's a decent description of the issue.
Thank you, this makes much more sense and it's a classic issue Matt Levine's readers will be familiar with.
Allegedly being investigated is also quite far from "been manipulating markets", I appreciate the clarification.
Jane Street was caught manipulating the India derivates market recently.
source?
thehappyfellow commented on Migrating to Postgres engineering.usemotion.com... · Posted by u/shenli3514
Two days ago, I'd have said the same. Yesterday, big box went down, and because it was so stable, it was a joint less oiled and the spare chickened out at the wrong time and apparently even managed to mess up the database timeline. Today was the post-mortem, and it was rough.
I'm just saying, simple is nice and fast when it works, until it doesn't. I'm not saying to make everything complex, just to remember life is a survivor's game.
You’re right, there are downsides like turbine you mention! We mitigate it by running a hot backup we can switch to in seconds and a box in which we test restoring backups every 24h, that’s necessary! But it requires 3x the number of big expensive boxes.
I still think it’s the right tradeoff for us, operating a distributed system is also very expensive in terms of dev and ops time, costs are more unpredictable etc.
It’s all tradeoffs, isn’t it?
thehappyfellow commented on Migrating to Postgres engineering.usemotion.com... · Posted by u/shenli3514
> By Jan 2024, our largest table had roughly 100 million rows.
I did a double take at this. At the onset of the article, the fact they're using a distributed database and the mention of a "mid 6 figure" DB bill made me assume they have some obscenely large database that's far beyond what a single node could do. They don't detail the Postgres setup that replaced it, so I assume it's a pretty standard single primary and a 100 million row table is well within the abilities of that—I have a 150 million row table happily plugging along on a 2vCPU+16GB instance. Apples and oranges, perhaps, but people shouldn't underestimate what a single modern server can do.
It’s incredible how much Postgres can handle.
At $WORK, we write ~100M rows per day and keep years of history, all in a single database. Sure, the box is big, but I have beautiful transactional workloads and no distributed systems to worry about!