parhamn

> I'm curious as to why would you think that?

Huh? From the Swagger site:

"The OpenAPI Specification defines a standard interface to RESTful APIs..."

From their OpenAI Initiative:

"The OpenAPI Specifications provide a formal standard for describing HTTP APIs"

Not sure I care to understand your POV more given this obvious bit was missed by you.

I am curious about this, whats the difference between the fastest json libraries (e.g simdjson) and protobuf?

It's interesting, to everyone but but the mega shops like Google, protobuf is a schema declaration tool. To the megashops its a performance tool.

For most of my projects, I use a web-framework I built on protobuf over the years but slowly got rid of a lot of the protobufy bits (besides the type + method declarations) and just switched to JSON as the wire format. http2, trailing headers, gigantic multi-MB files of getters, setters and embedded binary representations of the schemas, weird import behaviors, no wire error types, etc were too annoying.

Almost every project I've tracked that tries to solve the declarative schema problem seems to slowly die. Its a tough problem an opinionated one (what to do with enums? sum types? defaults? etc). Anyone know of any good ones that are chugging along? OpenAPI is too resty and JSONSchema doesn't seem to care about RPC.

I don't get your point. Sure, the git log isnt the "cathedral", but also being able to change things quickly doesn't imply or necessitate this.

Numberphile had a great video on this a few years ago: https://youtu.be/rXfKWIZQIo4

> that's damning proof that there is little empathy in the process, no?

No.

Part 3 came out in 1990. So, anyone born after (less than 34 years old) who didn't bother to go back and watch it, would be sufficient? I'm familiar with the series' existence, but had no idea what 1.21 reference was. AMA, hah.

> This study supports the inclusion of sleep regularity in public health guidelines and clinical practice as a risk factor for cardiovascular disease.

Does it? What they're measuring seems like a very likely proxy measurement for stress. I can't tell besides employment status/hours if they measure or include that at all.

Although, I agree with the general point, I am thankful for the bit of extra work they do when I travel abroad. The quality and availability of Netflix is far superior (many don't even work outside the US).

Those two paragraphs are at odds with one another, no? Moving air also increases the evaporation rate.

This is why fans are found to be generally effective to 104 degrees. https://time.com/5644737/fans-can-make-you-hotter/

Across a broad enough dataset (char count / 4) is very close to the actual token count in english -- we verified across millions of queries. We had to switch to using an actual tokenizer for chinese and other unicode languages, as that simple formula misses the mark for context stuffing.

The more complicated stuff is the effective bin-packing problem that emerges depending on how much different contextual sources you have.

I'm sure people will call out performance is likely due to the different nature of the beast that is now redis -- there are lots of wire compatible implementations that are faster thant redis, with some lost affordances.

Either way, the templating bit on the homepage is a pretty interesting concept. Storage and templating in one with write operations in the template. Im curious how this grows out and whether it will be great or a regret. Somewhat dynamic static sites like that could be fun.

TIL thanks

Hauwei ships 12 million phones per quarter [1]. If even a small percent of them included these chips, it should be pretty damn obvious no?

[1] https://huaweicentral.com/huaweis-global-smartphone-shipment...

Which?

Does such a thing exist that works for coding? Don't need the AR. My posture/back could use this for when I'm not working at my desk.

WebSQL should've just been Sqlite and the whole offline-first (and general app storage) ecosystem would've been so much nicer.

Is there any hope of that happening? Instead of abstracting and over specifying sqlite, can the spec just specify a version of the SQLite API browsers should support and roll the version periodically?

Put a CO2 + temp/humidity sensor in there and it's a no-brainer. The sensors could be nice to hack on too.

Stateless S3 apps have much more appeal given the existence of Cloudflare R2 -- bandwidth is free and GetObject is $0.36 per million requests.

This isn't true outside the theoretical best case. Definitely not true in most interpreted languages. Consider the performance difference of .reverse() (in-place or copy) vs using a descending for loop. Generally with interpreter chaining there are more "hidden" allocations/operations.

I think the killer case for this is not hiding the computational complexity of mapping/reversing/etc.

I write a lot of typescript and golang and I often notice in typescript my chains end up iterating the same array N times when it couldbe been done in one smarter iteration.

I don't think I care though -- both styles are way more than performant enough. You can be more careful about it in cases it is not.

Sure, most things are representable in a table. Its very tricky to get these things to perform well. Every query needs to have the additional filters/aggregations and every index needs to be smart and partial. E.g. you need all your indexes to be partial with a CREATE INDEX WHERE deleted_at = null for the deleted case as having a giant boolean filter can quickly include a large percentage of your data making the indexes useless.

I tried this once many years ago and it became quite a headache. Direct SQL access to the database to perform management queries outside your application becomes a headache too.

If you go by manufacturing jobs, BLS seems to have the data going back to 1939. Peaks at 18.4m jobs in 1969. Currently at about 12.9m.

N.B. the current U.S. population is 1.6x the population of 1969.

https://data.bls.gov/timeseries/CES3000000001

"Don't take in ferromagnetic metals that would get pulled by a 3T magnet with 6 inches of separation" is a bit harder to grok for pretty much everyone.

Not helpful.

Yeah I figured as much. Hence the "[t]his sort of tech" -- I imagine progress would be made soon on those fronts as well? Or am I mistaken?

Question for bio folks here, and not to steal from the joy of this article but I've been recently curious how far are we from engineering something like a virus that targets a subset of the population (e.g. via specific genetic markers). This sort of tech being commoditized feels much much scary than the LLM safety talk - by a mile.

Sorry I misread, I meant that the article itself points to the fact that theres more to the charge than the "dot", the just, oddly, happen to mention it on the last line.

> Technically the article never says the dot is related to the arrest, but it's certainly implied.

Given the last sentence of the article is "The prosecutor’s office in Ardabil alleged that Shanbehzadeh had been in contact with Israeli intelligence officers and was arrested when trying to leave the country, according to Voice of America." it's not even implied.

Yes! Happy to try it on a fairly large user base and contribute to it! Email in bio if you want a beta user.