HNHacker News
TopNewBestAskShowJobs

nxn

238 karma · joined June 30, 2010

submissionscomments
nxn··on Microsoft declares victory over Linux, names Apple and Google main rivals
Huh? I think zdnet is reading a bit too much into what appears to be a 15 minute edit done by someone from marketing. They might as well claim that Internet Explorer was defeated since they removed that text as well... oh wait.

No but seriously, I doubt MS has seriously looked at Linux as any type of threat in the last 3 to 5 years. It's not exactly parading in and stealing their average user from them. Maybe they just shortened it because they realized no one really cares to read filler like this -- with the exception of some news sites apparently.

nxn··on Building Windows 8
So what do you suggest they do? Stay with a stagnating UI that's not suitable for anything other than a desktop in fear of looking "desperate"? The UI they pulled off is far from desperate, in my personal opinion it beats everything available right now in the mobile world as far as usability and looks go. For example, I haven't seen any one call the new windows phone UI anything short of amazing and it's the same concepts that will be applied to the Win8 UI from what I've seen so far. Their approach also seems much more likely to remain unified across multiple touch device form/scale factors when compared to something like Android.

As far as being last to arrive at the scene, need I remind that this is Microsoft? They're always last, and sometimes that actually works out for them (XBox, .NET), and sometimes it doesn't (Bing).

nxn··on Firefox 6 available, version 8 to offer add-on control
Not sure if I'd call that "advertising" -- it's a small green number on a green background. Before the rapid release schedule you'd have a 72pt version number hitting you in the face when you went to their main page within a week of a major release.

Never the less, I see what you mean about it being still "visible" to the user.

nxn··on Firefox 6 available, version 8 to offer add-on control
Chrome has version numbers. And similarly, firefox doesn't make a big deal about new version releases since 4.0 was out. The ones that do make a big deal out of them are blogs and tech sites, but those will get bored of doing so soon enough.
nxn··on 2005 Zuckerberg Didn't Want To Take On The World
People really like to try to make him look bad; I mean, is it just me or does this article portray him to be some clueless dimwit that was standing on a goldmine and didn't know it until his face hit the ground so hard that he finally saw the shiny gold stars?

The reality is that it's very difficult to know what ground you're standing on until you dig deep enough to just see it with your own eyes. Predicting the future and investing in that wishful vision is a much more risky strategy than just acknowledging the current moment and trying to lead it closer to where you'd like it to go. I do not know whether he looked at the situation in this type of manner or not, but that's how I justify facebook's success.

As a side note, I wish people would stop pretending they never drank out of a big red cup before.

nxn··on Mono: A cure for Microsoft monotheism
Opposite experience for me. 2005 and 2008 were incredibly slow, painful, and prone to locking up or flat out crashing. I don't think I've had one lock up or crash since I switched over to 2010 about 4 or 5 months ago. Also, I can have multiple instances of it open now without my whole computer gasping for RAM. In fact, when I launch a second instance it comes up in a split second, making me feel like the core parts are sharing common resources.
nxn··on Next-Gen Web Apps: Google unleashes Native Client into Chrome
First of all, we're talking about the VM here, so why does not having ASP.NET or Windows Forms make any difference? Better yet, would you even want your browser to come with them? Also, although the VM bytecode does change with time, it doesn't change as much as the .NET libraries. I'm saying this because the 'lag time' argument isn't all that significant for this reason.

But outside of that, "substantial lag time"? In my opinion the mono team has always been exceptionally fast when it comes to implementing new features in the .NET world. Plus mono has its own tool sets and features that aren't in the regular .NET framework and wont be any time soon.

I am not saying that Mono is the VM I'd like browsers to implement, but my reasons are definitely not related to it not being able to come with the ASP.NET framework.

