Or die and pass it to your children. Buy, borrow, die. Kill the step up basis loophole.
No it doesn't work that way. If you pass on the stock options, you pass on the tax burden.
Readit NewsYetAnotherNick commented on If AI replaces workers, should it also pay taxes? english.elpais.com/techno... · Posted by u/PaulHoule
YetAnotherNick commented on If AI replaces workers, should it also pay taxes? english.elpais.com/techno... · Posted by u/PaulHoule
> If you don’t receive income then it obviously shouldn’t be taxed
Right, but you're ignoring the loop-hole OP mentioned where you borrow un-taxed money then deduct it. Kill the loop holes.
There is no tax loophole. The only thing they are getting is higher leverage against borrowing, and the only difference would occur if that individual would go bankrupt in that the entity that they borrowed from wouldn't need to pay income tax.
So the only way to pay less tax is to surrender all your assets.
The “distributed monolith” line is the key takeaway here.
Microservices only buy you something if teams can deploy, version, and reason about them independently. Once shared libraries or coordinated deploys creep in, you’ve taken on all the operational cost with none of the autonomy benefits.
I’ve seen monoliths with clear module boundaries outperform microservice setups by an order of magnitude in developer throughput.
If microservice or monolith is giving order of magnitude improvement in productivity, you clearly are doing something wrong, or having terrible practices.
YetAnotherNick commented on Native ads coming soon to Stack Overflow and Stack Exchange meta.stackexchange.com/qu... · Posted by u/exploraz
Great, then let me buy a specific version as a single purchase.
Would you be fine if that version is affected by botnet in the future, or if the documentation is not updated for newer windows version unless you pay.
And would you be willing to pay $200 one time or $10/month(say assume the average subscription time for users is 2 years), so to recoup the amount they need to increase the cost a lot.
YetAnotherNick commented on Native ads coming soon to Stack Overflow and Stack Exchange meta.stackexchange.com/qu... · Posted by u/exploraz
Recurring payments are fine for services that have a recurring cost, which is often not the case.
Development cost is recurring cost.
YetAnotherNick commented on The Tor Project is switching to Rust itsfoss.com/news/tor-rust... · Posted by u/giuliomagnifico
If Rust helps with their pains and they like Rust this seems very sensible.
That's exactly why we have different languages and tools, because they adapt differently to different projects, teams and problems.
But as soon as you get into the silly "tool X is better period" arguments, then all the nuance of choosing the right tool for the job is lost.
What are the project specific nuance you are talking about? Anything in this and linked post could be applied to any performant application which values memory safety.
So unless they provide some Tor specific nuance, it's more or less applicable to wide range of applications.
YetAnotherNick commented on Native ads coming soon to Stack Overflow and Stack Exchange meta.stackexchange.com/qu... · Posted by u/exploraz
> Nobody asked for this.
Well... the advertisers did.
No they didn't. Most advertisers are running at negative ROI, but they just have to run ads as they can't risk other companies taking over. Biggest advertisers would be happy if the ads are banned. It's the new and small companies that would find it harder.
YetAnotherNick commented on Native ads coming soon to Stack Overflow and Stack Exchange meta.stackexchange.com/qu... · Posted by u/exploraz
However, ads are also the reason why many services on the Internet are free. So maybe they are not completely bad.
HN complains about any monetization strategy including recurring payments, yet complains if the company revenue is low. Almost all of the internet is paid by ads, users almost never pays. Company pays, but then the company is paying the money that they directly or indirectly earned through ads.
YetAnotherNick commented on Days since last GitHub incident github-incidents.pages.de... · Posted by u/AquiGorka
I found out when Actions started failing again for the Nth time this month.
The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.
Idk, if being bad is the reason for leaving Github Actions, I think people would have left it ages ago. It stuck not because it is better than competitors but because it is included in the Github plans. It's decaying implies that it has somehow became worse, in fact it was one of the worst implementation to start with.
YetAnotherNick commented on Deprecate like you mean it entropicthoughts.com/depr... · Posted by u/todsacerdoti
Instead randomly trigger kill self process. That's a safer way than random wrong returns.