HNHacker News
TopNewBestAskShowJobs

near

5,473 karma · joined January 21, 2012

submissionscomments
near··on UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
> One example: "He could have stayed if he wanted to." You don't know that and can't really know it, so stop saying it.

As I keep saying, the only publicly available evidence is that your resignation was voluntary. Voluntary implies optional. Optional implies you could stay. There's no leap of logic here.

Yes, there could be behind-the-scenes NDAs and private events that meant you couldn't have. But unless you provide any shred of evidence, then I can't go on those.

Imagine this like a court of law. Your vague hints of knowledge I am not privy to would be inadmissable evidence. Because of course it would be.

> (which I refute all the time by saying I resigned)

Well there you go! There's our answer. You weren't fired, you resigned. Right from the man himself :D

> Who asked you to hold anyone in contempt?

Who asked you who could get married and who couldn't?

I have the right to hold any opinion I want about anyone. It's just an opinion; it has no authority. People in this thread are mad at Mozilla, claiming they fired you. If that is true, I want to join them in their anger. But I want evidence first.

> No third or fourth alternative?

Sorry, I'm not trying to be obtuse. I can't think of a third or fourth alternative. I'm not the brightest bulb out there, but I like to think I'm reasonably capable of imagining multiple possible scenarios. But I've got nothing here.

> "The protestors had zero control over the Mozilla board."

Come on, now you're just messing with me. Nobody here believes people on the internet shouting at you had the power to force Mozilla's board to act the way they wanted. It's a company, not an elected body. You yourself made that argument about oppression and agency. They may not have liked their options, but nobody held a gun to anyone's head and forced them to fire you. Even if keeping you meant burning the whole company to the ground, they still had full autonomy to make their own choice.

Or are you going to go reductio ad absurdum and tell me that I don't (and can't) know if any protestors held a gun to your board members' heads? :P

The rest ... fair enough. It seems I need to preface everything with "it's my reasonable assumption that ..." when speaking with you ;)

> Just consider your "He could have stayed if he wanted to." Why'd you write that?

If your resignation was voluntary, that implies you could have stayed. If you couldn't, it would thus not be voluntary. Because that is what the word voluntary means. It implies you made a choice. If you were saying you chose to resign instead of being fired, then you didn't make a choice, you were fired. Calling that a voluntary resignation is bullshit.

> I mean what needs did it serve to say something you can't possibly know, as if it were an incontrovertible fact.

Our basic communication breakdown here is that I am treating fact as "what's in the public record"; and you are treating fact as "you were actually there for it." Yours is obviously superior. But you won't share the latter with me, again which is fine! But if you don't do so, then don't blame me for treating the former as fact. It's no different than the way a court of law would treat it. I'm not being unreasonable here. I can't read the tea leaves and divine what really happened, nor can anyone else. That doesn't mean we can't ever talk about it. There are lots of unknowns in the world, and I am following the way reasonable people discuss and interpret those things as best they can.

near··on UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
> It's not for you to cross-examine me, though.

You're right. And in this case, I wasn't. I responded to someone who said you were fired with an official statement that contradicted it. You joined into the discussion with, "you don't know and I don't have to tell you."

Which is fine! In that case, I will continue to correct anyone who says you were fired by pointing to the only official statement on the matter that says you resigned voluntarily. Is that fair? Surely you can't blame me for not relying on secret information I don't know.

> It's nonsense to make complex human interactions involving mobs, boycotts, hidden C-suite action, and finally resignation into an either/or in every single case.

I'm definitely not making that claim in every case, only in this one case. I agree with your premise in general.

> did Nixon resign? Of course.

It was inevitable that he would have been impeached had he not. There was no indication that Mozilla did anything but stand behind you the entire time.

I do understand the point you're trying to make here. But please understand that I can't hold Mozilla's board in contempt for something without any evidence or even statements on the matter. And you don't want to give them and that's fine. Just, as such, the record stands that you left of your own volition.

> Can you not conceive of excluded middles left out by the two alternatives you pose as if mutually exclusive and exhaustive of all possibilities?

No, I can't imagine a scenario where you were both made to resign, yet Mozilla was not lying when they said you left voluntarily.

I am acutely aware that there was a huge reason for you to, even if I can't speculate that it had anything to do with your actual decision. But the protests and boycotts were a clear elephant in the room.

