https://www.wired.com/story/doge-direct-file-chopping-block/
Although the Brazilian tax authority does develop software to file personal income tax, and provides it free of charge, that software is currently not open source.
Depends on how the law is written.
You could get the official instance of an open source app certified but that takes a lot of time and money.
https://www.irs.gov/e-file-providers/become-an-authorized-e-...
It would be quite simple for employers to submit work schedules to the tax office, have employees check them, have the tax office send an invoice to the employer and have the tax office pay the salaries.
Have the employer report sick leave and request overtime at the tax office so that they can get fined.
The subsubcontractor system is full of fraudulent billing but if they have to report something to the tax office all the "mistakes" magically disappear.
Seems based on your income.
This is by design. Intuit spends loads of money to lobby politicians here and keep tax code complicated so they can stay in business. The US in general has a “let the private sector manage these things” mentality but our politicians don’t know how to create actual checks on these industries. Or they don’t care. Or they’re invested financially. Something something conflict of interest.
Seems more like people are complaining for the sake of complaining.
The accountants who are paid to keep up with these things and are most knowledgeable usually only deal with one or a few states. What incentive does any accountant have to lend their expertise to an open source project and help maintain it?
Also, you wouldn't have to make a solution for more than one state if you don't want to.
If I understand correctly, the IRS isn't hindering anybody from making a free or open source solution. So people who complain could either get on it, or use the options at hand.
I would love to never pay a commercial company ever again. I just no longer get excited when I see an open source project get started for it, because they never come out with the full solution.
The full solution needs to come from the government or some fully funded open source project with a team of accountants and devs.
I live in the Netherlands and the Dutch IRS provides everything I need to do my yearly taxes. Hell they fill in a whole lot of numbers automatically based on what they know about my salary from my employer. Before I owned my own home my yearly taxes took literally five minutes to fill in because of that. Just double checked some pre-filled numbers and done.
At one point, the government tried to force them into providing free tax filing for folks with simple taxes… they used every dark art / black hat tactic to trick customers into paying for even the simple free option.
But also, the right in the US is fundamentally anti-government (or at least government capacity). They want a return to the federal government of the 19th century, much much smaller.
One strategy they employ is to make people dislike the government. That means reducing its capacity (ala DOGE) so people have a poor experience dealing with it. And making tax compliance unnecessary difficult.
Enabling brash, high IQ individuals with incomplete/flawed data leads to the most catastrophic outcomes.
For example: Tesla wants Cybercab to go nationwide. For national safety purposes, Cybercab is self-certified (which is actually normal), but self-certified is constrained by NHTSA, who watches over what is happening and has the ability to halt what's happening if they don't think the manufacturer is following the rules.
Guess which part of NHTSA DOGE cut first?
They laid off a significant part of the NHTSA team with expertise in analyzing and regulating self-driving vehicles.
So while NHTSA has the legal authority to regulate the national push to allow Cybercabs on the road, many of the NHTSA personnel with the expertise to exercise that authority are gone.
Clever, clever.
In Brazil, this software has been made available for free by the Government for at least 25 years. I say this because that's around when I started using it. It was like that for a lot longer. Versions for Linux, Mac and Windows.
What's different now is that they've open sourced it. Great move, and I highly support it! That said, it makes no difference in terms of cost to use the software.
You can just dump the code into a public repo with minimal build instructions and let people figure it out. Costs you absolutely nothing unless you decide to write your own license and forget to put in the liability waiver. And its infinitely better than keeping it closed.
What I'm about to fantasize about is a "bucket list coding project" type thing, but I'd be happy to take a look at the famous IRS tax base mainframe code though. I'm a mainframe systems programmer and we hear stories about the "master file" and oodles of assembly code, which is right up my alley.
Could be transformed to C or C++ today for easier maintainability, but my guess is that they are maybe running without LE runtime services? So maybe that's why it's a challenge to upgrade? Still, it's possible, if you manually initialize libc with an assembler macro and setup your own prelude/epilogue for initialization, comedown, abort cleanups, register passing conventions, and put assembly thunks for all the places you are needing 24-bit memory etc or accessing certain parts of OS common state...
For those not in the know, on z/OS, LE (short for language environment, they didn't call it libc even though that's basically what it is because a lot of other mainframe compilers use it too and the dominance of C at the time on the platform was far from assumed for systems code, but is now probably the case) is basically "libc" (and specifically, here I'll be talking about the crt0 part). Without it you need to make your own allocators, handle all your own register save areas, etc. Back in the day when the IRS first computerized tax, the concept of a system wide "libc" you would link with didn't really exist. Every language had its own runtime library, and a lot of shops still wrote everything like it was a bare metal program using "OS" linkage which is a euphemism for basically linking the way the OS code does, not really "userspace" linkage like modern LE enabled XPLINK (much closer to the ABI and calling convention on a platform like x86_64 Linux, and much more efficient too in terms of padding arguments in registers) is.
Nowadays, you want to make sure the C runtime initializes first so it can clean up your messes (like, stuff that the runtime allocates during an uncontrolled failure), even if you are programming in assembly, and if not, at least you need recovery routines to jump to. Not always possible if you are accessing certain types of OS control blocks or low storage or addressing physically (running in DAT off part of the "nucleus" aka kernel), but still, would love to see the famous file.
And yes, the moment I saw who DOGE was bringing to the IRS to deal with this issue and that it was some hipster web dev groupie, I knew it was gonna flop. Probably ran away in terror when they saw what it was REALLY like programming in the 60s and the 70s as far as perf consciousness went. And that it always universally meant assembly (in a very historic and long lived, but also very CISC-y, ISA, although I suppose it was less CISC-y at the time) because compilers weren't great at optimizing yet.
Anyway, from my position of expertise, that's always been the one governmental piece of code that I thought would be on my bucket list. Who knows, I'll probably end up seeing it one day anyway if I continue consulting. Lots of consultants at the IRS needed to keep that same logic churning....but with more people who knows what you could do...if all the systems software engineers in the US were contributing you could probably get it into C or C++ using a modern version of either of those languages (the latest compiler is I think clang 22 on the platform, possibly even clang 23 for those who compiled themselves or are on a beta branch, so far from an ancient C compiler that doesn't support modern C/C++ standards, and far from the ones back in the days when the IRS code was being written that couldn't optimize well enough to fit in the much more limited memory and CPU budgets of the time.)
Such a task would be a Herculean effort ideally suited for an open source scenario, because you probably NEED every single person in the country that happens to know mainframe assembly and C or C++ if you want it to end up being a success. Especially in the assembly area, there really aren't that many of us, and we are spread out across all the big companies all over the country and can't coordinate a project like that so long as it's closed source.
Where are all of those hackers when you need them? Too bad this the tapes (punch cards? lol) containing that software aren't leaked.
Describe. What is anyone forced to use.
I do not know where are you from and what could be a relatable example for you, but I have seen it in different countries.
Ordinar people needing a tax advisor instead of having a simple way of filing on their own is more the kind of tax being referred to up-comment.
a) why pay foreign service providers x% of all card based transactions. It's not the whole merchant discount because a lot of that goes to the issuing bank, but it's still significant.
b) if the user/merchant costs are low enough, it displaces cash and helps to formalize the economy which means more accurate economic reporting and less tax evasion.
c) maybe you can provide payment services or software to smaller countries for a while
Yep, one day this year I bought fruits on the supermarket with nfc pix and later the same day I bought an electric car with pix. It's like living in the future with no fees being transferred to the USA.
Otherwise, if tax forms are translations of underlying laws, then how do you know the forms are themselves correct? It's the exact same problem that you're positing about whether code matches law.
Since the whole point of tax forms is to perform a calculation - and preferably perform it correctly and deterministically - it's much better to leave that task to a computer than to a human.
To give a concrete example of how tax forms could benefit from code, take the 2025 Canadian federal personal income tax form (T1), and I'll comment on some features. https://www.canada.ca/content/dam/cra-arc/formspubs/pbg/5006...
> Employment income (box 14 of all T4 slips)
This references another data structure (T4 slip) and asks you to sum all of them (implied by the word "all"). But it's ambiguous because in some programming contexts, "all" means returning a list of numbers or items.
> Elected split-pension amount (complete Form T1032)
This basically asks you to jump into a subroutine, do some calculations, and return the result here.
> Amount of dividends (eligible and other than eligible)
This is a filter operation followed by a sum.
> if negative, enter "0"
In math notation, this is x = max(y, 0).
> Use the amount from line 26000 to complete the appropriate column below.
This repeats something a few lines down and is only useful for clarifying for humans.
> Line 70 minus line 71 (cannot be negative)
This is a sanity check like assert(x >= 0).
> Enter whichever is less: $1,471 or line 1 plus line 2.
There are actually two line numbering systems happening simultaneously, one on the left of the money box and one on the right.
> Amount from line 42000
Some instructions merely copy numbers from other sections in order to get the data more local to the current problem being handled. Computers don't care about locality in this sense.
Open source and publish as a npm, NuGet etc. package.
Maybe then they will catch up with tyrannical Russia where government provides all the necessary software for filing taxes for free (for over a quarter of century). Some of it (most of it?) is also duplicated as online services.
https://web.archive.org/web/20170906160619/http://oss4gov.or...