bxparks

I think computed-GOTO is easier to understand and more flexible than Duff's device, but computed-GOTO is not part of the C standard. It is sometimes available as a non-portable extension, e.g. https://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html. Anyone know why it is not included in C?

I sold my RPi3B for the same price that I paid 6 years ago. No more unused Pi's in my drawer.

> It not only runs (included) ROM code from the HP-45, but also the HP-35 and the HP-80

I thought that ROM code is copyrighted and cannot be redistributed without permission. Maybe they got that permission from HP. The TI calculator emulators require a separate ROM dump from an actual physical calculator.

Dell Precision 77xx, 5750, 5760, 5770: https://en.wikipedia.org/wiki/Dell_Precision

(No first-hand experience with any of those.)

(Updated: to add more models.)

I didn't even realize that "Whatever" was the dismiss button.

The Kill Sticky bookmarklet is your friend: https://alisdair.mcdiarmid.org/kill-sticky-headers/

There's a newer version, but it breaks a number of sites for me, so I don't use it: https://github.com/t-mart/kill-sticky

The internet is a hostile place without Kill Sticky, uBlock Origin, and uBlock Matrix.

I don't recommend doing this. I followed those instructions to the letter, and got a completely broken Nexus 7. I somehow managed to recover enough to reinstall the factory image, but it took many many iterations and blind shots in the dark, consuming several hours of my time.

Can't believe someone downvoted your perfectly reasonable comment.

Ha, 125% for most things, except HN where I need to use 170%

You get an upvote for teaching me a new word today, "imprimatur". It looked like a typo.