nxn··on Next-Gen Web Apps: Google unleashes Native Client into Chrome
I was somewhat irritated when Microsoft was pulling stuff like this with IE. But on the other hand, if they ever do make PNaCl, I will gladly disregard every other browser and target all my personal projects specifically for Chrome. The unfortunate thing is that I haven't seen any news or heard of any progress being made on PNaCl in a long time.
nxn··on Poll: Spaces in if statements
And do you also add the space before the paren when you declare a function? I ask because a conditional block is often closer syntactically to a function definition than it is to a function invocation, yet I hardly ever see anyone put a space before the paren when defining a function.
nxn··on Xkcd Password Generator
So you're advising against what appears to be a more practical and secure methodology on the basis that it's worse when you share your password? If you share your password, your exact problem is that you're sharing your password -- it's not how easy or hard the password is to remember. In fact, why does this even have any significance when the person you're sharing it with can just write it down?

Oh and if within a year's time you do not change your password, that could very well be another problem. I think you'd be better off just using easy to remember pass phrases and changing them every once in a while. Shouldn't be a problem because they are, after all, easy to remember.

nxn··on Can we believe our eyes? Misleading people with Unicode.
I've been using Windows 7 at work for about a year, and I had absolutely no idea that the menu will show up when I hit the alt key until exactly 2 days ago. Every time I needed something from it I'd just rummage around all the visible menus, not find it, curse my head off and open up the command prompt.

I'm not sure which will look dumber as a consequence of this post: me or the Windows 7 UI.

nxn··on Linus Torvalds dumps Gnome3 for XFCE (G+ discussion)
By "ONE" do you mean at least one, as in implying there are none right now. Or by "ONE" do you mean that you wish there would be one and only one GUI/DE for linux?

If it's the first, I would agree because I would willingly pay money to use the Windows 7 or even OS X interfaces in Linux. Essentially, I feel that while Linux has software I can't live without, there is not a single WM/DE out there that I can use without being annoyed every 20 minutes or without having to spend weeks configuring it. Gnome came closest before the gnome-shell move, now KDE is the closest but it's seriously still too buggy and "WTF" inducing. I'm not sure if it would be less work to remove all the "default/assumed" features from KDE (like the wallet that irritates me even when browsing websites) or to set up XFCE to some bearable degree from scratch.

Regardless, I'd still take this selection of environments that are all either ugly, time consuming to configure, buggy, or flat out annoying over having no choice at all. Even if the "no choice" option was really excellent, I would not like the thought of being stuck with it knowing that under some rare condition it might be useless and my only way out is a complete OS switch. Example: as much as I praise the windows 7 UI, I would hate to try and deal with it if I lost my ability to use a mouse. Meanwhile, I know there are nice options in the Linux world that I could use if this was the case.

Pretty much it boils down to my opinion that no interface is going to be good at every use case. And for that reason I'd rather have a slew of mediocre ones that span a broader range over a single one that covers a small spectrum but does it well.

nxn··on The future Firefox UI
I don't know, that floating button in the top left bugs me in linux. It makes sense in windows because it just blends in with the tabs next to it, but in linux it's on its own line with the tabs showing up below it. The wasted space annoys me to the point that this is one of the main reasons why I do not use Firefox anymore.
nxn··on The future Firefox UI
Very nice, if they actually manage to pull this look off it would probably make it the best looking browser. My only concern is that they wont and that it will still look like crap in linux.
nxn··on Flame from Bill Gates Re: Windows Usability
> Xcode has a different level of abstraction, but the result is that Xcode devs consistently produce far more polished apps than Visual Studio devs. But yes, it's pretty darn good.

Don't you feel like you're ignoring some very important variables by saying that? For example: Cocoa vs Windows Forms, Cocoa vs WPF, etc?

nxn··on Flame from Bill Gates Re: Windows Usability
Urgh, there is so much corporate styled lingo and behavior going on here that I feel like they forgot how to concern themselves with actual problems. It seems like at some point sounding "professional" became more important to their career than actual communication. I mean, a lot of those replies are so high level you can't even see the original problem from that height.

Instead of concerning themselves with better search results and better download links/navigation they somehow arrive at needing to "promote" some downloads because they're "cool"? How is showing crap you THINK a user is interested in going to solve the problem of them not being able to get what they actually want? You can almost actually see the original message degrade and lose meaning with each new email that gets sent out.

