HNHacker News
TopNewBestAskShowJobs

personZ

2,015 karma · joined April 2, 2014

submissionscomments
personZ··on OVH servers exploited through shellshock
Ubuntu, for instance, has unattended-upgrade (that it defaults to on), the premise being that it will forcefully install and use critical security patches. Ideally you'd have done this yourself ASAP, but if not I have to think that unattended-upgrade came into play at some point.
personZ··on Texas Man Arrested for $4.5M Bitcoin Ponzi Scheme
Because there are a thousand other people saying "oooh, what a good scheme. Maybe I should try that."

Deterrence is a significant part of the justice system.

personZ··on Good Consultants vs. Bad Consultants
Your Java example seriously undermine your point -- you have set up a world where you have an opinion, and thus your opinion is the "truth", and people who believe otherwise are being fooled by liars.
personZ··on Good Consultants vs. Bad Consultants
I run a small consultancy (myself, though I engage peers whose work I respect as subcontractors for larger jobs), and the #1 issue I've faced are company representatives who look for consultants to make them, personally, rewarded: Their concern is primarily their own personal benefit, not the benefit to the company. Whether it's professional sports tickets, expensive dinners and lunches (which sound small in the small, but when you have a company representative who schedules regular "status meetings" during lunch/dinner, you know where it's going), and so on, it is an industry absolutely dominated by kickbacks, the whole notion of which feels dirty and fraudulent.
personZ··on Operator of Silk Road 2.0 Website Charged in Manhattan Federal Court
The government is saying that they will pursue people who break the law through any means possible. In this case, they apparently socially engineered their way in.

And? How is this possibly a problem? Is it really an attack on potential legitimate uses of anonymity? Is it really useful to conjure up a murderous prolife president?

To all of those the answers is of course no.

personZ··on Operator of Silk Road 2.0 Website Charged in Manhattan Federal Court
There is absolutely nothing untowards or abnormal about their claim, nor are they threatening the "public", which overwhelmingly doesn't operate black market sites.

Law enforcement absolutely includes an element of making examples, and deterring crime. That is one of the major purposes why organizations like the FBI exist. Not quite sure what this has to do with democracy.

personZ··on On the phenomenon of bullshit jobs
Has it worked? I'm not supporting any opposition to SOX, however we all know of many processes that offer no real checks or value, but we have to do it...just because why not, you're getting paid for it. In the case of SOX and the like, the argument can be "well everyone else has to do the same illusion of control work, so the drag is similar".

Most businesses are filled with processes that everyone knows are done for absolutely no value to anyone, but we do them anyways and they absolutely sap our soul.

personZ··on Dynomite – Making Non-Distributed Databases Distributed
You state this as if I've claimed that I'm going to create a Netflix clone just to prove something, which of course is nonsense. Netflix is a large company that has been around for years, yet their solution remains relatively simple for the scale of their operation.
personZ··on Dynomite – Making Non-Distributed Databases Distributed
Starting with a patronizing "sorry", looking down from heights, doesn't somehow give your comment more credibility.

There are a large number of services of the user scale of Netflix, with dramatically more complexity, that don't seem to have the heroic issues that Netflix does. Facebook and Reddit both are of a complexity scale multiple-magnitudes greater than Netflix. Someone else absurdly tried to draw Apple and Google in, but again, what they do absolutely dwarfs the entirety of Netflix's operation, to the point that it becomes almost laughable.

Netflix is a very simple application. Scaling it can be difficult, of course, but this is hardly some new grounds. Further, the particularly make-up of Netflix makes it one of the most profoundly scalable platforms going (silos, little to no need for transactional integrity. It is profoundly simple). You don't have to believe this, but your comically patronizing responses just sound...laughably unskilled.

personZ··on Dynomite – Making Non-Distributed Databases Distributed
They aren't creating all of this software just because they are having fun in their free time.

Sorry, but this is an invention of yours. No one said they're doing anything flippantly.

But they may be doing it ignorantly: Success in one field (in this case turning a mail subscription business into a stream service) doesn't imply technical innovation or leadership, and often is despite it.

