mattxxx · HackerTrans

vor 10 Monatendiscuss

typst is so good! the syntax is cleaner, and it's much easier to write re-usable and clever formatting.

LaTeX will have a special spot in my heart, but it's pretty bloated (even minimalist distributions) and suffers from being an early pass at a problem.

mattxxx

vor 10 Monatendiscuss

It's pretty daring to do something like this. Something so brazen has a 100% chance of getting caught given enough time...

That said, installing any package is a liability, whether it's a library or an mcp server.

mattxxx

vor 10 Monatendiscuss

well, manipulation is more about intent, rather than technique... I think it doesn't matter if you chose the correct "door" if you're trying to get someone to operate against their own interests.

mattxxx

vor 11 Monatendiscuss

> unless you're a mathematician

As a young math researcher, my mentor definitely did not believe that Math was the absolute descriptor of the universe.

You can definitely imagine a scenario where the world does not operate perfectly mathematically correct though Math still exists - as an abstract separate entity.

You can do this such that everytime you recognize a new quirk in the world, then you can invent some new math/logical framework to match/approximate the current understanding. I don't know if this is the reality of this world, but when you look at things like complexity theory you have to wonder "okay... maybe we designed a useful system rather than discovering a true law of reality"

mattxxx

letztes Jahrdiscuss

The article is good, but maybe a bit negative on the postgres feature. I think the article reads much better with the slant:

  "LISTEN/NOTIFY got us to this level of concurrency; here's how we diagnosed the performance cliff, and here's what we're doing now."

Which is like... cool, you were able to scale pretty far and create a lot of value before you needed to find a new solution.

mattxxx

vor 2 Jahrendiscuss

JOINs are just hard period. When you're operating at a large scale, you need to be thinking about exactly how to partition + index your data for the types of queries that you want to write with JOINs.

Streaming joins are so hard, that they're an anti pattern. If you're using external storage to make it work, then your architecture has probably gone really wrong or you're using streams for something that you shouldn't.

comments