The best Hacker News stories from All from the past day
Latest posts:
Humans can't endure temperatures and humidities as high as previously thought
Compound pejoratives on Reddit
Forebruary is a wall calendar that you do not need to replace every year (2013)
The Nettle Magic Project: Scanner for decks of cards with bar codes on edges
Show HN: Calculator for US individual income tax, from 1970-present
I wanted to share a simple web app I created recently, which lets you estimate income taxes owed in the US: <a href="https://taxsim.app" rel="nofollow">https://taxsim.app</a><p>All the calculations occur directly in the browser, and are powered by a Fortran program that has been converted to WASM using emscripten. This calculator was originally developed in the 1970s [1] by the non-profit National Bureau of Economic Research. NBER has been maintaining this F77 codebase for the last 50 years, and uses it primarily for academic research on tax policy. The Fortran source code itself is over 1MB of text, because it codifies both federal and all 50 states' tax laws for each of the last 62 years.<p>I first learned about NBER TAXSIM [2] a few months ago via an interesting paper they published "Automatic Tax Filing: Simulating a Pre-Populated Form 1040" [3]. The Fortran code itself is not open-source, but is available on request for research purposes. I reached out to NBER and proposed compiling it to WASM, so it could be run directly in a browser. With relatively little effort I was able to create a js/wasm version [4], thanks in huge part to previous open-source work [5].<p>This WASM build now powers <a href="https://taxsim.app" rel="nofollow">https://taxsim.app</a>, which is my attempt to create an interactive UI to allow for easier exploration of the US tax code. Specific tax scenarios can also be shared easily, by simply copying the browser URL. The code for this webapp is also open-source [6].<p>This was my first time experimenting with WASM, and I am already a huge fan. Not only was I able to take a 60 year old codebase and get it working on every modern browser and device, this work is also now benefiting the academic community. For example, the js/wasm can be run directly in V8, which means it can also now be run locally within R using libv8 [7]. Previously most researchers were uploading their tax scenarios to NBER's servers via ftp/ssh/http.<p>[1] <a href="https://taxsim.nber.org/feenberg-coutts.pdf" rel="nofollow">https://taxsim.nber.org/feenberg-coutts.pdf</a><p>[2] <a href="https://taxsim.nber.org/" rel="nofollow">https://taxsim.nber.org/</a><p>[3] <a href="https://www.nber.org/papers/w30008" rel="nofollow">https://www.nber.org/papers/w30008</a><p>[4] <a href="https://github.com/tmm1/taxsim.js" rel="nofollow">https://github.com/tmm1/taxsim.js</a><p>[5] <a href="https://chrz.de/2020/04/21/fortran-in-the-browser/" rel="nofollow">https://chrz.de/2020/04/21/fortran-in-the-browser/</a><p>[6] <a href="https://github.com/tmm1/taxsim.app" rel="nofollow">https://github.com/tmm1/taxsim.app</a><p>[7] <a href="https://github.com/shanejorr/usincometaxes/pull/11" rel="nofollow">https://github.com/shanejorr/usincometaxes/pull/11</a>
Show HN: Calculator for US individual income tax, from 1970-present
I wanted to share a simple web app I created recently, which lets you estimate income taxes owed in the US: <a href="https://taxsim.app" rel="nofollow">https://taxsim.app</a><p>All the calculations occur directly in the browser, and are powered by a Fortran program that has been converted to WASM using emscripten. This calculator was originally developed in the 1970s [1] by the non-profit National Bureau of Economic Research. NBER has been maintaining this F77 codebase for the last 50 years, and uses it primarily for academic research on tax policy. The Fortran source code itself is over 1MB of text, because it codifies both federal and all 50 states' tax laws for each of the last 62 years.<p>I first learned about NBER TAXSIM [2] a few months ago via an interesting paper they published "Automatic Tax Filing: Simulating a Pre-Populated Form 1040" [3]. The Fortran code itself is not open-source, but is available on request for research purposes. I reached out to NBER and proposed compiling it to WASM, so it could be run directly in a browser. With relatively little effort I was able to create a js/wasm version [4], thanks in huge part to previous open-source work [5].<p>This WASM build now powers <a href="https://taxsim.app" rel="nofollow">https://taxsim.app</a>, which is my attempt to create an interactive UI to allow for easier exploration of the US tax code. Specific tax scenarios can also be shared easily, by simply copying the browser URL. The code for this webapp is also open-source [6].<p>This was my first time experimenting with WASM, and I am already a huge fan. Not only was I able to take a 60 year old codebase and get it working on every modern browser and device, this work is also now benefiting the academic community. For example, the js/wasm can be run directly in V8, which means it can also now be run locally within R using libv8 [7]. Previously most researchers were uploading their tax scenarios to NBER's servers via ftp/ssh/http.<p>[1] <a href="https://taxsim.nber.org/feenberg-coutts.pdf" rel="nofollow">https://taxsim.nber.org/feenberg-coutts.pdf</a><p>[2] <a href="https://taxsim.nber.org/" rel="nofollow">https://taxsim.nber.org/</a><p>[3] <a href="https://www.nber.org/papers/w30008" rel="nofollow">https://www.nber.org/papers/w30008</a><p>[4] <a href="https://github.com/tmm1/taxsim.js" rel="nofollow">https://github.com/tmm1/taxsim.js</a><p>[5] <a href="https://chrz.de/2020/04/21/fortran-in-the-browser/" rel="nofollow">https://chrz.de/2020/04/21/fortran-in-the-browser/</a><p>[6] <a href="https://github.com/tmm1/taxsim.app" rel="nofollow">https://github.com/tmm1/taxsim.app</a><p>[7] <a href="https://github.com/shanejorr/usincometaxes/pull/11" rel="nofollow">https://github.com/shanejorr/usincometaxes/pull/11</a>
TikTok updated privacy policy to collect faceprints and voiceprints (2021)
FCC commissioner wants TikTok removed from app stores over spying concerns
Thunderbird 102
The PocketReform is a made-in-Berlin Linux handheld
Some Assembly Required: An approachable introduction to assembly
Some Assembly Required: An approachable introduction to assembly
Fresh is a new full stack web framework for Deno
Why hasn't Middle Earth had an Industrial Revolution?
Job interview questions engineers should ask, but don't
Detecting unauthorized physical access with beans, lentils and colored rice (2021)
Show HN: I stripped DALL·E Mini to its bare essentials and converted it to Torch
Mastercard and visa are the de facto regulators of porn
Amazon is intimidating and harassing organizing workers in Montreal
Ask HN: What tone to use in code review suggestions?
When writing suggestions in code reviews I have used all of these forms:<p>* Should we extract this to a separate function?<p>* Could you extract this to a separate function?<p>* I would extract this to a separate function.<p>* This could be extracted to a separate function.<p>* This should be extracted to a separate function.<p>* Extract this to a separate function.<p>As you can see, these have very different tones and I would like to be more consistent and as constructive as possible. Is there some general best practice for this? Are you or your team using a set of rules or guidelines?