Slashdot Mirror

Can web browsers do UDP from their sandbox these days?

https://nodejs.org/api/dgram.html

BTW, I'd really like to know why the Debian people decided to rename NodeJS to just Node. It took me quite a while to figure out why NodeJS didn't exist after having installed the package. Renaming the main executable for no damn reason will do that!

The Node.js folks also call the executable node, so, um, maybe they use Debian too?

PHP is almost exclusively used on Linux and is restricted to web development

What a crock of shit. Both PHP and JavaScript can be used in non web development. Just not many people do because there are other more established/efficient ways. But can you do it? Yes. Should you do it? Up to you. Enjoy the freedom to do whatever the fuck you want with whatever language you want, even if it doesn't make sense. If you are having fun who cares. If you have to work with a bunch of people use what you all know that gets the job done the easiest. Everything else is just pissing into the wind, making it difficult for yourself and everyone else standing behind you.

wget -O- https://example.org/install.sh | sh

is a very common installation method presented by various tools (or via curl). In most cases you even need to run them as root due to the fact that the creators of those tools do not understand how to have their software work as non-root users.

For example:
https://toolbelt.heroku.com/de...
https://docs.docker.com/linux/...
https://nodejs.org/en/download...

He was using node.js (which using V8 Javascript engine)

And he was using it for some security related function (in this case generating id's of sessions).

Maybe he should have been using a cryptographically strong pseudo-random generator:
https://nodejs.org/api/crypto....

Why did they need to 'fix' V8 Math.random () function which everyone knows is not meant for such things ? It even says so in for example the Mozilla documentation (the organisation that created Javascript in the first place):
"Note: Math.random() does not provide cryptographically secure random numbers. Do not use them for anything related to security."
https://developer.mozilla.org/...

This makes no sense to me.

You assume that Javascript is front-end That is no longer the case

Irrelevant to the topic at hand, JQuery (and front web development specifically which is the article's theme.)

This is like having a discussion on C/C++'s direct memory management and then drop a retort saying "you can get automatic garbage collection" with a link to Microsoft's C++/CX. #duh

You assume that Javascript is front-end
That is no longer the case

Java is actually mostly back-end these days, while JavaScript is decidedly browser-only, so the whole comparison is nonsense.

Have you not heard of Node.js? It is server-side JavaScript, built around Google's V8 execution engine.

Java = back end
JavaScript = front end
Need both to do useful things, no?

Node.js is an event driven framework for build web/network apps. It doesn't run in the browser, it is the server fulfilling browser requests. It just happens to use the javascript language.
http://nodejs.org/

You think? You treat a core contributor like this and then wonder why he steps down and leaves? The best part is that when they announced his departure they're like "yeah, uh we totally respect him and his amazing contributions now please respect our wishes and stop bringing up the fact that we are a bunch of SJW tools who treated a major contributor with less respect than Linus Torvalds treats people who intentionally crap all over his code base."

I've shown this crap to coworkers who were interested in learning Node and their reaction was "W...T...F..." that's how they treat their community?

Since Node.js made it possible to write server-side logic in JavaScript.

Happily enough, Alexa offers a download of the top million domains. Even calculating the MD5 hash for every domain every time and doing a simple string comparison using node.js, it takes only a couple of seconds to run through every single entry in that table.

arth1's domain isn't in the top million list, though.

But still, there are plenty of sites in the top million list you may not want to share with Valve that you visit, like #83, pornhub.com, or #84, huffingtonpost.com.

http://nodejs.org/docs/latest/...

I don't know why people keep submitting this garbage from Espresso Logic, who is just taking advantage of the fact the the term "reactive" has been overloaded to mean different things to exploit the hype surrounding the Reactive Manifesto and related technologies (e.g., Akka, Rx, Node.js, etc.) to push their own, completely unrelated product, which is based on the more traditional (i.e., the one you find in Wikipedia) definition of "Reactive Programming".

"Reactive programming", as defined by the Reactive Manifesto (which is what all the hype is about), is about designing applications that operate in an entirely asynchronous and non-blocking manner, so as to maximize CPU utilization and fully exploit parallelism, and ensure that the system is always responsive to new events (user input, incoming data streams, errors, changes in load, etc.) rather than having resources tied up waiting for external processes (e.g., blocking on I/O). It has nothing to do with "reactive databases".

There is no proprietary keywords and extensions involved here. It works with the standard V8-based Node.js implementation from http://nodejs.org./ In fact, that doesn't even come in the box, so you have to download and install it separately.

It's only used on the client-side because developers have no other choice, practically speaking. It's the only client-side language supported in most browsers.

No other choice? Take a look at NodeJS.

Cezary Tomczyk

Node.js supports the use of addons written in C/C++.

Use JS for libraries that are shared between client & server (e.g. HTML templating) and for logic that changes frequently or needs to be accessible to dedicated front-end devs (e.g. request routing). Use compiled C for code that needs to be extremely fast &/or robust (e.g authentication & creation of dynamic resources).

Here's a handy example addon from the node.js docs:
http://nodejs.org/api/addons.html

So, meantime node.js is no longer maintained. WHO CARES?

You stick to your old version, and you are good. If you need new features that belong into node.js and not into your software you hire one for it. Or you write it yourself.

And then you get hit by a vulnerability.

http://blog.nodejs.org/2012/05/07/http-server-security-vulnerability-please-upgrade-to-0-6-17/

You don't have to with C# either...

Then again, I'm becoming a bit of a NodeJS fan for server-side dev.

like this?

http://nodejs.org/

That should be http://nodejs.org/ not .com.

Indeed. Very good example. And (oh the horror!) JavaScript may even be the next Cobol and replacing Java, the way things are progressing.

Node.js FTW!

I'm curious as to what benefits this will offer over Node.js or Rhino. I mean my biggest aversion to Java has been the amount of boilerplate needed, to a lesser degree C# (.Net). Been really liking Node.js + MongoDB + WebStorm lately. Thinking of stripping down my API and pushing the base as a starting point framework for for building JSON web services.

If you want server-side javascript, then why not just use node.js, like everyone else is doing?

Apparently you've never heard of Node.js?

http://nodejs.org/

The code itself runs in Node.js, not a Microsoft toolchain... Node in the past two years has grown leaps and bounds as a JavaScript execution environment on just about every platform out there. I think they'll keep the compiler, and spec open... as they've done for a lot of things around development the past few years... the extensions into the UI for Visual Studio are far more compelling though. At this point, it really does make VS2012 a compelling tool for building Node.js based apps (most of which run in Linux, though MS has made effort to making it run better in windows/azure).

Agreed that PHP needs a major cleanup, but the resultant product probably shouldn't be called PHP 6

I agree entirely.. try some of these forks: http://www.ruby-lang.org/ http://www.python.org/ http://www.java.com/ http://www.microsoft.com/net, http://nodejs.org/

They are actually good for a change!

I would like to add that Javascript can be used to write back-end code also: http://nodejs.org/

By leveraging Node.js you can write web services and client-side presentation with standard html and javascript. Can't think of another language that allows you to write a server and client with the same language with as much ease. Also, the level of entry is very low, a teenager can quickly get up to speed and you don't need exotic tools or have to endure an elaborate setup, you can create all the code in a simple text editor and installing Node.js is very straightforward. Plus, Node.js has a package manager which provides a plethora of add-on modules that you can access from the commandline and in your node.js environment.

Nodejs.org

Javascript is out of place on server side, which is why server style Javascript has never caught on, and it doesn't really make a lot of sense as a general purpose programming language either.

Last I checked, server-side JavaScript seemed to be all the rage with the cool kids.

JavaScript was born for the browser ( and even has (horrible) features that only make sense in a browser ( try 'blah'.bold()), except that they dont), but that doesnt mean it is a bad language for all other purposes.

Just a quick note: Node.js now takes advantage of multiple cores with the Cluster API.

For instance...

See: http://nodejs.org/

JavaScript outside the browser.

You don't stop using a language for a particular purpose while it is the best-supported, most widespread and most evolved language for the job. You kill it when you have a better alternative and everyone is starting to use that. Google (and others) are just trying to spread FUD about JS to get people to use something they control, not because JS is so terrible ... (in fact, it has become a very decent language both for server-side work with CommonJS/RingoJS and NodeJS and recent client-side implementations are already competing with Flash performance-wise).

I think you mean node.js.
(Features non-blocking hot action, just like C.)

Out of curiosity I looked at your link to Node. Then at the explanation about what the project is. It fits in half a line: "evented I/O for v8 javascript" and I have no idea what that means, even after 25 years of pro programming. Fairly typical of undocumented open-source projects, unfortunately.

The link is to the source, not the project per se. It's pretty well documented (I hadn't heard of it before, either) at http://nodejs.org/. In brief, it's a reactor pattern for JS. In fact, I see it's even mentioned on the Wiki page: http://en.wikipedia.org/wiki/Reactor_pattern.

The code looks good to me. Pretty much stock, professional, quality, C++ system software. Some of the algorithms/heuristics (e.g. idle detection for GC) are perhaps debatable (in a good way), but the code itself looks good. If a job candidate told me they wrote this and showed it as an example of past work I'd consider their ability to produce quality code fully proven, and switch to their other abilities as an engineer.

Out of curiosity I looked at your link to Node. Then at the explanation about what the project is. It fits in half a line: "evented I/O for v8 javascript" and I have no idea what that means, even after 25 years of pro programming.

Actually it says:

evented I/O for v8 javascript - Read more
http://nodejs.org/

Surely clicking one of those links would be faster than asking for it on Slashdot and waiting for an answer? When you click the "Read more" link that is not even half an inch from what you've quoted you can find a big "Resources for Newcomers" section with links to the wiki and the home page.

JavaScript is of course the programming language. V8 is its high-performance implementation developed by Google for Chrome. I/O means input/output and evented means that it is asynchronous I/O based on event loops. I think that after 25 years of pro programming you should know that, and if you don't then you should at least know how to follow the hyperlinks to find it out.

Fairly typical of undocumented open-source projects, unfortunately.

Well if the only place where you look for documentation is the title of the project on GitHub then yes, it is fairly typical.

Out of curiosity I looked at your link to Node. Then at the explanation about what the project is. It fits in half a line: "evented I/O for v8 javascript" and I have no idea what that means, even after 25 years of pro programming.

Actually it says:

evented I/O for v8 javascript - Read more
http://nodejs.org/

Surely clicking one of those links would be faster than asking for it on Slashdot and waiting for an answer? When you click the "Read more" link that is not even half an inch from what you've quoted you can find a big "Resources for Newcomers" section with links to the wiki and the home page.

JavaScript is of course the programming language. V8 is its high-performance implementation developed by Google for Chrome. I/O means input/output and evented means that it is asynchronous I/O based on event loops. I think that after 25 years of pro programming you should know that, and if you don't then you should at least know how to follow the hyperlinks to find it out.

Fairly typical of undocumented open-source projects, unfortunately.

Well if the only place where you look for documentation is the title of the project on GitHub then yes, it is fairly typical.

main page

You've been talking to the wrong webdevelopers.

JavaScript definitely has bad parts, the environment that JavaScript is used in most, the browser isn't much fun either.

But if you stay away from both of those, it is very lean and expressive.

That is why there has been a lot of interrest from webdevelopers trying to use JavaScript on the server as well, like with NodeJS ( http://nodejs.org/ ).

I'm writing a browser in JavaScript that will run on itself !!!

Use jsdom with node.js. Still need decent GUI bindings (Gtk is in the works IIRC), but other than that it's ridiculously easy.

http://nodejs.org/

There's also JavaScript on the server. Most notable at the moment is node.js, and frameworks on top like express.

v8 (the javascript engine in Chrome) is already fast enough to be competitive with Java and .Net as a server side language (and much faster then Python, Ruby, and PHP) , and the JavaScript interpreter battles are still going strong.

There's plenty of programming languages out there worth learning as a primary language and ruby isn't one of them.

• go
• javascript / V8 see also node.js
• lua and luaJIT
• racket
• ...

Ruby is one of those languages that you learn in addition to another more general language. In that respect, PHP and ruby are about the same. As respects performance, both PHP and ruby are toys.

so you'll be aware of this then: http://nodejs.org/