Node 2 Incoming!

He looks like a cokehead these days.

LOL

Simple. Make your web server check if the ip that's downloading is from a datacenter. If so send the vulnerable one, else send the clean version.

Is there any reason in particular why that's more of a problem in that situation than in the usual situation where you install packages on deployment?

I feel that in practice you would just import stuff from CDNs.

Just like you don't just copy a link from wherever and paste it on your HTML, you usually just import stuff from CDNs.

Because package are apparently not signed

Using node ever since 0.10.
Even IF deno comes to fruition, it won't be able to get any traction.
Node is too big and too liked to be able to be replaced by something only marginally better. It will all boil down to how much companies would be able to save by migrating from node and how much that would cost. As it stands, it just wouldn't pay off.

If we pretend Node doesn't exist, it'll go away.

Cancer.
Either POSIX scripting or a programming language.

...

Last time I heard python is scripting.

POSIX is insane and barely suitable for scripting unless you extend it.
Scripting languages can be programming languages.

You are an imbecile.

why is the tech field filled with these zealots that must argue basic facts? it's like arguing with a sjw or worse.

It's reasonable not to call sh a programming language, because it has severe limitations that make complex computations in it a pain.
It's reasonable to call Python a programming language, because it lets you express any computation you could express in a language like C without much more fuss (and usually with much less). You can write full programs with it, they just won't be very efficient programs.

That doesn't mean it's not a scripting language.

I guess it will be like this. Inertia is just too strong in the IT world. It takes too much time, resources and effort to change some system already in place and being used by people who got used to it. If there's no huge benefits to change, companies will just shrug and keep what they already have.

Attached: 1470971213448.jpg (475x364, 23.64K)

That's why GCC makes optimization assumptions for CPUs from 2000 when making generic 64 bit x86 code.
They should up that a bit, 2004 would be a nice starting point but nobody is using those weird as fuck 64 bit steppings of 32 bit processors anymore. Make assumptions for 2009~ CPUs instead and you'll benefit both 10 year old systems and current systems without touching early 64 bit CPUs too much.

What's wrong with TypeScript?

Or Kotlin if you don't like Python 3

Too JS-like

literally worse than even js
Python 3 is one of them

Many flaws of the JS are still there for compatibility reasons.

The efficiency should be measured on real workload, and if the slowdown is measured in fractions of a percent, then it's obviously not worth dropping the benefit of using "easier" language.
For many tasks they will be actually efficient.
And even for some number crunching tasks: a typical example is github.com/magicgoose/simple_dr_meter/issues/4
Not sure if ffmpeg guys catched up yet (I need to ask the author to test again or do it myself), but a piece of python code which calculates the same thing was consistently faster when compared to ffmpeg, which is written in C and was compiled with full optimizations. It would not be possible if what you said was true, right?

Because said Python is neither POSIX scripting nor a programming language, it was saying Python wasn't a programming language. The rest of the subthread was about that claim.

I meant efficiency in the simplest sense - efficient use of memory and CPU time. I agree that that's not a useful metric to decide whether the language is appropriate to use for a task.
Your example is cheating by using numpy. There's nothing wrong with that, of course - I love numpy - but it doesn't tell you much about the speed of Python because it's really just Python wrapped around C, C++ and FORTRAN.
A better example would be an I/O-bound program. youtube-dl isn't going to get much faster whatever language you write it in, because it spends most of its time waiting for data to arrive.
Most code I write is Python.

Kotlin, Swift, Go, Flutter, Java, C# or Objective C.
Or on a more serious note, Python 3/4 or Perl 5/6.

Underrated post. Fucking money worshipping jews screw us once again

Nobody actually believes that soibois write code.

Why not purescript then user? It works on the front and backend.

At a glance, it looks like it's easier to teach Purescript to people who already know Haskell than to people who already know Javascript.

But why would you ever want javascript developers?

Same reason people want C programmers.
As awful as the languages are, they get closest to the way the runtime Really Works™.

I'm interested in Zig Forumss opinion on Node.js
I've never used it but I've read opinions describing it as the worst disaster in decades to hit the field of application development and programming in general.

Attached: nodejs.png (600x225, 21.61K)

w.r.t. application development I'm thinking of Electron apps.
But I've seen criticism of it for server side stuff too.

snekfags btfo

Actually this.

And this.

...

Javascript (ES6) actually has metaprogramming.