Like you said with agency, you should have still had it despite the protests. The protestors had zero control over the Mozilla board. Yes, you staying could have damaged the brand more (I doubt it would have done much damage, but that's a separate discussion.)

We're not making progress so let's try this from the other side: we both agree those calling for your firing were in the wrong, and should not have been listened to. I'll even go further and say it was wrong of sites like OK Cupid to use their site as a tool to boycott Mozilla by blocking your browser - as that forced their users into the boycott. But do you agree that the people voicing their displeasure with your donation and deciding not to use Firefox because you were made the CEO had a right to do so?

Discounting the two things we both agree on (calls for firing, websites blocking Mozilla), what would you have wished were handled differently? What else do you feel was unfair?

If secretly Mozilla led you to believe you would be ousted soon without resigning, then that would be on the board, and only the board, yes? And if that information remains secret, then we the public can't hold them accountable for that, can we?

...

And as for me ... it seems we're never going to get past discussing a donation you made eight years ago. So when it inevitably comes up again that you were 'fired for your beliefs', how about this?

I will respond that according to the only official statement from mozilla.org, you voluntarily resigned. I will then link to your discussions with me and state that you claim there are circumstances that are not public, and that people can make up their own mind on whatever that statement means from there. But again, that the only official record refutes their claim.

Would you accept that? It's really not my goal to keep annoying you (or anyone else) here. I just don't want to see conjecture passed off as fact. Especially not on HN.

near··on UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
> your "Eich chose to step down due to community pressure" line, which you made up.

You are correct. That was conjecture. I don't know the actual thoughts in your mind when you stepped down, because you won't tell me.

Right now, the only solid evidence we have is that mozilla.org blog post that you voluntarily stepped down. Unless you will renounce it, then to the public record, it will remain what is believed to be true. And anything else, "you were forced out", "you were fired", "you resigned due to pressure", etc is hearsay.

> This does not exclude other possibilities that are none of your business.

I believe it is the business of the public whether you were given an ultimatum or not. It would greatly influence how many felt toward the senior leadership of Mozilla.

> "Forced or resigned" is a false dilemma in general.

I disagree strongly. There's a world of difference between me choosing to leave my job to protect my company; and my company firing me, making me sign an NDA, and lying and saying I left voluntarily. The former is commendable (if unfortunate) on your part; the latter is absolutely reprehensible on Mozilla's part.

> Oppression does not remove agency from the victim.

It can. There was no serious option for me to move to a country with full marriage equality (the world does not have open borders - even permanently moving to Canada requires hosting by a family member, substantial capital to invest, or an asylum request); and only partial redress (state-level) were I to choose to move to, say, Massachusetts. Which also wasn't much of a possibility as my spouse did not want to leave his family behind in Ohio. But I guess you could say the latter was a matter of prioritizing.

Those ballot initiatives were definitely aimed at removing agency from gay and lesbian couples, that much is for sure.

> Can we agree on this much?

In the general case that the two can be true at once, yes. But I don't see how your resignation can possibly exist in a quantum state where you were both forced to resign and weren't. It can only be one or the other.

I can understand there being subtle hints and allusions that a firing would have been inevitable should you choose not to resign, but unless they were substantiated, they were just that. I'm not going to read between the lines to speculate on what might have happened had you chosen to stay onboard.

I'm dead serious: if you really were forced out but just can't tell me, then you have my sympathy. I never once called for you to be fired. Free speech only works when we all have it. The only thing I did, and stand by, is my own free speech to voice disapproval for your donation. I also stopped using Firefox until you had resigned.

(I do have some thoughts on money not being the same as speech, but that's a whole different issue.)

near··on UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
I didn't link to that because you didn't answer the topic being debated here.

Would you be willing to go on record and state whether you were forced to resign or not? If you were, then I agree that was wrong, and will stop linking to that FAQ post going forward. Instead, I'll link to your reply and offer my support that Mozilla was in the wrong for forcing you out.

However, if you're going to stay with, "NDAs and none of your business", then I can't work with that. I can only work on what knowledge is available to the public. And all publicly available evidence is that your resignation was entirely voluntary. I hope you'll agree that unless someone actually involved (such as yourself) goes on record, everything else is just baseless speculation. It wouldn't be fair to penalize Mozilla based solely on conjecture.

And yes, I was in Ohio during our 2004 vote to ban marriage equality via state constitutional amendment. I stated that people like you (as in, religious people imposing their views on others through force of law) helped make that happen. Marriage wasn't really on my radar until around 2008. I think it was just seeing California of all places vote against it that really crushed my spirit for a long time. I know empathy is really difficult, but imagine if our positions were reversed and I donated to successfully help prevent you from marrying your wife. How would you think of me? That I didn't live in California is 2008 is no reason I can't object to your actions.

As always, even if we strongly disagree, I appreciate that you're willing to respond and have a discussion with a nobody such as myself, so thank you for that :)

near··on Emulator Latency
I think it's just barely possible for the fastest NES and GB emulators to use this trick for one single frame of lag reduction.

Here, you have eight inputs (assumes one player on the NES.) But there's a trick: up+down and left+right aren't physically possible due to a rocker in the D-pad. So as a whole, there are nine possible D-pad states instead of sixteen. With four buttons, that's sixteen possible states. So the total is 144 states.

Now look at QuickNES, blargg's masterpiece NES emulator that runs fullspeed on a 66MHz PowerPC system. If you had the fastest, overclocked octacore CPU Intel makes, you may be able to pull off 144 instances of the emulation. Especially since you don't have to actually output the audio and video for all the missed predictions to the real hardware.

Or perhaps more sanely ... most games don't have you using start+select while playing. I think people would be willing to accept a large jitter when pressing those two buttons. So now you're talking 36 instances, which starts to look very reasonable. At least, for emulators that are okay with sacrificing accuracy.

The most popular NES emulators today require 800MHz (Nestopia), 1.6GHz (Nintendulator), and I'm not sure on puNES, but presumably just as high. 36 instances of those are unlikely.

Still, this would be a fun experiment if anyone were willing! :D

Of course, the end result is a 16ms lag reduction. And again, I need to stress ... I get that latency stacks, but ... you're really going to have a hard time even telling the difference between the two. Even if you're one of those people who can beat Dodonpachi or Ninja Gaiden or Battletoads on one life.

near··on Emulator Latency
Yes, the best thing that could happen to emulation latency reduction would be the creation of a skeleton OS framework. Something that piggybacks and can use existing Linux or BSD hardware drivers, but puts the emulator in kernel space and lets it manage the hardware as directly as is practical.

I talk about this briefly in my infeasible section. But I'm mostly referring to myself there: I just don't have the skill and the time to write my own real-time OS for this.

However, I do hope that one day we see a serious project that isn't just "lightweight Linux" (eg Lakka, etc) or something running on top of DOS.

I presume that 98% of emulator users aren't going to be willing to boot into an "emulator OS" just to play games; so it's going to be a lot of work for a little gain.

In that vein, the ultimate latency reduction would be an entire FPGA emulator, like kevtris' FPGA NES (http://kevtris.org/Projects/console/video/page1.html), but now you're approaching extreme effort for a userbase of maybe ten people :/

near··on Emulator Latency
> Why is the application audio buffer necessary?

It's more about the APIs used. With something like OSS, you just write samples to a (virtualized to many devices) /dev/dsp handle. So you have to take your background music, and each sound effect channel, and mix the values together.

But if you're writing a PC game on Windows, you'd open separate IXAudio2SourceVoice handles for each, and I'm presuming that XAudio2 will handle all the mixing and when to optimally push samples to the hardware for you. You're working at a higher level here when you can provide the hardware/OS audio API with more information.

But an emulator just gets a solid stream of pre-mixed samples. Sometimes the game software have their own mixers (like Tales of Phantasia on the SNES), and these tend to fall back on game console hardware mixers, that then pass a rendered stream of audio out to the speakers (hence, indirection.)

With audio, how you handle it depends on the backend API. With DirectSound and WASAPI exclusive, it acts like a ring buffer in RAM that loops around and you poll the cursor (sample) position to know when and where to write. With XAudio2 and WASAPI shared, you build up tiny blocks of samples and throw them at the sound API. In both cases, even at 44KHz, it's not a smart idea to do this for every single sample output. So you're going to have a software queue that accumulates these samples. And the size of these queues aren't just about minimizing calls to the sound API, but it's also about the API's own precision and at what resolution it can report when a pushed buffer is consumed or where the cursor is at. This varies wildly between PCs. So the best you can really do is offer the user a latency selection and let them see how low they can set the value without audio distortion from misses.

A final complexity with emulation is that we can still have multiple audio streams. When you plug a Super Game Boy cart into an SNES, or a CD attachment onto a Genesis; the emulation of these usually results in two streams.

As mentioned in the article, generally you can merge two streams in software in near-realtime. Presuming both sound sources run at the same frequency, you only need one sample queued from both sources before you can mix them and send them to your sound API output buffer. Though keep in mind we are making a parallel process serial, and the context switches between components is the biggest source of slowdown in all of emulation, so sometimes you'll have quite a few samples from one component queuing up before we get any from another. It gets a bit fancier when they vary frequencies (and they do in emulation) ... and then you get to pull in anti-aliasing, resampling audio filters (I use butterworth biquad type-2 IIR with cubic resampling in higan), so the queues have to get a little tiny bit larger.

On anti-aliasing, that's yet more fun ... a lot of these old game consoles produced sound in the megahertz range, so you have to strip out the frequencies above the Nyquist limit to prevent aliasing (annoying buzzing) when you resample it to rates PCs can handle (in the kilohertz range.)

near··on How bad is the Windows command line really?
It's really, really, really, really really bad.

It doesn't even have a logical history. Despite having used it for many years, I still don't understand why when I type one command (eg make), and then another (eg out.exe), I have to toggle between pressing up or pressing down from the new command-prompt to access the previous commands.

I can't make the window more than 80-characters wide dynamically. (I don't want to change settings and restart the program to get the width to change.) So any time I want to copy and paste one of the infamous wall-of-text C++ template errors, I have to waste a lot of time reformatting the text.

Copy-and-paste as well is just complete garbage that takes forever.

I have to dump batch files into a folder in PATH because there's no alias support nor .profile startup script.

I can't color-code the prompt separately for visibility. There's no tab-completion. There's no shell escaping backticks. On and on.

Batch scripts are just hopelessly broken. It really feels like we're abusing the hell out of them to do things they were never intended to do. The language is closer to Malbolge than C.

PowerShell is a whole other can of worms. I don't care for it either, but that'd be a separate discussion.

Bash on Windows sounded promising, up until "Windows 10 only" and "doesn't play nice with the regular Windows environment."

near··on W^X now mandatory in OpenBSD
An emulator is a very different use case than Firefox's JIT.

Take Dolphin (the Gamecube / Wii emulator) for example: you have a 4GiB DVD, it has a massive 80-hour game's entire code engine on there. You cannot recompile the entire disc at startup. Even if you could (you really can't), these games tend to push code into RAM to execute, which a static recompiler cannot handle.

