The intention of OrioleDB is not to compete with Postgres, but to make Postgres better. We believe the right long-term home for OrioleDB is inside Postgres itself. Our north star is to upstream what’s necessary so that OrioleDB can eventually be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres.

This seems like a good pattern, but of lower value for a SaaS app with many customers storing private data in your service. This is because the cache hit-rate for any particular company's data would be low. Is this an accurate assessment, or did I misunderstand something?

Comments URL: https://news.ycombinator.com/item?id=42240888

Points: 3

# Comments: 0

There are legitimate reasons for this, e.g. imagine an employee at a company that uses Office365 needing to set up an account for Google Adwords.

TOPS (Trillion Operations Per Second) is a meaningless score without including the precision. Are they INT4, INT8, INT16 or FP16? Microsoft's qualifications for a Copilot+ laptop require 40 TOPS at INT8: https://www.theregister.com/2024/05/21/qualcomm_windows_micr.... The new Snapdragon X Elite can do 45 TOPS at INT8.

Apple's M3 has 18 TOPS, and their M4 has 38 TOPS, but the M3 was measured at INT16 and the M4 at INT8: https://www.anandtech.com/show/21387/apple-announces-m4-soc-.... Cutting the precision in half lets you do ~twice the amount of work.

The Snapdragon is very impressive, but it's silly to see TOPS claims from companies repeated by journalists without adding some context.

Exposure to RCS from engineered stone causes silicosis typified by a faster onset and more rapid progression than that caused by RCS [Respirable crystalline silica] from other sources, including natural stone.

When engineered stone is processed, the dust generated contains higher levels of RCS, and that RCS has different physical and chemical properties that likely contribute to the more rapid and severe disease. There is also evidence to suggest that other components of engineered stone may contribute to the toxic effects of engineered stone dust, either alone or by exacerbating the effects of RCS.

...

The increased risks posed by RCS from engineered stone, increased rate of silicosis diagnosis amongst engineered stone workers, and the faster and more severe disease progression amongst this group, combined with a multi-faceted failure of this industry to comply with the model WHS laws means that continued work with engineered stone poses an unacceptable risk to workers. The use of all engineered stone should be prohibited.

https://www.safeworkaustralia.gov.au/sites/default/files/202...

> A total of 12 successful prosecutions have been reported since 2021, with many related to the uncontrolled processing (dry cutting) of engineered stone materials

https://www.safeworkaustralia.gov.au/sites/default/files/202...

AWS docs are the opposite. They are often very long and verbose, but once you read the whole manual, you can be guaranteed to have a good understanding of the service.

My advice for the Google team would be that if you are ever writing documentation and ask yourself “does the customer really need to know about this?”, the answer should always be yes.

You can version the Terraform configuration, either in a public Git repository or in a Cloud Storage bucket. Use Object Versioning to version configurations in a storage bucket.

https://cloud.google.com/infrastructure-manager/docs/overvie...