mattetti

14 ms·

91.
by mattetti 14y ago
I wrote a somewhat more balanced review based on my experience with RubyMotion over the last few months (beta testing) http://merbist.com/2012/05/04/macruby-on-ios-rubymotion-revi...
92.
RubyMotion pros and cons(merbist.com)
62 points by mattetti 14y ago|22 comments
93.
by mattetti 14y ago
You are absolutely right, the question is can Ruby compete in 80% of the cases?
94.
Getting started with mruby(matt.aimonetti.net)
33 points by mattetti 14y ago|7 comments
95.
by mattetti 15y ago
Thanks for correcting my abuse of language. I should have reviewed my post in detail. I did fix that now. That said, while I appreciate your perspective, I'm quite disappointed that you aren't offering any solutions besides asking people to
96.
by mattetti 15y ago
You seem to forget that he has almost always be paid for his contribution: * Merb / Rails - EngineYard * Sproutcore / Ember - Strobe (and via contract work) I myself struggle with the concept of asking $25k to build what he wants to build
97.
by mattetti 15y ago
Keep reading the same paragraph: > "I know, I know, you can turn off the asset pipeline and it got better since it was first released. But shouldn't that be the other way around? Shouldn't fun new ideas risking the stability of an app
98.
by mattetti 15y ago
I agree that it isn't the best comparison but I wanted to give an example of a product making upgrades/migration really easy.
99.
Learning from Rails' failures(merbist.com)
50 points by mattetti 15y ago|35 comments
100.
by mattetti 15y ago
Agreed, the post title is actually "Quick dive into Ruby ORM object initialization".
101.
by mattetti 15y ago
I hear you, but my point wasn't to show how to optimize AR but instead what's going on when you initialize a model. In other words it's more about software design and architecture decisions than performance.
102.
by mattetti 15y ago
Thanks for posting my article. Quick update, someone did more benchmarks with different versions of Ruby and adding MongoMapper: https://gist.github.com/1894055
103.
by mattetti 15y ago
I'm almost sure we will run more sessions in the future.
104.
by mattetti 15y ago
@nupark2 how was my explanation "disingenuous"? I merely exposed the reasons why the C Ruby team decided to use a GIL and are not planning on removing it. It's not because you disagree with the core team conclusion, that it makes my post a
105.
by mattetti 15y ago
You are rightto some extend, however serving static content is much faster than serving a dynamic request that needs to generate a response on the fly. Before optimizing the assets, improving the caching strategy and async rendering will yi
106.
by mattetti 15y ago
@Isb You have a good point about profiling and asset management but you are talking about performance on the client side (browser) not scaling as in increasing the throughput. There are a lot of improvements which can be made to improve the
107.
Video game web framework design(merbist.com)
18 points by mattetti 16y ago|0 comments
108.
by mattetti 16y ago
That's correct, I explained my view point about the NDA in this comment: http://merbist.com/2011/03/07/hey-apple-please-be-nice-and-s...
109.
by mattetti 16y ago
MacRuby allows you to write native Cocoa apps and call C/Objective-C directly without a bridge. Basically, it's an Objective-C replacement using the same runtime but a different language.
110.
by mattetti 16y ago
Steve, that's a fair argument but maybe we should let developers decide. If you want to write a simple task bar app, you might not want to embed 30MB worth of extra stuff when your app could just be a few KBs.
111.
by mattetti 16y ago
But at the same time they use it in their new OS, isn't that a double standard?
112.
by mattetti 16y ago
@cscotta as the author of the blog post, I can only agree with the concerns you raised and thank you for your kind words. Concurrency is something both Ruby and Python have to take seriously pretty quickly if both communities want to mature
113.
by mattetti 16y ago
Thanks Julio. I should have written it months ago but you know, procrastination... ;)
114.
by mattetti 16y ago
Yes, we are going to publish the book once finished. You will still be able to read it online in HTML tho.
115.
by mattetti 16y ago
So far the feedback has been great. You are right a lot of comments are 'superficial' but they are still very helpful. Editors only come at the end of a project and I was eager to share the book content with people interested. My publisher
116.
by mattetti 16y ago
Btw, Apple is not "sponsoring" MacRuby. Apple is developing MacRuby, it's an Apple project. Will it replace Obj-C? Probably not. Will it become a blessed alternative? Everything seems to point in that direction.
117.
by mattetti 16y ago
It's available in the svn repo.
118.
by mattetti 17y ago
MacRuby responds to the news via twitter: http://twitter.com/MacRuby/status/4519713150
119.
by mattetti 17y ago
For those who still care, here is my statement: http://merbist.com/2009/04/28/on-engendering-strong-reaction...
120.
by mattetti 18y ago
@kuniklo merb is designed to be modular and to get its pieces working together smoothly. However, this is a harder problem that having one well defined stack. merb isn't for all, and if you are happy with the framework you use, you should s

More ›