layer8

This looks the same as the iPad Pro tandem OLED pixel layout. That I happen to write this comment on.

You could buy one from the price difference of the touch MacBook.

I think there’s a wide space between refusing any AI use, and refusing AI use requirements imposed by an employer. For example, one might find AI valuable for search, research, and getting a second opinion, but refuse it for primary generation of content.

I’d be surprised to see current LLMs write as well (and as non-annoying) as the writing in this book.

I spot-checked a few random chapters, and it looks clearly human-written to me. But I share your general worry.

The new or the classic context menu? (https://learn.microsoft.com/en-us/answers/questions/2287432/...)

Alexa had already been using other models like Claude depending on the question, and the French version for example uses Mistral.

Just as friendly feedback, monospace fonts are difficult to read for me for that kind of content. The site also doesn’t explain what it is about. It says “terminal-grade communities” (whatever that means), but Fluxer doesn’t seem to be bound to terminals?

Not what you’re asking for, but see https://en.wikipedia.org/wiki/Secret_law#Secret_law_in_the_U....

Because not everyone likes macOS and dislikes Windows.

They are very similar, but maybe not identical. The iPad nano-texture reportedly is less prone to fingerprints than at least the XDR monitor; perhaps that’s just an additional oleophobic coating. There may also be generational differences as these weren’t introduced at the same time and may come from different production lines.

So how are the duties of the employee defined? In Europe it’s usually $hours/week in $role (minus holidays and vacation days).

Your employment contract lists deliverables rather than work time?

I’m still installing the classic (Windows 7) calculator [0] on each new Windows setup.

[0] https://win7games.com/#calc

Only because Windows 8 was such a dramatic step back. Windows 7 is still better than Windows 10 in terms of UI.

They had a different look, but usage and UI conventions including keyboard navigation worked basically the same. Since the mixing of mobile and desktop with web technology, it’s the Wild West.

As an unmodified binary from the 1980s on current Linux/Unix? Highly unlikely.

The student protest movement “hacked” the authoritarian rule.

Gaining ground in the two largest EU countries.

I thought that people don't know what they want until you show it to them? They thought they wanted faster horsies but Amazon gave them noxious cars?

That seems like wishful thinking. Why wouldn’t AI be able to assess what are good questions to humans, and pursue similar processes as those that lead humans to come up with good questions? AI is trained primarily on expressions of human thought and emotion. It’s difficult to see what secrets of the human brain we could be hiding from the models.

It would be nice to see how it looks like on a CRT.

Almost certainly it was an incremental discovery process, first cooking and/or fumigating tuna for other consumption, then extending its shelf life by fermentation and/or sun-drying, discovering that evening out the exterior with paste helps extend it, then solving the problem that extended drying leads to hard consistency by shaving off very thin slices, stuff like that. They didn’t set out with “oh we need very thin dried tuna slices for dashi and seasoning” and then invented a whole process for that.

It used to be that people set the width of their browser window to the text page width they’re comfortable with, and configured a different font if they didn’t like the default one on their browser.

We should be more ambitious in letting the browser software control the presentation according to the user’s preferences. This is not facetious. We should use the increased ease of building software to create software that is flexible, empowers the user, and accommodates different user preferences.

Greg Egan. It’s in his excellent short story collection “Axiomatic”.

The end game is described in this short story: https://gwern.net/doc/fiction/science-fiction/1995-egan.pdf

I disagree. Science is what we do to find out what is the case, i.e. real. The fact that it also has useful applications is directly tied to the extent to which the findings are real. It works because it describes something real.

The difference is that web browsers absolutely need to support JavaScript to correctly display many important web sites, whereas that’s not necessary for PDF. You also don’t have to deal with vulnerability footguns like XSS/CSRF/CORS in PDF. Except for some rare special use cases that PDF viewers don’t need to support, nothing has to happen online for PDF. It’s really not comparable.

The characterization of the PDF format specifically being “basically code” in any substantial manner is simply incorrect. The only PDF-specific features that reasonably meet that description is the PostScript support, which has fallen out of use decades ago and was completely removed in PDF 2.0, and the JavaScript support, which is optional, prohibited in PDF/A, and can easily be limited or omitted by a PDF viewer.