by mining bitcoin of course!

Doesn't work quite the same way in reverse though. "Every energy corporation deserves to be paid for their pillaging of the earths resources." Failure to pay for said pillaging has slightly different results.

There's a continuous reload loop on Android Chrome.

Thanks a lot for the feedbacks, Have been heads-down here and now its loading without any glitch. WIP on making it responsive across screens and improving ML models to understand natural language queries. Much appreciated!

Man who "paid himself nearly $2 million a day in 2022" says google pay their staff too much ...

I read the article and don't see where he says that. I do see that he thinks Google has too many staff, but not that the payment level is too high.

And frankly, if the son of a mechanic can get to the point of earning $2m/day, that's an indication that he has some amount of clue.

> “management should also take the opportunity to address excessive employee compensation.”

He has a clue how he should be paid more, yes.

Google is worth as much as it is because it can afford the best engineers. If it can't, they'll go elsewhere and it won't be worth that much. Obviously they should all be replaced with offshore contractors.

I saw a quote from him a few weeks ago where he did say they were overpaid.

Forjeyo, or rather For-Jay-(Y)o, I believe.

To my ear (native English speaker) it sounds like: for j o

Try doing this on a 5 year old project. You'll very likely end up in dependency hell.

There is a solution though - use of nvm and .nvmrc (to control the version of node and npm that you use), and use of npm ci (which installs packages as they were at the time, rather than installing newer versions than specified in package-lock.json (because too many devs rarely ever pin versions) instead of npm install / npm i).

nvm (Node Version manager): https://github.com/nvm-sh/nvm npm ci: https://docs.npmjs.com/cli/v6/commands/npm-ci

I rarely if ever get version mismatches for a normal npm install because upgrades by default only do minors. If a package has a breaking change in a minor it's not a JS issue, it's not a npm issue, it's a "this package author made a breaking change in a minor" issue.

And regarding nvm: That's obvious. This is the same for almost any runtime. If you have the wrong jdk version it doesn't work, if you have the wrong (whatever iOS uses for xcode) version it doesn't work, if you have the wrong version of gcc it doesn't work.

Obviously wrong is not always the same, more up-to-date versions of gcc can compile older programs (maybe) but that's also the same for Node unless otherwise specified in the packages.

"Buys out" and "owns" apparently now mean the same as "rent for a small period of time" ...

It’s common to say buying ad space. You have probably regularly heard an advertiser “buying a full page”. No one’s ever “bought” the whole thing, so the confusing language of saying “buy” in this context never came up before.

It's the physical bits of page space in reader's hands, in this case. The usage is pretty common for print ads.

Almost the entire AI / ML landscape is still stuck on the pretense of: "lets feed it a trillion pieces of data, correct the most obvious defects, and call it a day", which leads to some terrific results, but mostly really poor and low quality results. It is fast becoming the buzzfeed of software. Generated images are full of obvious glitches. Chats with AI are full of logical mistakes and very weird changes of topic. Generated text is a lot of the time borderline unreadable. What exactly is the end goal here? Release early, release often, release all hopes of being taken seriously?