1. I saw the same headline - the article stated that there were record SEASON sales, not Black Friday sales. The headline did not match the content of the article.
2. Record revenue, not necessarily record units sold. To be expected with inflation.
3. Savvy online shoppers may be bundling purchases to reduce shipping costs. Waiting for a seasonal sale to buy holiday gifts as well as detergent, snacks and underwear may be quite prudent.
Finally, increased sales revenue does not necessarily equate to more jobs. It can, but by no means does it have to.
Which is already happening. This is why stock buy-backs, IPO-less/private companies and private equity rule the future.
This "wealth" will NOT come from government subsidies or UBI. It will stay where it is, with enough income doled out to the masses to keep the supply/demand economy chugging along.
Isn't it just a matter of having each consumer use their own offset? I mean if the queue table is sequentially or time-indexed, the consumer just provides a smaller/earlier key to accomplish the offset?
(Maybe I'm missing something here?)
So, rather than Big Brother being government-imposed monitoring paid for by all taxpayers, the concerned citizenry is flipping the bill for the devices, network connectivity and electricity. Fascinating.
> (Technically speaking, if 100 people load the same page at the same time and the cache isn’t populated yet, then we’ll end up sending 100 queries to the database which isn’t amazing, but let’s just pretend we didn’t hear that.)
Isn't their tech to address that, like golang's "singleflight"?
Agreed. Isn't this precisely why key statistics (table statistics) are maintained in many DB systems? Essentially, always "push down" the predicate with the worst statistics and always execute (early) the predicates with high selectivity.
I'd be very surprised if virtually every RDBMS doesn't do this already.
I guess that. I have a paid account ($20/month flavor) and have the link saved. I just asked it to create an image of a landscape and it popped up this blocking request to use pyxl.pro
I managed to get rid of it (I was blocked by this) by clicking the "..." button in the input frame and choosing "Create image" which was prepended to my prompt.
No idea what happened there... I have a valid/paid account, no browser extensions... strange stuff.
Why is Social Security always represented as an expense along with things like defense and administration? It is sourced from separate taxes and has no business in the US govt. budget.
Apologies, but this strikes me as a rather silly question. What I would keep in the event of a prolonged network outage would be of minimal significance.
What I'd really be concerned about would be our modern society. Purchasing food, water, fuel, clothes and other necessities would be near impossible. Supply chains would not just have problems, but literally fall apart. Money would stop moving.
If anything is "too big to fail" it would be the internet.
How long before someone can buy a robot to do a manual labor job for them? I mean, buy a robot and send it to some company to do a daily job where the company pays the robot owner for the use of the robot?
* You know exactly what your app needs to do, up-front
But isn't this true of any database? Generally, adding a new index to a 50 million row table is a pain in most RDBs. As is adding a column, or in some cases, even deleting an index. These operations usually incur downtime, or some tricky table duplication with migration process that is rather compute + I/O intensive... and risky.