mc4ndr3

C levels can't survive a day in the trenches.

CEO goes to submit timesheet.

Corporate issued hardware explodes in face.

IT support hotline: Remember to turn the timer off and on again.

Middle manager: I need the task done yesterday. Yes, I know it's a holiday. Yes, I know the assignment breaks two DNS specs and several hundred federal and state regulations. Just get it done. No, you're not allowed to use utensils during working lunches, that's against company policy.

Exactly the wrong sorts of people will take this to mean we should remove access to important resources for anyone struggling.

The last paragraph seems to present a reasonable suggestion. But Hansson forgets that struggle occurs on a spectrum. There is no single, visible, hard line between normies and certifiables.

He should probably read a book or five about neurodiversity.

Anyone can cut costs.

It takes a pioneer to increase revenue.

See so mamy products like this.

If the product genuinely worked, it would make a natural candidate to upstream into the operating system. Better to wait for the feature to arrive there. Than to risk scams and bugs meanwhile.

`crit` loops over `cross` target triples for Rust projects, generating binaries for dozens of platforms. Now your users can enjoy more ways to install your apps.

See also `factorio`, for Go projects.

Imagine if everyone actually did this. Then we would have a myriad of base images hiding even more malware than we do currently.

Not to mention vertically integrating the entire Docker layer set defeats the whole point of using Docker in the first place.

That's a fair point, and when someone with a working brain mentions the fallout throughout the Internet that would result, I expect Docker Inc. will reverse course and embark on a PR campaign pretending it was all a mere tawdry joke.

I am confused by the meaning of Docker's announcement. They keep saying "organizations" will have Docker images deleted. Does that include personal FOSS images or not? Because the vast majority of Docker Hub images are uploaded by individual contributors, not "organizations."

Too bad about their poor relationship with the FOSS community. I've applied to them for years, and actually merged some minor patches to Docker to help resolve a go dependency fiasco. Zero offers.

I guess the next logical move is to republish any and all non-enterprise Docker images to a more flexible host like the GitHub registry.

You can go beyond Kubernetes into serverless, but other than those two, your tech department would be deviating from industry standards and paddling upstream by hand.

100x faster: Don't sort.

We need to go back to the days when satellites just blinked and everybody panicked about the end of civilization, when men were men and Bugs Bunny was a transvestite and you could smoke over the operating table.

My Mazda 3 also "smart" brakes for no bloody reason.

WSL + nodenv.

Or get a Mac and use nodenv.

bruh his entire dream is to remote manage a martian colony wth

People don't make jokes anymore. They make references. "That reminds me of..." Yeah, yeah very cool, you're using metaphorical reasoning like an early ape.

"It's like when..." Probably not, but the comfort one derives from a pretense of continuous thought must keep the blood pressure down.

Having employees is a big potential liability. Having a corporation is a big potential liability. Drinking water is a big potential liability. I guess just don't do anything at all and then recalculate your risk metric.

Rust isn't hard. Programming is hard. Rust just points out failure states before you encounter them in production.

That reminds me, time to sell off USD for Bitcoin.

What model of station? Do you have to PTT out WiFi layer 2 packets by hand? Is the attacking station using a wired Ethernet connection?

For the love of.... the compiler doesn't need a stupid initialism. Just say "the compiler". There is nothing memorable or disambiguating or intuitive or efficient about initialisms.

Treat IPv6 as an extension of IPv4, not a separate network space.

Deprecate software that doesn't support IPv6.

Stop DHCP servers from providing IPv4 by default.

Then we can enjoy a world with mass 6 adoption, almost no hosts bound to 4 addresses, and billions of available 4 addresses.

Sounds like the customer specifically planned to migrate from BMC to IBM.

Your deposit is insured. But sure, participate in panic.

We've had at least one recession every decade. Why on earth would that cycle stop now?

It's cheaper than buying the game. No buyer's remorse. Saves time compared with playing the game yourself. More informative than a game trailer. Watch celebrities (both A list and B list) play your favorite games. Learn tips and terminology from other gamers. Feel vicarious success from someone breaking a world speedrun record. You can do other activities while they play the game for you. No hassle with installation or compatibility or awkward controls. No need to invest in dedicated gaming hardware. You can skip ahead to the good parts.

Companies don't understand technology. They understand buzzwords.

There's a checkbox to put the legacy system in the cloud, with no requirement that the system's design adjust to account for modern design principles, scalability, or cost.

CEO: Just put it in the cloud now!

A coworker once called this absurdity, "lift and shift".

The FBI took ten years to find Osama, after 9/11 had already completed. Except according to Zero Dark Thirty, wasn't it the CIA? The balls on these goons. The FBI should be reminded of their horrendous origin story: Taking down non-white political dissidents.

I'm not saying the astronomer did or didn't deserve it. I'm saying you don't get to the position of questioning citizens by not having a big dick for a mythical impression of big government.

How does nsroot compare with chroot, CGROUPS, and Docker?

As a man, I can tell you assertiveness is not rewarded if you're not C level. Shut up, take the check, and help me lay out this red tape is the norm. Doesn't matter that we're not designing for scalability or testability or predictability or basic successful operation. Being a "team player" is seen as more important than customer value.

The article does not clarify how one pronounces Turkeiyueiuriwurouuuuuu