I think the argument comes from the full title being "The United Kingdom of Great Britain and Northern Ireland". If you drop NI then the other three countries can already be grouped under the Great Britain term.
I wonder how much effort it would be to put together something expanding on this that's really friendly to new developers exploring a system. The goal would be to have something that looks more like a traditional swimlane diagram, but with human readable labelling of the connections. The open telemetry data should provide a nice skeleton and then maybe use some LLM summarisation (with access to the source code) to label what's going on.
Retrieval augmented generation. In short you use an LLM to classify your documents (or chunks from them) up front. Then when you want to ask the LLM a question you pull the most relevant ones back to feed it as additional context.
Prices have dropped quite considerably recently. You can now pick up an e-bike as cheaply as €500. Once you get out of the "budget" range I'd expect to be paying more like €1500 for an average one.
Single Page App. Simply: the application is loaded once when you navigate to the page and more ajax calls are used to retrieve data, perform actions as you use the app.
It's getting pretty infuriating the direction they seem to be taking on this. I would gladly be using the wallet app without a card, KitKat on my Nexus 5 has it baked into the settings even, but Google seem to have no desire to put it out in the UK.
Your "This field is required" validation labels obscure the postcode lookup dropdown for me when I submit before inputting any details. Otherwise, very nice!
It seemed it was detached DOM elements that were causing most of the problems. We tried profiling with the Chrome dev tools but found it very difficult to pinpoint where to start looking from the thousands of elements generated every-time we repeated our workflow.
In the end we looked at the bottom line memory consumption and experimented until we saw reductions. We found using things like ng-show instead of ui-if, essentially preloading the partials and switching between them instead of reloading everytime, saved us enough memory to make the system viable.
Everytime I read an Angular postmortem I'm intrigued that I never see memory issues being raised.
In a recent rewrite of one of our applications into Angular we had huge issues with it consuming memory. I think our use case is quite distinct, we have a telephony component that needs to stay loaded so single page app really does mean single page app for us, but even so I would expect to see memory mentioned every now and then.