Took a while to find on their website but here’s a benchmark vs AWS Aurora:
https://planetscale.com/benchmarks/aurora
Seems a bit better, but they benchmarked on a kind of small db (500gb db / db.r8g.xlarge)
HN user
ohxh.net oliverhopcroft@gmail.com
Took a while to find on their website but here’s a benchmark vs AWS Aurora:
https://planetscale.com/benchmarks/aurora
Seems a bit better, but they benchmarked on a kind of small db (500gb db / db.r8g.xlarge)
Lots of non-chatbot uses in property management. Auditing leases vs. payment ledgers. Classifying maintenance work orders. Creating work orders from inspections (photos + text). Scheduling vendors to fix these issues. Etc.
They say "thus, on average, about two-thirds of cats preferred to sleep on the left side of their body with their left shoulder down", and their image for leftward lateral bias shows this. So I guess leftward means "lying on their left side", not "curling left".
But, they suggest this is because "Upon awakening, a leftward sleeping position would provide a fast left visual field view of objects", which seems suspect. When my cats sleep on their left, it's their left eye that's obscured by their paw, and their right eye that has a better field of view!
Here, I don't think it's even useful to look at this problem in electronic terms
I always thought this problem was a funny choice for the comic, because it’s not that esoteric! It’s equivalent to asking about a 2d simple random walk on a lattice, which is fairly common. And in general the electrical network <-> random walk correspondence is a useful perspective too
This seems unusually shallow for the hedgehog review. I thought we'd largely moved on from this sort of sentimental, "I can't get good outputs therefore nobody can" style essay -- not to mention the water use argument! They've published far better writing on LLMs too: see "Language Machinery" from fall 23 [1]
[1] https://hedgehogreview.com/issues/markets-and-the-good/artic...
Johnson-lindenstrauss lemma [1] for anyone curious. But you can only map to k>8(\ln N)/\varepsilon ^{2}} if you want to preserve distances within a factor of \varepsilon with a JL-transform. This is tight up to a constant factor too.
I always wondered: if we want to preserve distances between a billion points within 10%, that would mean we need ~18k dimensions. 1% would be 1.8m. Is there a stronger version of the lemma for points that are well spread out? Or are embeddings really just fine with low precision for the distance?
[1] https://en.wikipedia.org/wiki/Johnson%E2%80%93Lindenstrauss_...
“One could offer so many examples of such categorical prophecies being quickly refuted by experience! In fact, this type of negative prediction is repeated so frequently that one might ask if it is not prompted by the very proximity of the discovery that one solemnly proclaims will never take place. In every period, any important discovery will threaten some organization of knowledge.” René Girard, Things Hidden Since the Foundation of the World, p. 4
Or maybe they do believe this, and entered into trades to express this sentiment. Now, they need the market to correct to what (they believe) is accurate, so they can take profits and free up their capital again.
These are all special instances of a more general computational problem called the hidden subgroup problem. And quantum computers are good at solving the hidden subgroup problem. They’re really good at it.
I assume they mean the hidden subgroup problem for abelian groups? Later they mention short integer solutions (SIS) and learning with errors (LWE), which by my understanding both rely on the hardness of the shortest vector problem, corresponding to the hidden subgroup problem for some non-abelian groups. I haven't read into this stuff for a while, though
There’s a fun version of this that they have at 7-11 (or 7 & I) there. Probably other convenience stores too. They come in a plastic wrapper that separates the nori from the rice and filling so it doesn’t get soggy. When you pull a little tab, it somehow removes the plastic from in between without messing up the shape. Magic!
As far as I understand, web 1.0 is browser makes a request -> backend delivers some html, with subsequent requests just for css/images/iframes. This also had a characteristic style with layouts made from tables and simple but busy designs. Web 2.0 is many of the web apps you see today, where you don’t need to load a page to fetch new content, but instead asynchronous JavaScript grabs it and edits the html — think gmail or Google maps. Web 3.0 is unclear to me, but it seems like most people who use it refer to decentralized or peer to peer applications and crypto.
You've made something really cool here. Watching transfixed me in a way similar to a video exhibition I saw at the Tate Modern when I was younger. It was a loop with footage of a JAXA rocket launch, an anti-nuclear protest after the Fukushima-Daiichi disaster, and the eruption of a volcano, with narration from a shaman in Japanese (subtitled) contemplating our relationship with nature. "Transit" by Susan Norrie. https://www.youtube.com/watch?v=9TS3d4URcB4&t=173s
There’s an interesting approach similar to this called Wave Function Collapse [1] (no relation to wfc in physics besides inspiration). It can infer the probabilistic constraints from one input example, and it seems to generalize quite well. Here’s a little demo: https://oskarstalberg.com/game/wave/wave.html
Curious how you went about the WA LLC too — I lived there for a lot of my life and that was my other thought on states to incorporate in.
Just my thought -- perfection is the enemy of good. I've fallen into this before, trying to write the "ultimate" version of some program. Do you use your own web apps today? If you enjoy the work, why not start by focusing product that you need today? If something is good enough to work for you, others will find value too.
I'm working on something similar. In chrome you can request an image of the active tab from a background page, write it to a canvas to downscale it, and then dump it into indexeddb as a blob of base64. This only captures tabs that have been active at least once but I haven't noticed any additional latency using it.