HNHacker News
TopNewBestAskShowJobs

arturadib

1,906 karma · joined November 11, 2009

submissionscomments
arturadib··on Node.js - Convincing the boss guide
> Bad Use Cases: CPU heavy apps

I wouldn't say that Node (i.e. V8) is a bad use case for CPU-heavy apps. In math/statistics for example, V8 stacks up well against other scripting alternatives. See e.g. the benchmarks here:

http://julialang.org/

Of course it's still not as fast as C++, but not terribly off either. Expect dramatic improvements here thanks to the push for making web apps faster.

arturadib··on Show HN: Firebase, a scalable real-time backend
Care to elaborate? Firebase's FAQ seems to suggest that they're still working on a solution.
arturadib··on Show HN: Firebase, a scalable real-time backend
Another great step in the right direction.

That being said, I do believe the hardest part of all these attempts to abstract backends is authentication and security models. It seems to me that most of these services launch before figuring out that critical part of the puzzle.

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Yeah it's just in case there are no surviving references to those vars. For example in the hello world code app gets GC'd unless it's in a callback in setTimeout().
arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Think of Node-Five as a very small WebKit/Gecko engine for Node.js. It is written in JavaScript on top of Node-Qt, whereas Node-Qt itself is written in C++.

When I say "native apps" in this context I simply mean you don't need a traditional browser to run the apps, and the runtime interacts more closely with the OS (for example, Qt exposes native menu methods, native OpenGL, etc).

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Not the same, but sometimes similar. (For example the QPainter API is similar to the Canvas 2D API, etc).

Node-Five is for folks who are more familiar/prefer HTML5 APIs over Qt's proprietary API.

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
> do not allow running of the GUI in anything but the main thread

That's right. AFAIK everything is running in a single thread.

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Some Qt APIs are inherently asynchronous (like QHttp) but the graphics-related ones I'm binding to are not (like QPainter).

So the situation is analogous to the DOM in web browsers. The calls are synchronous and run in the main thread. As the web has taught us though, single-threads and blocking graphics calls can go a long way :)

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
That comes from node-gyp (Node's addon build tool)
arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Node-Qt apps are really semi-native since the app itself is written in JavaScript. So you can easily make your app auto-updating, just like a web app. (iOS is an exception due to Apple's restrictions, unless they're OK with QtWebKit which I doubt).
arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Hi, OP here. For folks who prefer HTML5 APIs, I'm also working on a layer that translates these Qt APIs into HTML5 primitives (like Canvas and AudioContext):

http://news.ycombinator.com/item?id=3816870

(There are some neat demos there :))

arturadib··on Node-Qt: Build native apps using Node.js + Qt (Windows, Mac, Linux)
Hi, OP here. As explained that message happens when you mess something up in the C++ bindings, not because of JavaScript actually running out of memory.
arturadib··on Play with the PDF.js API directly from your browser
OP here. Fire off any questions to @arturadib, happy to help.
arturadib··on Introducing Grunt
I think Grunt is great for a lot of projects because it offers out-of-the-box solutions for most common needs.

However, at Mozilla's PDF.js we needed more flexibility - there were so many JS packaging tools out there, each shining for specific purposes, but none general enough for our needs.

So I wrote a port of Unix shell commands (including a Make-like tool) for Node.js which works across platforms:

http://github.com/arturadib/shelljs

The downside is that we don't offer Grunt tools out-of-the-box; the upside is that the tool is more general and (if you already speak Unix shell) you don't have to learn a new framework.

Again, superb work!

arturadib··on Bot.io: The pull request test/build bot
Greetings, OP here. Bot.io has been keeping Mozilla's PDF.js project regression-safe since late 2011.

We decided to create a more general, customizable bot so that others could easily deploy it for their projects.

The bot is written in Node.js and is cross-platform tested.

Go ahead, give it a try - it's really easy to get started. Hit me up on Twitter if you need a hand: @arturadib

arturadib··on Firefox To Get Native PDF Viewer Powered by PDF.js
Big thanks to everyone who contributed to the project and made this ambitious project possible.

This is a true Open Source collaboration, with over 30 contributors since inception mid-2011. We're working on getting a new UI and constantly fixing rendering issues.

Don't forget to check out our repo - new contributors are always welcome! :)

