UDM Pro can do it. But there is no standalone security gateway that can do gigabit.

UDM Pro can do it, but can't do dual NICs yet. Still.

The USG3P can do gigabit (I get very close to gigabit speeds in internet speed tests - ~950/950) but I can’t use IPS/IDS without severe performance penalties. It basically becomes a fancy router with little in the way of actual “security” besides its basic firewall functionality.

I am aware of the UDM Pro and USG Pro but those things are expensive 1U monsters. Maybe fine for SMB use but this is for home use and I’m very space constrained.

If Ubiquiti made a small footprint security gateway with some modern hardware (the USG3P is some 8 years old at this point!) I’d buy it in an instant.

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.

Yeah it's a shame they watered down the Air's capabilities. I got a 2012 13" air as a second laptop to travel with, and it quickly replaced my pro as a daily driver since it was powerful enough, and so comfortable to use.

I wonder how the Air would compare to an iPad pro in benchmarks.

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.

It's sad that they target users, not developers though. Imagine how awesome the ecosystem would be if many developers use it.

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?

Possibly not that much, as long as their security is good enough that they don't get sued.

At the point where you are worrying about hashed passwords, your system has already been owned.

It also depends on public reaction to the incident, people won't necessarily blame tesco either and blame the "1337 chinese super h4x0rs"

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.

Actually chrome has this feature too. When you have saved a file once manually, it keeps track. So whenever you make live changes on the resources panel it live updates the DOM and upon clicking save, it automatically rewrites the file at it's original location. So it pretty much mimics the solution you suggested without any command line tools, extra file inclusion, downloads, etc. (http://www.youtube.com/watch?v=3pxf3Ju2row)

If you go up, you can read my comment in which i say why i dont like extra libraries, compilers for web work. (http://news.ycombinator.com/item?id=4219980) This is pretty much why.

And for the global mixin, (Which is pretty cool IMO, it really enables a lot more possibilities and creativity) you pretty much give the reason not to use them anywhere out side of practice work. 18 lines are huge. Plus css variables are pretty much on horizon, it is well worth the wait.

Good article, although short and without too much actual research or science. Not a fan of the second page that only contains a few sentences, though.

Okay so it wasn't just me.

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.

Looks like he's gone full-on sad Keanu. Which is too bad, I'd be a lot happier if I had one of those cameras. That thing has some really incredible reach. I wonder how it's controlled and how they make sure it doesn't collide with the actors?

They likely don't make sure it doesn't collide with anyone. There MAY be some local safety systems in place, like virtual light curtains and exclusion zones...

If you're filming a kung foo scene, you're already very careful to not collide with who you're "fighting". I don't see how this would be any different other than the robot is perfect and your opposing actor is not.

Your opposing human actor is not 2000kg and moving at 4+ m/s...