427 karma · joined August 23, 2009
Previously: fforward, Delphia, Autodesk, Kera
For the record they made sure the exact same code was published to 0.0.3 so that I didn't maliciously inject anything. I control subsequent versions though.
I think of it similar to letting a domain name expire. The original author removed the code and I forked it and published a new version with the same package name.
The main issue was there were so many hard coded dependencies to 0.0.3 so I asked npm support if they could allow me to re-publish that version and they complied since I was now the maintainer of that package.
Let's see if it really works before we worry too much about price.
We believe in the Lean Startup. Probably more than most. We launched three separate tutorial products trying to find something that people picked up easily while still giving great results. We basically ran out of time and had to scale our team back to just the three cofounders.
We are still kicking the can trying to get traction (albeit in a different direction).
If anyone wants more details about why we shut down the producg I'd be more than happy to share. It's fundamentally a CAC being higher than LTV type issue.
As an example you could have a web application that has multiple documents and inside each document there are panels that can be expanded and collapsed. As you switch between documents each document maintains its own version of which panels are expanded or collapsed.
In the Ember world the router would maintain which document was opened (addressable state) and the DocumentController would maintain which panels are opened (non-addressable state).
Also: We've been getting a lot of requests about what tools we use hence Taige's blog post.
I'd like to see what a fully decomposed meteor application is supposed to look like from an architecture perspective but every time I see an example it looks like this.
Testing frameworks force you to break things up resulting in a better overall design. This is what should be exposed to a nascent community if you don't want serious growing pains later on (look at the struggles the php world is having adopting testing and modular architectures)
Please correct me if I've overlooked something.
One thing this misses is the social proof aspect of the sharing buttons.