spear

That separate mode is incremental search and it's a big advantage. It lets you keep extending the search string until it matches the command you're looking for.

It's the same thing -- Comirnaty is the brand name of the Pfizer/BioNTech COVID vaccine.

I believe the included EVSE on the 2022 Bolt EUV now officially supports 240V.

Also, for the 2022 EV and EUV, GM will pay for an L2 outlet installation at home.

I had a black Amazon Basics cable that failed, although the insulation had more of a clean break rather than disintegrating.

My HP laptop charger blew the circuit breaker in my house. At least when my iPad charger failed, it wasn't that dramatic -- it just stopped working.

In my first HW design job out of college, I was very surprised when a senior engineer made that exact claim -- that God planted dinosaur fossils in the ground. I knew he was very religious and I could tell he was quite serious, but it was long ago and I had never heard of Young Earth Creationism, so I was shocked into silence. (Also, he was my manager and I decided I couldn't afford to argue.)

> The response from this individual rather shocked me. He said, sorry, but I’m looking for a design job, not a verification job.

This shouldn't have been too shocking. In the digital design industry, design engineers and verification engineers really are different positions. They require different skills, and though there are people who can do both well, they haven't been interchangeable for a few decades. I'm not surprised that an applicant for a design position would decline a verification job, especially if they're not just looking for an entry point at some prestigious team like Apple's CPU group.

The strange thing is that finding a bug and "fixing a broken design" is a design task, not a verification task. The verification engineer creates the simulation testbench and the tests to expose bugs. The design engineer uses these to find and fix the bugs. I doubt that most design applicants would balk at being asked to find and fix a bug in an existing design. So I'm not really sure exactly what he asked the interviewee that got the response he claims.

> One of the realities ingrained in the history and culture of Gisselquist Technology is that simulations rarely find the critical bugs.

This statement is so wrong that I think the author must have decided to redefine "critical bug" as any bug that simulation doesn't catch. In reality, there are critical bugs found at multiple steps -- design review, simulation, prototyping, ... not to mention critical bugs found in backend "verification" (timing analysis, equivalence checking, ...). The author pushes formal verification but it's not an alternative to simulation; it's a complementary strategy.

I didn't say my keyboard was noisy. For someone who gives advice on being agreeable, you sure make a lot of malicious assumptions.

I did ask my co-workers. No one complained.

You are otherwise reinforcing the point that you can't just bring whatever equipment you want to the office, as the parent poster claimed.

I brought in my own mechanical keyboard to the office. It has clicky keys so it's not quiet. I haven't gotten any complaints yet, but that could change depending on who my next cubicle neighbor might be.

Yeah, I do most of my work inside VNC servers running fvwm with emacs, xterm+tmux+zsh, and firefox. My config files haven't substantially changed in 25 years. The desktop login environment has changed many times over this period (enlightenment, sawfish, compiz, metacity, mutter, mutter-on-wayland, even Windows 7 and 10 for work) but I only configure that enough to set up virtual desktops in which I just bring up VNC viewers for multiple hosts.

Why is "Available Spare Threshold" showing as 99% on these M1 SSDs? I believe normal SSDs are more on the order of 10%.

I've been using two Unicomps since 2008, one for the office and one at home. They haven't died yet. I've only had the replace the rubber trackpoint nub on one of them.

Supposedly, the build quality since they retooled last year is even better.

I think you can hit Fn-backquote.

You can also order either of two HHKB-style layouts, where the backquote key is replaced by Esc (among other changes).

Confirmed for Santa Clara -- 11 cents for the first 300 kWh, slightly less for off-peak hours (if you install a Time of Use meter): https://www.siliconvalleypower.com/home/showpublisheddocumen...

The first computer I bought was a Power Computing Power 120(?). I think it's still in a box in my garage.

I went through a few Linux distributions for it: MkLinux first, then LinuxPPC, and finally Yellow Dog Linux. The driver for the Ethernet card needed to be patched for big-endian machines and the kernel needed a patch to allow the ADB keyboard CapsLock to be remapped to Control. Fun times.

Millenial or not, those friend networks are still how you'll be able to find the better jobs when you're older.

> Multiple people were killed in clashes with the police.

"Multiple"? Do you have proof of this? There was one woman who was shot by police.

As far as I know, it is not yet clear how the others (excluding the Capitol officer) died. I've seen reports that one man got a heart attack after tasing himself and another fell off some scaffolding.

I found the answer: Dec 25 (for WW 84) https://twitter.com/PattyJenks/status/1333861228695875584

Nice.

So when is HBO Max going to start streaming in 4k and HDR?

Another important safety measure is the HANS (Head And Neck Safety) device. Without it, that sudden deceleration (someone estimated a peak of 53[g]) could have resulted in a fatal injury.

A very important chunk of those developers who improved Linux hardware support work at Intel, and it shows -- the safest choice for Linux-compatible hardware is Intel (GPU, Ethernet, WiFi, ...). It's very doubtful that Apple is going to do the same.

Apple does use TSMC to build the M1 itself. So it's not quite bottom to top like the early computers up to the early to mid 90s, when a number of the workstation companies (eg. DEC, IBM, HP) still had their own fabs to make the CPUs.

I think that's a misleading way of looking at things. There is no "CISC philosophy". RISC designs came out as a new way of doing things and existing designs were called CISC for contrast. It's not like there were two schools of thought that were developed at the same time and the CISC designs intentionally rejected RISC philosophies.

Exactly right. With today's transistor budgets, the x86 ISA decoder/translator is just noise.

This is not the difference between x86 and ARM -- it's the difference between Intel's team and Apple's (also AMD's). You don't see Qualcomm being competitive even though they also use ARM.

Yeah, I think you mean this repo: https://github.com/Dunedan/mbp-2016-linux

I bought a 2017 MBP hoping the situation would eventually improve but it never did, so I never got around to installing Linux. I'm expecting it'll be even worse for these M1 systems.

Did you read your link? Even that article says the IBM 801 is considered to be the first RISC. And since you're citing Wikipedia, look at the entry for Cocke:

https://en.wikipedia.org/wiki/John_Cocke

Also, even though PowerPC is gone, IBM is still very much relevant in high-end RISC development -- they still make POWER computers.

My remaining use case for X11 remote display doesn't quite fit in the VNC/etc. remote display paradigm. At work, I submit a job to queuing software that picks a server (based on load and resource requirements) from a pool on the internal network. The GUI for that job then pops up on my X11 display. I don't really care which server is running the job, and the job is just using $DISPLAY -- we don't even forward over ssh.

I haven't tried it, but there's also this one for wlroots-based compositors (eg. sway): https://github.com/any1/wayvnc

Something broke here, at least on Fedora 32. Activation and deactivation doesn't happen consistently, as if it has lost track of the time of day. I usually have to move the temperature slider back and forth to get it to kick in.