There's actually two Engineering Emmy Awards. There's also the 'Primetime Engineering Emmy Awards' given by the ATAS (Academy of Television Arts and Sciences) while 'Technology and Engineering Emmy Awards' are given by NATAS (National Academy of Television Arts and Sciences), not confusing at all.

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

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

This is what MacStadium does. Here's a drawer design for the previous gen intel macs:

https://cdn.prod.website-files.com/687e650a56916806eaaf8f62/...

You can find a bunch more detail in their related patent filings:

https://patents.google.com/patent/US20240397658A1/en?q=(%22m...

I was thinking the units all face the front in a shallow drawer, whereas MS is doing a deep drawer, which is almost certainly even better for density.

Very few units sold. Distribution was poor, most were GSM only and only a couple supported 850mhz. I had the E70-2 and later E61i but I never meant anyone else with one.

Yep, I presume that’s primarily what the article author meant. To Americans Nokia mostly means "feature phones" whereas in Europe Nokia smartphones were, if not ubiquitous, commonplace enough around 2007 (remember that Nokia had been making smartphones for a decade by then). The N series in particular were targeted at consumers.

1. You can specify your terminal font via terminal.font_family in zed settings.json

2. Not sure.

3. For most languages, the default is to use prettier for formatting. You can disable `format_on_save` globally, per-language and per project depending on your needs. If you ever need to save without triggering format ("workspace: save without formatting").

Prettier is /opinionated/ -- and its default is `singleQuote` = false which can be quite jarring if unexpected. Prettier will look for and respect various configuration files (.prettierrc, .editorconfig, via package.json, etc) so projects can set their own defaults (e.g. `singleQuote = true`). Zed can also be configured to further override prettier config zed settings, but I usually find that's more trouble than it's worth.

If you have another formatter you prefer (a language server or an external cli that will format files piped to stdin) you can easily have zed use those instead. Note, you can always manually reformat with `editor: format` and leave `format_on_save` off by default if that's more your code style.

- https://zed.dev/docs/configuring-zed#terminal-font-family

- https://zed.dev/docs/configuring-zed#format-on-save

- https://prettier.io/docs/configuration

- https://zed.dev/docs/languages/yaml#prettier-formatting

- https://zed.dev/docs/configuring-zed#formatter

Thank you for the excellent and informative reply. Will try it out

It would be nice for prettier to throw a user warning before making a ton of changes on save for the first time, and also let them know where they can configure it

Just in case, this worked for me on a Mac with agnoster theme for zsh:

  "terminal": {
    "font_family": "Meslo LG M DZ for Powerline",
    "font_size": 13,
    "font_fallbacks": ["Meslo LG M for Powerline"]
  }

Very similar to the Beepberry. Exciting to see someone else building into that form factor. Also love to fun to see the Nokia BL-5C battery (originally introduced in the Nokia 3650 in 2003) still alive and kicking 20years later.

https://blog.beeper.com/2023/05/16/beeper-x-sqmfi-beepberry/

That appears to have been renamed to the Beepy, and the product page now has the repurposed Blackberry keyboard blurred out. Did whoever owns the corpse of Blackberry go after them for trademark infringement?

https://beepy.sqfmi.com/

Is this when they start pre installing QNX? https://carleton.ca/rcs/qnx/installing-qnx-on-raspberry-pi-4...

This was the question I was going to ask! I've recently been diving into Lua 5.x internals and have been extremely impressed with Lua's register-based bytecode implementation. Lua has a stable byte code interface between patch releases (5.4.0 -> 5.4.1, etc) but not between major/minor revisions (5.3 -> 5.4). SQLite on the other hand does not consider this a public interface at all!

> "Remember: The VDBE opcodes are not part of the interface definition for SQLite. The number of opcodes and their names and meanings change from one release of SQLite to the next." https://www.sqlite.org/opcode.html#the_opcodes

For anyone interested in understanding how a register-based VM operates I highly recommend:

A No-Frills Introduction to Lua 5.1 VM Instructions by Kein-Hong Man. https://www.mcours.net/cours/pdf/hasclic3/hasssclic818.pdf

I also like their Automated License Plate Reader (ALPR) record retention period (3 minutes):

> Records of number plates read by each LPR shall not be recorded or transmitted anywhere and shall be purged from the system within 3 minutes of their capture in such a manner that they are destroyed and are not recoverable, unless an alarm resulted in an arrest, a citation, or protective custody, or identified a vehicle that was the subject of a missing person or wanted broadcast [...]

https://law.justia.com/codes/new-hampshire/2022/title-xxi/ti...

This seems absolutely reasonable. Keep the data about people who have committed or you can reasonably suspect might be committing a crime, get rid of the identifiable information for law-abiding citizens and maybe keep the aggregated metadata.

This should be the standard IMO.

> to see how far it gets before killing itself (on a VM or easily re-flashed machine of course).

I did this, but with dd -- it completed. Was very anti-climatic. I was hoping it would crash or at least disconnect me, but the kernel, sshd and bash were still in memory and happily returned me to a prompt where I couldn't really do anything.

There's where the real fun starts. Now try to recover from this extremely restricted shell!

Doing at the block device level you're gonna have stuff stick around in cache, file-wise would blow things up faster

Sadly their Heroku dyno has fallen over. It's open source and works locally though.

Old Demo: https://www.youtube.com/watch?v=GLaMCr8g0n4

Github: https://github.com/kitzeller/barbara

Yeah "stone" 100GB M-DISC bluray discs are ~$10/ea. 100GB for 100yrs* ($0.10/GB). https://amzn.to/3KpYAfl

*maybe

Those are nice, but we need 10TB now.

They used to make BD-Rs using this technology, but switched to a cheaper (supposedly not as long lasting) method without any change in branding. It was a minor scandal among datahoarders