hadjian

I thought exactly the same! I remember, seeing screenshots of DotT for the first time and the new screens of RtMI invoke the same feeling. Love it!

Maybe here:

https://archive.org/details/mnkyega

Thanks for the history lesson. Yes, I know the rule from high school. Newton however did a much better job in making his name live forever. And they all succeeded in erasing their questionable behavior from lectures. Money can buy a lot.

Apple owns the hardware and MS managed to get HW vendors to adjust everything to Windows.

IMHO, owning the Hardware or agreeing on one existing HW among devs is a good approach. These come to mind:

Dell XPS notebooks, which specifically support Ubuntu or

https://system76.com/ They build or assemble hardware specifically for their Linux distribution Pop! OS

No personal experience with neither, but a colleague uses XPS with OpenSuse and talks about a seamstress experience.

I thought Newton was the ass of math history (e.g. Hooke and Leibnitz feuds). What did L‘Hôpital do?

This might be a bit off-topic, but since we’re talking big screens: I also have a 27“ display. I mostly work with emacs and a couple of shells, both in the kitty terminal. For emacs, this is great, but for a terminal, it really feels dumb, if you have a 3x2 terminal window and write something into the lower left one. It’s so far at the bottom and you have this huge real estate… I started to use a 1x3 terminal window. The bottom row is where I can glance at and the top one is where I swap out the terminal windows.

Anyone know of a new paradime for text based computing one huge screens? Sounds too niche, right? ;-)

This is really lovely. I think the search results are useful, if you're looking for more static information. Very pleasant, to see only results.

I think, I found a minor bug, while (of course) searching for my homepage:

https://www.alexandria.org/?c=&r=&q=www.hadjian.com

The status line below the search box says, that it found many results, but the results are empty. Also, when hitting F5 a couple of times, the number jumps around.

Keep up the great work. I think there is a lot potential to Common Crawl and things built on top of it.

Thanks for the answers. I think I realize that there is a difference between a todo list (have to do it) and a knowledge base (let’s organize what I’ve learned).

The former I also do with org-mode and then use the archiving feature for things I put to DONE.

I oftentimes do the latter, but don’t actually use it that often. In college, I used to summarize text-books, which helped me memorize my learnings. After finishing the book, by chapter summary served as a shorter version of the book. Was quite effective.

Haven’t been successful in replicating this for work, though.

I use org-mode, just FYI. I was wondering however: everyone shares how they store things, but how often or even how do you query your knowledge base?

There are often tips for creating habit to write down things „at the end of the day“ or such. But can anyone describe some habits when to consume this stuff? I‘d be interested. Thx.

I received my copy yesterday! Any plans for a hardcover instead of a paperback? Just lies nicer on a table and doesn't wear of as fast.

I mostly read PDFs on an iPad. The only books I bought as paperbacks are the ones I will reread over and over out of joy:

Knuth: The Art of Computer Programming

CLRS: Introduction to Algorithms

Strang: Introduction to Linear Algebra

H&P: Computer Architecture: A Quantitative Approach

and now I ordered yours, Bob! Just wanted to show my respect. When my crunch time is over at work I will answer the issue I opened on GitHub ;-)

Disclosure: I work at Siemens on an implementation of the Web of Things not related to the Mozilla Project.

What is mostly misunderstood about the Web of Things, is that it does not define a network protocol but a document format to describe devices in terms of properties, actions and events.

Interactions are then further described by „forms“ that contain Hrefs with the protocol scheme supported by the device (e.g. coap://, opc.tcp://). The idea is not to introduce the next unifying protocol, but to unify the description of devices that support arbitrary protocols. Think of OpenAPI for IoT.

It serves us well in industrial settings where protocols like opc-ua, bacnet, coap, modbus and the like will stay the leading protocol in their respective domain for the foreseeable future. Such a descriptive approach to me seems the only option to at least write applications in a uniform manner.

Looking at efforts like MS Device Description Language (DTDL) or AWS Things Graph Data Model (TDM), it makes sense to have at least one openly standardized description language to prevent fragmentation at that level. The war on fragmentation at the protocol level is already lost IMHO (and everybody lost).