Directives and the Platform Boundary | TanStack Blog
A Quiet Trend in the JavaScript Ecosystem For years, JavaScript has had exactly one meaningful directive, "use strict". It is standardized, enforced by runtimes, and behaves the same in every environm...
fix: fallback to Maintenance LTS if no Active LTS found by MattIPv4 · Pull Request #8251 · nodejs/nodejs.org
Description
There is no Active LTS release currently, just Current + Maintenance LTS releases, causing the main download page to render no content as it cannot find an Active LTS release. This upda...
PostgreSQL 18's UUIDv7: Faster and Secure Time-Ordered IDs
PostgreSQL 18 dropped last month with a bunch of exciting updates. While the performance improvements are always welcome, there's one developer-friendly feature that deserves the spotlight: native support for UUIDv7. This new format might change how model your database.
At the PGConf.dev 2025 Global Developer Conference, Bohan Zhang from OpenAI shared OpenAI’s best practices with PostgreSQL, offering a glimpse into the database usage of one of the most prominen
Speaker here — Bohan from OpenAI. Our application has hundreds of endpoints, whi... | Hacker News
Speaker here — Bohan from OpenAI.
Our application has hundreds of endpoints, which makes sharding non-trivial. We've already offloaded shardable workloads—particularly write-heavy ones—from PostgreSQL. What remains is primarily read-only and would require substantial effort to shard. Currently, the workload scales well on Azure Database for PostgreSQL, and we have sufficient headroom to support future growth.
That said, we're not ruling out sharding in the future—it’s just not a near-term priority.
Speaker here — Bohan from OpenAI.
Our application has hundreds of endpoints, which makes sharding non-trivial. We've already offloaded shardable workloads—particularly write-heavy ones—from PostgreSQL. What remains is primarily read-only and would require substantial effort to shard. Currently, the workload scales well on Azure Database for PostgreSQL, and we have sufficient headroom to support future growth.
That said, we're not ruling out sharding in the future—it’s just not a near-term priority.
Like many others, as a company, we are going through a steep learning exercise with coding agents. As we are all learning together how to face the challenges of this new era of coding, I wanted to share our learnings with you and, in turn, benefit from what you have learned in your journey with using coding agents.
railspulse/rails_pulse: Rails Pulse is a comprehensive performance monitoring and debugging gem that provides real-time insights into your Rails application's health.
Rails Pulse is a comprehensive performance monitoring and debugging gem that provides real-time insights into your Rails application's health. - railspulse/rails_pulse
Announcing llm-docs-builder: An Open Source Tool for Making Documentation AI-Friendly
llm-docs-builder transforms Markdown documentation for AI systems, reducing token usage by 85-95%. Open source tool with llms.txt generation and Docker support.
On September 9, without warning, Ruby Central kicked out the maintainers who have cared for Bundler and RubyGems for over a decade. Ruby Central made these changes against the established project policies, while ignoring all objections from the maintainers’ team. At the time, Ruby Central claimed these changes were “temporary". However,
None of the “temporary” changes made by Ruby Central have been undone, more than six weeks later. Ruby Central still has not communicated with the removed maintainers about restoring any permissions. Ruby Central still has not offered “operator agreements” or “contributor agreements” to any of the removed maintainers. The Ruby Together merger agreement plainly states that it is the maintainers who will decide what is best for their projects, not Ruby Central. Last week, Matz stepped in to assume control of RubyGems and Bundler himself. His announcement states that the Ruby core team will assume control and responsibility for the primary RubyGems and Bundler GitHub repository. Ruby Central did not communicate with any removed maintainers before transferring control of the rubygems/rubygems GitHub repo to the Ruby core team. On October 24th, Shan publicly confirmed she does not believe the maintainers need to be told why they were removed. While we know that Ruby Central had no right to act the way they did, it is nevertheless clear to us that the Ruby community will be better off if the codebase, maintenance, and legal rights to RubyGems and Bundler are all together in the same place.
If you are a Rubyist, you’ve likely been writing # frozen_string_literal: true at the top of most of your Ruby source code files, or at the very least, that you’ve seen it in some other projects.