Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Rapzid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
32 ms
·
601.
▲
by
Rapzid
3y ago
That's crazy. They raised a ton of money and the fact that the airplane.dev platform is being sunsetted.. How graceful was this.. landing?
602.
▲
by
Rapzid
3y ago
Pretty much everything is moving to UUID of sorts including Google auth. It's tricky because you often need to let people reference username/emails for mentions and etc, so you just have to index all of em and translate to UUIDs f
603.
▲
by
Rapzid
3y ago
Shout out to F# in the browser via Fable too.
604.
▲
by
Rapzid
3y ago
> Firefox complained that it was work LOL, as they do.
605.
▲
by
Rapzid
3y ago
To add to this for anyone reading later.. The OS doesn't write bytes to the storage; it writes blocks. For modern drives the sector size is 4k, and the block io size is likely to be 4k unless utilizing 512b emulation. So, the OS will a
606.
▲
by
Rapzid
3y ago
> The example with follower_count shows how to use the +1 technique to do without locking.. Without explicit pessimistic locking. There are always locks. More guarantees, more locks. That issue example can be tackled with optimistic conc
607.
▲
by
Rapzid
3y ago
Pretty much every RDBMS has this: https://www.postgresql.org/docs/current/explicit-locking.htm... There are multiple flavors in PostgreSQL with different locking semantics. And the exact locking semantics may diff
608.
▲
by
Rapzid
3y ago
I should have used more precise language; I mean the bytes written to disk don't work out with such a simple formula. Missed the footnote which discusses this, but there are even more things to consider such as how many rows are being
609.
▲
by
Rapzid
3y ago
The math on #1 doesn't check out. If you update 2 bytes in the record only 28 are still written. But are only 28 written in either case? Does Postgres not write out entire pages? It gets much more complicated when you consider full pag
610.
▲
by
Rapzid
3y ago
I rock a workstation for this reason and that I also don't want a separate computer for other workloads(games, etc). 5950X, 64GB of RAM, Windows 11 + WSL. An AMD based ThinkBook for travel.
611.
▲
by
Rapzid
3y ago
I've never noticed a problem with Chrome sync.. It's funny though that the issue the author has, address bar history sync, is something I explicitly turn off.. Because it does work, and I don't like all my browser histories s
612.
▲
by
Rapzid
3y ago
Yeah, I read complaints from people about more and more sites not working after updates and over time (banks, etc). How can they fulfill their mission if they aren't meeting users where they are at and being aggressive about being the
613.
▲
by
Rapzid
3y ago
Mozilla are dragging their heels on @scope: https://github.com/mozilla/standards-positions/issues/472 https://connect.mozilla.org/t5/ideas/implement-css-scope-rul... Someone who cle
614.
▲
by
Rapzid
3y ago
This is sorta indicative on my thoughts on Mozilla/FireFox in 2023. You got Chrome and Webkit/Safari on board. And then someone who just doesn't "get it" wasting three calendar years. I make snarky comments about Fi
615.
▲
Mozilla's Position on CSS Scope
(github.com)
1 points
by
Rapzid
3y ago
|
1 comments
616.
▲
by
Rapzid
3y ago
Calc deserved more attention in this article; it's really amazing what you can do with it. I'm using it in an application to center content inside a flexible container.. Using calculated padding. One of the coolest new features on
617.
▲
by
Rapzid
3y ago
This is why flexbox and grid didn't receive the fanfare they deserved; they launched during the dark ages.
618.
▲
by
Rapzid
3y ago
I hate how even if you pay for no ads shows can have ackward cuts designed around commercial breaks :|
619.
▲
by
Rapzid
3y ago
Definitely recommend it. The difference in detail and insight on the HttpClient information between the book and the Microsoft docs is a good case study. The docs are often limited to autogenerated API with some surface level remarks.
620.
▲
by
Rapzid
3y ago
It's punishing success like cutting the grass or trimming the bushes is punishing success.
621.
▲
by
Rapzid
3y ago
The form factor just isn't there yet for anything outside entertainment or niche business usage. Until it's significantly improved the tech is going to be stuck with the early adopter market. Most people would rather not wear a he
622.
▲
by
Rapzid
3y ago
This was flagged and dead so I vouched for it. It's a conversation people work really hard to shut down. John Oliver had a good segment on Israel/Gaza/Hamas/Palestine a few weeks back. There is a concerted effort to pain
623.
▲
by
Rapzid
3y ago
There is no way to know.
624.
▲
by
Rapzid
3y ago
I agree. People wanting to learn C# are told to watch YouTube entertainer videos and read the Microsoft docs haha. C# In a Nutshell still is worth it's weight IMHO.
625.
▲
by
Rapzid
3y ago
It's amazing how many people seem to not see further up the road than the cars directly in front of them. Even when driving tall SUVs or trucks. My favorite scenario is when someone super impatient pulls around (often suddenly without
626.
▲
by
Rapzid
3y ago
I'll switch to FF when they let the scrollbars be styled properly so my got-damn apps don't look like got-damn 1999 with those ugly ass scroll gutters. Between that and the embed situation FF is clearly engaged in some sorta self-
627.
▲
by
Rapzid
3y ago
It looks like dangling is key to the untangling.
628.
▲
by
Rapzid
3y ago
MobX and chill. Works with React, Vue, Solid, and etc.
629.
▲
by
Rapzid
3y ago
Oh and some of the React core team landed at Vercel, and React has been focusing on backend features and partnering with Next/Vercel on early development of said features. So there is frustration that the React project is now perhaps a
630.
▲
by
Rapzid
3y ago
Chrome Reaper... CReaper.
More ›