401 karma · joined February 22, 2014
Or just "I'm done with this shit". It's remarkably difficult to run a small (software) business in the US. Section 174, multi-state income tax filings. It's a bloody pain if your goal is not just to operate the business and be overhead, but to actually do stuff. Regulatory/tax complexity thresholds depending on business size would be a welcome improvement.
Setting up a business in Europe (for example in the Netherlands) requires significant paperwork. In the US, it's done in a few seconds. In the US, it requires years of court proceedings or (in this case) government agency investigation to shut down a business. (No idea how long that takes in Europe, but I hope your governments are more powerful than this.)
Regulation can be a good thing.
No. The terminology is confusing. Section 174, specifically point 3, classifies software development as R&E as of 2022 and requires amortization over 5-15 years. This prevents software engineering salaries as a standard business tax deduction. This has nothing to do with the R&D tax credit (section 41).
I had that exact same experience. Some of them even messaged me encouraging me to please cancel for them so that they would not incur a penalty. (I refused.)
I've been using yellow cabs in cities again. Simple & straightforward.
That's words vs. actions. His words were that he was going to take care of them, and his voters believed him. The fact that he didn't do it is just like any politician lying. They might not even have believed him either, but at least his voters felt like he listened to their pains.
Opensource/free software powers most of the stuff we take for granted. The software and their maintainers are equally taken-for-granted.
See e.g. https://www.investopedia.com/terms/m/medical-cost-ratio.asp
The worst thing is that people take it as acceptable that this loop is going to operate differently upon overflow (e.g. assume N is TYPE_MAX) depending on whether i or N are signed vs. unsigned.
for (int i = 0; i < 64; i++) result[i] = inputA[i] * inputB[i];
If inputA[i] * inputB[i] overflowed, why are my credit card details at risk? The question is: can we come up with an alternate behaviour that incorporates both advantages of the i<=N optimization, as well as leave my credit card details safe if the multiplication in the inner loop overflowed? Is there a middle road?
https://code.videolan.org/videolan/dav1d/graphs/master/chart...
Feel free to come on IRC, happy to help you dive into this, it's not very difficult.