I like how their number one benefit is Order to Seat. In one fell swoop it shows that:

* Their priority is revenue above all else (fair enough; honest too)

* They are either deceptive or stupid

Re the deception/stupidity - if everyone is moving to using the same app, how does everyone "get served first" as per their bullet point?

> So, a UK-only advice, and it strangely assumes that any other service in UK wouldn’t be bound by the same laws.

I suspect it's because whilst other services would be affected we only know about Apple currently and, thanks to iOS and Mac, a large percentage of the population will be using Apple by default for the services impacted. Only Google (Android) and Microsoft (Windows) really overlap in that regard.

Neither has the UK government.

* It wasn't the general election.

* They offered local councils the chance to request it if they were going through a reorganisation or devolution process.

* 18 councils requested and 9 were accepted as justified.

* And even those are only delayed until May next year (one year after the rest of the UK).

So to be clear the UK government not only didn't postpone the general elections but half the councils who requested the local elections were postponed were denied, with the other half having reasons and still doing it a year later anyway.

And all that is actually covered in the page you link to.

Why are we hearing that "studies" have "uncovered the concept of context rot as the number of tokens in the context window increases"? It's obvious, and we've always known this.

Agents are stateless, hence the need for context. This means that all they know about the ongoing session is what's in that context (generally speaking). As the context grows any particular element within it becomes a smaller and smaller percentage of the whole. The LLM is not 'losing focus'; it's being diluted with more tokens. But then I suppose anthropomorphism comes naturally to a company named Anthropic, and 'losing focus' does make it sound more human.

They didn't need a study and article, but it likely contributes towards the mystique. Hence the use of phrases like "this results in n² pairwise relationships for n tokens" to make it sound more erudite and revelatory.

Not quite what you wanted, but the Lone Wolf ones are (legally) available online [1]. You may be able to read the downloads, or even the online play versions, with Dutch translations.

[1] https://www.projectaon.org/en/Main/Books

I much prefer C# 11's raw string literals. It takes the indentation of the first line and assumes the subsequent ones have the same indentation.

  string json = $"""
      <h1>{title}</h1>
      <article>
          Welcome to {sitename}.
      </article>
      """;

And it even allows for using embedded curly braces as real characters:

  string json = $$"""
      <h1>{{title}}</h1>
      <article>
          Welcome to {{sitename}}, which uses the <code>{sitename}</code> syntax.
      </article>
      """;

The $ (meaning to interpolate curly braces) appears twice, which switches interpolation to two curly braces, leaving the single ones untouched.

Just a minor correction (as I'm the author of c#'s raw string literal feature).

The indentation of the final ` """` line is what is removed from all other lines. Not the indentation of the first line. This allows the first line to be indented as well.

Cheers, and I'm glad you like it. I thought we did a really good job with that feature :-)

Did you draw inspiration from Swift's multiline string literal, or was it the other way around? The syntax looks very similar, if not identical.

Really not trying to go into any of the "holy wars" here, but could you please compare C#'s feature to Java's multi-line strings? I'm only familiar with the latter, and I would like to know if they are similar in concept or not.

That's a fantastic design idea, and it seems to require all the other lines to have the same indentation "prefix".

Haven't used much C#, but I love Scala's `.stripPrefix` and `StringContext`.

Thanks for the correction. I never read the spec, just started using it. And as I tend to balance my first and last line indentation I never realised.

- Some mentions of Lazarus and FreePascal (so basically a cross-platform open source Delphi equivalent). And I'd agree with them.

- For C# I like AOT assemblies using Uno or Avalonia.

- For Go I like TCell (which does cross-platform console mode text GUIs [with cursor positioning, colours, mouse, etc]).

- If you're doing vibe coding I find it tends to work best with Electron.

- The big omission here is anything Python; I don't do desktop apps in Python so can offer nothing. Same for Ruby, though Hotwire Native looks interesting.

>The big omission here is anything Python

wxPython and PyQt are some options. PySide too. There are some other less-known ones too. I've not tried Kivy. There is also tkinter which comes built-in with Python.

IIRC, the Dropbox GUI client app was done with wxPython on both Linux and Windows.

Reading through the comments there seems to be some misunderstandings leading to issues with a stance that the potential class action is not taking.

The class action doesn't relate to normal training based on legally acquired materials, which US courts have already said is fair use. It is concerned specifically with training on materials obtained illegally (pirated content).

Just because something is on a public website accessible for free doesn't mean it is then public domain. Sharing is not necessarily giving.

(Though unfortunately in the Wild West Web of today it seems it does, practically speaking.)

That looks good (not actually cloned and tried it yet).

However the screenshots in the README show (for me anyway) as broken links, even though they work when clicked on. I can see you're linking to the images in the blobs. If it helps, for my own stuff in the README I link relative to the README file in the actual source. So for one of yours for example I'd use: ./ubiblio_menu.png

This also has the advantages of both being self-contained and also working locally (eg in the VS Code preview) before you've pushed the images.