730 karma · joined March 3, 2013
The biggest difference at a low level is that turbopuffer records have unique primary keys, and can be updated, like in a normal database. Old records that were overwritten won't be returned in searches. The LSM tree storage engine is used to achieve this. The LSM tree also enables maintenance of global indexes that can be used for efficient retrieval without any time-based filter.
Quickwit records are immutable. You can't overwrite a record (well, you can, but overwritten records will also be returned in searches). The data files it produces are organized into a time series, and if you don't pass a time-based filter it has to look at every file.
- https://www.interactivebrokers.com/en/pricing/stock-yield-en...
- https://www.fidelity.com/trading/fully-paid-lending
Some brokerages lend out spare cash (and pay a transparent interest rate, and are subject to strict reserve requirements) but the majority of assets controlled by a typical brokerage are securities. FTX assets were all subject to their leverage strategies, with no specific reserve.
Unlike AVIF, JPEG XL also has advanced progressive delivery features, which is useful for the web. And if you look at the testing described in the post, JPEG XL also achieved higher subjective quality per compressed bit, despite having a faster encoder.
This timecode format is a timestamp with seconds resolution plus a frame count within each second. To properly sync, all the timecode generators must use the same framerate. In other words, the audio recorder’s timecode framerate needs to match the camera.
Either way it's more sensible to build high throughput microwave networks given the tiny amount of shortwave bandwidth we have.
As you say the downside is available bandwidth and throughput.
“Chosen by fair dice roll. Guaranteed to be random.”
If some kind of moth wing inspired metamaterial can shrink the width of broadband sound absorbing panels by 10x that would be quite useful still.
The list of “Following companies and projects are already evaluating CLAP for their host and plug-in software” is pretty impressive and personally accounts for a large amount of my workflow. Hopefully it gets big enough for Native Instruments to implement, Kontakt could benefit significantly from some of the new features.
What? I'd be bothered with my own stupidity if I felt I couldn't get a good grade without cheating. I put in a minimal amount of time/effort in university where the subject matter didn't interest me, but always did fine without cheating.
NV seems to rasterize vertexes in small batches (i.e. immediately) but buffers the rasterizer output on die in tiles. There can still be significant overlap between vertex generation and rasterization. Those tiles are flushed to the framebuffer, potentially before they are fully rendered, and potentially multiple times per draw call depending on the vertex ordering. They do some primitive reordering to try to avoid flushing as much, but it's not a full deferred architecture.
i.e. golden handcuff equity grants with vesting schedules? Top performers in highly demanded areas can have some or all of their remaining equity bought out.
It definitely ties the value of the contract to the stock price. In a way the company is leveraging its stock - significant declines hurt talent retention, and significant gains help it.
I have an Apple keyboard and trackpad that I use at my TV wirelessly but have benefited from the ability to use while charging a few times when the battery died. Doesn’t stop me from using it wirelessly 99% of the time because the experience is better.
By the way, I have an older phone I leave plugged in all the time by my bed, the battery life on it has deteriorated but it works perfectly for music.
I think the sleek visual and ergonomic design specifically resulted in the charge port being put on the bottom, which resulted in their decision to disable the mouse when it’s charging. Not the other way around.
A fun hack is to run a captcha-free fake forum and allow random bot signups to generate outbound mail volume and trust.
How are you scrolling? When I’m browsing and reading my hand lives on the mouse. On mobile it’s even easier to click to play. In either case, clicking on a video takes less than 1 second.
I do agree that extremely short loops can be a different story, but 20 seconds is by far over that time for me. 5 seconds is around the threshold.
I’m sure this preference varies by person.
One common misstep is having a table with columns like (id, user, date), with an index on (user, id) and on (date, id), then issuing a query like "... WHERE user = 1 and date > ...". There is no optimal index for that query, so the optimizer will have to guess which one is better, or try to intersect them. In this example, it might use only the (user, id) index, and scan the date for all records with that user. A better index for this query would be (user, date, id).