jmlacroix's comments

Hello HN. My partner is a UX designer and I'm a full-stack dev. While watching her work, I found that she was wasting so much time building her usability evaluations reports that I built a tool to help her out.

It's a SaaS service for generating reports with a Chrome extension to allow capturing problems onsite.

I'd love to get feedback from fellow UX designers and usability professionals about their workflow and how to cover all the needs.

This looks like a great tool!

I've been working on that topic too in the last year. I developed Capian (http://capian.co), a tool to help usability professionals make better heuristic evaluations faster.

I'm a full-stack developer and my partner is a UX designer. There's a lot of missing tools in our space. Great to see other people trying to address them!

How about approaching the problem from the suffix point of view?

Instead of having 25 prefix having suffixes, you have 20 suffixes having prefixes.

The prefix technique has an average of 4.96 suffixes per prefix, and the suffix one has 6.2 prefixes on average for each suffix.

Maybe this would be easier to deal with?

Hello, I'm the author of the post.

These are all good points, I should have made my goals clearer. I do not use it as a web development machine or something that needs to be always on.

I use it as an occasional machine, to compile and test stuff that's not working or unavailable under OSX. I was looking for a powerful and cheap VPS (which is uncommon) when I figured I'd be better served by a headless VM.

Another big plus for me is having access to it when there's no connectivity.

Hello, I'm the author.

I mostly use OSX for everything. The only times I switch to the VM is when I'm having a hard time installing something (for an example, see my earlier comment - http://news.ycombinator.com/item?id=2969509) or want to try a tool that's not available under OSX.

I admit the post would have been better with examples and without then unfounded critiques, taking notes for the next ones.

It's been a while since I last used VirtualBox, so I can't really compare.

What I like in QEMU, is its simplicity. The learning curve is a bit steeper, but when you're used to it there's no turning back.

Hello, author here.

This is really a great overview of why I like this setup, I couldn't have put it more clearly.

An example of something I've been trying lately and didn't work well under OSX: ruby bindings for FUSE filesystems. I wanted to write a quick FUSE fs using ruby, so I installed gems and other dependencies. But since MacFUSE has been deprecated for a while, it's not easy to get everything working.

It could probably work under OSX, but given the current state of FUSE on Lion, I gave up (and did not try it under Linux yet).

While trying to setup my FUSE environment, I installed every FUSE version, many gems with a couple of ruby versions with rvm, rbenv, ruby-build, etc. When playing with new tools and environments, I always end up with lots of useless or broken stuff.

This setup allows me to keep my base system clean and simple.

I do not use it daily, but it's nice to have it ready to launch when needed.