Vert.x – JVM Polyglot Alternative to Node.js
11–20 of 83 posts
Re: Vert.x – JVM Polyglot Alternative to Node.js
#12Trying to install this on Ubuntu. Is it me or is the "binary" download link [1] not really a binary download link? [1] https://github.com/purplefox/vert.x/downloads
https://gist.github.com/2594983
Are you sure you're not looking at the github tags, rather than the downloads?
Re: Vert.x – JVM Polyglot Alternative to Node.js
#13Re: Vert.x – JVM Polyglot Alternative to Node.js
#14Impressive. It's basically a kinda-sorta-rewrite of Node.js APIs on the JVM. Looking through the docs, the main difference I see is that this is opting for a comparatively heavy-core approach which contrasts with Node's ruthless minimalism + third-party modules. For example: -file system access is convoluted with HTTP handling: req.response.sendFile() -pieces of web framework functionality by default, but no full sol…
I haven't looked in to it, but just guessing this is probably so that it can do 0-copy sending of files (e.g. doesn't have to buffer/stream the contents through the JVM).
Re: Vert.x – JVM Polyglot Alternative to Node.js
#15Impressive. It's basically a kinda-sorta-rewrite of Node.js APIs on the JVM. Looking through the docs, the main difference I see is that this is opting for a comparatively heavy-core approach which contrasts with Node's ruthless minimalism + third-party modules. For example: -file system access is convoluted with HTTP handling: req.response.sendFile() -pieces of web framework functionality by default, but no full sol…
> -file system access is convoluted with HTTP handling: req.response.sendFile() I haven't looked in to it, but just guessing this is probably so that it can do 0-copy sending of files (e.g. doesn't have to buffer/stream the contents through the JVM).
You can also serve files in the more conventional "node.js-style" way (i.e. pump the buffers manually from file to socket) if you like. It's just slower than getting the kernel to do the work for you.
Re: Vert.x – JVM Polyglot Alternative to Node.js
#16I was hoping it provided an alternative ideology to node.js in the form of fibers.
I know Fibers/Green threads are all the rage right now, and it is certainly something to keep an eye on, but I am not entirely convinced that roll your own threading is going to be any more performant than what the kernel can do.
If we can find a way of implementing fibers efficiently, that supports millions of fibers on a single JVM instance, I would be interested.
Re: Vert.x – JVM Polyglot Alternative to Node.js
#17The install pre-requisites recommends that Windows users install a linux VM - but I found the beta 11 version works directly.
Re: Vert.x – JVM Polyglot Alternative to Node.js
#18What all the JVM Node.js clones are missing and what Node.js sets apart are async libraries. There is no async (MySQL) JDBC driver for starters. If your IO drivers are not async, your async container is not very useful in real life.
Re: Vert.x – JVM Polyglot Alternative to Node.js
#19Combining this with languages like ruby, clojure, and scala seems like a definite win.
Re: Vert.x – JVM Polyglot Alternative to Node.js
#20Finagle works fine. Thank you. Love it. But it does not take off. Why? What all the JVM Node.js clones are missing and what Node.js sets apart are async libraries. There is no async (MySQL) JDBC driver for starters. If your IO drivers are not async, your async container is not very useful in real life.
Python, Ruby and Perl all have the same cultural tolerance for blocking code. The Node.js community has a complete lack of tolerance for blocking code.
I work with the JVM every day (Clojure) and wish it was different wrt the common use of non-blocking code, but it's going to be a long road to get there on the JVM.
Kyle