HNHacker News
TopNewBestAskShowJobs

xearl

1,467 karma · joined January 5, 2010

submissionscomments
xearl··on Pijul for Git users
Regarding your niche (2): what open source project do you have in mind?
xearl··on StreetLend.com shuts down, citing GDPR regulations
> Where in the actual text of the law does it say that they will never impose the maximum fine for a trivial or minor offence?

Article 83 (including related recitals)

xearl··on Europe’s New Privacy Rules Favor Google and Facebook
> I can press every button in an entire union, apparently every 40 days.

In most cases that will be considered "repetitive" and "excessive" - Art. 12 (5) - and businesses will be allowed to charge for fully responding to your "button presses".

xearl··on Fuchsia: Google's modular, capability-based, non-Unix operating system
Assuming that the C++ bit and the not having faith b/c of Chromium bit are related, would you mind expanding (briefly) on the problems you saw?
xearl··on Interesting commands for the Linux shell
Sorting by hash will always cluster lines with equal content together, whereas true randomisation won't.

Eg `(seq 3; seq 3; seq 3) | sort -R`.

xearl··on Interesting commands for the Linux shell
nice collection! upvoted for "15. `namei -l`" alone, which is far too little known.

a better "20. Randomize lines in file":

  shuf file.txt
instead of

  cat file.txt | sort -R
(sort -R sorts by hash, which is not really randomisation.)
xearl··on Deprecated Linux networking commands and their replacements
interestingly enough, `ss` (usually w/`-ltun`) was the first thing i successfully reprogrammed my muscle memory to (after 12y+ of using netstat). `ip r` instead of `route` being a close second.

i have come to very much appreciate the consistency and discoverability of the iproute2 cli.

xearl··on Announcing GVFS: Git Virtual File System
To me it sounds like these numbers are from a migration-in-progress. So they are trying, but instead of giving up and saying "not the right tool for us" they are trying to improve the tool.
xearl··on Dafny – A programming language with a program verifier
Perfect Developer [1] is another one not yet mentioned. You write and verify your "specifications" (program-parts to be verified) using a language called "Perfect" and generate C++, C#, or Java from that (SPARK Ada generator in progress).

[1] http://www.eschertech.com/products/perfect_developer.php

xearl··on Pyret – A language exploring scripting and functional programming
> "In general, types really just get in the way when scripting or prototyping or trying to do anything fast"

I've found the opposite of that claim to be true. Types are absurdly helpful in prototyping or trying to do anything fast, especially when exploring data coming from a file or an external API.

Anecdotes aside, BinTree in the example is both a data type and a type testing function ("detector") of signature `Any -> Bool`. See http://www.pyret.org/docs/latest/Declarations.html#%28part._... for details.

xearl··on Clojure.spec – Rationale and Overview
> And no, you can't have LISP without its syntax, because that's what's giving it power. The "code is data" mantra only works because Lisp is homoiconic

No. Homoiconicity is nice for "code is data" and macros, bot not necessary. Being able to reify and generate ASTs is sufficient. See for example Dylan, Terra/Lua, Scala LMS, MetaML, or Julia's or Rust's macros.

xearl··on RemixOS – Android for the desktop
It seems that "Remix OS for PC" will be at least "free to use":

> "With that in mind, Remix OS for PC is free to download, free to install, and free to use."

No idea about open source, though.

xearl··on An Opinionated Guide to Modern Java, Part 2
VMware is owned by EMC. VMware bought Spring Source. EMC bought Pivotal Labs. VMware and EMC subsequently decided to spin-out a few of their acquisitions, including Spring and Pivotal Labs: into a company they dubbed Pivotal Software.
xearl··on Green revolution cooling
as they claim the liquid coolant works efficiently at 40°C (104°F), using outside air to cool hardly requires a particularly cool climate. they also attribute fan removal to a significant part of the savings.
xearl··on Green revolution cooling
they have a video demonstrating how to do server maintenance:

http://www.youtube.com/watch?v=EZmm7P1mPZs

no need to shut down the server. you pull it out and swap the parts (for front-accessible hotswap HDDs you won't even have to pull it out). cabling is designed to accommodate that.

i can imagine, though, that "pulling out" a 4U storage box fully loaded with hdds may become a bit strenuous.

xearl··on IPv4 is depleted: Final five blocks allocated to registries
Spot on. It took Stanford roughly two years to move off their /8.
xearl··on IPv4 is depleted: Final five blocks allocated to registries
That's a question probably best asked directly to Linode (esp. if you are a paying customer).

As a basis for making up your own mind: Linode has, at the moment, nine /20's allocated. At 80% utilisation, that means roughly 30'000 IPv4 addresses.

xearl··on IPv4 is depleted: Final five blocks allocated to registries
Years away? Gosh! Depends a bit on where you want your servers to be located, I guess, but still. For a lot of server hosting customers, prices for additional IPs have already increased steadily over the last few months. But don't take my word for it, here's a bit from a recent APNIC announcement, for example:

"APNIC expects normal allocations to continue for a further three to six months."

(https://www.apnic.net/publications/news/2011/delegation)

xearl··on Node.js memory benchmark confirms V8's GC may not be ready for the server
When plotting the response time over time, this educated guess becomes even more solid:

http://earl.strain.at/2010/ringo-node-benchmark/buffer-alloc...

(This uses the very same dataset underlying the "buffer alloc" graph in the original post.)

xearl··on Node.js memory benchmark confirms V8's GC may not be ready for the server
Per default, Java 6 uses a generational collector with multi-threaded stop-the-world copying for the young generation and single-threaded stop-the-world mark-sweep-compact for the tenured generation.
xearl··on Node.js memory benchmark confirms V8's GC may not be ready for the server
I think the main point of this post (and also the edited headline) is that this is not an issue of Node per se, but rather of V8.
xearl··on Node.js memory benchmark confirms V8's GC may not be ready for the server
You're interpreting the graph incorrectly. There's no "bottom of the curve", the graph is showing a distribution, not some property over time. A correct reading will e.g. tell you that out of 50'000 requests a total of ~30'000 requests completed in 100ms or less. Or similarly for what you call the bottom of the curve: 5'000 out of 50'000 requests complete in ~25ms or less. This does _not_ state which 5'000 requests that were, and in particular it does _not_ imply that the _first_ 5'000 requests are faster. For this you'd have to plot response time over time.
← PreviousPage 2 of 2