Pat Metheny has done something similar with his orchestrion project, 12 years ago (https://www.youtube.com/watch?v=KsYEOUKS4Yk). At the time I went to see him perform with it in the Concertgebouw in Amsterdam, which was impressive, but still missing the band energy that normally makes the music come alive. He did mention that it was the first gig on the tour without major technical issues, it does seem like a nightmare to set it all up correctly.
It's a sad moment for gamers. He started working at Sharp, where he sold solar cell and light sensor technology, but he's best remembered for a long and highly influential run at Nintendo that effectively revived the video game industry following the 1983 crash.
Language inserted into the 2021 Intelligence Authorization Act gave the government 180 days to gather and analyze the data it has collected, and to release a report on the findings.
Why is everybody always so concerned with developer time, but never with user time? The author of this tool even complains about the startup time of photoshop, but somehow has no problem with building a tiny tool on Electron. The irony is quite strong here.
That sounds reasonable, until you have to debug an issue that only manifests itself when working with a huge dataset, in which case the whole thing becomes pretty much unusable. As the article says, debug mode is expected to be slower, but the difference between MSVC and the other 2 is just crazy.
Back in university I had a side job as a security guard in an office building, when this happened. Someone took the cargo elevator, which was built to carry a higher load than the regular elevators, so it had a massive counter weight. The thing slammed into the ceiling with a bang that could be heard through the entire building, and the damage was quite extensive. Took a while for the guy to calm down as well.
Yeah, I can understand preparing for the job itself, e.g. brushing up on your financial knowledge when applying for an HFT job or something. But interviews and actual jobs seem to have diverged to the point that there is now somewhat of an industry around 'preparing for the tech interview'. It's almost like a new branch of science.
Sean Barrett (who I think popularized the idea) has a FAQ on this (https://github.com/nothings/stb) where he justifies it by pointing at difficulties with deploying libraries on Windows. Which is a fair point, but by going straight to header-only he skips the step where you can also just distribute a bunch of headers and .C files. The convenience of only having to include a single header is nice for quick weekend projects, but for anything bigger you're dealing with dependencies and build issues anyway.
I get some of the reasons that you would initially start out with a header-only implementation, but when your library grows, you probably want to split it at some point. For me personally, that point would be some time before the header reached 25k (!!) lines.
If this line of thinking ever takes off, it will be just another one of those meaningless rituals you have to go through to signal that you're part of the club. Polish your resume, dress up nicely, read 'cracking the coding interview' the night before. There might actually be a great idea for a new book in there: "How to fill up your GitHub account with random crap so future employers think you're really really passionate".