I'm just an average user that no one cares about, but if you dare read the comments on that blog, it seems this bug and the slow response to it pissed off a lot of corporate IT folk whose self-signed apps they borked.
2,442 karma · joined August 27, 2012
I'm just an average user that no one cares about, but if you dare read the comments on that blog, it seems this bug and the slow response to it pissed off a lot of corporate IT folk whose self-signed apps they borked.
If there are any Mozilla folks reading this: What's up?
How is that a bad thing? Firefox was kinda stagnant before Chrome came around and took the performance throne, I don't see anyone criticizing Mozilla for that.
[1] Merchanisms? Sorry to weeb out, but they should really look at Danbooru (NSFW) sometime. Tag-based classification and search works extremely well when (1) the users submitting the content aren't the people that made the content, so there's no conflict of interest encouraging them to try to game the system by spamming tags and whatnot, (2) there are strong guidelines for what is and isn't acceptable, what is and isn't subjective, and (3) the users are as dedicated and passionate as anime fans and archivists are. Let the users contribute objective tags, add support for subjective/personal tags ("pools" in booru lingo) that don't show up in search results but provide a way for users to curate, and for the love of god let them "fave" things and see their friend's favorites, and participation on archive.org would explode overnight.
Ok, it's officially past my bedtime.
Eh, not sure I buy that. Since at least the Pentium, x86 implementations have had very fast stack variable access compared to contemporary RISC architectures, practically treating some number of bytes around the stack pointer as registers. As Linus points out, everyone architecture has to confront this problem anyway sooner or later because some stack access is unavoidable; the x86 implementers just had to confront it sooner because of their ISA had half or less of the registers of the RISC architectures. So while of course it's better to keep everything in registers if possible, I'm sure that the old Lisp compilers would have performed reasonably well on x86 if they'd tried instead of throwing their hands in the air and saying "we can't do it!"
And the "anisotropic instruction encoding" makes so much sense that ARM adopted it (in a much simplified fashion) with Thumb-2. Fixed width instruction encodings waste a lot of space because the common operations need 2-3 more bytes than they ought to, and because absolute addresses and constants above a certain size must be loaded from an indirect access to a location close by the instruction stream, instead of just being inline with the instruction. Instead of 1 byte of instruction + 4/8 bytes of data/address, you get 2-4 bytes of instruction including relative address + the 4-8 bytes of data you wanted to access in the first place. All this adds up after a while, and at some point, the waste of code cache hurts more than the more complicated ISA.
I love 68k too (which had a somewhat "anisotropic instruction encoding" itself, by the way), but let's give credit where it's due: it took a lot of engineering talent and confidence ("RISC is the future!") for Intel to prove that CISC chips could beat RISC chips on performance. It might have never been possible for Motorola to overcome their management problems and infighting to progress 68k at the zenith of RISC hype.
With most architecture+compiler combinations, a register is dedicated to holding the frame pointer, a pointer to a fixed position in the stack frame of a function containing the return address to the caller. For x86, ebp (rbp in 64 bit mode) is used for this purpose, and a stack frame looks something like this:
var_2 at [ebp-8] <-- top of stack, lowest address (yes this is counter-intuitive)
var_1 at [ebp-4]
return_address [ebp] <-- ebp points here
arg_1 at [ebp+4]
arg_2 at [ebp+8]
No matter how much data you push onto the stack in local variables (even variable length structures eg with alloca or variable length arrays in C), the parameters are always accessible at positive offsets from ebp while the (fixed-size) local variables are at negative offsets.Without a frame pointer, parameters must be accessed relative to the stack pointer instead. Disadvantages of this include:
Both parameters and local variables are at positive offsets in comparison to esp, so it's harder to tell the two apart.
The offsets can change throughout the function as variables are pushed and sometimes popped from the stack, making analysis even more difficult.
You can't allocate variable width structures on the stack because then the compiler would not know at what offsets the parameters/variables would lie.
And it's not even necessarily a performance win either, because x86 uses longer instruction encodings for sp-relative addressing vs. bp-relative addressing.
x86_64 and most RISC architectures don't have this problem, there are enough spare registers that the negatives of -fomit-frame-pointer outweigh the positives.
Not personally, but the stories that the press chooses to report absolutely has an effect on purchasing decisions in the aggregate. I'm not cool with people like Zoe Quinn using their incestuous relationships with the press to get a leg up on other, more deserving indies. You know, people that make good games instead of harassing suicidally depressed people, intimidating photographers, attacking other feminist organizations for competing with her charity, getting "The Most Expensive Game Jam in History" canceled over personal drama, attempting to censor controversy with DMCA takedown notices, and just in general being a professional victim.
Corruption should not be tolerated anywhere, so I'm happy some people actually give a shit and are taking a stand for once instead of forgetting about controversies the next day as usual. I can see people here being upset that others are putting more effort into GamerGate than they do into much more deserving causes like fighting NSA surveillance, but you don't get to choose what people care about.
As for why others care, I guess it's part being tired of being one of the internet's punching bags, part being tired of Silicon Valley yuppies and trustafarians complaining about the "privilege" of a bunch of roughly lower-middle class youth, part seizing a chance to strike out at the loathsome "clickbait" media that everyone else on HN would be condemning in any other scenario, part not wanting to see video games become yet another medium neutered by the cultural marxist PC police, part spite, and part breaking out the popcorn as they watch the other side make complete asses of themselves on blogs and twitter. The last reason is my favorite, it's absolutely hilarious how vile and hypocritical some of these people are.
EDIT: As I've alluded to, I think GamerGate is the start of something akin to the Occupy movements for the left, or the Tea Party movement for the older right. They begin with a frenetic spark, and it can be hard to discern what "they're about," and sometimes people do bad things in their name, but you have to look past the surface to see there is a meaningful sentiment being expressed. Give them time to find their voice and remember that many positive movements had a rocky start.
I think the vast majority of GamerGate supporters would agree with me about that; I check up on GG threads every day, and it's pretty clear that no one supports harming people. In fact, almost no one ever brings doxing up. On the rare occasion someone does, they're called an idiot, accused of "false flagging" (ie someone anti-GG pretending to support GG with threats of violence to make the movement look bad. yes, this has happened, people have been caught making violent comments just to take a screenshot that "proves" how evil GG is), and their posts are deleted pretty quickly. 99% of the focus now is on contacting advertisers and showing people all of the horrible things that the "journalists" in question say and do (like "nerds should be constantly shamed and degraded into submission. bring back bullying"). When someone actually does get doxed, the overwhelming reaction is not "fuck yeah, patriarchy" but "what the hell are you doing, idiot?"
The current suspicion is that GNAA (you know, the people that were in the news semi-recently for harassing Kathy Sierra) is behind most of the death threats and doxing. It's like a "double troll" for wackjobs like them: They get an excuse to harass people while another group takes all the flak for it. Everyone's mad!
But hey, that's just my two cents. You can bring on the downvotes now, echo chamber.
When I'm trying to keep it civil here and upvoting people I don't agree with when they make good points, and I get silenced in return, all it does is polarize me further. gg folks, have fun thinking I'm evil/brainwashed/sexist in your echo chamber.
Some examples of the second group might include the people who flagkilled half of my comments in this thread. Man, I know political threads on Reddit News are a steaming pile, but y'all could at least pretend to be capable of talking to people you don't agree with and downvote me into oblivion instead.
http://www.gamasutra.com/view/news/224400/Gamers_dont_have_t...
Phil Fish forced himself off the internet by being a contemptible jackass with an ego to rival that of Kanye West who fights with his coworkers, publicly shat on an aspiring Japanese game dev during a Q&A panel that asked him a polite question regarding his thoughts on their country's games, says that gamers are "the worst fucking people," tells people to "suck his dick, choke on it" then claims to be a feminist without a hint of irony, completely and utterly lacks self awareness, and just generally can't go a fucking day without throwing a tantrum on twitter.
EDIT: Oh neat, my other post in this thread, a collection of links from an opposing perspective, was flagkilled. Way to flag/downvote for disagreement, redd-I mean Hacker News.
Maybe I'm completely fucked in the head or something, but since only one or two other people in this comment thread seemed to catch my drift, I'll be explicit: the specific phrasing of "honeypot video gallery" makes me think "collection of videos that some police or 3 letter agency uses as a honeypot to catch criminals" which translates to "either gore/snuff or child pornography." Either something illegal to look at, or an article discussing the topic that could still ruin a sensitive or vulnerable person's day.
And of course such a thing would never reach 50+ upvotes on HN, but when I posted that comment, it was on the front page with 3 points and 0 comments. It was entirely within the realm of possibility then of being something horrible that a troll had used a voting ring to promote. Maybe now at 56 upvotes this concern seems ridiculous, but I hope my apprehension might make some sense within that context.
(also, I think it's ironic that literally the only time I've ever felt that a different submission title would be warranted, it remains unchanged...)
As the post mentions, early versions of Minecraft allocated significantly less garbage. You know, the versions programmed by one guy, before they had millions and millions of dollars and a whole team working on it.
Yes, Minecraft has changed quite a bit since 1.3, when Notch abdicated the development throne, but really not that much considering it's been over 2 years and that Minecraft is a generation's Mario. Most of the "slew of new features" came from mods (still no official modding API, either!)
>Maybe not enough people cared about the lag vs new features? It's not like Minecraft is a competitive FPS where lag matters a lot more.
You don't understand. The "lag" you described is a constant delay between input and response. An example would be vsync, which in most PC implementations trades an extra frame or two of latency for smooth, tearless video. The problem I was describing is jitter, which is variable delay. One frame may take 10ms, the next may take 100ms+, due to the garbage collector. This is extremely noticeable and annoying when playing Minecraft, because the game locks up temporarily every few seconds and makes even simple actions like walking in a straight line extremely choppy and disorienting. Aside from being unpleasant and breaking "immersion," it's even gotten me killed when a GC cycle kicks in just before a jump and the game misses the jump input. It absolutely affects the experience.
>First the Minecraft still doesn't have heavy hardware requirements.
It kinda does, if you want smooth performance. You can play it on a toaster, sure, if you ratchet the draw distance down and are ok with sub-30 FPS and lots of GC-induced jitter.
My point was simply that if you make your game perform worse than it could, you're pushing the cost onto the players, and while this is a normal part of the march of computing, at some point it stops being acceptable and you're hurting the experience for the average player. IMHO, considering how ridiculously profitable Minecraft is and how little the fundamental gameplay has changed over the years, it stopped being acceptable a long time ago.
>Second the cost of computing has been trending downward for decades.
That's nice, but little kids from all backgrounds love Minecraft. You can't just ask an elementary school kid in the projects playing Minecraft at his community center on a donated computer past its prime to upgrade.
>Programming Java isn't easy especially when you have an existing code base. It's even messier when you give precedence to performance.
Again, the code performed reasonably well before. The new devs "cleaned it up" without measuring the performance impact of their style changes, and now everyone is paying for it.
>If this is so easy, why not just make a better clone to fix the problem?
Ah, the old "you can't complain because I don't see you doing any better" schtick. Take it easy, I don't think it's so controversial to be perplexed that one of the most successful video game franchises of all time is managed so poorly; for example, you'd think hiring the Optifine guy would be a no brainer.
It makes absolutely no sense when you are selling a program to users that will use it on a wide variety of hardware, from high-end to decade old. That's a great example of a selfish externality, asking millions of players all around the world pay for expensive new machines (even top of the line ones are going to have problems managing 200 megabytes of garbage per second without dropping frames) just to make your job easier.