Learn Physics with Functional Programming (Scott N. Walck)（Z-Library）

【One-Line Pitch】 Learn physics by coding it in Haskell, where the type system checks your math as you model Newtonian mechanics and electromagnetism—perfect for programmers, physics students, or anyone who wants to see theory come alive through functional programming. 【Book Arc】 - **Opening (~0%–6%)**: Introduces Haskell basics—functions, operators, and the application operator—as the foundation for expressing physics, solving the problem of translating math into code. - **Early (~6%–19%)**: Covers lists, lambda functions, and higher-order functions, building the tools to handle sequences and approximations, like infinite series for exponentials, which are key for numerical methods. - **Early (~19%–28%)**: Delves into types, type classes, and equality checking, emphasizing why floating-point comparisons are dangerous in computational physics—a critical mindset for reliable simulations. - **Middle (~28%–44%)**: Moves into vector and tuple design, exploring how to represent physical quantities (like 3D vectors) with types, and introduces graphing with gnuplot for visualizing data. - **Middle (~44%–47%)**: Shifts to animation and simulation using Gloss, showing how to model dynamic systems like moving disks, then transitions to Newton’s laws and differential equations for real physics problems. - **Late (~47%+)**: Focuses on Newton’s second law, the Euler method, and force-dependent motion, applying all prior skills to solve one-dimensional and multi-dimensional mechanics problems. 【Key Takeaways】 - **Haskell’s type system is a physics checker** (Early): By encoding vectors and forces as types, you catch conceptual errors before running code—like ensuring a vector has exactly three components, not a list of arbitrary length. - **Lambda functions simplify physics expressions** (Early): Writing functions like `\x -> x**3` lets you define mathematical rules inline, making higher-order functions (e.g., integration) cleaner and more readable. - **Lists are powerful for numerical approximations** (Early): Infinite lists of successive approximations, like for `exp(x)`, let you explore convergence and accuracy, teaching you how to balance precision with computation. - **Avoid equality checks on floating-point numbers** (Early): Testing `Double` values with `==` is unreliable due to bit representation (e.g., `sqrt 5 ^ 2` ≠ 5); this is a universal lesson for computational physics, not just Haskell. - **Choose the right data structure for vectors** (Middle): A list is too loose (allows wrong lengths), a tuple is better but ambiguous, while a custom data type ensures type safety—showing how design choices impact correctness. - **Simulation requires a clear state model** (Middle): Using Gloss’s `simulate` function, you define an initial state, a display function, and an update function, making it easy to animate physical scenarios like a moving disk. - **Newton’s first law is about velocity, not force history** (Late): An object maintains constant velocity without forces, which is elegantly expressed in code by setting net force to zero—clarifying a common misconception. - **The Euler method bridges theory and computation** (Late): By integrating force functions over time steps, you solve differential equations numerically, enabling you to model complex motions like air resistance. 【Reading Tips】 - **Skim the Haskell syntax refreshers** (Early chapters) if you’re already a programmer; focus instead on how each construct (e.g., `$`, lambdas) is applied to physics problems. - **Deep-read the vector and type design sections** (Middle) because they’re pivotal—understanding why a custom `Vec` type beats a list or tuple will save you debugging headaches later. - **Practice the exercises on infinite lists and series** (Early) to build intuition for numerical methods; they’re short but crucial for grasping convergence and approximation. - **Don’t skip the floating-point equality warnings** (Early)—they’re a trap in any language, and internalizing this will make your simulations more robust. - **Use the animation and simulation chapters** (Middle) as a hands-on project; building a simple model (like the red disk) will cement the state-update pattern you’ll reuse for physics problems. 【Coverage Limits】 This guide covers the book’s progression through Haskell fundamentals, vector design, and Newtonian mechanics, but the excerpts do not cover the later electromagnetic theory sections (e.g., Coulomb’s law, Maxwell equations) or advanced numerical methods like FDTD.