Doubtful. When people have scalability problems it's not ruby, it's rails. Web applications don't need much cpu but they do need to use memory in a reasonably efficient manner - something that rails cannot currently do.
Gmail is really killer app for email, it's really the one place where no decent open source solutions exist. High volume email is extremely difficult to manage in the world of mbox/maildir type systems. And I have yet to se anything free or commercial that processes spam better.
19th century was a difficult time for american writers because there was no international copyright law. Publishers often just pirated the works of authors rather than paying them.
Uh no. It's actually quite hard to find stuff on limewire compared to something like itunes. Not to mention the lack inconsistent download times/quality.
It's not just a convenient categorization. Spinoza is using the word god in a meaningful sense, and a sense that has been used by many religious/philosophical thinkers before him.
The problem with Nadler and his ilk is that they have to reinterpret Spinoza to fit what they want. Saying, 'oh he doesn't really mean god when he says god' or 'he's just using god to make it less objectionable'. This is an arrogant reading of the Ethics.
Spinoza is selling pantheism. Also it is not correct to say his god-concept would can be understood as atheism. Pantheisitic concepts are quite common in all major religions/religious thinkers.
According to Zed Shaw, 37 signals was restarting their servers 400 times a day. This is one of the problems with 37sig; they won't speak on any negative aspects of RoR, you just have to figure it out by yourself.
Sure, the problem is that 1) Rails isn't thread safe/no native threads and 2) Ruby processes are very expensive in memory.
So. Since rails isn't thread safe you have to use a process model where one process handles one request. Now these ruby processes can get up to 100MB in ram (depending on application). That means it takes 100MB to post a comment, display a page,etc.. This is an extremely unforgiving environment when you are trying to scale. There are many scenarios where just a little extra i/o wait in your system will cause everything to crash and burn.
A lot of RoR developers are looking at merb. No native threads but it is thread safe and solves the problem I described above.
Current biological thinking is that domesticated animals were drawn into human habitat because their own habitat was taken over by more fit animals. Humans simply domesticated these animals, but otherwise they wouldn't have stood a chance in the wild.
I have no idea but I would think domestication was an adaptation on the animals part. By becoming so maintainable (and tasty), cows are by far one of the most fit species in todays environment. I'd suspect cows have lost their adaptations in the wild as who needs thick skin when you have a farmer that will just kill all your predators for you?
Now look, I didn't come to bash rails and I hope your applications run great. But you rails guys like to pretend your shit doesn't stink when any half ass engineer can see some seriously problems. I swear one mention of threads to you rails guys are like bees thinking their hive is under attack. In any case, real world beckons. best of luck.
no. Each new mongrel instance is a completely new runtime environment. My engineers estimate a cost of 20MB per mongrel process on rails 1.1. You don't know what your talking about.
dhh confirmed the 400 restarts as they were running out of memory. You can find the nugget somewhere in zed's rant (http://www.zedshaw.com/rants/rails_is_a_ghetto.html). Since you say you've studied the rails internals, reading zed's rant might help you see some of the issues. It's not something you should take personally - rails does a lot of innovative things. But it is in need of more critical engineers.
btw. Rails is not thread safe. Nor does ruby have native threads. That is *very* different than other languages/frameworks.
What makes the rails world different from other application frameworks is the developers as a whole seem to prefer to sweep their issues under the rug rather than deal with them in the open. Engineers resent that. Saying threading is not a big deal is silly. DRb is not a solution to threading. I remember someone sending me a link from zed shaw saying that before fastthread 37signals had to restart their servers 400 times a day. lol, i am really, lets get real here.
Multi-process model is unforgiving compared to multi-threads. In many heavy duty web application environments memory is your most precious resource (even more precious than i/o) and a process model is not going to handle this very well. Consider a case where your s3 service is slower than normal one day and your processes are waiting 2x longer than normal. Well while these processes wait they are holding up a good amount of memory that can't be used anywhere else.. it's just wasted. This is where scalability and capacity planning issues can hit you in a bad way.
I'd say the chances are pretty good for both. Not that java will be pleasant but that the virtual machine will become more workable to dynamic languages. Sun now has jruby and jpython developers on their payroll..
Re:Good old RubyOnRails
on
Advanced Rails
·
· Score: 5, Insightful
Not a well crafted explanation but:
1. Can't use threads, framework is not thread safe. This opens up all sorts of problems. i.e. uploading,persistent connections,complex webservices, etc..
2. Difficult to administrate. Compared to other frameworks, Rails requires a lot more work to set up/administer and seems to crash a lot.
3. Per #1 and #2: Doesn't scale well.
It's still a nice solution for a lot of things. But I imagine most of the bashers are developers who got burned when they found out rails develops well but administrates poorly.
Two reasons. 1) artists are good at creation not marketing/design/distribution etc.. Ultimately the do need someone to help them in that respect. 2) Because labels offer artists money upfront. i.e. signing the contract earns you maybe 20-100k. Labels take the risk and musicians get a nice chunk of money that they may or may not ever earn.
If you turn out to be an amazing artist this is a bad deal for the artist obviously. But for most artists I suspect this is a much too tempting way to cash in.
Music labels take the risk in exchange for value. The take the risk of development,distribution,etc, for possible profits. Signed musicians accept this and give up risk for little long term value. And what is wrong with that? Musicians may complain they got a bad deal, but only after they have proven to be successful and wish the took a risk in distributing/marketing their music themselves.
Perhaps slashdot readers should more focus on a better business model (if one exists) rather than making the recording industry the boogeyman.
Americans, as you describe, are using the word communism correctly. They are not messed up:) 'Communism' is a calque of a german word from Marx's manifesto. It has a specific meaning as to describe history,economy, etc. Marx was not using communism to describe local economic models or organizations.
Well I would say copyright works pretty well. Paying someone directly for working is useful in certain cases but you can't pay everyone who wants to create something. Copyright rewards the creator who takes the risk and investment into a work.
Do you really think the multi-million (billion?) dollar corporations need you here to stand up for them?
No, but people who create content do. It might feel good sticking it the man but if consumers refuse to respect copyright, creators loose the ability to assign any rights their work.
Slashdot Mirror
Doubtful. When people have scalability problems it's not ruby, it's rails. Web applications don't need much cpu but they do need to use memory in a reasonably efficient manner - something that rails cannot currently do.
Gmail is really killer app for email, it's really the one place where no decent open source solutions exist. High volume email is extremely difficult to manage in the world of mbox/maildir type systems. And I have yet to se anything free or commercial that processes spam better.
19th century was a difficult time for american writers because there was no international copyright law. Publishers often just pirated the works of authors rather than paying them.
Uh no. It's actually quite hard to find stuff on limewire compared to something like itunes. Not to mention the lack inconsistent download times/quality.
It's not just a convenient categorization. Spinoza is using the word god in a meaningful sense, and a sense that has been used by many religious/philosophical thinkers before him. The problem with Nadler and his ilk is that they have to reinterpret Spinoza to fit what they want. Saying, 'oh he doesn't really mean god when he says god' or 'he's just using god to make it less objectionable'. This is an arrogant reading of the Ethics.
No because einstein did not care for atheists either.
Spinoza is selling pantheism. Also it is not correct to say his god-concept would can be understood as atheism. Pantheisitic concepts are quite common in all major religions/religious thinkers.
According to Zed Shaw, 37 signals was restarting their servers 400 times a day. This is one of the problems with 37sig; they won't speak on any negative aspects of RoR, you just have to figure it out by yourself.
Sure, the problem is that 1) Rails isn't thread safe/no native threads and 2) Ruby processes are very expensive in memory.
So. Since rails isn't thread safe you have to use a process model where one process handles one request. Now these ruby processes can get up to 100MB in ram (depending on application). That means it takes 100MB to post a comment, display a page,etc.. This is an extremely unforgiving environment when you are trying to scale. There are many scenarios where just a little extra i/o wait in your system will cause everything to crash and burn.
A lot of RoR developers are looking at merb. No native threads but it is thread safe and solves the problem I described above.
Current biological thinking is that domesticated animals were drawn into human habitat because their own habitat was taken over by more fit animals. Humans simply domesticated these animals, but otherwise they wouldn't have stood a chance in the wild.
I have no idea but I would think domestication was an adaptation on the animals part. By becoming so maintainable (and tasty), cows are by far one of the most fit species in todays environment. I'd suspect cows have lost their adaptations in the wild as who needs thick skin when you have a farmer that will just kill all your predators for you?
heh my friend reading this thread pointed me a link at 37signals saying they 98% reliability is okay with them. http://www.37signals.com/svn/archives2/dont_scale_99999_uptime_is_for_walmart.php. lol. I think it's fair to say zed is correct.
Now look, I didn't come to bash rails and I hope your applications run great. But you rails guys like to pretend your shit doesn't stink when any half ass engineer can see some seriously problems. I swear one mention of threads to you rails guys are like bees thinking their hive is under attack. In any case, real world beckons. best of luck.
no. Each new mongrel instance is a completely new runtime environment. My engineers estimate a cost of 20MB per mongrel process on rails 1.1. You don't know what your talking about.
dhh confirmed the 400 restarts as they were running out of memory. You can find the nugget somewhere in zed's rant (http://www.zedshaw.com/rants/rails_is_a_ghetto.html). Since you say you've studied the rails internals, reading zed's rant might help you see some of the issues. It's not something you should take personally - rails does a lot of innovative things. But it is in need of more critical engineers.
btw. Rails is not thread safe. Nor does ruby have native threads. That is *very* different than other languages/frameworks.
What makes the rails world different from other application frameworks is the developers as a whole seem to prefer to sweep their issues under the rug rather than deal with them in the open. Engineers resent that. Saying threading is not a big deal is silly. DRb is not a solution to threading. I remember someone sending me a link from zed shaw saying that before fastthread 37signals had to restart their servers 400 times a day. lol, i am really, lets get real here.
I've seen merb and looks good. I haven't dug too much into ruby threads but it seems like the threading lib has some fundamental problems: http://headius.blogspot.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html
.. it's just wasted. This is where scalability and capacity planning issues can hit you in a bad way.
Multi-process model is unforgiving compared to multi-threads. In many heavy duty web application environments memory is your most precious resource (even more precious than i/o) and a process model is not going to handle this very well. Consider a case where your s3 service is slower than normal one day and your processes are waiting 2x longer than normal. Well while these processes wait they are holding up a good amount of memory that can't be used anywhere else
I'd say the chances are pretty good for both. Not that java will be pleasant but that the virtual machine will become more workable to dynamic languages. Sun now has jruby and jpython developers on their payroll..
Not a well crafted explanation but: 1. Can't use threads, framework is not thread safe. This opens up all sorts of problems. i.e. uploading,persistent connections,complex webservices, etc.. 2. Difficult to administrate. Compared to other frameworks, Rails requires a lot more work to set up/administer and seems to crash a lot. 3. Per #1 and #2: Doesn't scale well. It's still a nice solution for a lot of things. But I imagine most of the bashers are developers who got burned when they found out rails develops well but administrates poorly.
Two reasons.
1) artists are good at creation not marketing/design/distribution etc.. Ultimately the do need someone to help them in that respect.
2) Because labels offer artists money upfront. i.e. signing the contract earns you maybe 20-100k. Labels take the risk and musicians get a nice chunk of money that they may or may not ever earn.
If you turn out to be an amazing artist this is a bad deal for the artist obviously. But for most artists I suspect this is a much too tempting way to cash in.
Music labels take the risk in exchange for value. The take the risk of development,distribution,etc, for possible profits. Signed musicians accept this and give up risk for little long term value. And what is wrong with that? Musicians may complain they got a bad deal, but only after they have proven to be successful and wish the took a risk in distributing/marketing their music themselves. Perhaps slashdot readers should more focus on a better business model (if one exists) rather than making the recording industry the boogeyman.
Americans, as you describe, are using the word communism correctly. They are not messed up :) 'Communism' is a calque of a german word from Marx's manifesto. It has a specific meaning as to describe history,economy, etc. Marx was not using communism to describe local economic models or organizations.
Well I would say copyright works pretty well. Paying someone directly for working is useful in certain cases but you can't pay everyone who wants to create something. Copyright rewards the creator who takes the risk and investment into a work.
Do you really think the multi-million (billion?) dollar corporations need you here to stand up for them?
No, but people who create content do. It might feel good sticking it the man but if consumers refuse to respect copyright, creators loose the ability to assign any rights their work.