HNHacker News
TopNewBestAskShowJobs

mstachowiak

159 karma · joined September 20, 2011

3x founder => 3 exits

Formerly co-founder of MyVR, YC W12

Prou investor in Zapier, Omaze, Clever, Brightback, Anduril, and more.

submissionscomments
mstachowiak··on Works With Nest
There are standards for Home Automation communication out there - ZigBee and Z-Wave. These are the low power communication protocols that home automation devices can use to talk to each other (WiFi is too power hungry and heavy weight). If you take apart a Nest thermostat you can find an unadvertised ZigBee radio buried inside.

ZigBee is an open standard developed by an alliance of device manufacturers. Z-Wave is a proprietary standard developed by Sigma Designs. Both are able to create a low power mesh network for communication between home automation devices. These protocols have been around for a while and are supported by 100s of device manufacturers.

That said, I have no idea what Google/Nest or Apple plan to do. They may be creating their own standards for communication, or they may build a communication protocol on top of ZigBee or Z-Wave.

If you're interested in working with an interoperable standard now though, you can buy off the shelf ZigBee or Z-Wave radios, devices that speak ZigBee/Z-Wave, and build your own HA solution. However, I've found through personal experience that interoperability between devices using the same standard is not always perfect. I'm looking forward to the heavyweights getting into the ring and hopefully cleaning up the industry and making it more interoperable.

mstachowiak··on Django REST framework 2.3 released: ViewSets and Routers
Nice, I didn't recognize you could use multiple default filter backends glancing at the 2.3 documentation. That would provide a means of addressing the main concern - creating a reusable object that could be applied to any api view that filters the queryset in a predefined way (eg: limit the queryset to objects owned by the current user). Another point for DRF.
mstachowiak··on Django REST framework 2.3 released: ViewSets and Routers
I'm actively using both frameworks on separate projects and have roughly 1 year of experience with Tastypie and 2 months of experience with DRF. Both have strengths and weaknesses with very similar feature sets, although I personally prefer DRF, backed up by my choice to use it over Tastypie when starting a new project 2 months ago.

Tastypie has a rather monolithic structure (most of the logic is wrapped in a single resource object) that passes responsibility from function to function. I find the code hard to read and mentally compartmentalize the various components. It does a great job providing basic functionality out of the box, but as soon as you start to do anything complex you will find yourself repeatedly digging through Tastypie source code to track down behavior. Tastypie approach to URLs is also rather limiting.

DRF uses Django class based views and generally follows Django's design patterns. I find the code much easier to understand and more inline with the direction Django is heading. The module class structure makes it much easier to build reusable components. One downside with DRF is their permissions system, it has a rather large oversight for multiple object permissions. DRF completely excludes the queryset from the permission decision which leads to some terrible workarounds (I'm not sure how you can make an informed permission decision on a set of objects without access to the set of objects themselves).

The documentation and community on both is rather strong, although there is more information on Tastypie as they've been around longer. As a point of reference, Tastypie has ~750 questions on stackoverflow vs 153 for django-rest-framework. Both are actively maintained, but Tastypie's design architecture handcuffs it's ability to move forward.

tl;dr; My $0.02 - Tastypie was the standard, DRF is becoming the standard. I would personally choose DRF over Tastypie for any future project.

mstachowiak··on Airframe - Portable Smartphone Car + Travel Mount
After getting denied by KickStarter, AirFrame made use of Lockitron's Selfstarter framework to launch their own crowdfunding page. Kudos to Lockitron and well done Kenu.
mstachowiak··on Ten predictions (2004)
Just for edification - regarding #2, GitHub is insanely profitable.
mstachowiak··on GoDaddy's DNS Service is Down
For those looking for a quick route around, you can find GoDaddy's IP address here: http://who.is/dns/godaddy.com/
mstachowiak··on Jury rules Google violated copyright law, Google moves for mistrial
The judge still has to decide if the APIs have copyright protection. Bad initial result for Google/Android, but more important rulings to come
← PreviousPage 2 of 2