This has MorningLightMountain vibes.

Power lines and pylons are superficially the same all over the world, but differ in details we subconsiously remember. The power lines in DayZ felt like home.

There are also Rivers - when spaces between words on multiple lines align vertically. Harder to control for than widows and orphans.

Where is ‘here’? France?

It works for those who want to be sorta legal. Usually I ask to talk to their GDPR officer first thing. Call ends.

But not everyone wants to be sorta legal.

It seems application state is mainly maintained in the widgets. Reminds me of Delphi. Is there a similar concept for representing state in a well-suited data structures, that can be created and composed visually like the UI widgets?

Decker heavily emphasizes the concept of "reified data", representing information as tangible entities within a deck.

You can create "contraptions" as specialized data containers/editors for specific applications:

http://beyondloom.com/decker/decker.html#customwidgets

For example, "WigglyKit" offers several contraptions which operate on a shared convention for representing animated images:

http://beyondloom.com/decker/wigglykit.html

You can also represent composite data as a series of cards in a deck, or use cards as encapsulated "objects" that you communicate with via events:

http://beyondloom.com/blog/sketchpad.html#cardsarerecords

In a pinch, you can also easily encode arbitrary data in fields as a JSON superset with their ".data" attribute.

Feels more like jerry-rigged SmallTalk to me. Maybe more like Rebol?

But without an MS accoutn it would not be connected to the browsing history

This is not true either; to Microsoft, every anonymous GDID is its own unique account on their servers.

My reasons to hate XML:

- element vs attribute ambiguity

- model of the document does not fit nicely to programming model of structs, dicts and arrays

- too many complexities (entities, cdata, parser directives)

- cardinality unknown without schema (is that a single value, or an array that just happens to have one element)

- order of elements may or may not be significant depending on schema

- not really extensible if the original schema does not explicitly allow for extensibility

- some types of valid XML documents are not representable by a schema (e.g. any number of different elements in any order)

- verbosity

- namespace identifiers being URIs that may or may not be resolvable

What I want for general data exchange is JSON with comments and sane namespaces.

Edit: line wraps

JSON does data exchange ok. Protobuf does it very well. Google fumbled its ecosystem, should've focused on establishing it as an easy alternative to HTTP+JSON, instead focused on gRPC which is its own thing. Textproto is quite readable and supports comments, great for config files.

XML is so much fuss for nothing. All that xmlns uri whatever stuff and it still doesn't tell the other side how to parse it.

I never understood why file open/save dialog is a separate thing. I want to use my file manager to open and save files!

You need a separate UI to handle things like entering the file name and filtering for appropriate files. Windows was designed so that the same file browser component is used in the Explorer and in open/save dialogs (but with Windows 7-era UI), but on Linux, which file manager should GTK use? GTK sometimes likes to pretend it’s separate from GNOME.

> GTK sometimes likes to pretend it’s separate from GNOME.

It is. I happily use a GTK desktop environment and it is not GNOME.

GTK being GIMP ToolKit and not GNOME ToolKit, I hear they frequently annoy the GNOME team by not deleting features that GNOME wants to delete.

I'd love if that UI was part of the file manager. totalcmd.exe or Finder.app or mc or Krusader etc.

Win32 has good news for you!

path-based auth middleware is a bad practice IMHO

I think there’s a solid argument for global auth middleware, where this is a problem if you use the path for exceptions like health-checks or a login endpoint.

Why put such crappy display on such a high power device?

That's pretty simple - the chosen display is best for core usage. Cleay visible in bright sun or dark, sharp angles, easy on the battery. For anything else, there's a HDMI out isn't there.

Them actually calling it HDMI now stood out to me. They made a point of avoiding that before.