Minor correction, registrations are never free. Come 2019-02-28 16:00:00Z, they will be available at the base price. Registrars set their own prices, so depending on which registrar you're using, expect that to be around $12-20/yr (including the initial year).
Free in the sense that there is no initial up-front cost (compared to the pre-sale pricing). Everything else is an initial dollar amount ($11,500, $3,500, $1,150, etc.) in addition to the $12 maintenance cost. After February 28th, there is no up-front cost but there is still a maintenance cost.
Treehouse used to do 4/10s and from what I remember listening to Ryan Carson's podcast with Jason Calacanis, it didn't work out for them. So I don't think this should apply to every workplace. For more mature companies, it makes sense. For startups, I don't think so.
Treehouse’s abandonmnent of the 4-day work week suspiciously coincided with their taking on a Series B round of funding. I’m implying they were pressured to drop it by investors. This was followed by significant layoffs.
Furthermore, no formal analysis was done of the Treehouse experience.
Nothing conclusive can be inferred from the Treehouse experience until/unless they release data and a rigid analysis is done.
To be fair, I have both 2018 MBP 15 (work) and 2015 MBP (home), I notice the weight of the 2015 a lot. Performance has been relatively the same - hasn't been mind blowing if I'm honest.
I really do hate the new keyboard to the point where I simply don't do any dev work until I plug in my dongle with my screen/keyboard. It's really that bad. The touch bar has been useless as well and more of an announce sometimes, especially when it would freeze randomly.
I experienced this at a small cyber security business. They didn't pressure but they REALLY insisted that we review them on GlassDoor in order to get more people to apply for the jobs. In reality, their problem was they were paying ALL the staff compared to the market average.
What is happening is that all of the stuff that I have been explaining in the "Local fix" section for a decade and a half, alongside the practice that clients had of timing out and then retrying the transaction without the extensions, is now being declared moot. If DNS lookup does not work because of this problem, it is being declared entirely the server-end's problem. Clients are no longer going to be expected to put such local fixes in place, or have timeout and retry bodges.
As someone who's been required to maintain bug-compatible software before, this fills me with great joy. Congratulations on getting to deprecate the brokenness!
EDNS is basically DNS2, and it has better support for handling larger messages (needed for DNSSEC and such), and EDNS itself is about signaling what features you support.
