I've seen tens of thousands of lines of code compile in 30 minutes.
I've seen a hundred thousand lines of code compile in 2 minutes.
It really depends on how the project is laid out. If you're using lots of header-only libraries and try to compile monolithically (like soooooo many C++ applications do these days), you're going to have a bad (compile) time.
CMake helps a good bit, ccache goes further, and ninja helps a bit too. But none of them can help templated header-only libraries with complex interdependencies. It gets particularly bad when the developer #includes a convenience header to bring in _everything_ in the library instead of just what they need.
Agreed. Good use of PImpl when you have large external header-only libraries is also generally recommended to keep the dependency graph nicer.
Also from what I've seen, large header-only codebases tend to be external and thus generally don't change that much, so if you can limit your own internal dependency tree ccache can still save you.
I use Azure all the time (app services, storage, cloud services,VMs, SQL, CDN etc) and almost never run into this issue. Can you share some example on what you mean?
I use all that stuff and constantly run into it, are you using it in anger?
Here's a few I can remember off the top of my head:
- A (relatively) huge 6ms lag between the website and the DB
- One (random) site will mysteriously max out on memory on app-pool startup and take all the others down
- Their scheduler has no concept of timezones
- Their scheduler uses your local time when setting up the job, but UTC for other parts (this has been an open issue for over a year I think)
- Files will get mysteriously locked in deployments and the deployment process will silently fail
- Deployments will suddenly take an absolute age for no reason
- The entire admin UI will slow to an absolute crawl for hours on end
- Some admin tasks always claim they've failed, even though they've succeeded
- Their API wrapper is just wrong on almost every level
Add on top of that the worse management UI I've ever had to deal with and it makes Azure very painful to use at times. Some-one thought nesting menus in a standardised format was a good idea. It wasn't. Everything is fairly terribly named too. Want to see how your deployments doing? That's under "Deployment Options".
Performance is also dogshit compared to the cost, my 4 year old laptop is faster than their "premium" offerings.
No I'm using it happily. We don't use the scheduler and create new deployment slots when deploying (which maybe prevents locking issues). Sometimes I experience oddness in Azure portal and has to refresh but has never had it slow down. As for SQL latency it's been insignificant to us so I'm not sure if what we experience is better or worse than yours.
Portal i agree is partly confusing/messy but we set up things once and then do deploys via CI infrastructure. And even the initial setup we try to automate using PS instead (to make it reproducible).
When it comes to pricing I agree, but my laptop does not do multi-datacenter so well.
Im not questioning anything you say of course. Maybe I've gone blind or don't see the issues as critical as you, or maybe I'm just more lucky.
I'm not agreeing with the assertion in this case, but there are very different standards for people "of public interest" and ordinary common folk. This distinction is made in a lot of places, including European privacy laws e.g. in Germany.
There is a photo floating around that might be Kim Wall in the tower of the submarine o̶n̶ ̶F̶r̶i̶d̶a̶y̶,̶ ̶d̶u̶r̶i̶n̶g̶ ̶d̶a̶y̶l̶i̶g̶h̶t̶ ̶h̶o̶u̶r̶s̶.̶.̶.̶w̶h̶i̶c̶h̶ ̶w̶o̶u̶l̶d̶ ̶b̶e̶ ̶o̶d̶d̶.̶[1,2] That doesn't imply girlfriend though. Could also be that the "Friday" was a mistake and the picture is from Thursday.
That's if the installer is designed well and all the questions are front-loaded. Unfortunately not all installers are... Heck, I think it took Microsoft until Windows Vista to do it for the OS.
Thats an odd way to phrase it considering v1 was released 15 years ago. Like saying I've spent almost half of the last 10 years with my 4 years old son.