The problem is worse outside London, hotels in conservation areas that get planning for health clubs on the basis that locals can buy memberships too, then quietly withdrawn. A car park that should be open for public paid parking becomes private.

It's a fantastic idea, but enforcement sucks on intangible things like this. In a few years time I'm sure it will be 'closed for maintenance' then never reopen to the public or a nice restaurant will go up there and suddenly you'll need a restaurant booking to use the lift.

Same with the "affordable housing" criteria of new build housing developments. They'll accidentally forget to build the affordable part then get a slap on the wrist afterwards, or build much fewer than were in the plans, or build whatever they want then apply to regularisation afterwards.

Apart from the "maintenance" thing, how are these "untangible"? Needing a restaurant reservation or whatever is not free.

This shouldn't be hard to enforce.

They become locations to film movies and tv shows. Conveniant views of london without need to close off a "public" area.

UUIDv7 is arguably better, because it is entropy plus time.

It is what I usually use for its sorting, but some people don't want to leak time info.

Entropy is not a requirement in the UUID spec.

OK, I had not considered just using GeoJSON for my flatland CRS (indoor routing). Quite obvious in hindsight, thank you.

I kind of agree with you, I would hazard that this is perhaps targeted towards folks (maybe TPMs, small business owners) who are using ai to start a software side business or make a website and have never bought a domain before or configured DNS.

I guess also; something that saves me 20 minutes a few times a year is still nice.

I think about 80-90% of the UK can order >1G broadband, fairly similar in most of europe, though some countries do lag behind. Realistically the number of homes with more than 20metres of cat5 structured cabling is very very low (much less than 1%). Typical new builds might give you a CAT5 from the utility cupboard to the TV and study if you're lucky. As such for now it's fine as 10G is 'OK' and even in the case the cabling doesn't support 10G, it should at least do 5Gbase-T.

Most providers are topping out at 2.5Gbps and big part of that is that you can't actually use even that much over Wi-Fi and anything >2.5Gbe consumer side is comparatively expensive/rare and no hard wired cabling in most houses anyway. So as such most ISP routers are 2.5Gbe LAN with only a few exceptions (https://www.choose.co.uk/broadband/sky/reviews/sky-gigafast-...).

Cat5e/Cat6 is extremely easy to work with and does 10G at 30 metres. I take the view that's enough for me on any one link.

I think there's probably two ways to address this.

1) Most likely we make self retracting reels, or just very easy cable/slack management and sell fixed length cables with a hard connector one end and a snap on connector the other end (https://youtu.be/6dop-9_0_g8?t=43&si=DdAXLMU_A7wTuCTn). That solves the problem of accounting for the plug in drilling holes. We could easily do this tomorrow on 2mm white 1f or 3mm 2f cable. This size is important as it is about the maximum you can just use adhesive to stick to the top of skirting.

2) we use plastic optical fibre and build a whole bunch of infrastructure around that. That is much easier to terminate, cut and safer to use but a load of work will be required.

I'm not sure if we'll see >10G over twisted pair/CAT but I'm sure we'll definitely see 5G and 10G baseT become far cheaper with 2.5G the baseline (e.g standard on cheap things like raspberry pi).

Base level Mac studio is already 10G as standard and it's only $100 extra on a mac mini.

Long time until 10G per device isn't enough at home.

I also doubt above 10G will be seen at least on consumer grade hardware, but until we start seeing SFP+ or similar on consumer hardware (and not just enthusiast and server hardware) there is a realistic chance. But that is so far out in the future making predictions on it doesn't make sense.

I love this and agree with it almost in entirety. One thing that would be good to retain is 'regions' e.g 3 DCs under 10KM apart linked with free/very low cost internal network. It is cheap to build in colo these days with the advent of campus XCs and ever lowering cost of DF, optics and 400G/800G switches.

This is cool! In my experience the absolute most important factor for performance is that we are able to hold the FIB in CPU Cache, and my reading of this is that at >250K prefixes patrica may use less space? Did you find this?

E.g with a CPU with say 256MB L3 cache lookups are many many times more performant because you don't need to check ram on many/any lookups. Hot top levels in L2 > hot path in local CCD L3 > rest somewhere in socket L3 > DRAM misses (ideally almost 0)