The way dynamic recompilers handle the tremendous burden is to recompile small blocks at a time, and track which ones are hot and cold. When the buffers fill up, they start dropping old, stale code.

It's hard to say exactly what the performance impact would be, and it'd probably vary per game title. But it'd be a lot worse than a web browser recompiling jQuery plus another 200KiB of custom Javascript once on page load.

Plus, I am sure there are many more uses cases for W|X than just emulators and JITs. It would be a shame to try and eradicate them all from existence.

near··on W^X now mandatory in OpenBSD
I've always been in favor of all OpenBSD security enhancements I've seen, but I have to say, and please hear me out, this is an objectively terrible idea.

Yes, most programs should disallow W|X by default. But trying to banish the entire practice with a mount flag, knowing full well few people will go that far to run a W|X application, is bad practice. I'd rather see this as another specialty chmod flag ala SUID, SGID, etc. Or something along those lines. One shouldn't have to enable filesystem-wide W|X just to run one application.

The thing is, when you actually do need W|X, there is no simple workaround. Many emulators and JITs need to be able to dynamically recompile instructions to native machine code to achieve acceptable performance (emulating a 3GHz processor is just not going to happen with an interpreter.) For a particularly busy dynamic recompiler, having to constantly call mprotect to toggle the page flags between W!X and X!W will impact performance too greatly, since that is a syscall requiring a kernel-level transition.