This industry is absolutely rife with people creating solutions to problems they themselves invented and caused. In the case of Netflix, an enormous amount of their solutions have been founded around the notion of deploying on huge numbers of miserable Amazon EC2 instances, and then dealing with the problems related to that. Others simply deployed distributed data centers hosting their own purpose suited, reliable hardware with big fat storage arrays, and the problem is solved. It's like trying to build a car out of toothpicks and then detailing the innovations you created in toothpick redundancy and robustness.

personZ··on Dynomite – Making Non-Distributed Databases Distributed
Neither that or the number of open engineering positions tells you the difficulty of the problems they are solving. It might just tell you the difficulty of the problems they are making: If Netflix has a technology side with a history and the executive ability to overcomplicate, they might be making little problems into big problems. My perspective as an outsider is to look at the complexity of their app platform (again, separating the video streams which happen from systems that never seem to be the foundation of these tech blog entries), and it is unarguably not a complex system.

Early on I remember the heroics that Netflix went through running on EC2, building numbers of complex tools for varied performance, reliability issues, etc. At the time many much larger sites just quietly worked 24/7, minus the heroics, and minus the effort, often by using purpose-suited dedicated servers. Later, once Amazon rolled out SSDs, Netflix triumphantly announced how much of an improvement it was to their product, again demonstrating that they were creating a problem (huge numbers of horrible I/O machines) that they then solved with gusto, albeit unnecessarily.

I'm not trying to be overly down on Netflix, but it is a company that seemed to make tech blog entries a product of the company years ago, and the result is that people have bought into this notion that they're doing some hugely complex task. They aren't.

personZ··on Dynomite – Making Non-Distributed Databases Distributed
Comments that contrive absurd strawmen annoy me, even if they provide the author that righteous sense of striking down an imagined position.
personZ··on Dynomite – Making Non-Distributed Databases Distributed
How is it a 'fallacy'? To be clear, this has nothing to do with the actual streaming (which does not happen from EC2) but instead are the basics like viewing history and categories. It absolutely is the simple part of the application, albeit, as mentioned, at a very large scale. Given that someone else mentioned it, does Netflix even bother with the whole recommendation algorithm thing anymore? My personal experience has been that it gives the most superficial of recommendations.

And if we're being honest, the Netflix app layer is kind of terrible. I could enumerate the problems, discoverability being king, but it is not the compelling part of the service.

personZ··on Dynomite – Making Non-Distributed Databases Distributed
Netflix always makes for an interesting case, but what always strikes me is how incredibly "trivial" their application really is: It's a simple application at a very large scale. This doesn't dismiss their accomplishments, of course, but often it does seem like Netflix spends an enormous engineering effort on fairly low value aspects of the service.
personZ··on HTTP/2 all the things
Okay, so you have a strong opinion in a field that you are opposed to. I think that can pretty soundly be discounted by anyone who cares about this industry.
personZ··on HTTP/2 all the things
The web is currently slowly centralizing and turning into Facebook. Google could fight this trend by using SRV records for HTTP/2.

I fail to see how HTTP n.n has anything to do with the web centralizing towards Facebook, nor have your posts provided any clarity on that.

personZ··on HTTP/2 all the things
And as soon as the buttons and the scripts are delivered from other servers, you effectively can't speed their delivery up.

Aside from the fact that choosing to use those sorts of resources is optional, those (facebook/google+ buttons and likes, etc) are virtually always asynchronous loads -- they do not hold up the render of the root page whatsoever. So if your target is displaying the recipe in 200ms, but the Facebook button takes 400ms -- guess what, the recipe page will still be shown in entirety in 200ms.

personZ··on HTTP/2 all the things
No, of course that's not why the web is slow.

What is the point of this sort of lowbrow sarcasm, fueled by raw cynicism?

Web applications have gotten significantly more complex. From a developer perspective, managing resources separately is a lot easier than using image sprites, giant merged CSS files, etc, though such is often forced because of the known inefficiencies of HTTP. Yes, this seems like an improvement. Are there sites that have other problems? Yeah, sure, of course. That doesn't make it less of a benefit.

