I think you are wrong since this people die of this exact scenario almost everyday. The camera might be making it darker but that doesn't mean that every driver (Everyone's eyes and reaction times are different) would have been able to see her and get out of the way.
Running sites that large, even for something simple, cost a lot of money. Unless it is funded by a wealthy benefactor or publicly funded there is no way that it will every work. It's obviously not a technical problem but a funds problem.
Most of the time you have to write metrics into the code (and have a place set up to collect the data), that alone is a step a lot of places don't do or don't do enough.
There might also just be the ability for the developers to understand what actually went wrong. I think the guys at Epic spent a lot of time building their system so they can understand it and I'm not sure that PUBG developers started out with that in mind.
I think you are right, go is not the best language for your project, single threaded just moving blobs of data around node is a good solution. I'm not sure why anyone would have a problem understanding that. (And I'm a guy who hates node but loves go)
Tuning is part of the job if you need high performance. It can take many forms from code optimization, build flags, platform configurations, to even hardware tweeks. Most people hate this kinda stuff but some of us think it's fun.
Personally I have found I was more annoyed with forms not allowing me to autofill before the change than times I have seem chrome fill the wrong fields out after.
Whatever you say bud, I think most people on this forum are stuck in an echo chamber which of course makes everything seem more important then it really is.
I don't work at Microsoft, I just like that the Windows works more than I do Linux. I use Linux because that is what we release on so I guess I don't fall under "Linux Nerd"
The argument that people always throw at me is that too hard for people to know two languages, well, for frontend devs to know two languages. Now in a perfect world the frontend people who just can't figure out two or more languages would never touch the backend but the world of software now is "that'll do" not "what is the right tool." It's a shame to me really but I'm not a frontend dev for a reason.
Article is about digital cameras, not phones. The article indicates that there was already a decision about cellphones and that it applies to cameras as well.
Processor is a little more powerful, testing shows them comparable in some testing since Apple can tune the chips a little more then Dell is allowed to. I have twice as much ram which is the real big leap forward, my hard drive seems to be a little faster also.
My real life side by side test show that turning off my machine at the end of the day isn't a big deal. The fact that I can run 2-3 VMs when the rest of my team can barely run one is a big deal. More ram is a huge benefit, everything I run in the linux subsystem runs faster than the macs I work next to.
I use the XPS 15 in an office with only mac users and this machine is just more powerful since Apple wont update the Macbook Pro line with developers in mind. I hated working on an under performing laptop when I was using the macs.
I've been loving it for the past couple of months. I boot into Win10 and use the ubuntu sub-system to build everything. Upgraded to 32gig is the biggest boost, I love the extra headroom. One this to notice is that I have not been able to charge from the thunderbolt port when almost everything I hear about it seems like it should be charging fine. I have the TB16 w/ 240W supply and still wont. This isn't a huge deal but it destroys the dream of a single cord desk setup.
Yeah each build would take about an hour, 4-5 hours for the whole CI/test to get finished. It was crossed complied so there was an MSBuild and a gcc build. It was sone in serial since we didn't want to waste time building the release if the testing or QA builds failed.
Generating the code leads to a lot easier debugging for me. In C++ debugging generics are annoying to put breakpoints in, since it is harder to hit the exact implementation I want (VS has a way to do this but it is a little annoying to get right). I don't mind doing that because all too often I've seen a 'generic' implementation gain more and more flags to make it less and less generic. I've only ever needed to do that a few times, the built in containers cover 95% of what I need. I came to go because I was formulating an opinion of c++, java, javascript etc and they aligned very closely to what the main team of three guys were talking about when they were first releasing it. Most of the time I never scale the application but I still love the way to solve problems in go, especially when I'm doing something in a concurrent manner.
I've also had a large (5M+ lines) C++ project that would need to be complied 3-4 times to do things like CI and automated testing. So each build taking 1-1.5 hours, which is not crazy, because of rebuilding code that is static 99% of the time mean that it is worth it to me.