ttfkam

11 ms·

31.
by ttfkam 1y ago
Would much rather have "Mongo" for SQL like this: https://github.com/microsoft/documentdb I am skeptical that SQL with Mongo backing it would be at all performant except in the most trivial cases. On the flip
32.
by ttfkam 1y ago
> Allow generated columns to be virtual, and make them the default Yes!!! > Add OLD/NEW support to RETURNING in DML queries Wow! That's a feature I'd never considered and now can't imagine living without moving for
33.
by ttfkam 1y ago
Lord, grant me the confidence of this man who claims objective understanding of what does and does not constitute "good code".
34.
by ttfkam 1y ago
C++ compiles quickly? News to me.
35.
by ttfkam 1y ago
Yes, Rust compiling is slow. Then again, I wouldn't say that C++ is exactly speedy in that area either. Nor Java. None of those are even in the same zip code to Go's compile speed. So if you're cool with C++ or Java compile t
36.
by ttfkam 1y ago
I liked checked exceptions. I just think they were overused. Had a CS prof that summed up the optimal case like this: Programmer's fault: runtime exception Not programmer's fault: checked exception Reading from a file but the disk
37.
by ttfkam 1y ago
The Result type works for an awful lot of people. Be careful with absolute statements like "does not work." When it works for many others, they might just assume it's a skill issue.
38.
by ttfkam 1y ago
It's also highly dependent upon the team's skill and diligence. You can easily ignore errors and skip error handling in Go with predictably hilarious results. In Rust, you can't just skip error handling. You have to proactive
39.
by ttfkam 1y ago
Apples to apples, Postgres might lose, but that'd be tying both hands behind its back first. Remember that Postgres's feature set is far larger than those alternatives. If you can use a range with an exclusion constraint, an unnes
40.
by ttfkam 1y ago
If the engineering demand is lower than the engineering supply, you're still winning. If your transactions per second only amounts to 60% of the Pi's capacity for a given use case, why complain?
41.
by ttfkam 1y ago
Which is why most folks use CloudFront like AWS recommends, which is typically free for services to route through. Prices for CloudFront egress are competitive with what you described for other vendors. I don't know anyone paying $90&#
42.
by ttfkam 2y ago
AI runs 24/7, not just when the Sun is shining and the wind is blowing. If folks want to put build out limits on AI, that's an option I guess (not a good one IMO). However if AI computation is going to continue to grow, it'll
43.
by ttfkam 2y ago
I'm not sure that was their position. They're not saying tech from the 60s was inherently bad. They specifically mentioned that we today are not constrained by the same hardware restrictions that gave rise to the software in the 1
44.
by ttfkam 2y ago
Party over, oops, out of time! Tonight we're gonna party like it's the year 2009!
45.
by ttfkam 2y ago
I have the same perspective regarding bandwidth, but I also consider any client to be running on a computer at least ten years old and at least three OS revisions behind. I like to consider myself a guest on a client CPU, GPU, and RAM. I sh
46.
by ttfkam 2y ago
Contrary to intuition, bigint ends up only 25% smaller on disk than UUIDv7 and no improvement in speed. Honestly in 2024, 32-bit ints are generally a poor fit. Either the table is small enough to be considered a lookup table (16-bit int) or
47.
by ttfkam 2y ago
> Easy enough: almost no one writes SQL queries by hand these days, not for querying the database nor for doing schema upgrades. It's all done by tools Your experience does not match mine. Tools like ORMs make horrible schemas in my
48.
by ttfkam 2y ago
> For a UUIDv4 PK To be fair, this blows out any db that supports clustered indexes as well. Non-k-sortable primary keys are just a bad idea all around. With UUIDv7, the WAL write amplification problem goes away just as the clustered ind
49.
by ttfkam 2y ago
> the old central gate keeping DBA team model I have mixed feelings about this. On the one hand I agree that ownership should be shared. On the other, app developers really don't consider their data structures as carefully in SQL as
50.
by ttfkam 2y ago
> the multi-table pipeline write pattern WITH new_order AS ( INSERT INTO order (po_number, bill_to, ship_to) VALUES ('ABCD1234', 42, 64) RETURNING order_id )
51.
by ttfkam 2y ago
I use transactional DDL all the time, even during development. It's nice to not have to fully reset your schema every time you test a migration file locally. With transactional DDL, you run the whole list, and if any fails, it rolls ba
52.
by ttfkam 2y ago
I hear you. When all you know is an ORM, you tend to treat SQL databases like dumb bit bucket add-ons to your app server. It's amazing how much potential performance and scalability are left on the floor because app developers can&#x27
53.
by ttfkam 2y ago
Yep, that was our strategy as well: just keep iterating until the script run cleanly from start to finish without errors.
54.
by ttfkam 2y ago
> JSON can often be used in place of arrays This is like storing UUIDs as text. You lose type information and validation. It's like storing your array as a comma-delimited string. It can work in a pinch, but it takes up more storage
55.
by ttfkam 2y ago
You think people choose Postgres because it's the incumbent? That's an… interesting take.
56.
by ttfkam 2y ago
Upgrading from v11 to v16 is not materially different in Postgres from v14 to v16. Same tools. Same strategies.
57.
by ttfkam 2y ago
If you want performance to steadily increase rather than steadily decrease, the answer to your question is yes. That doesn't mean tools couldn't be better, but there are clear technical advantages to their on-disk format updates.
58.
by ttfkam 2y ago
Unless you want support for the MERGE command (v15), bidirectional replication (v16), and some behind the scenes optimizations, you're not really missing anything. Whether you go from v14 to v17 or v14 to v20, I doubt it'll make a
59.
by ttfkam 2y ago
You're thinking only in terms of application. Types in the db save storage space, allow for better validation than plain strings, can be correlated cleanly with other columns with the same type, etc. Yes, more drivers and libraries sho
60.
by ttfkam 2y ago
Uhh… not wanting to see emojis is a matter of taste, not engineering.

More ›