4 ms·
> I don't know why you would expect to find npm modules that can get the job done 100% for you all the time? Get the job I'm doing done 100% of the time, do th
by noir_lord 11y ago
> I don't know why you would expect to find npm modules that can get the job done 100% for you all the time?
Get the job I'm doing done 100% of the time, do the job they are supposed to do 90% of the time I'd like that, constant version churn, API changes, strange incompatbilities between things that are supposed to work together not to mention stuff like browserify/watchify which when they work are great and when they don't a complete pain.
Also makes me chuckle whenever it throws a ENOENT not because I don't know what it is but that a high level original browser dependent language is throwing it and not "No such file or directory" or anything friendly.
npm/node reminds me of the implementation of a server side scripting language implemented solely in JavaScript written by people who have only ever heard other server side scripting languages described to them on a broken radio.
- notNow 11y agoAgain you're lashing out at JS due to your experience with node or npm which none is part of the language itself. That's like someone after ordering a regular Big Mac meal (burger + fries + soda), he complains that the dessert portion of the meal either sucks or there are too many options available and some are not optimal enough when actually there was no dessert included in the meal in the first place. Can we get real for a moment here? npm/node reminds me of the implementation of a server side scripting language implemented solely in JavaScript written by people who have only ever heard other server side scripting languages described to them on a broken radio. 'Everyone is entitled to his own opinion, but not to his own facts.'
- noir_lord 11y ago'A witty saying proves nothing.' - Voltaire.