Some CPU heavy operations like crypto are not put in a threadpool. While it may be running C code, it will block the main thread while executing. See https://github.com/nodejs/node/issues/678
Perhaps the new worker threads may alleviate this, but I'm not sure (it's still an experimental API).
Why is the 16GB RAM + FHD screen (1080p) variant not available in the US and Canada? It seems like this has been a long-standing issue since at least the 9360.
This is very frustrating since I don't need the 4k panel (in fact I don't want it for resolution scaling reasons) however I absolutely do need the 16GB of RAM.
What's worse is the 4k screen is a touch screen and very power intensive. When I looked a few months ago it took the expected battery lifetime from 20 hours to 12 hours. What's worse is that also meant you got a glossy screen instead of a matte. I passed.
I hope you're right, because I've tried and failed to create such a configuration on the website. Would you mind providing a link to a RAM-configurable 1080 model?
EDIT: Found it, and you're right! You have to start with the i7 rather than the i5 on the product home page, but yes, it's there! This is awesome -- never really used the 4K or touch, and could definitely use the extra battery life. https://www.dell.com/en-us/work/shop/dell-laptops-and-notebo...
Sorry the majority of the troubleshooting and management bits are all in python. You can even get a bash shell on an Arista if you want. Quite nice hardware.
This is fantastic! The biggest standout feature in my opinion is workspaces. I've been using workspaces on a client project with many sub-projects and it has been a pleasure.
Shared modularized code without creating private npm packages or doing some "linking" magic has been wonderful for productivity.
It's as simple as creating another local package and symatically everything else has remained the same as a regular npm package, plus the benefits of having immediately updating code. For anyone with a large modular codebase wanting to forray into a monorepo approach I highly recommend checking it out. They also released a blog post here detailing the feature: https://yarnpkg.com/blog/2017/08/02/introducing-workspaces/
How are people handling CI/CD servers/services with the mono repo?
The barrier to mono repo seems to have always been the need to create massive amounts of bespoke tooling to handle the build pipelines(how do I build just this proj?, how do I run tests on just this proj?, how do I build just this proj and its deps?, etc). These are totally solvable with dedicated dev resources, but these are typically the problems you try to avoid rather than spend time on at a lot of companies; say < 1k engineers(snark).
Workspaces and Lerna seem to be a small piece of the puzzle even if critical. Are there tools to help out with rest? For instance if I'm using Bitbucket pipelines, what should I be looking for to help building from a mono repo?
Subversion used to let you check out a subdirectory of a repo, which generally helped with this problem. The chapter on SVN in Beautiful Code does a great job of explaining how this works and why it helps with concurrent access to the repo.
This is a giant blind spot in Git, and none of the proposed workarounds come anywhere close to the tiny cognitive load of svn's answer to this problem.
But nobody on the git design committee seems to give a shit about cognitive load, so I'm probably just shouting into the tempest.
