CPlatypus

21 ms·

121.
by CPlatypus 15y ago
As the first paragraph of TFA points out, the VC is always a chicken. They're not "committing big-time" so that appeal falls flat. If someone wants to take a risk because their partner is taking a risk that's fine, but anyone who takes
122.
by CPlatypus 15y ago
I disagree with the author; most developers' attitudes toward state machines are poisoned not by academic experience but by experience with other developers' half-assed state machines. Back in '93 or so I used state machines extensively fo
123.
by CPlatypus 15y ago
I think redefining volatile wouldn't be harmful enough because so few people use volatile correctly anyway. By contrast, the break/continue or double-free suggestions would show up too quickly. I don't think I can come up with anything as
124.
by CPlatypus 15y ago
Here's a better strategy: burn the other guy's boats. Limit their options, put them in a position where their backs are to the water, make them take on enemies or burdens at no cost to you. Burning your own boats is a poor substitut
125.
by CPlatypus 15y ago
Semantics matter. Would you rather argue about syntax?
126.
by CPlatypus 15y ago
Well played, sir. Brief in text as well as code. :)
127.
by CPlatypus 15y ago
Damn, your reply and the other four pointing out that they're Ruby VMs reflects very poorly on the intelligence of HN commenters. Did you guys even RTFA? I know these are Ruby VMs, but the article is about the C code that's used within
128.
by CPlatypus 15y ago
"Very few people out there know that the volatile type qualifier exists"? Only if there are "very few" kernel programmers, embedded programmers, and others who have used C for anything low-level and/or multi-threaded. Otherwise, no. Sorr
129.
by CPlatypus 15y ago
If I worked on static code analysis tools for a living, this would make me cry.
130.
by CPlatypus 15y ago
It sounds like you've had some bad experiences and I don't know which projects address those specific issues, but personally I've had good luck with Unison. Somebody else pointed me toward lsyncd which seems to take an interesting (inotify
131.
by CPlatypus 15y ago
Being non-mountable isn't a core good feature. It's a serious deficiency. If you want to store locally and sync so you can work offline, this is only one of about a hundred solutions. It just happens to be one that also allows you to u
132.
by CPlatypus 15y ago
This is the difference between equality and equivalence. It's not cross-platform to the extent that Dropbox is, though the fundamentals are portable to any platform that supports FUSE and thus GlusterFS. There's also no web UI, though the
133.
by CPlatypus 15y ago
You're really not getting it, are you? I never said ZFS was the problem, as you seem to think. I'm just saying it's not the solution either. It's a crappy solution, failing to protect against host failures and creating myriad problems in
134.
by CPlatypus 15y ago
Perhaps you should RTFA. The author says explicitly that what they do now is "lean on ZFS" and "keep the network out of the storage solution" which made their provisioning more complex because they could no longer treat local disks as ep
135.
by CPlatypus 15y ago
Actually, C/A/P are more like variables you can multiply together. Even more accurately, they define a three-dimensional space with the CAP theorem (especially in Gilbert and Lynch's formal proof) only saying that you cannot be at the po
136.
by CPlatypus 15y ago
He only gets it half right. A filesystem interface instead of a block interface is the right choice IMO. Private storage instead of distributed storage is the wrong choice for capacity, performance, and (most importantly) availability rea
137.
by CPlatypus 16y ago
The point is not that working for someone else is an entrepreneurial activity, but that experience is a prerequisite to successful entrepreneurship. School doesn't confer that experience, except to the extent that students often have a lot
138.
by CPlatypus 16y ago
RTFA. "We looked at how polarizing each movie is by measuring the standard deviation of the ratings for each movie." That's pretty clear, even if it's still a bad measure. There are plenty of valid criticisms of this survey; you don't need
139.
by CPlatypus 16y ago
>and a big part of the reason for posting here was for someone to say "hey, here's a wheel you can buy off the shelf!" not "hur hur, you're stupid because you're assembling a web stack, fail!". I don't think assembling a web stack is au
140.
by CPlatypus 16y ago
Seems like a lot of reinvention to me - cluster management, DNS service, caching, queue service, etc. Reinventing cluster-management infrastructure, for example, is just a bad idea plain and simple. It will take a lot of time, and that
141.
by CPlatypus 17y ago
I did say that I'd written about it on my site. Here are a couple of links. http://pl.atyp.us/wordpress/?p=2240 http://pl.atyp.us/wordpress/?p=2258 Here's one from Randy Bias, which I had also alluded to. http://cloudscaling.com/blog/
142.
by CPlatypus 17y ago
Please try to remember that it was originally written as a comment on Dennis's article, not as an original article in its own right. So yes, it is essentially unedited. Sometimes facts and timing are more important than polish.
143.
by CPlatypus 17y ago
Gee, so sorry I didn't write the post you would have, and chose to approach the issue satirically instead. You do understand satire, don't you? You do understand how _A Modest Proposal_ was more effective than some dry exposition of the u
144.
by CPlatypus 17y ago
If you are going to say something, just say it. If you're going to accuse someone of libel, just accuse them. Don't be all passive-aggressive when you're accusing others of being passive-aggressive. It looks kind of like you're project
145.
by CPlatypus 17y ago
Some notes from the OP author. ;) (1) Neither PVFS2 nor Lustre requires shared storage except to do hot failover for a failed server. I've personally run both in configurations where the only storage was node-local RAM. Disk failures can