It's worth pointing out that plenty of pilots take off and land safely at uncontrolled airports. ATC is a throughput optimization; the finite amount of airspace can have more aircraft movements if the movements are centrally coordinated. It feels like we are nearing the breaking point of this optimization, however, and it's probably worth looking for something better (or saying no to scheduling more flights).
The FAA already does issue temporary ground stops for IFR flights when ATC capacity is saturated. This acts as a limit on airlines scheduling more flights, although the feedback loops are long and not always effective. The FAA NextGen system should improve this somewhat.
I think the choice of breed has meaning. The border collie is the smartest breed of dog, and its origin is in herding sheep. Calling your coworkers sheep isn't particularly nice. Calling yourself the smartest breed of dog isn't particularly humble. That's why the person you're replying to objects.
Ridiculous. We should be calling people out for being performatively offended. It reduces the impact and gravitas of situations where real offense is given that should be considered.
I have herded cats, sorted sheep, and wrangled cattle all throughout my career. I can come up with more that are quite accurate to the situation.
And I've been the cat, sheep, and cattle likely more than I have been on the other side.
It's simply part of working with groups of humans. We become dumb in groups and lend ourselves towards herd behavior. It often requires someone tending to us to break us of the habit.
That's probably reading too much into the metaphor. I think it's apropos because regardless of whether the others are smart or not, we all have blind sides, and in order to get things done that need to be done you have to apply pressure in the right way to overcome a certain amount of group inertia. Those things still fit with the metaphor without necessarily being disrespectful.
I still don't understand why people don't cheat in FPSes by looking at the video stream and having a USB mouse that emits the right mouse movements. (The simplest thing is to just click when someone's head is under your crosshair, in games with hitscan weapons.)
The problem with these bots is that they are indiscriminate which makes them vulnerable to active detection methods. They can also introduce an amount of latency that begins to defeat the purpose for sufficiently skilled players. 100ms is an eternity when you are playing with shotguns in close quarters.
I've been on a grand jury... the cops lied through their teeth, couldn't keep their stories straight through a prepared monologues reading from notes and ... everyone in the room picked up on it and didn't indict the suspects. Our grand jury was so cynical the DAs stopped giving us cases and made the other two grand juries stay late to make up for the lost capacity. It was great. We did something good. And it was just a bunch of random people from Brooklyn.
The establishment likes to pat the establishment on the back but ordinary people seem to know what's up. In my minimal experience, anyway.
(One thing to keep in mind... grand juries really are a cross-section of the population, whereas lawyers get to select jurors after talking to them, so there is some selection bias on ordinary juries that grand juries don't have.)
Back in 2000 I got the M1 Air with 8G of RAM (needed the cheapest Mac to test some arm64 stuff) and that laptop served me very well. I never felt RAM-limited. I was always expecting to run out of memory during a big Bazel build or something, but never did.
It isn't the most powerful computer in the world but I never ran into any problems... so it's probably an OK compromise for most people, especially in the world where RAM is scarce because of AI datacenter buildouts.
The M1 Air would have blown people’s minds in 2000. 128MB of RAM was luxurious at the time for a laptop. In 2003 I borrowed and bought several sticks for a presentation (senior thesis on 3D presentation software), and got to 1GB in my desktop and felt like I’d broken some law of physics.
Shortly after I had a TiBook (PowerBook G4) that was _only_ 1-inch thick! Compared to 1.75” Dells my coworkers had, it seemed like the future. DVD drive, modem, Ethernet, full sized DVI port, FireWire, WiFi, Bluetooth, optical audio in and out, gigantic display with a bezel that was unrivaled for years, even among Macs. What a beast!
(I know you meant 2020, but it’s fun to think about the air in 2000).
In the year 2000, a M1 MacBook Air would have been the world's fastest supercomputer (or second fastest if you had the base model with the 7-core GPU).
Impressive, of course; but not quite that impressive.
Only true if all you're running is matmul (supercomputer has general purpose CPUs so more flexible than M1 GPU) - also those flops are probably FP64 in supercomputer ratings and FP32 in M1.
As a smart man I knew used to say, supercomputers are about I/O not raw compute. Those have terabytes of RAM not 8GB.
Your question hits directly at latency vs. throughput distinction. Depends on which you mean by "fast."
Throughput-wise, the supercomputer is competitive because it has a lot of local RAM connected to lots of independent nodes, which, in aggregate, is comparable to modern laptop's RAM throughput (still much more than disk) with a caveat, that you can only leverage the supercomputer bandwidth if your workload is embarrassingly parallel running on all nodes[1]. Latency-wise, old RAM still beats NVMe by two or three orders of magnitude.
[1]: there's another advantage that supercomputer has which is lots more of local SRAM caches. If the workload is parallel and can benefit from cache locality, it blows away the modern microprocessor.
as someone who wasn't around for PowerPC mac times (I was alive but I didn't have internet and only knew apple for iPod and Apple II), did non artist people use FireWire for anything other than synchronizing their first generation iPods? Was it common to have a firewire external drive and were there any other devices that aren't cameras, film scanners or audio interfaces that utilized firewire?
There were FireWire HDDs too. Non-artist people also used FireWire for their DV camcorders for home videos. It wasn't really common because most PCs didn't have Firewire.
It was also used by the PS2 for local multiplayer between multiple consoles. Although Sony eventually removed that port.
I have a 2008 iMac with (I think) 16Gb of RAM which is used for just Firefox. I've been meaning to upgrade it to Linux but that generation didn't boot from USB, need to burn a CD.
All our intel MacBooks now run Linux just fine. The oldest is 2012, with 4Gb but most are 8 or 16Gb.
I would always recommend more RAM first over a faster processor; back when I would build desktop machines for Windows, I would use the second best CPU and put the savings into RAM.
I see the suggestions and then choose something different anyway. I don't want to use one of the top 3 most popular responses to an email from a friend. Even if it's something transactional.
You can actually make go spit out .o files and link it with your favorite linker. Bazel does this, if you ask it to.
I played a lot with experimental linkers when I was trying to get build time down for our (well, $JOB-1's) large Go binary, but they didn't help that much. The toolchain that comes with Go is quite good.
I think it depends on the codebase. There are some reflection calls that you can make that can cause dead code elimination to fail, thought I believe it's less easy to run into than it was a few years ago. One common dependency, at least in my line of work, is the Kubernetes API and it manages to both be gigantic and trigger this edge case (last I looked), so yeah, the binaries end up pretty big.
Another thing that people run into is big binaries = slow container startup times. This time is mostly spent in gzip. If you use Zstandard layers instead of gzip layers, startup time is improved. gzip decompression is actually very slow, and the OCI spec no longer mandates it.
The Space Shuttle sure blew up a lot for something with that much process applied.
reply