consider it like this: you are not paying the amount of worked hours but for the expertise to judge, coach and guide the AI and its output according to your wishes. so if the result is good and within time and budget, why would you care?
My house also doesnt generate cash flow/interest by itself, must have an intrinsic value of zero. Surprisingly it can be used as collateral for a loan as long as other people assign a (however disputable) value to it.
So, of course you could be right when all (not just you) other people decide that BTC has a value of zero. Meanwhile i use my BTCs as collateral.
Value is more of a social judgment, not a law of nature. Hence the misconception?
Houses do generate income, called "rent". Either you rent out your property and get paid an explicit rent, or you live in the house in which case you get
paid in kind. So, bad example!
Like bitcoin, gold is too a "bubble asset", but unlike bitcoin, gold is a physical object with use value and limited availability.
The thing about gold is that its price appears to to be negatively correlated with the economic cycle. Because of this some people argue that it makes sense to include it in a portfolio of stocks and bonds, so that the volatility of the portfolio is reduced, although personally I would advise against it.
for this requirement i choose to use encrypted sparse files (can be created with the disk manager app) which i store on the icloud. is only of use if you happen to have a laptop with you as mounting them is not supported in iOS
NSO is just a strawman for the government of Israel. Surveillance technology is a very successful soft power tool, as the dictators crave its capabilities to stay in power. Pegasus is world class technology, so Israel could score a lot of brownie points by allowing these sales. Too bad they got too greedy and sloppy and allowed the phones of some US officials in Africa to be infected. Coincidentally there was a leak of 50000 phone numbers and NSO goes boom. Israeli "security diplomacy" rebuilt NSO and is still going strong, surprised i am not :-(
In this case it's important to note though that this is a necessary side-effect of offering a powerful extension API.
If you – for example – install some badly coded extension that blocks the main thread to parse the open file into an uncached AST on every keystroke before rendering the input, that's the extensions fault.
Take my example with an ounce of saltt as I've never coded a VSCode extension. It is very well possible that the extension API prevents this particular example. I guess normally things like parsing source files have to follow guardrails that prevent this kind of bug, or at least discourage coding this way. And ASTs are exposed by VSCode's core for the natively supported languages.
Still, it's probably safe to assume that there is a lot of badly written code out there that does not pay attention to performance, or follows an "optimize-later" mindset.
Features surely often seem tempting to implement in a slow and unoptimized way, and anyone can contribute to VSCode extensions.
I think the comment you're replying to was blaming slowdowns on the size (in lines of code) of individual files, rather than the total size (in number of files) of the codebase.
