Now that I started looking for it, I think it was Repton because I remember buildings.
I think the crack protection was pretty clever - it let you play a couple seconds of the game to get a taste of it. If I had the means I would have bought it, but I was a poor 14 year old
I think that this cartoon was a play on a booklet from that era which the electric company gave out. It illustrated the grid and all kinds of possibilities around the home and farm for those who were not used to electrification. My dad had kept it around and I remember reading it when I was little. It had all the wiring plotted out like a Richard Scarry book. I have not been able to find it since.
I'm glad to see someone else describe their experience this way too.
bazel has arrived at $WORK and it has been a non-trivial amount of work for even the passionate advocates of bazel. I know it was written by the Very Smart People at google. They are clearly smarter than me so I must be the dummy. Especially since I never passed their interview tests. :-)
Of course given all things google, by the time I'm fully onboard the train, the cool kids will be making a new train and then I'll have to hop onto that way to enjoy the rewards of the promised land that never quite seem to arrive.
> know it was written by the Very Smart People at google
For Google. That's the key. I have the privilege of experiencing both sides, having been at Google for nine years. I never had a problem with Blaze, but using Bazel in a smaller company has been extremely painful. I think there are just very few places that have the exact problems as Google where something like Bazel would be a great fit.
That's the rub. It provides scalability for very large organization, of which, there are few. It's similar to running OpenStack. Meta also has some projects like this, such as buck2 which lacks the really good virtual FS acceleration stuff (eden). Megacorp FOSS tend to skew towards offering whizbang features that are incomplete, complicated, poorly documented, and require a lot of extra work.
Actually if you could make something like github, where all software would be part of a single megarepo and built constantly that would be incredibly useful, and bazel would be excellent for that (or at least the closest thing we have to reasonable)
The problem with bazel and almost every other build system (all except the "scan the source files and build a dependency graph" ones) is that you'll be writing build instructions for all your dependencies that aren't using it. If that was done for you, they'd be incredible.
Compiling things and wanting a robust build cache so developers spend less time waiting isn't a problem remotely unique to Google. You might not have Google scale to hire a team of developers to be able to optimize it to the N'th degree like they can, but holy shit we are not gonna use Makefiles for advanced build systems anymore.
> Compiling things and wanting a robust build cache so developers spend less time waiting isn't a problem remotely unique to Google.
That wasn't my argument at all. Plenty of modern tools address this exact need; it isn't unique to Bazel. If you read the article, the author made many interesting remarks on how Bazel reflects the unique design choices of Blaze, which were often picked due to Google's needs.
My point is that when people hit these barriers, they need to understand that it's not because they are unintelligent or incapable of understanding a complex system. That's what the OP I responded to was saying, and I was just providing some advice.
While Jefferson is an understandably venerated figure in the foundation of America, he was not active in the creation of the constitution. He of course wrote The Declaration of Independence and while having misgivings about the strength of the executive branch, he went on to become a hugely influential president.
On the filp side, it took him a while to come around to see the folly that was the then French Revolution whereas his political critics - notably Adams, Washington, and the frequently maligned Hamilton, were quick to keep their distance from it.
I like Jefferson but he sometimes seems to have an overly rosy and romantic view of revolutions. Tearing down is easy. Building up is very hard.
https://www.thefp.com/p/google-memo-james-damore-vindication...
Basically he has kept a very low profile.
reply