Dev Weekly #123 covers a broad set of tech releases and articles. Highlights include Node.js 26.6.0 and 26.7.0 with performance and crypto improvements, Next.js 16.3 with 90% dev server memory reduction and 22% SSR throughput gains, and Karafka 2.6 with Kafka Queues groundwork and dynamic worker scaling. On the Ruby side: RuboCop 1.89 adds project-wide analysis via rubydex, Ruby Native v0.12 brings Android out of beta for Rails mobile developers, and a deep dive covers Ruby Hash memory optimization across versions. Also featured: JetBrains releasing an LSP extension to bring IntelliJ IDEA's Java/Kotlin intelligence to VS Code and Cursor, a discussion on applying DDD bounded contexts to Rails apps, and a tool called MyJourney that auto-generates narrated product demo videos.
Questions this post answers
What performance improvements does Next.js 16.3 include?
Next.js 16.3 reduces dev server memory usage by 90%, speeds up builds with disk caching, and improves SSR throughput by 22% under load. It also introduces Instant Navigations, an opt-in feature set that makes server-rendered apps feel as responsive as SPAs, plus root params, glob imports, and custom error boundaries. Teams shipping Next.js upgrades track breaking changes and performance wins like these on daily.dev.
What is new in Node.js 26.7.0?
Node.js 26.7.0 adds Perfetto support for performance profiling, private key loading through STORE loaders, Symbol.dispose in ModuleHooks, and expanded test runner coverage options. It also includes stability improvements across crypto, HTTP/2, and FFI, plus updated dependencies for npm, V8, and native libraries. Developers maintaining Node.js services watch release notes like these on daily.dev before rolling out upgrades.
What does RuboCop 1.89 add with rubydex integration?
RuboCop 1.89 introduces optional integration with rubydex for project-wide analysis, enabling cops to resolve cross-file references. This allows detection of issues previously invisible to single-file analysis, such as constant typos, duplicate methods, and dead code, while also reducing false positives. Ruby teams evaluating static analysis tooling follow ecosystem updates like this on daily.dev.