idlemind

Check out api.tfl.gov.uk which should have everything you need for London in a more structured format.

Also a great teaching language, as used at London Imperial College Electrical and Electronic Engineering dept. in the early 00s. Gave you lots of power but not too much, and enough rules to force you to learn without doing mad things. I have fond memories. And I miss the compilation speeds!

The problem is people buying cheap devices that skirt or fake existing battery quality regulations. There would surely be a higher number of people making that kind of purchase if they were to be allowed on UK public roads.

I can’t see how anyone would be made safer by decriminalising scooters - either charging them at home or out on the roads.

Also you can mostly still click straight though to the image file itself, a feature which I believe Google removed at the request of site owners.

Sunshine is the other big variable. Most fruit will only get sweet during ripening if it's receiving enough sunlight. This is why red grapes are seldom grown in northern latitudes - their dark skin blocks sunlight and prevents them from sweetening during ripening.

Article is from 2015. Should this be added to the title?

It’s not in particularly common usage anymore though, if at all.

I'm guessing they don't do this voluntarily because they've seen how the music industry had its revenues eroded by Spotify/iTunes (where mostly the user can pick one and get pretty much everything). They're probably ignoring the fact that music piracy is presumably lower than ever because of this.

Was hoping someone would say this. Times by 8 divide by 5 is super easy. And easy to reverse when you’re doing km to miles.

A lovely tribute - and please take this as constructive criticism nitpick - but it would be even better if the Readme was in markdown so that GitHub would render it correctly on mobile.

Our build system very much needs to be on-premises for the foreseeable future.

Yes I got that impression. Azure DevOps wouldn’t be the right solution for us unfortunately.

It’s nice to see the .NET Core team hitting on the same solution as we are heading for internally for our multi-repo builds - the “dependency flow” with Maestro sounds very similar to what we intend to do with propagating latest NuGet package versions to consumers via PRs, then auto-merging those PRs if all checks pass (and the repo owner has opted into this, of course).

Will the .NET Core team open source this tooling I wonder?