Well then your one basket is your machine, or your backup system. And Office and Onedrive still work IIUC, so you're not really comparing apples to apples.
It's much better UX if everyone within the company uses the same office suite/email, it makes collaboration much nicer when everything is well integrated. And people get used to one system.
My guess is that having duplicate system would cost (in money for double subscriptions and lost productivity) much more than the benefit of being available 0.01% more. Especially for universities where almost nothing is really urgent and can't be delayed by a day.
I don't see a reasonable alternative here. Pay for another email/office suite provider, and duplicate all mails and files? Twice the cost and exposure surface just to cover 0.01% of downtime.
Sure, it makes sense for mission critical companies (utilities, emergency services), but I don't think it does for an average company. Especially that you don't take much blame if everyone is down.
I think pricing that rewards searching is actually very fair and good. You give customers choice between money and effort - rich people will book the first flight and pay more, subsidized poorer people.
If agents make finding cheaper tickets trivial and the default, customers lose that choice.
But in this case, collecting the data is already a part of USPS core business so there isn't much overhead. And there's no individual processing needed per request like in your body cam example.
To me it's obvious that anything related to caching has little to do with the model itself. And it's nice to know from the title that you could only be affected if you used this model.
It took me until "We have remediated the issue" to realize Cloudflare is talking about an issue they have in their infrastructure, up until that point they're not making that clear at all, and seems to point towards something else, unless you of course already are aware of what exact names Cloudflare uses for their products...
No, there's a lot of stuff where formal proofs don't make sense or are highly prohibitive.
The flagship case is AI itself, where we rely on benchmarks, not proofs (how could one prove "is good at seducing people").
Something that could have qualified as a "CS discovery" would have been, for example, a SAT or SMT solver that dwarfs in performance any existing one.
Something that could have qualified as a "physics discovery" would have been a new particle. Anyway, something that would come out of experimental data.
You'd only get plain unstyled rendering with browser support. And at that level you don't need any complexity from Hugo or Obsidian - you only need a very simple script to convert md to plain html. No config or anything to maintain.
> You'd only get plain unstyled rendering with browser support
What I imagined is browsers rendering the content with headings, quotes, etc. Browsers could have some default styles to render MD files. Those styles could be configurable the same way “Reading mode” is usually configurable.
The plain unstyled rendering of strings of text is, of course, available even now. That's why I'm saying this needs a browser-level support.
> you only need a very simple script to convert md to plain html
I get, that it feels simple compared to other software. Even more, MD was designed specifically to be simple!
But if you think about it, this is still too much complexity to just share some text.
With native browser support, you could run zero commands to build a website.
I think this is mostly important for regular users, not developers. Imagine if creating a Word document would require the same level of complexity as building a web page: I doubt that the format would be so popular as it is nowadays.
reply