https://github.com/longbridge/gpui-component

Reality is way more nuanced. Something can have high demand AND be on the precipice of financial catastrophe. See: Spirit Airlines.

Quite convenient how the same people trying to run roughshod over the others to get these bubble mania mausoleums built NEVER live near them but are HAPPY to make others who can't afford a second home live next to them.

SO tried to optimize the Q/A by eagerly rejecting repeat questions, without considering what the consequences of that were. If you’re in a classroom / lecture hall, your teacher / professor isn’t going to chide you for asking an “obvious” or “repeat” question (bad ones might). Imagine if every time you wanted to talk to a TA or professor you first needed to lookup previously asked questions in a database and then, iff your question hasn’t been asked before, you may ask the professor or TA after hours. Programmers might call this system “efficient” but most people would be pretty unhappy with it.

https://www.youtube.com/watch?v=C7gJ_UxVnSk

My only complaints are:

1) Memory usage is a bit high. We went with the AWS instance they recommended in the docs and even that went over our provisioned memory. It's not much but I think it could be improved

2) You need to buy their enterprise plan if what you're storing is remotely sensitive like health data, PII, etc. Any row level security or credential features are locked behind that license. Our use case isn't that sensitive so we can get away with putting it in a VPN and password protecting it, but if you need DB-level security the FOSS license is severely behind Postgres in terms of features.

Other than that, it's never gone down, it's very, very fast and comes with it's own webui for querying your data. We migrated from AWS Timestream and couldn't be happier with the switch.

What changes have LLMs (Not AI, not machine learning in general, I'm not going to waste time discussing the definition), LLMs made in the past 4 years that indicate anything close to the above? Solving a whiteboard math problem?

- Sam Altman & Worldcoin collecting everyone's eyeball scan - Discord attempting to roll out worldwide age & id verification - LinkedIn collecting data on your web browser extensions - WhatsApp collecting browser data via a local server running on device

For example, your section on effects:

> Functions which guarantee they do not unwind (absence of the panic effect)

* I actually don’t see how this is any more beneficial than the existing no_panic macro https://docs.rs/no-panic/latest/no_panic/

> Functions which guarantee they terminate (absence of the div effect)

> Functions which are guaranteed to be deterministic (absence of the ndet effect)

> Functions which are guaranteed to not call host APIs (absence of the io effect)

The vast majority of rust programs don’t need such validation. And for those that do, the Ferrocene project is maintaining a downstream fork of the compiler where this kind of feature would be more appropriate.

I think rust is in a perfect spot right now. Covers 99.99% of use cases and adding more syntax/functionality for 0.001% of users is only going to make the language worse. The compiler itself provides a powerful api via build.rs and proc macros which let downstream maintainers build their desired customization.

This is a common line of phrasing parroted by Flock and their supporters to no end but it's a myth. The SC, as much of a joke as they are now, established that a person has a reasonable expectation to privacy in their long term movements in Carpenter v. United States (2018). To date there is NO precedent carved out in the constitution or ANY Supreme Court case stating that people have zero expectation to privacy in public.

https://www.supremecourt.gov/opinions/17pdf/16-402_h315.pdf