Personally, I don't think its possible to even work in your 100% capacity with WFH. Some might think that focusing extra hard on your work while ignoring the noises and family feuds will help but the long term toll it takes on your mental health and the amount of stress it builds is devastating.
But (without intending to spread unsubstantiated rumor) it seems like it's temporarily unmaintained at the moment:
- in the README.md there is some complaint about being difficult to reboot into a Linux dual-boot, maybe the measurements+website were being published manually
That issue appears to be someone who was upset with the methodology of the benchmarks and the delay in accepting his/her programs so they resorted to repeatedly changing the title of one their issues.
Mixed success. For google it has been somewhat a failure but the business model for disrutpion was exported and a few companies have been able to take root.
A few weed like companies (resiliant but too small) have popped up to cover how the landscape never really changed.
That's exactly what any CEO or "Downsizing Consultant" would say. That may be an OK situation for a corporate company, but for a non-profit foundation like Mozilla, its unhealthy and rings some disaster bells.
First of all if you use querySelector or querySelectorAll for everything your code will likely be smaller without jQuery, but it will be just as slow.
If you access the DOM with string parsing your application can be anywhere from 1200-10000x faster. It will be more verbose, but certainly not as much as most people fear. If you are good with scope and abstractions you will solve for most of the verbose DOM interaction with reuse and custom abstractions.
So really dumping jQuery means choosing between smaller code or substantially faster code and both are a win.
Opinions vary on that one, does a footprint reduction by 90kb really matters in the day and age where megabytes of bloatware like angular, react, vue, etc. goes unchecked?
If adding 90kb helps me write `$(document.ready()` instead of `window.addEventListener(DOMContentLoaded)`, I'd rather add that because making code more intuitive and readable is what software engineering is about.
I prefer to assign events handler's directly to node event properties instead of addEventListener. The only advantage to addEventListener is that you can plug in a bunch of marketing spyware nonsense without worry that its going to clobber your event assignments.
I need a simple seo tool to find keyword rankings and check backlinks without going through the complex routine of google adwords or costly keyword platforms. Will you be able to build such a tool and make it open source?
Off-topic but medium has almost turned into a paywall these days, it won't allow you to read more than 5 articles without subscribing to their paid service. Should HN and Google be promoting such a walled garden, especially when creative commons content is found aplenty on the interwebs?
They kept bugging me to log in. When I did, they started throwing things about limits around. So I deleted data related to the site and never log in. Since then I get to read as much as I want.
