This is the clearest example of an attention grab I have seen - it does nothing for commercial use of Llama unless they provide a version of the weights produced by them and not Facebook. (and they don't...they ask you to download them from Facebook's repo)
As someone replied above, it's because SQL is just 1 backend and it's weird to expose an API that only works on 1 backend. Once you have many devs working together, you need a remote server. If you have a remote abstracted backend, it needs to have a unified API surface so the same client can talk to any backend. You might argue "This interface should be SQL", and to that I would say there are many file stores (like your local file system) that are not easy to control with SQL.
SQLite is literally a backend for MLflow, so the argument being made really is that you should just use SQL when you can, which is kind of adjacent to any criticisms of MLflow
Right - I think this is part of the "scaling" of the internet. Those of us (relatively small set of earlier heavy internet users) are forced to change as the product is built for the wider audience.
This resonated a lot with me. Often if I'm learning a language and I see no one is doing what I'm querying for, I take a step back and try to ask a more basic question
I think what HN and the SWE community at large has just missed about Google over the last 10 years is that the product is being built for the masses. Most people would prefer if you just rewrote the title to what it actually was rather than having to take on the cognitive load of understanding what SEO even is.
...and there's a reason for that. Automations to update the status page are rarely acceptable, since the status page statuses have legal and financial implications. Therefore, the IM usually has to update it (or tell someone to update it). But, realistically, when you get paged, you first need to figure out what exactly is wrong and at least a vague idea of why. Then, you need to tell someone to update the page. Then, it gets updated.
The status page will always lag the outage. It's not a conspiracy.
I mean, sure? mumblemumble is still right though. If you're looking for a cynical reason for everything FB related, then, sure, it's true that a human error looks bad.
This is just completely false - if you're working on a feature, you want a PR splash controlled by you, not a stream of silent leaks. PR begets other PR.
You're being super presumptuous by saying engineers shouldn't care about the PR around the feature they worked on, even if someone else is running the PR
Underrated truth - have owned a Tesla for 5 years, and the number of stupid things that go wrong with it is incredibly high. It works like a phone...after a number of years, it takes forever to boot and has plethora of bugs. Random stuff breaks/falls off. We're going to see even more of this in 10 years, as the cars that were produced during the scaling period start falling apart. What sets automakers apart is that you can buy a used car after 10 years and expect it to still work.