There are definitely use cases. Pis have lower power consumption than NUCs. This is the main reason I went for one to run Home Assistant rather than a NUC.
I have a NAS/home server that I could put it on but I don't want my home automation going down when I tinker with it.
If you don't want anything to do with EA, Konami ain't much better. They actively sabotage their former employees job prospects.
> One employee from a staffing agency said that Konami "files complaints to gaming companies who take on its former employees," causing one game company to "warn its staff against hiring ex-Kon" - "ex-Kon" being a nickname for ex-Konami employees. "If you leave the company, you cannot rely on Konami's name to land a job," one former employee said.
Rust is already making substantial inroads in browsers, especially for things like codecs. Chrome also recently replaced FreeType with Skrifa (Rust), and the JS Temporal API in V8 is implemented in Rust.
One aspect of Transmeta not mentioned by this article is their "Code Morphing" technique used by the Crusoe and Efficeon processors. This was a low level piece of software similar to a JIT compiler that translated x86 instructions to the processor's native VLIW instruction set.
Similar technology was developed later by Nvidia, which had licensed Transmeta's IP, for the Denver CPU cores used in the HTC Nexus 9 and the Carmel CPU cores in the Magic Leap One. Denver was originally intended to target both ARM and x86 but they had to abandon the x86 support due to patent issues.
Code morphing was fascinating. I had no idea nVidia tried anything similar.
I always felt Transmeta could have carved out a small but sustained niche by offering even less-efficient "morphing" for other architectures, especially discontinued ones. 680x0, SPARC, MIPS, Alpha, PA-RISC... anything the vendors stopped developing hardware (or competitive hardware) for.
So glad someone else also knew about this connection :) Details about Denver are pretty minimal, but this talk at Stanford is one of the most detailed I’ve been able to find for those interested. It’s fascinating stuff with lots of similarities to how Transmeta operated: https://youtu.be/oEuXA0_9feM?si=WXuBDzCXMM4_5YhA
There was a Hot Chips presentation by them that also gave some good details. Unlike the original Transmeta design they first ran code natively and only recompiled the hot spots.
`bcrypt` is probably the "standard" in the sense that it has the widest adoption, but since 2015 [1] the "standard" in terms of what you should recommend for new work has been `argon2id` (and you can find parameter recommendations here [2]).
Also argon doesn't care about input length compared to bcrypt which only ever compares the first 72 bytes of a hash.
Okta actually fell victim to this because they concatenated userid + username + password. If userid + password were over 72 bytes then the password would never be checked thus you could login with userid + username.
Still fits "It feels to me more like OSes ought to be more secure."
New USB-HID keyboard? Ask it to input a sequence shown on screen to gain trust.
Though USB could be better too; having unique gadget serial numbers would help a lot. Matching by vendor:product at least means the duplicate-gadget attack would need to be targeted.
I wish Apple had some sort of "Geforce Now" style setup to run a Mac in a box. I know they'd never go for something like a legit image you could run in a VM, but surely they could come up with something.
My work sent over some old MacBook for when we need to test something unique to Safari, so it's not even the hardware aspect. It's the "I need to find another place to stash a machine, and then wire up KVM switches to use my highly opinionated I/O device choices, on a finite sized desk" factor.
No. Back when smartphones were still in the process of taking over the market, Zuck saw the adoption curve and realized that future ad revenue would be from phone scrollers.
At the time most features were designed and implemented first for desktop and later ported to mobile. He issued an edict to all hands: design and build for mobile first. Not at some point in the future but for everything, starting immediately.
Maybe this doesn't sound major, but for the company it was a turn on a dime, and the pivot was both well informed and highly successful in practice.
> Amprius Technologies, Inc. has never developed or manufactured batteries for power banks. For accuracy, please attribute the certification issue to Apex (Wuxi), not Amprius. Recent reports have incorrectly linked Amprius Technologies, Inc. to a battery certification issue. The company involved is Apex (Wuxi) Co., Ltd., formerly known as Amprius (Wuxi) Co., Ltd., a Chinese lithium battery manufacturer based in Wuxi, China.
> Apex (Wuxi) was once a subsidiary of Amprius Inc. but was never part of Amprius Technologies, Inc. In early 2022, Apex was spun off, renamed, and has operated independently since, with no ties or relationships to Amprius Technologies, Inc.
According to the recall notice, these powerbanks were "manufactured between January 1st, 2016, and October 30th, 2019" [0], so that was very much during the time before this says that they were spun out into a separate company.
Going from that last quote, they would in fact have been made and sold by Apex(Inc) at the time it was a subsidiary of Amprius Inc. and claiming otherwise seems like deliberate deception.
Their own website makes clear that Amprius Technologies Inc and Apex (Wuxi) are related in the description of their CEO, who served as CEO of both companies simultaneously. [1]
I have a NAS/home server that I could put it on but I don't want my home automation going down when I tinker with it.
reply