Archive for January 6, 2023

Friday, January 6, 2023

ViewFinity S9

Michael Potuck:

Samsung announced its new lineup of monitors at CES this morning. Two of the most exciting models for Mac users include the company’s first 5K monitor, the ViewFinity S9 with a slick design not unlike Apple’s Studio Display but with even more features and a new 27-inch version of the popular Smart Monitor M8.


Pricing and launch details haven’t been shared yet.

It’s 27 inches, like the Studio Display.

Eric Slivka:

The ViewFinity S9 features a matte finish to minimize glare, is equipped with USB-C/Thunderbolt 4 connectivity, and includes a 4K SlimFit camera.


Update (2023-01-12): Dan Seifert:

A weird thing has happened at CES this year: display manufacturers not named Apple have announced true 5K and 6K monitors designed for creative work and productivity. […] It’s hard to overstate how rare this actually is.

Carl Hewitt, RIP

Stanford (via Hacker News):

We were saddened to learn of the death of Carl Hewitt, eminent AI researcher and visionary computer scientist.


Hewitt was best known for his work on the actor model of computation. For the last decade, his work had been in “inconsistency robustness”, which aims to provide practical rigorous foundations for systems dealing with pervasively inconsistent information. This work grew out of his doctoral dissertation focused on the procedural (as opposed to logical) embedding of knowledge, which was embodied in the Planner programming language.

See also: his blog.


Update (2023-01-12): Christine Lemmer-Webber:

RIP Carl Hewitt, founder of the actor model of computation. He could be a difficult person, but he listened to and was happy to talk to me and many others, and there are few people whose vision impacted so many areas of CS. He also was excited about Spritely (even though I would troll him by calling it “Lambda: the Ultimate Actor Model”). RIP.

Chris Lattner:

I’m v sad that Carl Hewitt passed recently. I was fortunate that Carl visited Apple many years ago and shared his ideas on actor models. It took many years, but his thinking had a big impact on the Swift concurrency manifesto.

Joe Duffy:

Carl was hugely influential on our work on safe concurrency at Microsoft. When he learned about us, he was flattered and wanted to help, like your experience. For such a titan, moved me.

Off to reread A Universal Modular ACTOR Formalism and celebrate an industry giant.

User Stylesheets

Nick Heer:

As Kyrnin writes, web designers usually do a better job these days, and most browsers no longer support user stylesheets by default. Google removed them from Chrome nine years ago and they were made optional in Firefox in 2019. But Safari, my browser of choice, still makes user stylesheets easily visible and, if you have the inclination, I recommend its use for a low-effort way of blocking irritations and overriding bad design choices.


But user stylesheets have drawbacks and are evidently from an earlier era of the web. The ways you might employ user styles today are often similar to browser extensions like StopTheMadness or any number of ad blockers. Modern extensions are far more powerful, too, as rules can be tailored to individual websites or run globally. The biggest advantage to the user stylesheet is also its Achilles’ heel: it only works globally, meaning the same rules are applied to all websites. That means your CSS selectors need to be highly specific.


Unlike browser extensions, there are no security or privacy questions to worry about, and it is entirely controlled by the user. I saved my stylesheet in my iCloud Drive so it syncs between my Macs; Safari for iOS does not support user styles.

Memory Safe Languages in Android 13

Jeffrey Vander Stoep:

For more than a decade, memory safety vulnerabilities have consistently represented more than 65% of vulnerabilities across products, and across the industry. On Android, we’re now seeing something different - a significant drop in memory safety vulnerabilities and an associated drop in the severity of our vulnerabilities.


This drop coincides with a shift in programming language usage away from memory unsafe languages. Android 13 is the first Android release where a majority of new code added to the release is in a memory safe language.


While correlation doesn’t necessarily mean causation, it’s interesting to note that the percent of vulnerabilities caused by memory safety issues seems to correlate rather closely with the development language that’s used for new code.


In Android 13, about 21% of all new native code (C/C++/Rust) is in Rust. There are approximately 1.5 million total lines of Rust code in AOSP across new functionality and components such as Keystore2, the new Ultra-wideband (UWB) stack, DNS-over-HTTP3, Android’s Virtualization framework (AVF), and various other components and their open source dependencies. […] To date, there have been zero memory safety vulnerabilities discovered in Android’s Rust code.