gazpacho (u/gazpacho)

gazpacho commented on Nest 1st gen and 2nd gen thermostats no longer supported from 10/25/2025 community.hubitat.com/t/n... · Posted by u/RyanShook

h2zizzle · 3 hours ago

Recent extreme frustration with Google products in mind, I'm tempted to read the crux of this post as, "Google engineers/designers are incompetent." It might be unfair, but on a day when Google Search, Youtube History Search, and (whaddya know) my Nest Thermostat have all failed me, the temptation is strong.

gazpacho · 3 hours ago

I think the reality is that the engineers are competent but this was just not a priority they were given and they were not going to spend nights making this happen instead of hanging out with their kids.

gazpacho commented on What Are Traces and Spans in OpenTelemetry? oneuptime.com/blog/post/2... · Posted by u/ndhandala

psnehanshu · 6 days ago

The amount of additional code that it needs is horrible. We will now have to spend more brain juice on telemetry when working on a feature.

gazpacho · 6 days ago

I work for Pydantic. We make Logfire, a commercial OTEL backend. But we’ve made wrappers around the OTEL SDKs in various languages that simplify configuration and usage. They can be used with any OTEL compatible backend (although we’d love if you try our SaaS offering): - JavaScript / Typescript: https://github.com/pydantic/logfire-js - Rust: https://github.com/pydantic/logfire-rust - Python: https://github.com/pydantic/logfire

gazpacho commented on Building your own CLI coding agent with Pydantic-AI martinfowler.com/articles... · Posted by u/vinhnx

dcreater · 7 days ago

thanks for clarifying. I guess my comment was more directed to the fact that pydantic, the company is 1) VC backed 2) Unclear how/when/what you will monetize 3) how that will affect the open source stuff.

I strongly believe you guys should be compensated very well for what you bring to the ecosystem but the probability of open source projects being enshittified by private interests is non-trivially high.

gazpacho · 6 days ago

I work at Pydantic and while the future is obviously unpredictable I can vow for all of us in that we do not intend to ever start charging for any of our open source things. We’ve made a very clear delineation between what is free (pydantic, pydantic-ai, the logfire SDK, etc) and what is a paid product (the Logfire SaaS platform). Everything open source is liberally licensed such that no matter the fate of the company it can be forked. Even the logfire SDK, the thing most integrated to our commercial offering, speaks OTLP and hence you can point it at any other provider, basically no lock in.

gazpacho commented on AI capex is so big that it's affecting economic statistics paulkedrosky.com/honey-ai... · Posted by u/throw0101c

gazpacho · 2 months ago

I just wish we forced every new data center to be built with renewables or something. The marginal cost over a conventional data center can’t be that big compared to the total cost, and these companies can afford it. Maybe it can help advance the next generation of small modular nuclear reactors or something.

gazpacho commented on Embedding user-defined indexes in Apache Parquet datafusion.apache.org/blo... · Posted by u/jasim

SiempreViernes · 2 months ago

So, can we take that as a "no"?

gazpacho · 2 months ago

There is no spec. Personally I hope that the existing indexes (bloom filters, zone maps) get re-designed to fit into a paradigm where parquet itself has more first class support for multiple levels of indexes embedded in the file and conventions for how those common types. That is, start with Wild West and define specs as needed

gazpacho commented on Cloudflare Introduces Default Blocking of A.I. Data Scrapers nytimes.com/2025/07/01/te... · Posted by u/stephendause

gazpacho · 2 months ago

From an open source projects perspective we’d want to disable this on our docs sites. We actually want those to be very discoverable by LLMs, during training or online usage.

gazpacho commented on Show HN: Tritium – The Legal IDE in Rust tritium.legal/preview... · Posted by u/piker

gazpacho · 3 months ago

I like the idea! I wish I could use git / PRs to do rounds of edits on legal documents instead of whatever Word’s track changes is.

Speaking of, could we start using version control for keeping track of laws and updating old laws? It seems to me like a much better system than randomly burying in a new law that it strikes out some text from an old law.

gazpacho commented on Jemalloc Postmortem jasone.github.io/2025/06/... · Posted by u/jasone

Svetlitski · 3 months ago

I understand the decision to archive the upstream repo; as of when I left Meta, we (i.e. the Jemalloc team) weren’t really in a great place to respond to all the random GitHub issues people would file (my favorite was the time someone filed an issue because our test suite didn’t pass on Itanium lol). Still, it makes me sad to see. Jemalloc is still IMO the best-performing general-purpose malloc implementation that’s easily usable; TCMalloc is great, but is an absolute nightmare to use if you’re not using bazel (this has become slightly less true now that bazel 7.4.0 added cc_static_library so at least you can somewhat easily export a static library, but broadly speaking the point still stands).