We also have app stores banning the use of this technique as well. This is a very troubling trend lately; it is throwing the baby out with the bathwater.

EDIT: tj responded to me on Twitter: "the per-mountpoint idea is just an initial method; it'll be refined as time goes on. i think per-binary w^x is in the pipeline." -- that will not only resolve my concerns, but in fact would be my ideal design to balance security and performance.

near··on Ask HN: Oldest code you have written that is still in use?
Certainly, backward compatibility is critical and has always been a weakness of mine. I've always been an idealist there.

But in xkas' case, this was code from before I really learned how to program; let alone design a proper parser. This would be like asking for strict compatibility between Linux 0.01 and Linux 3.0.

I understand how SMWC became trapped in a cycle of using xkas v06, but any new projects really have no sane reason to be using it anymore. And I'm not even saying, "use bass instead!", there's dozens of cross-assemblers that work much better than it ever did (it would seem that writing an assembler is a rite of passage for ROM hackers.)

near··on Ask HN: Oldest code you have written that is still in use?
It's a native code execution exploit.

He exploits the parser to corrupt the stack frame, and executes raw x86 instructions embedded in that file.

How exactly it converts that pile of gibberish into a valid x86 program is beyond even my comprehension.

Alcaro's always been a wizard at stuff like this. Here's an example of an SNES ROM image he crafted to execute native x86 code from inside ZSNES: https://www.youtube.com/watch?v=Q3SOYneC7mU (Yes, you can potentially get a real PC virus from loading up an SNES ROM in ZSNES. Or a specially crafted source code file in xkas v06.)

near··on Ask HN: Oldest code you have written that is still in use?
There's a reason I stopped associating with that scene/site years ago. Almost everyone in it is toxic and stuck in their rebellious teenage years. Case in point: http://www.romhacking.net/forum/index.php/topic,21797.html

The newer versions are called bass, and you can compare yourself here: http://byuu.org/tool/bass/

There is full documentation of every possible command, the code is readable by human beings (eg variables are named words instead of single letter abbreviations, C++ is used for more than just the class keyword, there's more than one source code file, I learned how to use the spacebar key in my code, etc), it has a real recursive descent parser that builds a proper abstract syntax tree for evaluations, it has a macro system that supports recursion and conditional evaluation, supports multiple architectures instead of just one, allows the user to dynamically add/change the actual opcode mnemonics used by the assembler (useful as the SNES has games using several strange coprocessors), has no known bugs (as opposed to xkas' that allow native code execution), etc. xkas was written when I had about a years' worth of real programming experience, bass was after over a decade's worth of experience; including experience using assemblers to create code.

If you want to know why RHDN users threw a fit about it; it's because I used // as a comment delimiter instead of ; and decided to add a closing marker to defines so you could say "lda {macro}_b", which was impossible with the old "lda !macro_b" because it'd look for "macro_b" instead of "macro".

That's really it. That's the whole of why many people there say they'll never use it. The syntax is 99% compatible otherwise. I could link you to posts saying as much, but I really don't feel like browsing their site any more than I have to.

SMWC's case is very different: they're all hacking the same game, so they require 100% backward-compatibility with a decade's worth of game patches; and they only make the problem worse as time goes on. This constraint would not apply to new games started on from scratch.

near··on Ask HN: Oldest code you have written that is still in use?
I couldn't find said example (sorry), but I did find one of his other examples of abusing the assembler:

http://bin.smwcentral.net/u/1686/boredom.asm

You won't believe me unless you try it for yourself, but ... download xkas v06 here:

http://www.romhacking.net/utilities/269/

Then download the above boredom.asm. And now run the following on the command-line:

    touch boredom.sfc
    xkas boredom.asm boredom.sfc
Note again that this is a cross-assembler to produce code for the Super Nintendo. Yet you will be greeted by a fully-playable game of Snake in the terminal window. No, I am not kidding. (The black hats here can probably guess what's going on.) For those who won't/can't try it out: http://i.imgur.com/LTSAHw1.png
near··on Ask HN: Oldest code you have written that is still in use?
There's an entire community of video game hackers (smwcentral.net) using a cross-assembler I wrote in 2001 named xkas. I added a few minor patches and by early 2004 I had released the final version, v06.

I never really intended for anyone to use it seriously. I made it for myself, but went ahead and posted it online anyway. It is a 1500-line single-file, nearly-commentless, nearly-spaceless abomination of code with no documentation, and an endless list of critical bugs that every user keeps encountering. They have elaborate workarounds for many of these bugs.

It became a negative feedback loop: "Why do we use xkas? Because everything else is written in xkas", and so now even more code was created and written in xkas. And so even though I've since written a proper assembler that's dozens of times nicer, no one can/will use it.

Lately, people have been writing their own versions (in addition to countless forks) that try to offer backward compatibility with all the crazy parsing errors and (mis)features of xkas, like left-to-right evaluation of math expressions, and the most convoluted macro evaluation system you've ever seen (one user proved it was Turing complete and wrote a Brainfuck parser in it.)

It's surreal. I feel terrible that so many people are stuck with this mess, but even I can't stop it anymore :/

near··on The Trouble with CloudFlare
Hello, please also consider VPN usage. Unlike Tor, we even pay for this service, because we take it so seriously.

Despite using the most reputable VPN provider I could find with a serious privacy policy; I've seen a steady increase in Captcha requests from CloudFlare to simply view read-only pages. And all I can think is that the Captcha page often requires the same amount of bandwidth as the page I was requesting in the first place.

The net effect is that it's not saving you any CPU usage or bandwidth (if anything, it's costing you more as we still request the actual page after the Captcha system runs), it's making customers like me abandon your customer's sites out of frustration, and it's eroding the last line of defense we have against invasive tracking.

I'm sympathetic to the problem you're trying to solve, but surely there must be a better way for simple GET requests.

This doesn't just affect people like me as a user. Having experienced this, I would be averse to deploying or recommending CloudFlare in its current state.

near··on To defend the free web, save Mozilla
> You have no idea why I stepped down, or about anything else that went on behind closed doors.

I'm going off what Mozilla has said publicly: "Brendan was not fired and was not asked by the Board to resign. Brendan voluntarily submitted his resignation. The Board acted in response by inviting him to remain at Mozilla in another C-level position. Brendan declined that offer. The Board respects his decision."

Source: https://blog.mozilla.org/blog/2014/04/05/faq-on-ceo-resignat...

You're absolutely right that I have no idea what happened behind closed doors. If you'd like to speak to that, I'd be very interested in listening. What you've said in this thread doesn't contradict anything I've said about you voluntarily resigning.

> Calling me a name because you assume things about me

What is there to assume? You donated money to a group that was formed for the sole purpose of taking rights away from people. Rights that you enjoy, rights that caused harm to no one, rights that had no effect on your life otherwise. There's nothing at all ambiguous about what you did. It was an objectively terrible thing to do. I cried on November 2008. That was one of the hardest months of my life, and I don't even live in California. I can't imagine how much harder it was for all the families trapped in limbo as the courts decided whether to dissolve their marriages.

A bigot is "a person who is intolerant of any ideas other than his or her own." You don't like gays marrying? I don't even care, good for you. But what you did is even worse than that: you took action to legally prevent them from enjoying the same rights you have.

I'm sorry if you don't like the word, but you donated that money, and I didn't write the dictionary. I hope one day you'll come to understand what you've done and apologize, but it's been seven years, so I'm not holding my breath.

And the "intolerant of intolerance" response is nonsense designed to do nothing more than shut down debate.

> Save it.

I'd love to. On this issue, you lost. Marriage equality is the law of the land, and you can't vote our rights away this time.

Personally, I'd like nothing more than to not hear your name again. But every article on Mozilla at HN brings you up again and again. (And of course, we're also stuck with Javascript.)

near··on A Constructive Look at TempleOS
What really gets to me about all this is that I probably see more articles about losethos/TempleOS than I do about the BSDs.

There's a whole world of hundreds of small and innovative hobbyist/niche OSes (Sortix to name just one), but we only ever hear about this one. Again and again, over and over, because the author's mental health makes for good clickbait articles for people to gawk and stare at, apparently. It's really quite sickening.

I'm okay with this article though, I like that it presented something new for a change.

near··on Apple’s Tim Cook Delivers Blistering Speech on Encryption, Privacy
Does Mozilla's track record include their suggested advertising tiles on your newtab page, based off your browsing history? Or their defaulting to Yahoo to send your searches because they were the highest bidder?

Now yes, they say the tiles are based on your local history and not transmitted anywhere; so it's not as bad (I don't care if other people don't see it, I don't want my data mined even locally for the purpose of showing me ads); but it's pretty clear that Mozilla is a business that wants to earn money. And as the saying goes, "if you're not paying for it, you're not the customer -- you're the product."

But you're right about one thing: they're probably the least bad of all the browser manufacturers on all this. Maybe what we need is a crowdfunded browser, where the company listens to their users and has no conflicts of interest.

near··on Intent to deprecate: Insecure HTTP
Oh, certainly. I agree completely with everything you said.

But right now, the situation is that I go to arstechnica.com, which offers no encryption whatsoever, and Firefox just loads it up like nothing's wrong.

Yet I go to self-signed.example.com, and Firefox presents me with a giant warning screen, followed by a pop-open warning dialog, where I have to click to confirm the security exemption, add the certificate in, and OK another scary prompt. It's so over the top that laymen probably think proceeding will give that site complete interception control over every site they ever go to again in the future.

That's absolutely ridiculous. Worst case, self-signed should be treated like HTTP is now. No padlock, no green address bar.

People who are knowledgeable and able to confirm self-signed certs should be able to very quickly and very easily do so. This will greatly help with developing inside the local network, or for small communities that know what they're doing and don't want to pay hundreds of dollars for wildcard SSL certs.

near··on Intent to deprecate: Insecure HTTP
But what kind of technology would think self-signed certificates could ever be better (let alone not infinitely worse) than no encryption at all? That sounds like hell. We should call this new, purely hypothetical protocol, SSHell, or SSH for short. Not that such a thing would ever be used by anyone, of course.

(Yes, I know that technically SSH uses key pairs; but they show you the key, you choose to trust it. Same real chance of a MITM as with a self-signed SSL certificate. But at least you (and others) can now detect when there's a change in who's sending your data, and choose who to trust yourself instead of relying on Mozilla to pick who to trust, like they did CNNIC.)

near··on Former Nvidia Dev's Thoughts on Vulkan/Mantle
The idea that nVidia and AMD are detecting your games, and then replacing shaders, optimizing around bugs, etc should be absolutely terrifying. And vice versa, the idea of having to fix every major game's incredibly broken code is equally terrifying. And it's a huge hit to all of us indie devs, who don't get the five-star treatment to maximize performance of our games. So overall, I'd say this is a step in the right direction.

However! Having written OpenGL 3 code before, the idea that Vulkan is going to be a lot more complex, frankly scares the hell out of me. I'm by no means someone that programs massive 3D engines for major companies. I just wanted to be able to take a bitmap, optionally apply a user-defined shader to the image, stretch it to the size of the screen, and display it. (and even without the shaders, even in 2015, filling a 1600p monitor with software scaling is a very painful operation. Filling a 4K monitor in software is likely not even possible at 60fps, even without any game logic added in.)

That took me several weeks to develop just the core OpenGL code. Another few days for each platform interface (WGL/Windows, CGL/OSX, GLX/Xorg). Another few days for each video card's odd quirks. In total, my simple task ended up taking me 44KB of code to write. You may think that's nothing, but tiny code is kind of my forte. My ZIP decompressor is 8KB, PNG decompressor is another 8KB (shares the inflate algorithm), and my HTTP/1.1 web server+client+proxy with a bunch of added features (run as service, pass messages from command-line via shared memory, APIs to manipulate requests, etc) is 24KB of code.

Now you may say, "use a library!", but there really isn't a library that tries to do just 2D with some filtering+scaling. SDL (1.2 at least) just covers the GL context setup and window creation: you issue your own GL commands to it. And anything more powerful ends up being entire 3D engines like Unity that are like using a jack hammer to nail in drywall.

And, uh ... that's kind of the point of what I'm doing. I'm someone trying to make said library. But I don't think I'll be able to handle the complexity of all these new APIs. And I'm also not a big player, so few people will use my library anyway.

So the point of this wall of text ... I really, really hope they'll consider the use case of people who just want to do simple 2D operations and have something official like Vulkan2D that we can build off of.

Also, I haven't seen Vulkan yet, but I really hope the Vsync situation is better than OpenGL's "set an attribute, call an extension function, and cross your fingers that it works." It would be really nice to be able to poll the current rendering status of the video card, and drive all the fun new adaptive sync displays, in a portable manner.

near··on Jon Ronson: How a Tweet Can Ruin Your Life
The world is replete with examples of why you should never use your real name with your online identity in any way (although in this case, the guy's employer found out over a photograph; which is even more troubling.)

If there's anyone worse than Adria in this story, it's both Hank's and Adria's former employers. You don't destroy a person's life over a comment or a blackmail threat. But as they say, if corporations are people, then they are clearly sociopaths.

That said, there was this excerpt: "I know you didn’t call for him to be fired. But you must have felt pretty bad." "Not too bad, he's a white male. I'm a black Jewish female."

Followed by this later on, in the same interview: SendGrid, her employer, was told the attacks would stop if Adria was fired. Hours later, she was publicly let go. "I cried a lot, journaled and escaped by watching movies,"

Her lack of empathy is absolutely staggering. And, "if I had kids, I wouldn't tell jokes"? Seriously?

near··on Giving Stephen Hawking a voice
Interesting article ...

> "I'm trying to make a software version of Stephen's voice so that we don't have to rely on these old hardware cards," says Wood.

So back in 2010 we had someone help us extract the program ROM code from the SNES DSP-n coprocessors (used in games like Pilotwings and Mario Kart.) It turns out these chips were NEC uPD7725 DSPs. There was basically only one very terse document on how the chip worked, and no emulators for it, so I had to write one. Had a bit of help in fixing the overflow flag calculations from Cydrak.

A while later, I spoke briefly through a liaison with Sam Blackburn (who was then Stephen Hawking's assistant) back in 2011'ish. They were looking for permission to use my uPD7725 emulation code (which I said yes to, obviously.) Apparently the Speech Plus text synthesizer uses NEC uPD7720s. This is basically the same chip and ISA, but with less ROM/RAM. It's a neat little fact, but not too surprising. These DSPs are really versatile, and different programs can make them do very different things.

Reading this article, it sounds like the effort was as yet unsuccessful, though :(

(It's also important to note that the uPD7720 is probably an infinitesimal part of the overall system, so I suppose they ran into additional problems.)

near··on Ask HN: Can we talk about FreeBSD vs. Linux?
Like others have said, being unbiased is difficult, but I'll try. First, Linux v FreeBSD is really tough, so I will instead approach this from Debian v FreeBSD.

I really like how easy Debian on the desktop is: install it, apt-get install xfce, and I have a nice desktop. It's very easy to add Adobe Flash, Steam, Skype, etc.

The FreeBSD desktop isn't as nice. You can add things like Flash and Skype on FreeBSD, but you have to fight harder and often use the Linux emulator. We're missing nouveau, I've had some kernel panics with the nvidia binary drivers (caused by nvidia's own shoddy code, not FreeBSD's fault), there's a lot of missing and unstable features due to developers primarily targeting Linux these days (Thunar's file refresh is glitchy and often fails to update, Thunar volman only really works with udev/Linux, mousepad crashes when you open a file an even multiple of 4KiB due to a bug in their code and a quirk of Linux mmap, livbte-based terminals tend to crash sometimes when you open them due to a bug somewhere between libvte and FreeBSD's /bin/sh, file-roller explodes when you try and extract large archives, Firefox has freezing issues with loading gigantic images unless you set MOZ_DISABLE_IMAGE_OPTIMIZE=1 in your environment, on and on.)

And it's also not really configured well out of the box for the desktop. I have to make this org.freedesktop.consolekit.pkla file and add entries to it in order to get the restart and shutdown buttons in Xfce to work. I have to create a fontconfig/fonts.conf file and substitute Helvetica with Sans in order to get Firefox to anti-alias text on web pages. And so on.

You are also doing all the setup from scratch. You install xorg, you install your video drivers, you set up xorg.conf, you create .xinitrc, you install a display manager if you want one, etc. This is both good and bad. It's great if you love tweaking your system, it's bad if you just want to throw it on a box and run it.

Moving on ... I really, really appreciate Debian's branches. If you install Wheezy, you can get security updates for packages, but not get version bumps. With FreeBSD, you have to choose between "the packages made at release time", or "the absolute bleeding edge." These updates can and do break workflows, especially on the desktop (Firefox pushed Australis on me, ibus moved to this braindead, slow-as-molasses super+space IME changer, etc.) The actual package installs are about the same for binary (apt-get vs pkg), but I much prefer FreeBSD's ports for building software (which is great when you need to patch software bugs.)

But if you're patient and good at fixing problems, you can end up with a rock-solid desktop. And hey, maybe PC-BSD will save you all of the above steps, too. I kind of look at FreeBSD vs PC-BSD as I do Debian vs Ubuntu: I'd rather know how things work than have it all done for me.

In terms of features, I really like FreeBSD's ZFS, even though it does eat a lot of RAM. Snapshots, whole-disk encryption on root, encrypted swap, mirroring/striping/RAID even across different disks, easy resilvering, etc. I also really like pf a whole lot more than iptables, as I find the syntax a whole lot more readable and flexible, although I will lament that FreeBSD's pf ships with ALTQ (QoS) off by default. I prefer the base system being maintained by the FreeBSD team. I like the consistency, the minimalism, and the great documentation.

Whenever I spot a difference between FreeBSD and Linux, I almost always favor the former's design: /dev/random behavior, jails vs cgroups, SO_NOSIGPIPE socket opt instead of needing the MSG_NOSIGNAL flag, etc.

I like that FreeBSD avoids a lot of the 'licensing wars' BS of Linux. I have Firefox instead of Iceweasel, I have cdrtools instead of cdrkit (I continue to this day to have issues with burning on Linux), I have ZFS instead of btrfs, we had sound mixing in an OSS fork instead of ALSA, and just in general I favor the BSD/MIT/ISC licenses to the GPL.

I very much like that FreeBSD is much more conservative about major changes, and open to choice, so we don't get things like systemd, Pulseaudio, etc pushed on us before they are ready for production. I used to love this about Debian as well, but they've really lost their way as of late in pushing systemd on everyone before it was ready. I greatly value stability over whiz-bang bleeding edge features. I like that FreeBSD is run by a democratically elected core team instead of by a benevolent dictator (I don't have to read what crazy thing Linus or Theo said today in the news.) I like that FreeBSD isn't balkanized into hundreds of different distros. I love not having people telling me to say "GNU/FreeBSD" whenever I mention FreeBSD. I like that third-parties like Redhat don't exert so much control over upstream.

I like the community of FreeBSD more, as it feels that most of the members are more technically oriented. Distros like Ubuntu have brought in a lot of users with little to no experience nor interest in learning the unix way of doing things. I'm not saying this is a bad thing, or that I think less of eg Ubuntu users, just that I prefer the company of sysadmins and developers over gamers and web surfers. I dislike that I can't really discuss the OS with anyone in real life, because it's too niche.

near··on Systemd redux: The end of Linux
> WAIT you NEVER had an audio problem in Linux before PulseAudio?

To be fair, I didn't say I never had Linux audio issues prior to Pulseaudio (whereas I did say that about FreeBSD.)

Back in '98, my SB16 ISA card would only output sound at 8-bit monaural under mikmod, and I could only play CD-audio with that passthrough cable between the CD-ROM drive and the sound card. Once I was able to get sound working well enough, the only way I was able to play MIDIs was through Timidity and Soundfont emulation. And until ALSA, there was obviously pain whenever two things would want to play sound at the same time. This of course was due to the OSSv3 author changing the license before introducing his own audio mixing, and all of those awful sound server daemons (esd et al) never really worked, since there were multiple daemons and each application wanted different daemons or just wanted to stab right at the OSSv3 ioctl's.

But once ALSA was established and working, yes. Audio under Linux at that point worked just fine for me. Pulseaudio was a solution looking for a problem.

> (Previously a Sound Engineer and Record Studio owner)

I won't claim to be either of these. I like to listen to music while I write code, I'll occasionally watch some movies or play some games, and I want Pidgin to make a chime when someone sends me a message.

In particular, I'm very sensitive to latency in gaming (emulation), but that's about the extent of what I need speaker sound output for.

> What people are complaining about is the philosophy aspect.

To me, the worst part is the backroom politics, the complete disregard for portability, and the lock-in effects of consuming other daemons and services, and making software dependent upon it.

However, I do also object to the design itself, as well as to the developers responsible for working on the project, and the attitude of disdain they present to the community at large.

near··on Systemd redux: The end of Linux
> Yet, name one problem you had with sound on linux in the past year?

That's just it. Linux sound worked fine for me before Pulseaudio, and FreeBSD sound has always worked perfectly fine for me. In fact, FreeBSD solved sound mixing sooner via /dev/pcm virtualization (while Linux chose to create the Linux-only ALSA instead), and has always had lower observed latency.

Pulseaudio screwed up my audio so badly that for a year I was running the closed source OSSv4 binaries and manually recompiling all the audio libraries to use OSS instead of ALSA/Pulse.

It is not fantastic to push horribly broken code onto the entire Linux userbase while others frantically jump in to help patch and fix the trainwreck.

And we're doing the same thing again with systemd. Instead of having a few years where users can choose between systemd, sysvinit, openrc or upstart, while all of the major bugs are worked out, we're being forced immediately from sysvinit (Wheezy) to systemd (Jessie). I was on Lennart's treadmill with Pulse, I'm not getting on it again with systemd.

near··on Summary of ZFS on Linux for Debian
I haven't had any issues so far using four drives mirrored on ZFS, but the ECC issue certainly worries me.

I'd love to run ECC RAM, but I'd have to buy a much more expensive processor, a much more expensive mainboard, and all of my RAM would have to be swapped for moderately more expensive replacements. And DDR3+ is not cheap.

I'm curious though, if ECC consists of a ninth parity bit, is there any reason why a memory controller can't be designed that would, worst case, use every other (identical) stick just to get parity bit(s), as a BIOS configurable option? Sure it'd halve your RAM, or you'd pay a lot more in RAM costs, but not having to buy Xeon processors and mainboards, and getting to reuse your existing RAM, would be worth buying an extra stick of RAM in my opinion.

It seems as processes keep getting smaller, and RAM sizes keep getting larger, that the effects of cosmic radiation are just going to keep getting worse. If we can't get desktop CPUs and mainboards to just switch to ECC, surely this would at least be a better-than-nothing option.

near··on Native GUI library for Go
> I keep hearing this kind of defeatism about cross-platform GUI items and it rubs me the wrong way.

To be fair, I do it anyway. My applications run on Windows, OS X, Linux and BSD. I even have a 'stub' GUI so that many can run on the command-line anywhere. I still believe that a Mac app that "sort of looks like a Windows app" is better than "no app at all." But I know that if I were selling a product, "good enough" wouldn't cut it.

It's a bit annoying though how Microsoft and Apple have extensive HIGs, and yet they constantly violate them and go in totally new directions anyway. At the least, it'd be nice if third-party vendors got the same apologist leeway to violate the HIGs, but I understand why first-party vendors get that and we don't, since it's their OS.

> I mean, a unified menubar vs the separate mene/titlebar of Windows/Gnome is exactly the kind of thing I'd expect to be abstracted away by a unified GUI kit.

It sounds like it, sure. Qt tries really hard to do a lot of this stuff. There are special flags you can set on menu items so your preferences and about items automagically move to the right spot. But it's deeply limited: sure it moves your about option, but it doesn't collapse the menu item separator above it, so your menu ends with a separator. Yes you can have a generic FileOpen dialog API, and there's a flag in Qt to make it use sheets too. But what if your app didn't expect another window to remain active during that modal event? This goes on and on and on and on and on.

"But you don't have to take my word for it," look at the reception of Qt apps among OS X users. The only time it's really accepted is when there's no Cocoa-native alternative.

And the more you abstract, the less control you have to really refine the end product. Probably the best and worst solution to cross-platform is going to be declarative user interfaces, something Qt has been dabbling in lately. I just really don't see that approach scaling to rich applications like graphics editors and music libraries.

> I absolutely would expect a unified GUI kit to be tremendously limited by selecting a common baseline of widgets that share functionality and forcing you to fit into a common paradigm that can be easily translated across platforms.

And end users won't like that. Windows users like that little spin box to select numeric values, and jump lists. OS X users like their badges on the dock icons. Gnome 3 users like their new fused title bar to system menu thing.

It's like 3D graphics and the uncanny valley. 90% isn't good enough. It's the little details that make someone say, "yeah, this is definitely a Mac OS X application."

near··on Native GUI library for Go
I wrote a cross-platform library that is the thinnest possible layer around Cocoa, and creates the actual Cocoa controls directly. They are truly 100% native widgets.

And yet, it's exactly like you say. It has nothing to do with the base widgets. The problem is that to look native on OS X, you have to use widgets that only exist on OS X, like their merged titlebar+toolbar that changes and resizes the entire window content used on preferences dialogs, or the blue left navigation sidepanel, or the big question mark button, or the segmented control, or the color selection popup menu with the wide color boxes in each list item, or the combo box zoom setting in one segment of the status bar.

And then your labels have to be right-justified while the controls are left-justified against those. You have to add about three times as much spacing between widgets as on other platforms. You have to have a single menubar that's outside the main window, and always has a "program name" menu where your preferences option has to be, a view menu, a window menu, and a help menu.

You have to be sure to tie in to all the OS X only things like AppleScript, Core(Image, Audio, ...), dialog sheets that slide down on a window and then are only modal to just that one window, etc. Your message boxes can't have titles anymore, but everywhere else expects one.

Even if you tried to add the extra spacing and hack in those OS X only widgets to Windows and Linux, then the Windows/Linux versions would be super hideous and unnatural. By the time you customize all of that, the code's a bigger mess than just making two separate GUIs. Defeats the entire purpose of using a cross-platform toolkit.

Bottom line is that Apple just does way too much stuff differently to be able to craft a cross-platform app that looks great everywhere with no platform-specific customizations.

And now Metro, Gnome 3, Unity and KDE 4/5 are trying to go in entirely different directions as well. And iOS and Android are big targets now, too. Sadly, the dream of write-once, run-anywhere and look nice is dead.

← PreviousPage 3 of 4Next →