Javascript on suicide watch

Many packages suddenly disappeared massive issue for us because of this. Please resolve asap

@antoniobrandao It is possible. I have re-published some of the packages that were missing with the code that was available on git-hub. The original author has deleted his NPM account and dropped all his packages. But it seems like NPM keeps dropping packages. No idea why.

Not the first time this happened, there was a widescale issue due to the same reason (dev of a very popular package killed their repo because of drama or some shit, every site using the library, which was a lot of them, became outright unusable for a week or so).Or is it the same one?

try to do something with nodeeverything has millions of dependenciesdependencies have dependenciesit never endsI have no fucking idea how node ever got popular considering it's easily the worst thing ever.

Is webdev still fairly lucrative? It seems that every other day I hear loads of shit about it, and most of it doesn't sound good.The OP for startersSomeone shills a new framework or new library<"React has saved me so much time and frustration, will change JS as we know it 10/10"Some retard complains about a library not doing something the way they want it, usually follows that up with shilling something else that "totally fixed everything" instead of actually writing their own codeArticles upon articles in literally-who blogs that contain copypasted code that magically fix a problem without any explanation of how or whyTo me the the webdev/JS landscape sounds like it's too convoluted and fucked to put any effort into.

I didn't, but that doesn't really surprise me. I wish there was some kind of exploit that could be used to fuck over the modern web as we know it. Something really devious, something that would make people think twice about trusting every script that runs on their browser. If anything like that was found or is ever properly exploited, the framework of the nu-web would fucking implode. Wishful thinking, I guess.

Most probably wouldn't at first. I'd imagine they'd just throw their phone or laptop in the garbage and buy a new one like they always do when their device starts to slow down. In the long run they'd notice, although I'd imagine that would lead to devs getting sneakier with their miners.Would be funny as hell, but not that practical or impactful in the long run.

It's a new one, which makes the problem that much worse.npm have been scolded for this before, you can delete your package and your package name becomes instantly available to be used, perfect for malware.npm worked so that package must be the package right? Nope.

I know you're just shitposting, but the first thing I noticed about Lua is how close it is to JavaScript, but less shit. If only they dropped variables being global by default and had 0-indexed lists it would great.

Somebody looked at this an thought this is a good idea to have as an dependency with a readme and a full copy of the mit licence.Also in its dependency kind-of:[...]var type = typeof val; if (type === 'boolean') return 'boolean'; if (type === 'string') return 'string'; if (type === 'number') return 'number'; if (type === 'symbol') return 'symbol'; if (type === 'function') { return isGeneratorFn(val) ? 'generatorfunction' : 'function'; }[...]

Yes, kind-of just returns typeof for the types used! You can't make this shit up!

lua.org/pil/2.3.htmlThe number type represents real (double-precision floating-point) numbers. Lua has no integer type, as it does not need it. There is a widespread misconception about floating-point arithmetic errors and some people fear that even a simple increment can go weird with floating-point numbers. The fact is that, when you use a double to represent an integer, there is no rounding error at all (unless the number is greater than 100,000,000,000,000). Specifically, a Lua number can represent any long integer without rounding problems. Moreover, most modern CPUs do floating-point arithmetic as fast as (or even faster than) integer arithmetic.Wow this is top pajeet. Either go full high level and provide big integers like python or provide fixed width integers. Everything else is just retarded.

Yeah, i use lodash for this usually too. But, for work, we have a bulk import system where we need to write data transformation scripts and lodash isn't included with it.So at first I was, painstakingly, doing that shit manually.Now I just paste the following snippet in: fromDotNotation: function(obj, path) { var i = 0, path = path.split('.');

This is quite possibly the most useful thing we can do to improve the health of the internet.

And I like it, because this tactic has a proven track record. Infiltrating and attacking from within is quite effective, historically celebrated, and very difficult to defend against, especially when it comes from many different vectors.

We could fix javascript. By fix I of course mean destroy and purge all record of it's existence as punishment, while erecting a 50ft granite statue at the center of the world's largest landfill shaming the creators.

Yeah, but it is still confusing to look at. Old Man Crockford is right when he says that, when writing code, you should avoid confusion above everything else (sans the code working properly, of course).

I highly doubt that it will work second time. After left-pad fiasco npm changed rules for removing package (now you can't if someone depends on you). And with their security tools (there was a minor fuckup caused by them recently) you probably will not be able to change it to something malicious.

Confirm your age

About Privacy

We use cookies to personalize content and ads, to provide social media features and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners.