crest

<rant>

So go and put them in the ground next to their disgusting traitor ancestors. The abolitionists should've made sure to break the southern slaver class any would miss them for good.

Any reasonable person knows it's wrong to deny an other human their humanity to enrich themselves. They should've retroactively made owning slaves as well as helping someone else keep slaves a crime punishable by a quick death and redistribution of all their worldly possessions among those they enslaved.

The descendants of the slavers still lust for twisted reimagined memory of former stolen wealth and power to this day. We can see it was a mistake to show them mercy. Let those southern trees carry strange white fruits!

</rant>

If you had explicitly been told there is no embargo on these bugs then making noise is the right thing. So what should you have done differently?

The orphan crushing machine is a meme (https://knowyourmeme.com/memes/orphan-crushing-machine). Most of Meta's products hurt society from driving impressionable young girls into an early grave, over supporting genocide and ethnic cleansing, to splitting voters into rabid fans with blind devotion on "their team" over everything else.

They also work hard to force users into their walled gardens and to stop the useful content users to this day feed into they intentionally broken services from escaping into the real world wide web of hyperlinked and discoverable content.

In short they're at the forefront of making the internet harmful to society and less useful to almost everyone.

Also it has a glorious viewing gallery to watch and listen to a thousand doomed orphans get fed to Zuckerberg’s ego so it can illuminate the path to total enshittification.

The battery only has to last 5 to 10 minutes for this to be useful, because adding a second battery to drop just before picking up the wounded wouldn't be hard so loiter time wouldn't be much of an issue if they go down that route. Also multi-copters become more efficient flying in a reasonably straight line compared to high-g manoeuvrers or hovering in place.

If the alternative is certain death the answer it remains simple: do you have the drone to and can you afford to send it? -> give it a try.

It becomes a whole lot more complicated if you have other options and have to implement triage.

Slowly dying in no man's land vs. a chance to make it out alive makes it a fairly tempting risk to take. I can totally understand the Ukrainians trying such stunts with their wounded when the alternative wouldn't be a medivac chopper, but watching them perish in agony through the spotter drones. Even if was a 50/50 chance to crash and or be intercepted I don't think many wounded soldiers would hesitate at a chance to fly to an aide station or even proper surgical care in minutes instead of hours, days, or more likely never. Acute pain and the expectation to die otherwise shift the risk tolerance completely.

I wonder if someone will step up and implement modern OpenGL versions on top of Metal (iirc something like this already exists for OpenGL ES).

Is someone late on their bribes?

Than you modelled it incorrectly or n is small. A large lookup table is not O(1) in the real world as anyone who compares the access time of a register file, an L1 cache, and HBM3 (or DDR5) memory would realise. Even in a world of spherical cows in a vacuum lookup latency increases at least linearly with the radius of spherical volume the signal has to pass through.

Msps = Mega samples per second

Now if you could also make it transmit such samples a few of those could make a nice DIY phase array for some of the most fun bands to play with.

Having to optimise for three very different microarchitectures with the G3 (short narrow pipeline, no AltiVec, small caches), G4 (short wide pipeline, focus on in-order AltiVec, useful OoO otherwise, large L2 yet memory bandwidth starved), and G5 (long and wide pipeline, focus on super-scalar OoO, AltiVec just glued on, more memory bandwidth) must have been "fun".

How many variants of the codecs did you have to implement to make it work?

Sometimes a bit of wood, rope, and a sturdy blade will help.

"You've reached your quota. Please hold your credit card or mobile phone on the card reader within the next 10 seconds or you'll be liable for the resulting crash."

Best of luck getting a good deal for new hardware right now from anyone right now. All hardware pricing negotiations these days start with give us your company credit card, drop your pants and bend over the table.

Does any other architecture allow split cacheline atomic operations across sockets?

"Nuke the entire site from orbit ... it's the only way to be sure."

They also fucked up their parity RAID repair so that the next disk failure on a different disk will destroy the data, argued that the pathological B-tree performance reported by a user couldn't be real, because they didn't understood the tree depth would only be logarithmic to the base of the fanout if the entries are the same size. insert shocked pikachu face

No reasonable person has ever argued that a consumer buying a (digital) copy of a game obtains the exclusive rights to the game. This is such a cheap embarrassingly stupid attempt to come up with a straw man.

I'll listen to Sony management and lawyers whining about copyright after they paid the damages and fines and get out of jail for every rootkit they deployed. Should be any century now.

A CDN *cache* server is a special case. Netflix cache appliances can accept the risk of running FreeBSD -CURRENT and upgrading half their fleet to the latest snapshot every ~2 weeks and we thank them for battle testing FreeBSD's active development branch in production. It really helps to reveal regressions (both correctness and performance) early in the subsystems and drivers that matter to their usecase.

Most users will neither be willing nor able to accept the trade-offs that Netflix chose.

If you run the latest (laptop) hardware you may still have to track stable or backport some patches from -CURRENT.

You're just wrong. FreeBSD stable branches are the development branches from which new minor releases (with a stable ABI) are forked. If you want to be pedantic you want to follow the releng branches for most production deployments (release + security and non-security errata patches). Unless you build from source yourself you the tools (pkgbase, freebsd-update) don't make that distinction visible to the user.

The ARM v7M architecture helps a lot here because the NVIC supports priority inheritance without disabling interrupts. Yes you have to assign your priorities correctly and yield CPU time for anything compute bound, but again the architecture helps you in the form of the SVCall+PendSV exception pair. The PendSV handler can easily be multiplexed on the Cortex-M3/M4 using atomic operations on bit-banded memory. I've needed only a few dozen lines of Forth to set this up on bare metal without an RTOS to split peripheral drivers in a short interrupt handler saving the required state and delegating protocol handling to a lower priority callback.

A 1GHz superscalar Cortex-M7 can still hit a 12 cycle interrupt latency if the system stack is kept in the 2x32 bit wide zero cycle dTCM, and the VTOR and handler are in the iTCM thanks to lots of bandwidth and a reasonably short pipeline. The NVIC is truly the underappreciated superpower of the Cortex-M family. You can implement a full RTOS or complex bare metal application without ever having to disable interrupts. On other MCU architectures (most RISC-V, PIC32, even older crap refusing to die) you'll easily end up with closer to 100 then 10 cycles of jitter from critical sections having to run with disabled interrupts e.g. context switching code.

Really an attacker controlled system() call?!?

One advantage they have for building larger systems is that they allow you to crack stores into two parts. The part that has to retire in order for the local CPU and the write back to memory. Now assume you have multiple banks of memory and one of them stalls. A system with TSO can't allow the other banks to make progress because that would make the stores visible to other CPUs (or peripherals) out of program order. So you have to stall stores to otherwise ready memory banks and hold on to valuable ROB and store queue resources for longer.

It must be a snow day in hell.

Should we also ask the Saudis what drawings to punish by beheading or the Taliban which writings to punish by stoning?

They're also too stupid to understand that they've been dropping UDP datagrams with src port == dst port and < 1024. This obviously breaks IPsec IKE. I showed them dummy traffic captured with netcat and tcpdump, but they refused to admit they caused the problem. They repeatedly claimed to see nothing dropped between the pcap files, that I was doing it to myself with a firewall that wasn't even enabled, or that this is just how a network is supposed to work.