nxn··on Mozilla is building an operating system
Thanks for the reply.

My opinion is that relying on line-height being unable to decrease a height of an element is a really bad idea and the owners of those sites should just be forced to fix it. Of course, I understand how from your perspective making a change that breaks a site like youtube (and probably a decent percentage of sites in general) is probably not an acceptable solution.

Oh well, I personally only needed line-heights on button elements, so the mentioned change will actually solve my UI problems. Thank you.

nxn··on Every language fixes something - a DiGraph - just for fun
Yeah, actually I have noticed and was well aware of it when making my comment. The topic of this particular comment thread, however, was specifically about the first graph since the mentioned link's validity was being "defended" by saying the graph was not an "inheritance / 'paternity' graph".

In fact, I could have also mentioned myself that the link was taken off the second graph to further my case that it was just plain wrong. The only reason I did not was because I thought it was something so obvious it would not be necessary to state it.

nxn··on Every language fixes something - a DiGraph - just for fun
So you agree with the diagram is stating: that JavaScript fixes Java's syntax by using the same C-like syntax?

No, the given reason for Java -> JavaScript is completely wrong. I'd understand if the reason was "Java browser applets suck", but syntax?

nxn··on Mozilla is building an operating system
Well, as a user you have the option of using another browser. Though, admittedly, with 1 gig of RAM I can't think of any decent one that wont give you problems after a few hours of browsing -- maybe chrome?

As a web developer, I wish they'd concentrate on making a browser that lets you change the line-height of a button/input element. Such a simple change, yet the problem has been around since 2006, if I recall correctly.

nxn··on Ask HN: What's your most-used function that you wrote yourself?
Heh, wrote the same function, except called mine $> because it's really just a flipped $.
nxn··on Ask HN: What's your most-used function that you wrote yourself?
"Also... lack of semicolons is bad style. Lack of braces for if clauses is bad style. Fix it, you'll thank me later. :)"

Although a popular opinion, it's still just an opinion -- one I strongly disagree with. Almost all semicolon problems in javascript are not caused by not using them, they're caused by not understanding when they will be inserted. The infamous example:

  function func(param, param2) {
    var meh = 0, gah = 0;

    <some more logic here>;

    return
      { meh: meh
      , gah: gah
      };
   }
Note: using a semicolon did not save you from returning undefined.

My point is that whether you use or don't use semicolons is not the problem. Not understanding when and how they're inserted is the problem.

I also find that people who do not use semicolons have a much better understanding of the few situations where they are actually needed to avoid errors.

nxn··on Ask HN: What's your most-used function that you wrote yourself?
A few months ago I was writing a little application where I was doing a lot of asynchronous calls in javascript and having to track their completion to do some other stuff, it resulted in this:

  // Synchronizes asynchronous calls: sync(functions..., completionHandler)
  var sync = function() {
    var argLength = arguments.length - 1
      , completed = 0
      , callback  = arguments[argLength]
    
    for (var i = 0; i < argLength; i++) {
      arguments[i](function() {
        completed++;
        (completed == argLength) && callback && callback();
      });
    }
  };
It pretty much takes a number of functions that perform asynchronous operations and execute a callback function upon completion of whatever the async operation is. Once they're all complete it calls the last function it received as a 'completion handler'. Example that I wrote out without bothering to test at all (treat it as pseudo-code):

  var pageData = null;
  sync
    ( function(cb) { $('#pageContainer').fadeOut('slow', cb); }
    , function(cb) {
        $.ajax(
          { url: 'page.html'
          , success: function(msg) {
              pageData = msg;
              cb();
            }
          }
        );
      }
    , function() {
        $('#pageContainer').html(pageData).fadeIn('slow');
      }
    );
So that will start by beginning the jQuery fadeOut animation on the pageContainer html element, while immediately doing an ajax call to get another page's data. Once both operations are complete, it will take the new page data, put it into the pageContainer element, and fade it back in.
nxn··on Firefox doesn’t hoist function declarations in blocks
I assume you mean this form: var f = function () {}; ?

