HN user

Sottilde

20 karma
Posts1
Comments13
View on HN

I just picked one up a little while ago. The keyboard is easily the best in the 2016+ range, but the 10W thermal capacity is really a disappointment. It's barely faster than the "MacBook" and often dips down into the 3-4W range on CPU when loaded. I see DRAM often taking up 3W on its own.

Too bad it's so anemic.

I love it when the creators of complex systems use common and well-understood formats for configuration. The use of CSS for styling your window manager is genius and really speaks to their dedication to the project.

This is great, thanks for posting! I would love to see a generalized driver, either from the OSS community or even AMD/NV (we can dream). It's a little more complicated than existing 3D implementations, as you know, but if the Rift becomes popular enough, anything's possible.

And imagine how much being hacked affects revenue!

I don't doubt, though, that some sort of similar short-sighted thinking led to this decision. Is it really possible that such a large organization simply doesn't understand password policy? Not to mention, an organization that's on the board of PCI-DSS?

Ninja is a harbinger of great HTML5/CSS3 tools to come. We have been doing by hand what Flash animators have always had a great GUI for.

Montage, on the other hand, gets me less excited. It fills a niche that is already filled by tried&true frameworks like ExtJS, KnockoutJS, and BackboneJS and appears to be more verbose than all of them. Reusable components and event bindings are great though. It will be interesting to watch.

The most elegant way to handle this (IMO) is to use a combination of Compass(http://compass-style.org/) and Vogue(http://aboutcode.net/vogue/).

Compass has a great command line feature called "watch" that simply watches for file system events (linux, os x) or polls (windows) your folders for changes and recompiles your stylesheets.

Vogue detects stylesheet changes right away and reloads them in your page via WebSockets.

Instead of dealing with Chrome's inspector, making changes, then copying them to your CSS (and translating if you like SASS), I simply make changes in my editor on one monitor while watching my site on the other monitor. The overhead is minimal - I see changes within about 500ms.

Compass is great even just as a build tool, and I used it before I learned SASS. It's fantastic for its simple mixins like linear-gradient and even better when you start chaining them together. One of my favorite mixins I use throughout my code:

  @mixin buttonGradient($color){
    @include basicBackgroundGradient($color);
    &:hover, &.hover{
        @include basicBackgroundGradient(hover-color($color));
    }
    &:active, &.active{
        @include basicBackgroundGradient(active-color($color));
    }
  }

  @mixin basicBackgroundGradient($color, $percent:12%){
    background: $color;
    @include background-image(linear-gradient($color, darken($color, $percent)));
  }
Then, anywhere I want a green button to be created, I use the style @include buttonGradient(green);. Or any color. Keeping a stylesheet full of site-wide colors is incredibly useful and being able to modify them via functions like darker() and lighter() really saves time. Consider that this simple include actually generates 18 lines of CSS each time I invoke it - in the words of an old boss, now you're really cookin with gas.

Keep in mind that updating Sublime will revert this file. Add the bottom two lines to your Preferences > Key Bindings > User file if you want to keep them.

This goes for all preferences files in Sublime. Any declarations in the User file overrides Default settings, and Default settings are overwritten on any upgrade. This caveat has bitten me quite a few times with my packages in Package Control.

I worked for a startup that used to advertise its open positions as "Silver Java Guru" or "Java Geek".

Needless to say, we got one awful applicant after the other. Most could Fizzbuzz. Some could not. And others must have cheated their way through the phone interview - when you got them in person, it all fell apart.

One thing I noticed from the process is that little things like spelling mistakes, incorrect formatting, etc., in a resume was very telling. Without fail, the kind of person who had typos in his resume was the kind that failed our programming tests, miserably.