It doesn't make sense to require a backend tool for frontend technologies. That's just me though. So that's why I'm asking. Couldn't they just create a package system that's not based on some backend tech?
I get NPM for backend development but I don't understand why frontend developers require NodeJS just to utilize it's package management. It really does not make any sense to me considering that NodeJS is server side javascript. If my backend is Python or Go or .NET or Java or whatever, now I'll need NodeJS for the frontend and only for NPM (and now this). It's a reason why I don't enjoy dealing with "modern" frontend technologies.
I blanket block every ad (or whatever the list currently has). If a site has ads, I'll manually block those too. I'll go into their code and find their ad service url and add it into my list. I'll do whatever it takes to remove them, regardless if its simple or not. I do not want to see them and I will continue to visit those sites. I just wish a good adblocker would come to mobile because I'd use it there as well.
That's cool. I never said I wasn't affected. Just that I don't click on them. Ever. Like I said, I'd go to amazon or drive somewhere before I click ANY internet ad. And thus far, I have never clicked on one... willingly.
And I respectfully disagree. I don't enjoy ads, I never click on them even if the item is something I'd use at the time, I will not click on it. I'll just go to amazon or whatever and get it there. I will never, ever click on an ad. So I'd rather not even see them.
Wouldn't that just make the code more confusing? You'd get some random name that doesn't mean anything to what its intended purpose is. Keeping the simple 'a-z' scheme the beautifier does allows people to not use the variable name as a descriptor of what it handles.