SaltwaterC

7 ms·

1.
by SaltwaterC 15y ago
tl;dr Lennart is an ass.
2.
by SaltwaterC 15y ago
You still need to provide an access key id and secret access key with that session token as returned by Security Token Service. And properly sign every request with those credentials. With a proper session token, but invalid credentials, th
3.
by SaltwaterC 15y ago
They add useless latency and another point of failure. And sometimes, the AWS APIs DO fail.
4.
by SaltwaterC 15y ago
It looks like it doesn't like recursion.
5.
by SaltwaterC 15y ago
The API doesn't bother me as much as the temporary authentication via STS. Temporary credentials for database access? Seriously? I am the only one who sees how ridiculous this is?
6.
by SaltwaterC 15y ago
Well, since you're complaining, I added SimpleDB support to aws2js. It was like 12 lines of code actually, but since people don't ask ...
7.
by SaltwaterC 15y ago
While we're at it, can the Adobe folks explain to the rest of the world when Flash is going to suck less? I mean really. Don't care about the on paper gibberish.
8.
by SaltwaterC 15y ago
The Wikipedia's definition of "notable" is a heap of crap. Maybe somebody should donate Jimmy a dictionary, besides the cash he's looking for.
9.
by SaltwaterC 15y ago
This is exactly what they said on their blog post: Long term archival data is different than everyday data. It's created in bulk, generally ignored for weeks or months with only small additions and accesses, and restored in bulk (and then o
10.
by SaltwaterC 15y ago
Says right there on the front page: "Build by SpiderOak on the same proven backend storage network which powers hundreds of thousands of backups".
11.
by SaltwaterC 15y ago
Zed has the balls to post stuff under his own name.
12.
by SaltwaterC 15y ago
http://linux.die.net/man/2/fork - this explains better.
13.
by SaltwaterC 15y ago
Spawning a new process is not the same thing as forking, but people often forget this bit. This post wasn't about forking.
14.
by SaltwaterC 15y ago
PS: the number of update() calls isn't the issue. Increasing the ReadStream buffer from the default 40 KiB to 1 MiB makes it 0.2s slower although there are 25X less update() calls.
15.
by SaltwaterC 15y ago
The comment about blocking the event loop is all about hogging the CPU with the hash computation, stuff that's not light. See the "node.js is cancer" article for more details. fs.readFile(), although non-blocking, is worse since it actually
16.
by SaltwaterC 15y ago
In the real world people use node.js for other stuff that web servers. Like background processing that involves a lot of I/O, therefore the bias against spawning a shell has no ground.
17.
by SaltwaterC 15y ago
node hash.js – 29.661s sha256sum – 5.093s openssl dgst -sha256 – 4.567s Updated the article as well. I usually post all the output to avoid the appearance that I made up the results. Even though they are fully reproducible up to an extent.
18.
by SaltwaterC 15y ago
You can address up to 64 GiB of RAM with a PAE kernel. Happens that a single process can't access more than 4 GiB of RAM. But in the end, how many people actually run a process that large on a notebook?
19.
by SaltwaterC 15y ago
In fact it is good recursive code, mathematically speaking. It's just that some compilers are bad at it aka doing brute force instead of tail recursion. The main selling point of these "interpreted" languages is the programmer productiv
20.
by SaltwaterC 15y ago
Not having to backup because the data is "in the cloud" is just a pipe dream. Wake up, people! Redundancy is good. It saves your ass when the critical piece of infrastructure that should not fail, fails.
21.
by SaltwaterC 15y ago
Can you post something that actually means something?
22.
by SaltwaterC 15y ago
Thanks. Missed that one. My "3rd party" language support is not perfect.
23.
by SaltwaterC 15y ago
There isn't an original article. In fact, my article isn't something to give the node.js police ideas on how to "fix" various stuff. This is about how various runtimes handle bad recursion. In fact, V8 isn't stupidly slow compared to PHP, C
24.
by SaltwaterC 15y ago
This may be the subject for a part 2. Aka more intensive testing for the implementations that actually perform. And other recursive algorithms (such as the classic factorial). I didn't test the language (implementation!) performance, but th
25.
by SaltwaterC 15y ago
Buzz marketing. These days nobody gives some attention to a purely technical article without any incentives. Seriously, on HN usually it matters who wrote the article, not the factual contents of it.
26.
by SaltwaterC 15y ago
One of the reasons I get why people advise against certain levels of optimization without understanding its implications. As I write few lines of C code, usually I don't bother with deep understanding of all the concepts of compiler optimiz
27.
by SaltwaterC 15y ago
Good catch. fib|⇒ gcc -O4 fib.c -o fib fib|⇒ time ./fib ./fib 0.65s user 0.01s system 100% cpu 0.657 total fib|⇒ gcc -O3 fib.c -o fib fib|⇒ time ./fib ./fib 0.66s user 0.00s system 100% cpu 0.657 total fib|⇒ gcc -O2 fib.c -o fib fib|⇒ tim
28.
by SaltwaterC 15y ago
Did you ever bother to read the HTTP vs. the FTP specs? "Remotely close" rings any bell?
29.
by SaltwaterC 15y ago
The point is moot. HTTP is just the transport protocol in this case. Doesn't have to say that it has to be the front end service that talks to the end user web browser. The OP of the "cancer" article made up that shit. I can bind the listen
30.
by SaltwaterC 15y ago
Old wordpress.com gag ... X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.

More ›