Hacker Newsnew | past | comments | ask | show | jobs | submit | tmm1's commentslogin

atuin.sh


I'm an atuin user and if this feature exists, I have not seen it and would love to have it. Could you expand on how to get per-directory history as something separate from global shell history?



Thank you! Now that I know what the feature is even called it's much easier to learn about, definitely adding this to my config file.


Hit CTRL + r (by default) in the atuin menu to toggle the filter mode. Super useful.

https://docs.atuin.sh/configuration/config/#filter_mode


So the --headless=new doesn't work on any released version of Chrome yet?


What was used to author/render these docs?


Check out Channels DVR


Thanks for sharing this! I tried it and indeed it works quite well.

This will be much simpler/easier than gfortran+dragonegg, and removes some roadblocks preventing me from using the latest emscripten/llvm.


You can switch to text boxes via the gear at the top right.


In 2014, the Policy Simulation Library [1] added a model called Tax-Simulator [2], which is a Python reimplementation of TAXSIM [3][4]. It is available as open-source [5], and designed to let researchers both change existing policy variables and implement new tax reforms in Python.

[1] https://pslmodels.org/

[2] https://taxcalc.pslmodels.org/

[3] https://taxcalc.pslmodels.org/about/history.html

[4] https://github.com/PSLmodels/Tax-Calculator/blob/master/taxc...

[5] https://github.com/PSLmodels/Tax-Calculator


My team at PolicyEngine [1] is also now further reimplementing Tax-Calculator in the Python-based OpenFisca framework [2]. OpenFisca US [3] includes all tax logic in Tax-Calculator, plus many means-tested benefit programs like SNAP, and some state tax logic (currently only Massachusetts is complete, though we'll finish the country in the next 12-18 months). You can try it in our PolicyEngine US web app [4].

(OpenFisca US is part of the Policy Simulation Library, and it's developed by a number of former Tax-Calculator developers, myself included.)

[1] https://policyengine.org

[2] https://openfisca.org

[3] https://github.com/policyengine/openfisca-us

[4] https://policyengine.org/us


France has an open source implementation of their tax code [0]. The paper [1] gives an overview of the implementation language, mlang.

[0] https://github.com/MLanguage/mlang [1] https://arxiv.org/abs/2011.07966


France has also developed the OpenFisca framework [1] for tax and benefit rules as code, and its OpenFisca France [2] model is widely used (I think significantly more than mlang). We've extended it to the UK [3] and the US [4].

[1] https://openfisca.org

[2] https://github.com/openfisca/openfisca-france

[3] https://github.com/policyengine/openfisca-uk

[4] https://github.com/policyengine/openfisca-us


`policy_current_law.json` is really interesting:

https://github.com/PSLmodels/Tax-Calculator/blob/master/taxc...

Looks like the data in there goes back to 2013/2014. I'd love to see older historical policy data.


From the abstract of NBER paper I mentioned [1]:

> Each year Americans spend over two billion hours and $30 billion preparing individual tax returns, and these filing costs are regressive. To lower and redistribute the filing burden, some commentators have proposed having the IRS pre-populate tax returns for individuals. We evaluate this hypothetical policy using a large, nationally representative sample of returns filed for the tax year 2019. Our baseline results indicate that between 62 and 73 million returns (41 to 48 percent of all returns) could be accurately pre-populated using only current-year information returns and the prior-year return. Accuracy rates decline with income and are higher for taxpayers who have fewer dependents or are unmarried. We also examine 2019 non-filers, finding that pre- populated returns tentatively indicate $9.0 billion in refunds due to 12 million (22 percent) of them.

[1] https://www.nber.org/system/files/working_papers/w30008/w300...


One problem is that information is not tabulated by the IRS in time for a mid-April return date.

Order your tax “transcript of account” in late March and again in late August. It’ll be substantially more complete in late August.



Holy moley, that's a lot of extra code... any bets on if it might contain new vulnerabilities? :)


Hahaha, giving you an upvote because new vulnerabilities have, in fact, been found. (And I think one of them relates to this new code not being sufficient? Though I'm not following much anymore.)


git clone --local will hardlink the existing git objects from the first checkout so no extra space is required.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: