Bookmarks

Learn where NaN came from in JavaScript and why it cannot be compared

In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.

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...

The easiest way to use LLMs

Micro benchmark comparing DSPy and BAML for structured outputs - prrao87/structured-outputs

The framework for programming—rather than prompting—language models.

Kimi CLI is your next CLI agent. Contribute to MoonshotAI/kimi-cli development by creating an account on GitHub.

Brokk brings code intelligence to AI

Key information and FAQs about using credits

One year from now, with the release of Chrome 154 in October 2026, we will change the default settings of Chrome to enable “Always Use Secu...

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...

Go 1.25 includes a new experimental garbage collector, Green Tea.

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.

PostgreSQL support native boolean data type and Oracle started supporting boolean from 23ai. HexaRocket handles this mapping automatically.

Fully distributed PostgreSQL

pg_textsearch brings BM25 ranking to enable hybrid search to Postgres. Build RAG systems with keyword precision and vector semantics in one 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

Why you should just use Postgres instead of Kafka for small-scale message queuing and pub-sub patterns. Benchmarks and practical tests included.

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.

A real-world Rails 8 upgrade story about evolving an existing app, preserving its value, and moving forward without starting over.

Rails Pulse is a comprehensive performance monitoring and debugging gem that provides real-time insights into your Rails application's health. - railspulse/rails_pulse

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.

A more helpful way to view differences between complex data structures in RSpec. - splitwise/super_diff

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.