ta20210405

It's the same illogic as: "If you pay taxes, you support bombing children in Iraq. You support the status quo."

Work is for work, movie theaters are for watching movies. Should moviegoers stand up and make political statements during a movie? No, "movie theaters should just be for movie watching" and "work should just be for work."

It's the other way around:

Minorities have the privilege and luxury of politicizing EVERYTHING. Whites do not enjoy such privilege and luxury.

>because it doesn't affect them negatively like it does, say, minorities.

Source for this claim? One could say politics negatively affects white people more negatively than minorities because white people foot the bill more so than minorities.

Truly end of an era. Imagine the things that have come to life in the century that he was alive. Transistors, home air conditioning, laptops/PCs, jet engines...

GUIs are great, but not having a CLI is an anti-pattern. Also, having an API, but no reference CLI is an anti-pattern (depends on your API, but if your examples are poorly constructed bash scripts with cURL lines you need a proper CLI).

Facebook servers do not have cron installed.

This is incorrect. Rivian also uses 2170s.

It's insanely apt and spot on. I'm going to be using it from now on.

Cable is ALWAYS a better choice. Cable to each desk, connected to a docking station. Fast, stable, no nonsense.

>"if you like your doctor, you can keep your doctor."

Which was always a stupid line because it's not "your" doctor, it was never your doctor. It was your insurance's doctor. If you get a new job and "your" doctor isn't in the insurance network, they're no longer your doctor.

No, it's a high quality article. I agreed with the title, but after reading it decided to upvote. When I returned to read comments, it's flagged.

Somewhat of an end of an era. Worked at a shop that had one of the largest Mesos fleets in the world. Thousands of physical nodes, petabytes of data. True Mesos in production was something to witness.

Here is an article that covers performance between Linux and FreeBSD, and it leaves BSD in the dust: https://matteocroce.medium.com/linux-and-freebsd-networking-...

Also, it specifically outlined how more rules slow down of on FreeBSD, and how poor multicore support is on pf.

I wonder if Google will continue to move away from Java even after winning this ruling.

What will Java look like at Google in 2030?

>The key is “for each packet”, because it’s bucket based it will entirely skip evaluation for packets that do not match.

That is how it works in nftables.

>but I can see how it could be confusing if you’re used to iptables and only think in those terms.

Considering you're misunderstanding some basics about nftables and iptables here, I think you need to look in the mirror.

>I posted the architectural diagrams of both in another comment on this thread yesterday, I think you missed that.

I saw, and it only reenforced the fact that that's how nftables works. Hilariously enough, the OpenBSD webpage crashed and wouldn't load, giving various 500 and 42X errors.

>nftables (like iptables before it) is rule based and not bucket based.

What does this even mean? Do you have any documentation to explain?

>So high numbers of rules will not affect pf’s performance like it does with nftables.

This is wrong. From OpenBSD documentation:

"More lines being evaluated for each packet will result in slower performance."

[0]https://www.openbsd.org/faq/pf/perf.html

It's not 2001 any more. Nftables and Linux have left the BSDs in the dust.

Amateur hour at Ubiquiti. Sadly they leave us without a decent replacement. Mikrotik is the only contender and they leave a lot to be desired.