If so, I don't think that will circumvent the issue since only the variable declaration will be hoisted, the function being assigned will probably not be. You'd end up with 'not a function' like error when invoking instead of undefined.

EDIT: Actually, I'm not sure if your last sentence is talking about the problem in the article since the person your reply was to has deleted their post. If it isn't, then disregard.

nxn··on Hacker News gives "Unknown or expired link" Often when I click "More"
Seriously? Having 'paging' tied to the GC in this way, or any way at all for that matter, does not sound like a good idea to me.
nxn··on PDFKit, a powerful PDF generation library for Node.js
Too late to switch to PDiddy-F?
nxn··on Waldo: Search the JavaScript Runtime in under 1 KB
That's actually quite awesome -- I am amazed that I went on for this long needing something like this yet not getting the idea to write it.

Not strictly related to the project, but I think it would be a good idea if posts that introduced some javascript project/tool automatically loaded it into the page. This way developers could just open the browser's console and play around with it instantly.

nxn··on A new JavaScript pattern that saved my project
I wouldn't really consider this as a "new" pattern, it's been around for as long as I can remember. It's pretty popular in jQuery plugins.

I would recommend, however, against declaring the functions directly on the object you're putting them into. Declare them somewhere else in the closure and just assign them by name on the object you're creating. This way at least the functions are shared instead of being created every time a new object is created.

nxn··on Mac OS X Lion: This Is Not the Future We Were Hoping
I agree with two things:

1) Bringing touch based user interfaces/behaviors to the desktop is not going to work when the keyboard and mouse are the means of operating them. For desktops I don't see the mouse and keyboard going away since I would not wish to spend as much time as I do in front of a computer with my arms extended out the whole time (or at all actually). The only reason why I'd see doing this would be in hopes of having one OS run on different types of devices and therefore having the need to support multiple modes (IE: the win8 reason).

2) Limiting your calendar/contact apps to look like the physical objects they're meant to replace is an incredibly bad idea. The whole point of going digital was to remove constraints and make performing tasks easier through the freedom of not being stuck within the confines of paper. Where's the advantage now? More intuitive apps? Were the majority of users not able to figure out how to use the old calendar app? Why do I feel like more people just wont use it now because it will be too tedious to perform tasks they became used to with the previous versions?

Not to mention this makes it look like it was intended for elementary school students. OS X had the advantage of having a very clean and professional look to it that I am sure won it a lot of customers before. I mean I get ill looking at ANY Windows text editor (since they all seem to come with like 50 icons spread out over 5-10 different toolbars), but if the alternative is an app that has a giant crayon for a cursor -- because that's so intuitive -- I'll still stick with Windows.

nxn··on Button Basics
I understand that, in fact I mentioned that the aspect of zooming was completely ignored in my first post, and I found it ironic that it was.

But anyway, lets forget about that fact for now. If you need to zoom in 400-800x on some pixels to even be able to spot the differences, then in practical terms there are no differences. You can't expect your typical visitor to sit in front of the monitor with a magnifying glass sweating at your pixel perfect buttons. Honestly, no one is going to give it much more than a glance, so attention to detail you can hardly spot with the naked eye is almost completely pointless.

Now to come back to my main point: what isn't pointless is maintaining quality when zooming in with the browser. This is something I often do myself when I'm too lazy to put my contacts in to just casually browse the web. Just about every website looks like a mess of blurry/pixelated crap when you do that. Had he just went with the css3 approach, the quality at non standard zoom levels would far outweigh the minuscule pixel details at normal zoom levels between the css3 and photoshop versions.

Anyway, that's all I really wanted to say. Had the point been that CSS3 styling was still iffy with older browsers being around and the photoshop button was superior for that reason, I wouldn't have said anything. But to dismiss it based on some differences in pixelation you wouldn't even spot normally, while ignoring that if you had actually zoomed in the browser there would be no pixelation at all with the "inferior" css3 version, was just too much.

← PreviousPage 4 of 7Next →