oh great more webdev garbage
if I am made King by Divine Right I will execute every single last one of these greasy javascript niggers. javascript is satanic cancerous niggerware

The best invention since orgasm, tbh.

Node really isn't that bad. It's the webdevs that think that they are real devs that is the disaster.

Yeah no thanks.

This. Deno is Node with slightly less HIV but it's still HIV+ so who gives a fuck.

import { test } from "unpkg.com/[email protected]/testing.ts"
Specifying the version at every import will make dependency updates really painful, but I can understand wanting to get rid of package.json (and npm)

Yeah well I'm still cumming over C++20

Well it doesn't have macros and it still doesn't have an integral data type separate from "Number"

why?

TypeScript and JavaScript are like C++ and C.

Attached: never-google.png (838x846, 294.08K)

Every Plan 9 larper ended up either being dead or working at Google, not just Pike. I'm not a Lisp faggot, but I'm fucking 100% sure the whole Unix paradigm spawned this SaaS and cloud "service" kikery because all these people had a literal baby duck syndrome and refused to develop personal computer software because they were used to using mainframe from a dumb terminal, be it AT&T UNIX, Bell Labs Plan 9, or Google mainframe. Consider it an extension of same oppressive sociopathic conformist Silicon Valley cult. Microsoft, blame them for thousand years, partially escaped this cancer in those years because they constantly moved cities before settling in Seattle and Redmond.
Also the quotes are from this site for those who are interested:
usesthis.com/
It's full of "coffee shop Macintosh transvestite WWW developers" as youngsters would say, but has a nice batch of free software and hardware developers's interviews including Stallman and Torvalds.
Here is an example of your average Intel engineer: usesthis.com/interviews/bo.adepoju/ :^)

Big computer =/= mainframe. UNIX is not mainframe system, but minicomputer one: portable, without focus on specialized proprietary hardware, with loose coupling between services - which is opposite of mainframe culture
Cloud kikery is direct descendent of mainframe business practices. Company could buy PDP and do whenever the fuck they wanted with it, IBM was rental for all but largest clients, with every fart being billed separately.
Today personal computer is closer to minicomputer in design and functionality, than to what was considered personal computer then.
Because they targeted low-end platform for which such basic things as MMU were luxury.

Attached: 14233534210010.jpg (1024x768, 136.64K)

Sauce on the wallpaper?

Kek, saved.hope he has GRIDS too

He's right. There's no reason our networks are not distributed and reliable without trust.
I think it's absurd that the left side boasts about Plan9 but uses those quotes as negatives. As if distributed computing wasen't the entire point of Plan9. You should have the power of big irons on your phone, there's no reason you shouldn't. The device itself need not be that strong, you just need to be able to cooperate with one that is and that's 100% possible to setup and use practically, since the fucking 90s but we still insist on building 1 machine per person, while not utilizing them effectively.
When you really consider how much computing power is out there and how much is used, it's ludicrous.

Say what you will about Plan9 itself, in concept it's good. And that's all you can ask from a research OS. Even if we're not using Plan9, we should be using something with the same ideals. I can't see anything wrong with remotely aggregating resources and abstracting away the concern of if it's actually local or not. If I have access to resource X, I should have access to it on every machine I interact with, without having to manage the state myself, the system should take care of all of this.
Maybe when companies run 1 giant cloud and ask you to use it. But this is not that, this is you setting up or joining multiple clouds, and making them interoperate. Maybe you host an entire machine, maybe your friend John lends you his processor, maybe you pay Google for access to a disk pool. In any case, it shouldn't concern you more than the initial setup. You should only have to worry about how to authenticate with the network. A network that doesn't have to be inherently centralized and shitty as it is now. A network where losing connection to said networked resources, is unlikely.

I cum pretty easily when there's updates

Javascript (ES6) has Macros and ES2017 has int32, int64, float and all the standard numerical types.

This is the reason why I use a laptop as a personal terminal device for input and display. I have a personal Lignux server that's intended to carry out batch computations.

It has neither of those things, you liar. Sweet.js can be used for macros, but that's not part of javascript. Typed arrays allow you to store arrays of integral or floating-point types of various sizes, but there is no primitive integral data type. Rather, there is just "Number."

Pike's about a week from cutting his penis off for progress. Hail Theo.

Theo is a swap german and a cloghumping virgin cuck rat

It took node almost a decade to be not-shit

The cuckening

JUST

Is he planning of deprecating npm support? b/c that SJW-infested hive of horseshit needs to expire.