personZ··on HTTP/2 all the things
Of the varied bizarrely negative posts this submission has earned, yours is the one that perplexes me most. How is HTTP/2 going to "bite" Google (even if we assume that Google is the only initiator of the HTTP/2 spec, while they're far from it)?

Is the web, right now, failing? Are those little sites somehow not existing? You seem to be positing that a new standard not supporting your pet feature is suddenly going to destroy the web, which seems a little hysterical.

Interesting to note that as a relatively small shop we've already seen huge benefits from SPDY (the precursor) because it allows us to serve from a single site in the US, offering a much, much better experience for our users in Singapore (the benefits to high latency connections are significantly higher than the results commonly reported).

personZ··on Go 1.4 Beta 1 is released
Worth noting that Go has been able to generate Android-compatible binaries for some time -- Linux ARM binaries -- however they are executables, not libraries. Still possibly usable, but more awkwardly.

So now they added the ability to generate libraries. Which is interesting because, to my knowledge, they still don't support building libraries on any other platform. It would be useful.

personZ··on Redis latency spikes and the 99th percentile
Does fork not use copy-on-write? I would expect it to add overhead to all overlapped memory operations going forward, but am really surprised if it literally duplicated the entire memory contents.
personZ··on Why I can't have conversations using Twitter
There was never a shortage of people taking some of those words out of their context, and arguing against what those words supposedly say.

Long ago I learned that if you want to have "viral" success, even on a more informed site like HN, avoid making more than one statement or claim in a piece.

"Modern Java application servers offer surprisingly high performance" (followed by details of performance improvements, etc), for instance, is okay: everyone who agrees will forward and agree and post, while those who might not agree or care will remain ambivalent and disengaged.

Change that up slightly, though, and conversationally add "...which might allow you to deploy on fewer servers than a similar solution built in Ruby" and you'll instantly gain armies of very motivated detractors who will go forth to denounce everything you've ever said, declare everything you've written stupid and misinformed, etc. Not based on objective disagreements, but based on a knee-jerk opposition that, much as with politics, can't be on a point or issue (e.g. "agree to disagree"), but has to encompass everything.

People who might agree or yield value skip the piece after seeing endless criticisms and complaints.

The crux being that it's very hard to gain agreement, easy to gain enemies. If you state ten things, people who disagree with but one of them will often fall in the latter camp.

Not that this changes how I personally write -- where I'll load pieces with things that people can disagree with -- but I see it constantly as stories tread the bottom of the front page, the detractors who find that one tiny thing they disagree with and blow it up to be all-encompassing, and it gets flagged to oblivion.

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
Cartier-Bresson's "Man Leaping" could not have been captured with a cell phone camera. The shutter lag is just too bad.

Humorously, he didn't even see the man leaping, and wasn't timing for that. He took some shots, and it turned out to be a keeper. Such is exactly the nature of smartphone shots, as an aside -- people take countless shots, and among them some gems appear.

for millions upon millions of historic and sentimental potential pictures

This is where your argument falls apart. A modern smartphone has better image capture than SLRs -- top of the line SLRs --from just ten years ago. Despite your focus on shutter lag (where you can prefocus/expose on a smartphone just like an SLR, and then have a close to instant shutter), the shutter lag on current smartphones is, again, similar to top of the line SLRs of a few years ago.

With a large sensor and lenses, at any given time you'll always yield a better result (presuming you assume that such is always available when the moment arises). However at the core of photography, the technical side is far less important than it is held to be, and if we really need to bring up history, a modern smartphone was better than what the most committed photographer had in their arsenal not that long ago.

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
Your pictures hold importance to you for obvious reason, but your impression that they are the result of some sort of technical perfection of hardware is absurd. I see very similar photos, by the dozens if not hundreds, every day on Facebook. By people taking the photos with their iPhone, GS5, or whatever else they happen to have. Those "fleeting moments" when, exactly because they are fleeting moments, they grabbed what they have on their body 100% of the day.

I feel like this is a debate from 2008, discussing the camera on your new Blackberry.

personZ··on Spidermonkey has passed V8 on Octane performance
I suspect that the reason people keeps tabs open is a deficiency of all modern browsers -- if we had the ability to search the contents of our history of sites, it would dramatically reduce our need to desperately hold onto tabs.

Right now you can search the history, but it searches only the title and basic metadata, and as we know well from HN, titles are often wholly unrelated with the content.

So many times I've found a page that has interesting information, and I can easily remember snippets of the page, but without walking through my history manually for hours, I'm left with trying to remember unique phrases and instead searching the world of information on Google, having to winnow through a lot of chaff. It would be so great if a browser (or an evil cloud-synced variant) generated a search corpus of every page you visit -- understanding the overhead and costs, made viable by many cores and massive IO performance -- allowing you to say "I saw a site about banking regulation and overcommitments in the past week...where was it?"

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
"Splitting the difference between candlelight and daylight, around 6 years of technology has made up for the massive difference in the size of the lenses and sensors between the best phone and the $2,000 DSLRs."

"Phil Askey from DPReview described it as “the absolute best in its class, with the best image quality, lowest high sensitivity noise, superb build quality and excellent price.” He described the “Excellent resolution”, the “Noise free ‘silky smooth’ images”, with “very low noise levels even at ISO 1600.” The EOS 10D ran rings around the film that we’d been using for 50 years in terms of clarity and freedom from grain.

Yet it’s comprehensively humbled by modern phones. The iPhone out-shoots it, and the Nokia out-resolves it, all by huge margins."

Should I continue? Did you actually read it? Did you just rush to it to find a confirmation that SLRs are better? Of course they are better. Its point is that the same SLRs we lauded as extraordinary a mere decade ago -- and in some cases much more recently -- are now humbled, badly, by standard smartphones. Do you think the SLR owner of a decade ago was saying "yes, my device is junk. Just sticking with the form factor until it gets decent."?

As to the chart that you seemed to take offense at, its point was demonstrating the extremely rapid improvement in smartphone cameras. Each year the camera is significantly better than the year before, still in the tiny, integrated little module.

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
Yes, of course. I'm not saying that SLRs don't have a place. If you're a wedding photographer, you probably shouldn't bring your iPhone to the job.

But the post I replied to took it to the point of absurdity, where people questioned whether these were really "cameras", and you either have the fools amazed by their crummy results, or the pros who see through that ruse. That is nonsense. I've owned a number of SLRs through the years, back to a 35MM Minolta 9xi with a number of lenses. I am amazed at what is possible with smartphones, and constantly surprised at the very good shots they yield.

Further, just to put this into perspective, an iPhone 6 or a recent Lumia, with its tiny little sensor and tiny little lens, has attributes that beat out God like SLRs from just a few years ago. Those cameras were pro quality, best of the best then, but now the devices that beat them aren't worth calling cameras?

http://connect.dpreview.com/post/5533410947/smartphones-vers...

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
The Galaxy S5 and iPhone 6 both feature on sensor phase detection. Further it's worth nothing that the whole notion of "n points of autofocus" is a flaw of phase detection, not a feature -- contrast detection has millions of possible points of autofocus. And indeed, most high-end SLRs have contrast-detection modes (e.g. Canon LiveView) that brings benefits that often merit its regular use, and are mandated for things like video mode.

I think you're presenting some sort of knowledge gap that is contrived. I used SLRs for years. I seldom use it anymore because the results of my smartphone, under many normal circumstances, are comparable. This is the case for many people. The camera you have and all of that, and they just keep getting better and better.

personZ··on Low Light and High Dynamic Range photography in the Google Camera App
Worth noting that this is the case across most compact camera devices. Most smartphone camera sensors are 4:3 (e.g. iPhones), while the screen on the device is often 16:9 or 16:10. In contrast full-sized SLRs are usually 3:2 owing to the 35mm legacy.
personZ··on Low Light and High Dynamic Range photography in the Google Camera App
They are entirely different sensors, and share nothing at all in common. To start, the Nexus 5 has a 1/3.2" sensor, while the 5s has a 1/3.0" sensor (making evident from the start that in no universe are they "bordering on identical"). The iPhone has a f2.2 lens assembly. The Nexus has a f2.5 lens assembly. Empirically in both of those cases the iPhone has the superior option, not even getting into the specifics of tiering and segmentation.

The Nexus 5 has a camera sensor equivalent with the iPhone 5, on paper, but is handily and easily beaten by the 5s, and it shows.

← PreviousPage 4 of 18Next →