Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ttfkam
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
32 ms
·
331.
▲
by
ttfkam
3y ago
> Rule 5. Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming. This goes double for dat
332.
▲
by
ttfkam
3y ago
One of those history lessons is that change happens. This is why Rust has editions: allows for new features without breaking old code. There is still code complexity, but that complexity has been shifted/amortized into the compiler sui
333.
▲
by
ttfkam
3y ago
I had two 4K monitors in portrait mode. Meant less vertical scrolling. I generally put different contexts on different screens, eg. code/terminals on one monitor and browsers with results on the other. Laptop screen left open as well f
334.
▲
by
ttfkam
3y ago
I'm not a gamer. I'd be fine with a single cable that served two 4K monitors at 30Hz from the Mac if it meant I never needed another dock ever again. That said, TB3/TB4 should be able to handle dual 4K at 60Hz from a single D
335.
▲
by
ttfkam
3y ago
All my old laptops since 2003 still have functional CPUs and RAM. I'm not overly concerned about the CPU/RAM situation, especially have seen the advantages to a shared CPU/GPU/RAM Arm architecture. Would I prefer upgrade
336.
▲
by
ttfkam
3y ago
A 2009 MBA can still be used if the SSD dies. You can get a replacement or you can plug in an external drive to install on and boot off of. You can upgrade the storage space on that model if you want to. Since 2018 and the T2 chip, the BIOS
337.
▲
by
ttfkam
3y ago
CloudFlare remade their primary reverse proxy in Rust and had so few development issues, they ended up finding kernel bugs instead when problems arose. I've worked on projects with non-trivial C++ codebases for a variety of companies,
338.
▲
by
ttfkam
3y ago
Perhaps it would help to know that I upgraded the RAM and hard drive on my 2005 Santa Rosa MBP. Really easy due to standard DDR2 SODIMMs and SATA connectors. Did the same to my 2009 unibody, put a 500GB hybrid solid state hard drive in it a
339.
▲
by
ttfkam
3y ago
Guilt by association and/or ad hominem are weak sauce. What part was factually inaccurate? • That storage is soldered unlike the vast majority of laptops on the market, which use standard NVMe sticks? • That the BIOS is stored in those
340.
▲
by
ttfkam
3y ago
> Conceptually, Rust forbids certain patterns in programming which are otherwise very valid and necessary. Rather than forbid, Rust requires you put logic like this inside unsafe blocks. This limits the number of places you need to look
341.
▲
by
ttfkam
3y ago
Watch the video I linked. Modern Macs are a single capacitor failure away from shorting 13v straight to those "amazing focus on quality" SSD chips. Either one of the two chips dies, you have a brick. No booting from external drive
342.
▲
by
ttfkam
3y ago
Au contraire, mon frère! https://www.postgresql.org/docs/current/jit-reason.html
343.
▲
by
ttfkam
3y ago
This statement… > "maybe crash, maybe accidentally continue running and make things far [worse] than crashing" instead "definitely crash" …is functionally indistinguishable from your reply. > (two pointers can refe
344.
▲
by
ttfkam
3y ago
Two things I've been waiting on for years: • MST (DisplayPort daisy chaining) in MacOS. The hardware has supported it for over a decade. The OS is the weak link here. It's the difference between spending $75-$300 for a dock in add
345.
▲
by
ttfkam
3y ago
Billionaire wants more uncompensated labor to pad his bottom line. News at 11.
346.
▲
by
ttfkam
3y ago
I truly adore the work done here by Hasura. It follows the principles underlying SQL itself of defining an interface where the user request WHAT data they want, not HOW to get that data. Between this and Postgraphile's Grafast engine,
347.
▲
by
ttfkam
3y ago
> Furthermore, simple grammar is only superficial, and the new algebra will actually bring performance improvements. For example, using ordered grouping instead of hash grouping, using merge instead of hash when associating, and so on. A
348.
▲
by
ttfkam
3y ago
> esProc SPL is a JVM-based data computing class library Those who ignore the lessons of the past are doomed to reimplement them… poorly. Your first example is what MATCH RECOGNIZE is for, no? https://modern-sql.com/featu
349.
▲
by
ttfkam
3y ago
Let's examine these limitations in the context of Svelte/SvelteKit: • functions named handleClick,handleSubmit Agreed, not as descriptive as it could be, but when your component is noticeably smaller, arguably not as big a deal. •
350.
▲
by
ttfkam
3y ago
> Look, Google has a huge writing culture. Design docs are the norm there. I don't know what Google they're talking about, but for non-customer-facing code, Google was atrocious for that when I was there. "Docs? Just read
351.
▲
by
ttfkam
3y ago
It was a debate, and Buckley got his ass handed to him. Soundly. Baldwin literally wiped the floor with him, and everyone there knew it. It was legendary for Buckley only insofar as he got the debate version of a royal beat down in public.
352.
▲
by
ttfkam
3y ago
Millions of rows with a JSON column? Yes, indeed I have. Recently in fact. When all normalized fields are populated, you're absolutely right. However that wasn't our dataset. We had entries with sparse keys. This was due to the na
353.
▲
by
ttfkam
3y ago
Re: JSON https://www.postgresql.org/docs/current/datatype-json.html Re: RDBMS was not designed to store JSON https://youtube.com/watch?v=rpw_x8TtqTo
354.
▲
by
ttfkam
3y ago
Impressive
355.
▲
by
ttfkam
3y ago
Rare?
356.
▲
by
ttfkam
3y ago
All this pain when most of the time folks could just fire up Postgraphile or Hasura, point them at their Postgres database, and go sip mai tais by the pool. I honestly don't understand why folks insist on writing their resolvers by han
357.
▲
by
ttfkam
3y ago
I for one am sad to see this go. I understand the rationale—not wanting a spec dependent upon a single implementation (SQLite)—but IndexedDB was never a better alternative. It worked in a pinch, but IndexedDB was always a solution in search
358.
▲
by
ttfkam
3y ago
Every time I see one of these articles saying how good the memo hooks are and also how folks aren't using them correctly (of which there seem to be dozens every month on various sites), I can't help but feel "you're hold
359.
▲
by
ttfkam
3y ago
The locks I was referring to were a direct result of many (most?) ALTER statements. Multiple clients trying to migrate isn't even in this equation. Just one client migrating can ruin your day with a single ALTER statement given a large
360.
▲
by
ttfkam
3y ago
> Start migration, create transaction and locks If you do that on a table or two with millions of rows, you've effectively locked your database from all other access, even SELECTs. ALTER statements typically grab exclusive locks,
More ›