Your TI calculator use 4xAAA batteries, yes? Why not use NiMH rechargeables instead of disposables? NiMH are so cheap these days that they pay for themselves after only a handful of recharge cycles. The other advantage of NiMH is that they rarely leak (I've never seen one leak). In contrast to disposable batteries which tend to leak and destroy electronics.

No you are not being irrational. Customs and Border Protection have been known to detain and force US citizens to reveal their passwords:

https://arstechnica.com/tech-policy/2017/02/what-could-happe...

The chance of this happening to you is very small, but not zero.

The MacBook Pro 2015 (13 and 15) are amazing, but they have glued-in batteries. iFixIt says it would take 45min to 2h to replace, and it is rated "Difficult". It's the only reason why I won't buy them on eBay.

https://www.ifixit.com/Guide/MacBook+Pro+15-Inch+Retina+Disp...

https://www.ifixit.com/Guide/MacBook+Pro+13-Inch+Retina+Disp...

I see 3 countries with negative DST in their RULE records:

* Eire after 1971: https://github.com/eggert/tz/blob/main/europe#L526

* Morocco after 2019: https://github.com/eggert/tz/blob/main/africa#L928

* Namibia between 1994 and 2017: https://github.com/eggert/tz/blob/main/africa#L1167

My ~/.ssh/known_hosts used to look like that, but now it looks like the host part is encrypted? It looks like:

  |1|{base64-encoded-string?}|{another-base64-encoded} ssh-rsa AAA{long-string}

This is on Ubuntu 22.04 (Linux Mint).

The best experience of stackoverflow is when I search a problem, and the top search result is a stackoverflow link, I click on it, and... it's been closed by the mods with no answer or pointer to a solution. "But I have the exact same problem!" I blurt out. "Too bad," says stackoverflow.

That is a very interesting observation. I am starting to have a similar distaste for the visual noise caused by the ':' in my fully type-annotated Python code. This is particularly noticeable after spending a few weeks writing Golang, then going back to my Python code. The Go code feels far cleaner syntactically and visually.

I crashed at 2499.1 mph by going sideways for a long long time. How accurate is your physics? If I hit orbital velocity, will I just orbit the moon? What if I hit escape velocity?

I went off screen, turned around and crashed at 394.6 MPH.

Awesome, the highest crash landing speed I was able to achieve was 97.7 MPH after about 20-30 attempts.

Yeah, I've been looking at those TI calculators for a few years, hoping to dabble in some Z80 assembly programming for nostalgia.

I've also been eyeing their TI-92, 92II, 92Plus, and Voyage 200 series of calculators. They use the 68000 processor and have qwerty keyboards. It looks like there is a C compiler for it (http://tigcc.ticalc.org/), so it ought to be possible to do some interesting things, like this Fuzix OS, or a FORTH, LISP or Lua interpreter, or a terminal program over a serial link to a battery-powered ESP8266/ESP32 to the internet over WiFi.

Are there any readily available dev boards using these classic microprocessors (6800, 6502, 6809, Z80) that have the various peripherals (UART, serial USB, flash and static memory) already installed? A quick search on Amazon or eBay did not reveal much.

That's the nice thing about the newer chips (AVR, ESP8266, ESP32, STM32, etc). All those peripherals are already included on the SoC or the dev board. It is very easy to quickly upload the firmware through serial-USB, and start having fun.

Your post is a great example why I wish Go lang was named something different. Because you use the lower cased versions java, rust, js, ts, nodejs, deno, etc. But all your 'go' refer to the verb, not the Go language.

As far as I understand, that's a consequence of the automatic insertion of trailing semicolon by the lexer, not a decision by gofmt. It's explained here: https://go.dev/doc/effective_go#semicolons

I find this useful in unit tests where I often find myself duplicating blocks of assertions multiple times. The {block} helps to prevent accidentally reusing variables which are defined by previous blocks of assertions.

I rarely use a free-standing {block} in actual code. I think it's because if something is worthy enough to be logically grouped into a {block}, then it is probably worthwhile to pull it out into its own function, method or lambda expression.

Yup. I keep a cheap backup Android phone with Google Authenticator installed just for this purpose. Every time I add a 2FA code, I add it to the backup phone. I also print out the QR code, but a backup phone is far more convenient.

I dropped my main phone into the toilet a week ago, completely fried it. Moved the SIM card to my backup phone, and carried on like almost nothing happened. I then powered up my 10-year old Nexus 7 tablet, and duplicated all my 2FA codes to the tablet. When I get a new replacement phone, I will duplicate my 2FA codes again.

The macOS version of GNU Make is stuck at 3.81, which I discovered does not print the information needed by vim's quickfix feature when traversing subdirectories using `make -C`. Installing the latest version of GNU Make (4.4) using `brew install make` fixed that problem.

I map 'S' to this in my .vimrc:

    nmap S :wall<cr>

which saves all changed buffers into their respective files.

It is probably the single most productive customization in my .vimrc file. I save my files very often, and I usually have multiple files and buffers open. 'cc' is an alias for the old 'S', so I don't lose much.

I don't have an iPhone, so I would say that the lightning symbol and the plug icon means the cable is connected and charging.

You are not wrong about WiFi. But sometimes worse is better. :-)

With WiFi, I don't need any other technology stack, no hubs, no bridges. I can use my existing network infrastructure. The data packets from the ESP8266 devices get delivered directly to the MQTT broker over TCP/IP over WiFi. It's cheap (~$3 for a D1 Mini), dead simple, and good enough.

Every 15 minutes seems about right for temperature/humidity sensors. Increasing it beyond 15-30 minutes becomes a diminishing return, because at that point, the Deep Sleep power usage becomes greater than active WiFi usage.

People do say that WiFi reconnect can be done in 2 seconds, but I have never been able to achieve that myself on my network, no matter the signal strength. I tried static IP, static subnet, and various configs before going to sleep (to retain WiFi signal strength? I can't remember). I always get 5-6 seconds.

I think I remember measuring the NodeMCU with a higher Deep Sleep current than the D1 Mini, but I don't remember what that value was.

The other thing I forgot to mention that consumes current is the USB-Serial converter on boards like the D1 Mini and NodeMCU, but not present on the ESP-01. I don't know which consumes more, the voltage regulator or the USB-Serial converter.