Hjfrf

Considering the history of mysql_escape_string it's an important argument

Covering index is right.

Select * has a few valid use cases.

If you're selecting from a cte or subquery then writing the same column list twice is redundant and increases complexity/risk of mistakes.

* is also harmless for count and exists.

We can always hope that trading Chia is made illegal, along with proof of work algorithm based currencies in general.

Governments so-far failing to regulate existential threats to themselves is honestly odd.

With an exchange, you can have a centralised database of how much is in each person's account.

So for internal transfers, you can just update the good old relational database and dodge the fees.

For transfers between exchanges, they can settle the net balance daily (or have some thresholds etc) to minimise any actual on-ledger transfers.

Of course all this makes the decentralized aspect of the currency pointless, but most people don't actually understand or care.

The default options for shadow-IT are VBA and Powershell, since you don't need to ask permission or install anything to make a mvp.

I guess there will be many Powershell users in future for that reason alone.

Despite all that, people mostly trade crypto on centralized exchanges.

The users really hate the decentralized aspect of crypto, as shown by immediately giving away their wallet to some "trusted" third party if it reduces fees.

Hopefully

It's an exciting idea that as phones get more powerful, plugging the phone into a monitor could replace the desktop entirely for many home users.

Yes all databases will use indexes for joins. There's quite a few mistakes like that.

My guess is the author heard something about not using implicit inner joins (deprecated decades ago) and misunderstood.

E.g. This old syntax- SELECT * FROM a, b WHERE a.id = b. a_id

Does that still look ok if you're selecting 10+ columns with functions, or would you split out the first line situationally?

LIKE 'abc%' will use indexes but LIKE '%abc' will not.

At least for the latest versions of every database. If you go back to a version from 10+ years ago there's no guarantees.

Lots of mistakes (or at least rare opinions going against the crowd) here.

Here's a better general performance tuning handbook - https://use-the-index-luke.com/

Nobody steals just one backpack.

By prosecuting one person, you could prevent thousands of future stolen bags.

Google did it with an allied op recently. Not NSA, but as close as we're likely to hear about. https://www.technologyreview.com/2021/03/26/1021318/google-s...

Excel's spill functions are in that space.

If you're just going to use off-chain centralised exchanges with a relational database backend anyway, what's the point of bitcoin?

You could do the same with dollars.

I can sell Jack's tweet right now.

That's a bigger issue than Jack being able to sell it multiple times.

If you can just find a young person and a rich person, you'll be sorted.

Reads like an advert

How can you not mention Google using education to build a moat around their monopoly?

It's more like buying a receipt, not the good itself.

They can display the receipt but have no more right to the art than you or me.

Power query for Excel. It trivialized data transformation for admin/operations users, who would have spent 50x the time on a VBA solution or (more likely) not bothered.

Forest is a clear exagerration, but this article goes over numbers.

A few weeks of ordinary household energy usage per NFT is realistic.

https://www.loop-news.com/p/the-big-problem-with-nfts-energy

The only bits people actually know are yyyy-mm-dd and pre-92 implicit joins.

Why is this a complaint at Firefox, and not at Google for abusing their monopoly to create new features on a whim regardless of what it does to other browsers?

They choose to offer refunds but also to bury the unsubscribe button behind 5+ screens with misleading text and reminders of what you'll "lose".

Rather than good customer service, Amazon try to be generous on the visible aspects that people might talk about, but quietly cheat you with antipatterns.

Your first question is fairly common too- select * is to be avoided if your table can change or you care about order of columns.

Select * is better from cte/temp table because you then only need to make changes in one place.

I'm not sure how much deeper it's possible to go.

Facebook messages are emails, I believe.

At least an email to the user's @Facebook email address gets picked up in messenger.

That might not have helped in this case, if the email was sent from the same account.

The hacker had access to messages from the sender side without access to the account being reset.

No need in the case of PH. It's already full of illegal content and getting caught would sabotage KYC regulations for years.

Elon knows exactly why -

https://mobile.twitter.com/elonmusk/status/12562398152567971...