1,730 karma · joined June 10, 2010
It does have some features to facilitate CI and testing at scale, e.g. `plz query changes` can be used to find a minimal set of tests to run for a PR.
We'd also tried Gradle previously but that was pretty awful for anything non-Java which made it a non-starter.
To be clear, I'm one of the original implementors, although I imagine that was obvious already...
(I'm one of the original developers, but these days do less maintaining of it than tatskaari does)
There is even an app for this, in case you're out and need to know which is the nearest to you: https://play.google.com/store/apps/details?id=lbc.app.com
This is solvable using arbitrary-precision decimal libraries, but relying on one of those for just dealing with general time stuff is a Bad Idea.
I don't agree with the kind of always-on DRM that's led to this, but I don't think full refunds for everyone is a reasonable solution either.
It's still not hard to stand on any of the trains as long as you're not right beside the door on a Tube (unless you're extremely unusually tall, but the odds are well against that).
I don't agree about DRY; the whole point is that the data has not been adequately provided until you see it. You do see people with apparently great CVs who are unable to demonstrate the skills in person.
I mean, the point of the article is a little shocking, but it carefully doesn't mention the commute time, which appears to be the thick end of 7-8 hours per day (2h 30 flight each way, and Stansted is not exactly in the heart of London). As a result, there's no shortage of people paying London's high rent prices. I'm one of them, and I wouldn't trade cheaper rents for that kind of commute (or, honestly, even commuting for 1-1.5 hours from the many towns outside London where such a thing is practical). So why does London need rent control?
In fact, I'd argue that you very often have to use RAII with exceptions, since there's no 'finally' block on a try-catch statement and hence it's the easiest way to ensure stuff gets cleaned up (well, except for catch(...) and rethrowing, but that's kinda ugly).
Although it is still possible to make it faster by overallocating in the same way as std::vector, but at the cost of more memory use.