Josh Owens queso
I remember first getting started with Rails back in 2004, it was a "magical time" - of course I remember get questioned at least once a week why someone would want to use rails. My answer was always the same, developers love the framework because they can build things faster in a way they enjoy to work. I've been working with Meteor full time for over a month now and I wanted to give some answers to "Why Meteor" because I am hearing the same question a lot.
When a client asks us to build an app, they are really asking for a fully interactive web app that utilizes javascript to get rich client interfaces. The problem is when you start with something like rails then javascript was an afterthought - something bolted on long after the technology was built. Sure, you can spend a few days getting something cobbled together that is workable and a developer could be happy working in, but rails was developed and became widespread because it adopted convention over configuration.
| activerecord-3.2.14/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245→ query | |
| activerecord-3.2.14/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245→ block in execute | |
| activerecord-3.2.14/lib/active_record/connection_adapters/abstract_adapter.rb:280→ block in log | |
| activesupport-3.2.14/lib/active_support/notifications/instrumenter.rb:20→ instrument | |
| activerecord-3.2.14/lib/active_record/connection_adapters/abstract_adapter.rb:275→ log | |
| newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/active_record.rb:36→ block in log_with_newrelic_instrumentation | |
| newrelic_rpm-3.6.0.83/lib/new_relic/agent/method_tracer.rb:235→ trace_execution_scoped | |
| newrelic_rpm-3.6.0.83/lib/new_relic/agent/instrumentation/active_record.rb:33→ log_with_newrelic_instrumentation | |
| activerecord-3.2.14/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:245→ execute | |
| activerecord-3.2.14/lib/active_record/connection_adapters/mysql2_adapter.rb:213→ execute |
| Hey Josh, | |
| Sounds like a pretty intriguing event. | |
| We have plenty of space for that size group. When you say working on projects for 48 hours, do you literally mean that you'd need the space for 48 hours straight? That'd be the only potential complication I see, but is still something we could figure out. | |
| Since we're open to the public on Sat & Sun, we usually charge a minimum purchase fee based on the amount of space we need to reserve. For a group that size, we'd charge $1,000min (not including gratuity) for every 4 hours that we're open when you rent the space. So, if you guys spend at least $1,000 over that time period, then you wouldn't owe anything else, but if you spent just $500, you'd owe another $500 as a rental fee. The minimum should be pretty easy to cover. If you have 100 people and everyone has 2 beers, you'd be at $1,200. | |
| We have plenty of power, but most of the outlets are placed in the tasting room and around the brew deck, so we'd likely need to run extension chords down to the area |