Reminds me of the year 2038 problem, which will be more scary than this.
So if you are storing epoch time (no of milli seconds after 1970) in integer variables, your code will most probably break, which I feel is going to happen in a lot of scenarios.
Google also used to have a go app which they deprecated later on, while now i think about it what is the use of having a go app, if the websites which are shown in search results are not optimised for slower networks.
I had the same doubt. With CLIs you can make your own custom shortcuts, LLMs can use it to get things done for you as well. With TUIs I think either these are hobby projects or meant for people who are obsessed with speed.
Though speed impacts are also something which I am uncertain about. Comparing Vim with IDEs, for sure there will be few things which are faster in vim but decent no of things which can be done faster in an IDE as well, so can't comment on your overall speed gains.
Amazon used to be really customer centric 5-10 years ago, I remember once I ordered a physical book which was late in delivery and I urgently needed that book, so they gave me a free kindle edition till the book got delivered.
Last week I had a vendor tell me that they did warranty service through Amazon, and I should contact Amazon for a replacement, even though I was outside of their return window. It turned out to be a lie. But Amazon refunded me the full amount anyway, without prompting. The handful of times I've contacted Amazon tech support this has been my experience. The previous one was when they replaced a $250 porch pirated delivery, no questions asked.
This behavior genuinely earns them more of my business.
The "danger" of their policies (and I've benefitted from them, too) is that they obviously can be gamed, and they obviously have to have defenses against that - which means if you cross some invisible line (and now likely AI-monitored) you're doomed; no recourse.
or get requests with query params already handles this in majority of the cases, unless the query size is too big (which ideally should not be the case since in the end it is a get request)
This theory seems to be BS, If let us say a founder is raising a seed round of 2m at 20m valuation, then according to hypothetical accrual tax rate, they would need to pay a tax of ~ 3-4m.
There's no such thing as a correct result to a search query. It certainly delivered exactly what was asked for, a grep of the web, sorted by number of incoming links.
They also don't use it at all anymore, they barely even care about your search query.
Google is successful, however, because they innovated once, and got enough money together as a result to buy Doubleclick. Combining their one innovation with the ad company they bought enabled them to buy other companies.
So if you are storing epoch time (no of milli seconds after 1970) in integer variables, your code will most probably break, which I feel is going to happen in a lot of scenarios.
reply