http://github.com/mozilla/pdf.js

Feel free to hit me up on Twitter at @arturadib for direct correspondence or join our mailing list at:

dev-pdf-js@lists.mozilla.org

arturadib··on Tacocopter - Flying Robots Deliver Tacos To You
Similar stuff could be said to Henry Ford about cars back in the early 1900s ("What? You want us to zip around town with a vehicle full of GASOLINE? Yeah right...").

This is a truly revolutionary idea, one that has so many different positive side-effects (reduce traffic congestion, reduce pollution, faster deliveries, cheaper mailing costs, etc). It needs to be pushed forward by visionaries, folks who really believe in it.

Yes, they'll have to be a little crazy. Yes, they'll likely have to deal with setbacks.

But if they persist and succeed, their name just might one day be written in history books.

arturadib··on JSON 3: A modern JSON polyfill compatible with nearly all JavaScript platforms.
Speaking of new JSON versions, is it impossible to create a backwards-compatible JSON spec that supports comments? I've been waiting for this for ages.
arturadib··on Make Any Webpage Look Like It Was Made By A 13 Year-Old In 1996
Oh man, this is like seeing dusty old family pictures. So nostalgic!
arturadib··on Yahoo Crosses The Line
It conveys the tone of the post much more than the original title. And those are Fred's actual closing words. I say this title is spot-on.
arturadib··on The SendHub API: Heroku for Twilio
New category "SaaSaaS"? (Software-as-a-Service)-as-a-Service
arturadib··on ShellJS: A port of Unix shell commands to Node.js
PDF.js is a JavaScript project - that's the language we know for sure all our contributors speak :)
arturadib··on ShellJS: A port of Unix shell commands to Node.js
I agree that async APIs are almost mandatory in the context of servers (since you don't want to block them while you run I/O commands).

But for shell scripts, not so much. In fact, async would just introduce unnecessary complexity, in particular a nested callback hell as most shell scripts are basically sequences of I/O commands (promises, etc would mitigate the problem somewhat, but again at the expense of another layer of complexity).

That being said... if there's enough demand to use these commands within web servers, adding callback support should be easy. Contributions are welcome! :)

arturadib··on ShellJS: A port of Unix shell commands to Node.js
Yep, similar in spirit but PBS is a wrapper around existing shell commands, whereas ShellJS implements those commands on top of the Node API (which makes the commands portable/cross-platform).
arturadib··on ShellJS: A port of Unix shell commands to Node.js
OP here.

At Mozilla's PDF.js project we have a large Makefile responsible for everything from custom-bundling our .js files to building our Firefox addon extension and firing up a localhost server.

ShellJS is part of our effort to minimize our dependencies, particularly on Unix commands so as to offer homogenous support to our Windows users. It should also be of use to folks who want to do traditional shell scripting on multiple platforms using JavaScript and a familiar syntax - no need to learn another library. All commands are synchronous, including exec().

We're looking for early adopters and contributors who can help us mature the code. Thanks!

arturadib··on Hacked: commit to rails master on GitHub
Time from exploit to fix in production: < 1h. On a Sunday morning.

I'd buy Github stock if I could.

arturadib··on Hacked: commit to rails master on GitHub
Regardless of the 'hacker's motives/personality, I think this is yet another testimony to the power of open source.

When you have this many eyeballs looking at your code, the odds of a good-intentioned (however playful/immature) coder to discover a vulnerability is much greater than those of a real ill-intentioned hacker simply due to the sheer number of the former. The issue will quickly get fixed by the community, the kid will get the attention he wants, and life will go on.

arturadib··on Hacked: commit to rails master on GitHub
I'm confused. Is this a generic Github vulnerability or is this a vulnerability in tools outside of Github used by Rails? The 'hacker' seems to suggest it's the former ("Github pwned"), which would be pretty serious stuff.
arturadib··on Node.js to pass Ruby on Rails in search popularity
To be fair you'd have to compare "node" and "rails", which is almost entirely contaminated by out-of-context results.
arturadib··on Node.js to pass Ruby on Rails in search popularity
Agreed. But to be fair one would have to do the same for Node: add "node" and "nodejs". It'd be tough though, since like "rails" there are multiple contexts the words can be used. This is just one milestone; not meant as an exact comparison.
← PreviousPage 4 of 9Next →