Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
whizzter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
44 ms
·
721.
▲
by
whizzter
2y ago
Sadly iirc the US laws that makes GDPR compliance problematic cover subsidiaries so making them independant enough is probably more or less impossible in practice.
722.
▲
by
whizzter
2y ago
Our tendency as programmers is to make it perfect (or bust), take the seeing it getting traction as an indicator that you can often release earlier than you thought.
723.
▲
by
whizzter
2y ago
That's insanely bad advice, yes GPU memories was a tad anemic only a few years back so it could've been an option, BUT the introduction of raytracing (RTX) means that the GPU's needs to have a full world in memory so memory s
724.
▲
by
whizzter
2y ago
Actually noticed the compo in time this time (no idea good ideas for the theme though), got 2 or 3 interesting failed attempts to scrounge code from (but not sure of the approach to take yet).
725.
▲
by
whizzter
2y ago
13kb of 44khz 16bit MONO audio is 150ms, even with compression sampled audio is more or less out of the question. With pixel art images however you can get a fair bit in if you're comfortable with low resolutions in 8bpp or lower.
726.
▲
by
whizzter
2y ago
That sounds a lot like party-line arguments honestly, maybe rooted in 1960s issues 1: If I've paid on a non budget airlines _site_ (like Lufthansa,Air France,SAS,etc) and then see another livery on the plane I'm boarding that I&#x
727.
▲
by
whizzter
2y ago
Seems to me like an ego issue honestly since the article points out that a large part of the bloat is from codesharing, using the actual operators code feels like an obvious solution unless egos are too fragile.
728.
▲
by
whizzter
2y ago
At some point CPU manufacutrers started treating overclocking as a feature rather than somethings hobbyists do and then computer OEMs started to tune things for this, but due to the quick generation cycles without any kind of long term test
729.
▲
by
whizzter
2y ago
I broke the first CPU I've bought for my own money, it was a PPro 180mhz back in early 1997 (2 days before Intel introduced MMX). I ran it overclocked at 200mhz for a good while until I started getting stability issues, had to downcloc
730.
▲
by
whizzter
2y ago
In regular trading shares don't go to or from a company but rather changes hands between investors, so BsH selling off won't affect their cash reserves (unless it's part of an IPO, funding round or buyback). Looking at the ar
731.
▲
by
whizzter
2y ago
Hearing about the lone Swede reminds me of the weird history/role of that, https://www.npr.org/sections/parallels/2017/12/04/547390622/...
732.
▲
by
whizzter
2y ago
It's cute and neat to be able to do it 100% constexpr, however as you mention the indexers feels a tad inelegant. I've written 2 iterations of a reflection library where you needed to annotate structs slightly with an ugly macro b
733.
▲
by
whizzter
2y ago
Probably either an unwillingness from Apple to share HW documentation with MS or MS viewing Apple as a direct competitor now that they have their own machines so they prefer not to undermine their own business.
734.
▲
by
whizzter
2y ago
Yeah, the early hopeful news spread widely but the scandal and fallout certainly kept things in the news over here for a long time. There's a Netflix pop-documentary called "Bad Surgeon" with a that does cover the viewpoint o
735.
▲
by
whizzter
2y ago
These kinds of ideas to use stem-cells with foreign materials seemed in vogue back then, no idea how feasible they are in reality but an improvised similar technique for tracheae was how Paolo Macchiarini first got hyped and then convicted
736.
▲
by
whizzter
2y ago
Python "threads" have no impact on the slowness of Python. 1: Threads are still under GIL's (global interpreter locks) because the entire object model is thread-unsafe. 2: The Python interpreter works with full objects, JS in
737.
▲
by
whizzter
2y ago
Checksumming is also useful when storage goes bad or other random hardware corruption like cosmic rays or overheating/old computers.
738.
▲
by
whizzter
2y ago
Since contents of certificates contents sadly often diff there was a ballot to streamline the contents to lessen the burden on implementations to interpret the differences. Entrust missed/ignored the updates to how certificates were su
739.
▲
by
whizzter
2y ago
Actually, once C++ has reflection it'll be possible to get rid of the ugly macros and the "only" issue left is root-pointers/shadow stacks. Googling just now to find the boost_pfr library I noticed a newer one that would
740.
▲
by
whizzter
2y ago
500 are the transcription/llm/tts steps (ie the response time from data arriving on the server to sending back), the rest seems to be various non-AI "overheads" such as encoding, network traffic,etc.
741.
▲
by
whizzter
2y ago
The author of the linked article (and Kajiya) quit Embark to work on an indie title with his wife around mid 2022 if memory serves me right.
742.
▲
by
whizzter
2y ago
Insertion in AVL tree's is fairly simple and doesn't really have any cascades so they are quite predictable, deletions on the other hand cascades upwards with a bunch of different imbalances and thus rotations(and post rotation ba
743.
▲
by
whizzter
2y ago
Mainline OS's have been 64bit for about 15-20 years by this point, the point is to trim parts of X86 that isn't used when running a 64bit OS. Notice that only 32bit kernel/R-0 is removed, but not usermode/R-3 so even whe
744.
▲
by
whizzter
2y ago
The worst part about now in hindsight is how they probably could've moved to a work-list system like Vulkan or io_uring and kept it all in separate processes to retain that stability. Yes, memory wasn't as plentiful back then and
745.
▲
by
whizzter
2y ago
Packetloss with TCP creates unnecessary latency for games. The OS TCP stack basically will show data in a sequential fashion to the userspace code, this greatly simplifies things like a HTTP stream but in a game it also means that even if 9
746.
▲
by
whizzter
2y ago
If algae grows quickly and uses carbon you probably have to remove parts during operation, then there's 2 options, bury it (thus removing it from the loop and becoming negative) or optimally produce cheaper carbon fuel sources, thus we
747.
▲
by
whizzter
2y ago
In Sweden doctors have a fair bit of automation/systems around them, the sad part is that much of it has been co-opted for more stringent records keeping,etc that's just making doctors unhappy and ballooning administration costs i
748.
▲
by
whizzter
2y ago
Keeping SQL updates as part of the build does sound intriguing but does it work flexibly, not something for a live DB i hope (so when is it updated?) and assumes local copies for each DB. What build system has good integration for doing the
749.
▲
by
whizzter
2y ago
And we're still running desktop programs that rely on single-threaded performance, remember that the Python GIL removal project only got up to speed in the past year(s) and that's not even mentioning a bunch of other workloads a
750.
▲
by
whizzter
2y ago
Well back in the P6 to Conroe timespan we had that detour for more Ghz with P4 that turned out badly where probably assumed wider issue wouldn't be an issue when you increased the clockrate. Also back in those days 32bit x86 with it&#x
More ›