I’ve been meaning to ask Qi if he’d be open to cutting a final 6.0 release on the repo before re-archiving.

At the same time it’d be nice to modernize the default settings for the final release. Disabling the (somewhat confusingly backwardly-named) “cache oblivious” setting by default so that the 16 KiB size-class isn’t bloated to 20 KiB would be a major improvement. This isn’t to disparage your (i.e. Jason’s) original choice here; IIRC when I last talked to Qi and David about this they made the point that at the time you chose this default, typical TLB associativity was much lower than it is now. On a similar note, increasing the default “page size” from 4 KiB to something larger (probably 16 KiB), which would correspondingly increase the large size-class cutoff (i.e. the point at which the allocator switches from placing multiple allocations onto a slab, to backing individual allocations with their own extent directly) from 16 KiB up to 64 KiB would be pretty impactful. One of the last things I looked at before leaving Meta was making this change internally for major services, as it was worth a several percent CPU improvement (at the cost of a minor increase in RAM usage due to increased fragmentation). There’s a few other things I’d tweak (e.g. switching the default setting of metadata_thp from “disabled” to “auto”, changing the extent-sizing for slabs from using the nearest exact multiple of the page size that fits the size-class to instead allowing ~1% guaranteed wasted space in exchange for reducing fragmentation), but the aforementioned settings are the biggest ones.

gazpacho · 3 months ago

I would love to see these changes - or even some sort of blog post or extended documentation explaining rational. As is the docs are somewhat barren. I feel that there’s a lot of knowledge that folks like you have right now from all of the work that was done internally at Meta that would be best shared now before it is lost.

gazpacho commented on US vs. Google amicus curiae brief of Y Combinator in support of plaintiffs [pdf] storage.courtlistener.com... · Posted by u/dave1629

0xbadcafebee · 4 months ago

I'm not sure people understand what the consequences of taking away Google's ad revenue is. If a large enough bank goes under, it takes out not just the bank, but huge sectors of the economy, affecting many more businesses and jobs. That's why the government bailed out the banks when they failed.

The same will happen when Google loses its ad revenue. Google is an ad company. By opening up all its trade secret data, it loses its advantage. That will make it lose its core revenue. The end result will be Google collapsing entirely within a few years. Then those component parts people are talking about "opening up" will be gone too.

Here's a small number of things that will die when Google dies. Can you imagine how the world will be affected when these go away?

  - Google Maps
  - Google Mail
  - Google Drive
  - Google Docs
  - Google Groups
  - Google Forms
  - Google Cloud
  - Google OAuth
  - Google Search
  - Google Analytics
  - Chrome
  - Android
  - Android Auto
  - Fitbit
  - Google Fi
  - Google Fiber
  - Google Flights
  - Google Translate
  - Google Pay
  - Waymo

In the best case, killing these will force consumers to move to Apple. You wanna talk monopoly? You haven't seen anything yet.

Apple has no alternative for much of the Business-focused products, so that will take considerable time for companies to adopt alternatives. But in the meantime, the world will become pretty broken for a lot of companies that depend on these tools. This will affect many more people than just Google's direct users. The whole web will shrink, and huge swaths of the worldwide economy will disappear. Businesses closing, lost jobs, shrinking economies, lack of services.

There are plenty of parties who want to see Google lose or take part of its businesses. But if it's not done extremely carefully, there's a very large stack of dominoes that are poised to fall.

gazpacho · 4 months ago

I agree. At risk of being totally off base because I have not been keeping up with the details of the legal matter it seems to me that the solution isn't to kill Google's core business but rather to force it to sell off some of these branches, with thought and strategy. E.g. one of the comments below pointed out that Google Flights competes with other sites / businesses. Seems like a good candidate to spin off: it could probably be a profitable business in it's own right. Android? Chrome? Idk about those: who / how are they going to be funded? Each piece needs to be analyzed and a deal needs to be struck that's not based on principles as much as it is on what is pragmatically the right balance that benefits people (the American people in particular) the most in the medium to long term.

gazpacho commented on AI as Normal Technology knightcolumbia.org/conten... · Posted by u/randomwalker

gazpacho · 5 months ago

I liked this article. My hot take lately has been that AI is like Excel / Word but deployed quicker. That can still cause some level of societal collapse if it displaces a large fraction of the workforce before it can retool and adapt , no AGI super intelligence required.