tjriley82

Yes, it would. Apple experiemented with this in the mid 90s: https://en.wikipedia.org/wiki/Macintosh_clone it didn't really work out.

NYC, New York - World on a Hanger - Full time (Rails/Mongo)

I’m looking for an exceptional Rails developer to help build a niche SaaS application within the fashion space. We’re somewhat distributed (between the US and Europe) but the core management and development team will work out of NYC. You should love to build projects from scratch, choosing the right technologies/languages for the job. You should be a little obsessive over user experience and good design and be happy joining an early stage startup. Founded by YC alums.

Email: [email protected]

This seems like an awful lot of work to solve a really small problem - that your front end developer doesn’t have a working Ruby installation and is shy about using the command line. Just teach them. It won’t take long, they’ll learn something new and they’ll be able to use the correct tools for their job.

Fabricly carries out the sourcing and production. The designer only has to worry about design and a joint marketing effort.

I somewhat agree, but I don't think it's such a big deal for the average visitor.

Oh, we're not ignoring brand name at all. Our first mini-collection is by a relatively established upcoming British label that only has very limited exposure in the US. We have exclusive collections from several other labels coming up. Small labels can find themselves in very precarious financial positions as they try to grow, even after many "successful" seasons. Fabricly is about providing a very low risk route to putting out a collection. Almost like a book publishing model for fashion.

OS X gives you the option to submit a report to Apple after an app crashes. The report contains stack traces and you can view the traces in the dialog box before sending. Every time Safari crashes for me (and for anyone else I know) it's within the Flash plugin.

The article just seems to be putting Rails 3 design improvements to the test. Personally, I am pretty impressed at how easy it is to swap out Routes/ActionController::Base if you need something leaner or just a completely different approach to routing requests. Remember when we were all banging our heads against a wall with Struts? What's not to like?

If you have a "continuous authority" facility enabled on your merchant account you can make arbitrary charges on card numbers authorised and stored by your payment processor. CA doesn't seem too hard to acquire, at least here in the UK it was easier than we expected at worldonahanger.com. The downside with this approach is that in the event that you want to switch payment processors, you have to ask your customers to resubmit their card details for reauthorisation (as far as I can tell).