Java Proposes Built-In Simple JSON API via JEP 540 Incubator Stage

·2 views

OpenJDK has introduced JEP 540, a proposal to add a native Simple JSON API to the Java platform. The feature is currently in the incubator stage, meaning it is available for early testing but not yet finalized. The initiative aims to provide Java developers with a straightforward, built-in way to handle JSON without relying on third-party libraries. The proposal is publicly documented on the official OpenJDK website for community review and feedback.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer solves AI hallucination in bank statement tool with balance validation

A developer building StatementDecoder, an AI-powered bank statement converter, found that the hardest challenge was not parsing statements but detecting when the AI output was wrong. Early versions using LLMs to extract structured JSON worked well on sample files but failed on real-world statements from banks like Wise and Revolut, which had unexpected formats and quirks. The developer discovered that prompting improvements and model changes did not solve the core problem of using the same AI to both generate and verify its own answers. The breakthrough came from implementing an independent mathematical validation layer that checks whether opening balances, transactions, and closing balances reconcile — a check that applies regardless of how the data was extracted. This approach meant the system could flag or repair errors before users exported data, shifting the design philosophy toward verifiable AI output rather than perfect AI output.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Brazilian bank deploys AI agent in VS Code to enforce infrastructure policy at scale

An engineer at Latin America's largest bank built an AI-powered system to automatically audit technical debt and enforce infrastructure policies across thousands of daily deployments. The core problem was that well-written internal guidelines were routinely ignored during fast-paced sprints, simply because developers had no time to consult documentation. The solution uses an MCP (Model Context Protocol) server to give Claude, running inside GitHub Copilot in VS Code, real-time access to policy documents, databases, and APIs. Instead of requiring developers to seek out rules, the system delivers relevant guardrails directly inside the code editor at the moment a decision is being made. The setup is now used daily by thousands of developers and routes queries through a layered AWS infrastructure including Route 53, Network Firewall, API Gateway, and Lambda.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Dev Tutorial: How to Build a Multi-Skill Playwright Test Automation Pack

A developer tutorial series on automating Playwright with Claude Code has released Part 6, focusing on expanding a single test skill into an organized multi-skill pack. The guide builds on earlier installments by growing the 'playwright-form-tester' skill into three distinct tools: a locator policy enforcer, a page object generator, and a flaky-test debugger. Each skill is designed with a single responsibility so it triggers only on relevant requests, avoiding unnecessary token usage. The pack shares a common references folder to prevent duplicating conventions across multiple skill files. The approach is positioned as a practical replacement for team onboarding documentation, automatically providing new teammates with established testing conventions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

s3fifo v1.0.0 Brings Production-Ready Zero-Allocation Cache for Node.js

Developer has released s3fifo v1.0.0, a production-ready caching library for Node.js built on the S3-FIFO algorithm, which uses pre-allocated TypedArrays to eliminate garbage collection overhead. The library organizes cache entries into three queues — Small, Main, and Ghost — to prevent cache pollution from one-time-access items while retaining frequently used data. Version 1.0.0 introduces cold-start persistence via dump and load methods, allowing cache state to survive container restarts and prevent database stampede scenarios. New developer features include a dispose callback for resource cleanup on eviction, a side-effect-free peek() method for monitoring, and full JavaScript iteration protocol support. The release follows extensive stress testing and achieves 100% unit test coverage, making it suitable for high-throughput Node.js microservices.

0 comments Read more at DEV Community