We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Hacker News·Jun 30·5 min read
Parse, Don't Validate – In a Language That Doesn't Want You To
TL;DR
TypeScript developers often rely on validation instead of parsing, leading to loss of information. Parsing provides a more precise type and retains context, enhancing code reliability.
✦ Why It Matters
Engineers can enhance TypeScript code quality by prioritizing parsing over validation for better type safety.
Key Takeaways
- Shift focus from validation checks to parsing for better type safety.
- Use parsers to retain information and improve code reliability.
- Explore functional programming languages for better parsing practices.
- Refactor existing validation-heavy code to utilize parsing techniques.
Full Summary
Many TypeScript codebases accumulate validation checks that merely confirm data validity without enhancing type safety. In contrast, parsing transforms data into specific types, such as converting a string into an EmailAddress, which retains valuable information for future use.
This principle, articulated by Alexis King, emphasizes that parsers provide more than just validation; they enrich the type system. While languages like Haskell and Elm encourage this practice, TypeScript does not enforce it, leading to a reliance on validation.
The structural typing in TypeScript can further complicate this issue, making it easier to overlook the benefits of parsing. By shifting focus from validation to parsing, developers can create more robust and maintainable code.