I didn't expect to see so much hate for Metallica. Yes, the black album was marginal and everything after that pretty lame except for Death Magnetic if you can get past the compression issue. Death Magnetic is fucking awesome and the drum work is simply amazing. I used to know how to play every song on every album through the black album on guitar, so I obviously love Metallica and was pretty disappointed with the last few, but to say that Death Magnetic sucks means you either haven't really listened to it or you just don't like Metallica. Funny how people can hate so much and yet they couldn't pluck out mary had a little lamb if their life depended on it.
Risk vs Reward. Cash strapped startups can use Amazon Web Services to scale their app to hundreds of servers temporarily when they have that initial spike of interest. There is no affordable way to do this with traditional dedicated servers. When the traffic spike ebbs, server instances are terminated and costs go back to normal.
The risk is trusting your infrastructure and data to a third party, but if this is the risk you have to take to make it in business, I would say it is acceptable, at least until you can afford dedicated machines.
I think what Amazon is doing is amazing. Google got it all wrong by forcing you into their way of doing things. You must develop in python (this may have changed) and use their API. With Amazon, you can use any language and nearly any flavor of OS (mostly linux) you want to use. You can use any software or framework to build your apps. It's total freedom. There is no vendor lock in. If you decide to go dedicated one day, you can do it, no problem.
I asked a friend of my wife, both of whom are Spanish, if he would be interested in working with me on a personal project (RoR) and he contributed some code. The interesting thing was that I work as a Sys Admin and he asked me if I had considered a position as a programmer. I told him I wasn't ready to leave my current position and he told me that he could have a good paying job for me in Spain the day after I decide I want it. So, the outlook in Spain must not be quite as bad as some are saying. The biz he works for develops only in Java, and I've already told him that I know very little about Java and that didn't seem to matter much to him.
My only complaints about Spain would be that everyone lives in flats and the traffic around big cities is a bit crazy. Being from the U.S., I'm a bit spoiled with a big yard with trees to hang out in and, though my wife's flat (now mine also I guess) is fantastic with awesome tile work and such, I miss having a yard when I'm there.
The Spanish seem very friendly to Americans in general. The more you can learn their language, the more they will accept you of course. Very friendly people and their culture is amazing. Barcelona is awesome to say the least.
Apparently you don't get it. The company doesn't have to give a "share" to the original developer, they just have to "share" their code with anyone to whom they distribute the code. (Assuming we're talking about the GPL here.)
Wow...modded flamebait. How so? No self-respecting web developer would create a website where you have to scroll right IMHO. Is this not a major pet peeve for the rest of slashdot's population? If not, do you really dig myspace's page layouts also? sheesh.
And with all of these little incremental updates, how do you not kick all of your users off of the system repeatedly? Sit around and wait for everyone to log off?
Couldn't agree with you more. If a company like Ubuntu, who gives away a TON of effort and information are considered evil for making a bit of profit through related services, then who, exactly, is not evil? The company that gives EVERYTHING away doesn't make a profit and ceases to exist. So, in this idiot's opinion, it would be better for Ubuntu to just cease to exist rather than make a bit of money. Lame. The parent couldn't have said it better....FUCK OFF.
I've often wondered how many times it happens that a lone programmer creates a unique application or fills a niche and gets screwed by one of his first employees taking his ideas and running with it. Imagine that he put years of thought into the structure and algorithms. Maybe the actual code wasn't extremely difficult to write, but the though process behind it was unique and the relations of his models took a significant amount of time and effort to produce. He hires a few hackers to help with final testing and the implementation and during that time, one of them was secretly writing his own version of the app. He didn't steal the code, but stole the model and the work that went into putting all of the relationships together in a cohesive way. Maybe the thief is a better programmer or has more resources and, instead of putting that talent and resources into making the original app the best it could be, he creates a better version, gets the market share and leaves the original guy in the dust. On his own, the "thief" would never have come up with the app, but once he saw the value, it was easy to steal and call it his own.
Does this happen regularly? Do you feel that it is just the "free market" at work? What did the original author do wrong? Should he have had a non-compete? If not, how does he prevent this scenario?
Like I said, I love Rails, but what it takes to get it set up, at least for me, is difficult. Perhaps I'm asking for too much, but I want everything working correctly and together. Are you using WebDAV, ssl, ssh, apache and mongrel?
Your results are not in line with most people's. In fact, here is text from the "Deploying Rails Applications" book from an "expert".
"I quickly discovered after the joy of development, deployment was a real drag. All of those waves of euphoria completely disintegrated against the endless stream of crash logs, Rails error pages, and futile install scripts. I spent hours wading through the Rails wikis, blogs, and books for answers, but each one gave me a mere fragment of what I needed. Much of the information I found was contradictory or flat out wrong."
My intent is to build a server that can be used for testing and then replicated and moved into production. Yes, I know that I could set up a test server and run Webrick, but there is no way you could go to production like that. My requirements are: Ubuntu 6.06 LTS, Apache 2.2.4, Mongrel, Subversion 1.4.4, WebDAV, Openssl, Openssh, MySQL5, and Capistrano. I had everything working great right up until I tried to implement Mogrel and found out that Apache 2.2.4 was required. (I started off with 2.0) At that point I basically had to scrap everything and start over by compiling Apache a thousand times using different "configure" options. I never have gotten the magic formula right to get WebDAV working, much less mongrel. Apache 2.2.4 doesn't seem to load it's files in the same directories as an apt-get install does on Ubuntu, which causes more confusion.
Then I found DepRec which supposedly has all the necessary commands to build a Ubuntu 6.06 server from scratch. That worked great until I did the svn setup and it blew up. I looked at the source and I think I know why the error happens, but don't know to fix it.
I'm surprised that you haven't found any obscure errors or config options during this process. Have you seen the tutorials for setting all this up? My current setup script is over 600 lines of commands. Change the config in this file, run these ten commands, change the config in that file, run 20 more commands.
For the love of God, if you've actually, successfully set up a RoR server, please fill me in on how to do it. I've been trying for 3 weeks. See my rant below. shagymoe@yahoo.com
All the posts I've seen so far complain about RoR's scalability. These people have obviously not worked with RoR because, while scalability might be an issue, if they'd really worked with RoR, they would know that DEPLOYMENT is what kills rails.
I jumped on the RoR bandwagon full bore and have been developing my app for over 1 year. The Ruby language is awesome and the framework takes the messiness out of web development. When I look at PHP code now I was to puke. With that said, I can deploy a PHP application is seconds...literally. Rails on the other hand, has had me working almost full time for 3 weeks trying to get a fucking test (not production...test) server up and running. It is completely fucking ridiculous to get a server set up that you could seriously test with or, God forbid, move into production.
I've been a Systems Admin for over 7 years and a programmer for 6 years and using Linux for at least 8 years so I'm no newbie or idiot. I've tried setting up everything manually as well as using Capistrano and Capistrano/Deprec and still haven't had success getting a server setup.
It is unbelievable how many crazy little nuances and bizarre configuration parameters you will encounter. In a short period of time you are just copying and pasting any random crap someone posted on the net that claims to have a working server. I've followed countless tutorials TO THE LETTER and this shit still doesn't work.
I even purchased the "Deploying Rails Applications" book from Pragmatic Programmers and STILL CAN'T FUCKING GET SOMETHING DEPLOYED!!! Possibly the worst written book ever and claims to give you everything you need to get the Rails stack set up on Ubuntu Dapper Drake and has almost zero setup commands. What a load of crap. Anyone could have written this book since he just lifted it all from internet posts. Good job asshole, thanks for nothing.
You know what happens to people who can successfully set up a Rails application? They start a fucking hosting company and make a shitload of money because hardly anyone else can do it. EngineYard, SliceHost, and RailsMachine are all examples of Rails programmers who started hosting companies because they actually made something work. It really just shouldn't be that hard.
Maybe someday Rails will be easy to deploy, but right now it is a fucking nightmare. It totally ruins all of the great things about Ruby and Rails. I'm starting to think it's all a conspiracy and Rails was just some kind of carrot to lure us all into purchasing expensive hosting.
The hype about Rails' faster development time is true right up until implementation and then it's a load of shit. Implementing a PHP app is like 2nd grade math, whereas implementing a Rails app is like quantum physics.
I've never been so fucking frustrated about anything computer related in all my life. If you don't have a high tolerance for wading through tons of bullshit, then I don't recommend trying to implement a Rails app at this time.
Just make them personally responsible for the mental health bills for all these children and that should be punishment enough. They'll never have another cent to their name.
I like ubuntu and my 13yr old installed it by himself (and got connected) with no problems. However, installing the java plugin for firefox was a PITA and not something a normal user could do like creating symbolic links for the plugin to the java install directory. Does it really need to be that difficult? It wouldn't install automatically from firefox. Maybe there was an easier way, but from what I can tell, you have to do it manually. Also, a lot of the instructions on the Ubuntu website referred to old apt package that were not found.
Re:Ruby as a first language?
on
Beginning Ruby
·
· Score: 1, Insightful
Maybe the problem is that, like a troll, you didn't give any good reason for your assertion that ruby is a bad language to start with. (assuming that puh-leese is an assertion.)
Personally, I could never go back to perl, java or php from ruby, so it that is the case, why not bother starting with ruby?
Re:Ruby as a first language?
on
Beginning Ruby
·
· Score: 4, Funny
I started with Perl...I'll probably never recover from that.
...and what's so hard about it? I'd rather alt-tab than swivel to look at a different monitor. I'm forced to use windows at work and don't remember now if it is alt-tab on linux, but I'm sure there is a similar option.
Yeah, but how do you actually SAY that? p0wned. Is it like pohned? Or is is pee-owned? Or maybe P, zero, wned! Could it be like POW...ned? Or, keeping with the zero theme, is it peezowned?
I think we have to sort out the taunt before we really embarrass ourselves.
I didn't expect to see so much hate for Metallica. Yes, the black album was marginal and everything after that pretty lame except for Death Magnetic if you can get past the compression issue. Death Magnetic is fucking awesome and the drum work is simply amazing. I used to know how to play every song on every album through the black album on guitar, so I obviously love Metallica and was pretty disappointed with the last few, but to say that Death Magnetic sucks means you either haven't really listened to it or you just don't like Metallica. Funny how people can hate so much and yet they couldn't pluck out mary had a little lamb if their life depended on it.
Risk vs Reward. Cash strapped startups can use Amazon Web Services to scale their app to hundreds of servers temporarily when they have that initial spike of interest. There is no affordable way to do this with traditional dedicated servers. When the traffic spike ebbs, server instances are terminated and costs go back to normal.
The risk is trusting your infrastructure and data to a third party, but if this is the risk you have to take to make it in business, I would say it is acceptable, at least until you can afford dedicated machines.
I think what Amazon is doing is amazing. Google got it all wrong by forcing you into their way of doing things. You must develop in python (this may have changed) and use their API. With Amazon, you can use any language and nearly any flavor of OS (mostly linux) you want to use. You can use any software or framework to build your apps. It's total freedom. There is no vendor lock in. If you decide to go dedicated one day, you can do it, no problem.
I asked a friend of my wife, both of whom are Spanish, if he would be interested in working with me on a personal project (RoR) and he contributed some code. The interesting thing was that I work as a Sys Admin and he asked me if I had considered a position as a programmer. I told him I wasn't ready to leave my current position and he told me that he could have a good paying job for me in Spain the day after I decide I want it. So, the outlook in Spain must not be quite as bad as some are saying. The biz he works for develops only in Java, and I've already told him that I know very little about Java and that didn't seem to matter much to him.
My only complaints about Spain would be that everyone lives in flats and the traffic around big cities is a bit crazy. Being from the U.S., I'm a bit spoiled with a big yard with trees to hang out in and, though my wife's flat (now mine also I guess) is fantastic with awesome tile work and such, I miss having a yard when I'm there.
The Spanish seem very friendly to Americans in general. The more you can learn their language, the more they will accept you of course. Very friendly people and their culture is amazing. Barcelona is awesome to say the least.
Hope that helps.
Apparently you don't get it. The company doesn't have to give a "share" to the original developer, they just have to "share" their code with anyone to whom they distribute the code. (Assuming we're talking about the GPL here.)
Wow...modded flamebait. How so? No self-respecting web developer would create a website where you have to scroll right IMHO. Is this not a major pet peeve for the rest of slashdot's population? If not, do you really dig myspace's page layouts also? sheesh.
Scroll right for search results = FAIL
And with all of these little incremental updates, how do you not kick all of your users off of the system repeatedly? Sit around and wait for everyone to log off?
You can't get the same scaling from a physical server as you can get from "the cloud" for anywhere near the same price.
Sorry, spaces are not accepted in variables. Double capitalizing is bad form and it is nil not null.
If they're anything like my bi-polar ex-wife, you're going to regret that.
Couldn't agree with you more. If a company like Ubuntu, who gives away a TON of effort and information are considered evil for making a bit of profit through related services, then who, exactly, is not evil? The company that gives EVERYTHING away doesn't make a profit and ceases to exist. So, in this idiot's opinion, it would be better for Ubuntu to just cease to exist rather than make a bit of money. Lame. The parent couldn't have said it better....FUCK OFF.
Well, at least the roads will not deteriorate...because no one will use them.
I've often wondered how many times it happens that a lone programmer creates a unique application or fills a niche and gets screwed by one of his first employees taking his ideas and running with it. Imagine that he put years of thought into the structure and algorithms. Maybe the actual code wasn't extremely difficult to write, but the though process behind it was unique and the relations of his models took a significant amount of time and effort to produce. He hires a few hackers to help with final testing and the implementation and during that time, one of them was secretly writing his own version of the app. He didn't steal the code, but stole the model and the work that went into putting all of the relationships together in a cohesive way. Maybe the thief is a better programmer or has more resources and, instead of putting that talent and resources into making the original app the best it could be, he creates a better version, gets the market share and leaves the original guy in the dust. On his own, the "thief" would never have come up with the app, but once he saw the value, it was easy to steal and call it his own.
Does this happen regularly? Do you feel that it is just the "free market" at work? What did the original author do wrong? Should he have had a non-compete? If not, how does he prevent this scenario?
Why doesn't "script/server" as a testing server (using Mongrel, Lighttpd, or Webrick) work for you?
Because I feel that the testing server should be exactly what you are going to put into production.
Like I said, I love Rails, but what it takes to get it set up, at least for me, is difficult. Perhaps I'm asking for too much, but I want everything working correctly and together. Are you using WebDAV, ssl, ssh, apache and mongrel?
I'd be interested to see your set up script.
Your results are not in line with most people's. In fact, here is text from the "Deploying Rails Applications" book from an "expert".
"I quickly discovered after the joy of development, deployment was a real
drag. All of those waves of euphoria completely disintegrated against
the endless stream of crash logs, Rails error pages, and futile install
scripts. I spent hours wading through the Rails wikis, blogs, and books
for answers, but each one gave me a mere fragment of what I needed.
Much of the information I found was contradictory or flat out wrong."
My intent is to build a server that can be used for testing and then replicated and moved into production. Yes, I know that I could set up a test server and run Webrick, but there is no way you could go to production like that. My requirements are: Ubuntu 6.06 LTS, Apache 2.2.4, Mongrel, Subversion 1.4.4, WebDAV, Openssl, Openssh, MySQL5, and Capistrano. I had everything working great right up until I tried to implement Mogrel and found out that Apache 2.2.4 was required. (I started off with 2.0) At that point I basically had to scrap everything and start over by compiling Apache a thousand times using different "configure" options. I never have gotten the magic formula right to get WebDAV working, much less mongrel. Apache 2.2.4 doesn't seem to load it's files in the same directories as an apt-get install does on Ubuntu, which causes more confusion.
Then I found DepRec which supposedly has all the necessary commands to build a Ubuntu 6.06 server from scratch. That worked great until I did the svn setup and it blew up. I looked at the source and I think I know why the error happens, but don't know to fix it.
I'm surprised that you haven't found any obscure errors or config options during this process. Have you seen the tutorials for setting all this up? My current setup script is over 600 lines of commands. Change the config in this file, run these ten commands, change the config in that file, run 20 more commands.
For the love of God, if you've actually, successfully set up a RoR server, please fill me in on how to do it. I've been trying for 3 weeks. See my rant below. shagymoe@yahoo.com
All the posts I've seen so far complain about RoR's scalability. These people have obviously not worked with RoR because, while scalability might be an issue, if they'd really worked with RoR, they would know that DEPLOYMENT is what kills rails.
I jumped on the RoR bandwagon full bore and have been developing my app for over 1 year. The Ruby language is awesome and the framework takes the messiness out of web development. When I look at PHP code now I was to puke. With that said, I can deploy a PHP application is seconds...literally. Rails on the other hand, has had me working almost full time for 3 weeks trying to get a fucking test (not production...test) server up and running. It is completely fucking ridiculous to get a server set up that you could seriously test with or, God forbid, move into production.
I've been a Systems Admin for over 7 years and a programmer for 6 years and using Linux for at least 8 years so I'm no newbie or idiot. I've tried setting up everything manually as well as using Capistrano and Capistrano/Deprec and still haven't had success getting a server setup.
It is unbelievable how many crazy little nuances and bizarre configuration parameters you will encounter. In a short period of time you are just copying and pasting any random crap someone posted on the net that claims to have a working server. I've followed countless tutorials TO THE LETTER and this shit still doesn't work.
I even purchased the "Deploying Rails Applications" book from Pragmatic Programmers and STILL CAN'T FUCKING GET SOMETHING DEPLOYED!!! Possibly the worst written book ever and claims to give you everything you need to get the Rails stack set up on Ubuntu Dapper Drake and has almost zero setup commands. What a load of crap. Anyone could have written this book since he just lifted it all from internet posts. Good job asshole, thanks for nothing.
You know what happens to people who can successfully set up a Rails application? They start a fucking hosting company and make a shitload of money because hardly anyone else can do it. EngineYard, SliceHost, and RailsMachine are all examples of Rails programmers who started hosting companies because they actually made something work. It really just shouldn't be that hard.
Maybe someday Rails will be easy to deploy, but right now it is a fucking nightmare. It totally ruins all of the great things about Ruby and Rails. I'm starting to think it's all a conspiracy and Rails was just some kind of carrot to lure us all into purchasing expensive hosting.
The hype about Rails' faster development time is true right up until implementation and then it's a load of shit. Implementing a PHP app is like 2nd grade math, whereas implementing a Rails app is like quantum physics.
I've never been so fucking frustrated about anything computer related in all my life. If you don't have a high tolerance for wading through tons of bullshit, then I don't recommend trying to implement a Rails app at this time.
Just make them personally responsible for the mental health bills for all these children and that should be punishment enough. They'll never have another cent to their name.
I like ubuntu and my 13yr old installed it by himself (and got connected) with no problems. However, installing the java plugin for firefox was a PITA and not something a normal user could do like creating symbolic links for the plugin to the java install directory. Does it really need to be that difficult? It wouldn't install automatically from firefox. Maybe there was an easier way, but from what I can tell, you have to do it manually. Also, a lot of the instructions on the Ubuntu website referred to old apt package that were not found.
Maybe the problem is that, like a troll, you didn't give any good reason for your assertion that ruby is a bad language to start with. (assuming that puh-leese is an assertion.)
Personally, I could never go back to perl, java or php from ruby, so it that is the case, why not bother starting with ruby?
I started with Perl...I'll probably never recover from that.
...and what's so hard about it? I'd rather alt-tab than swivel to look at a different monitor. I'm forced to use windows at work and don't remember now if it is alt-tab on linux, but I'm sure there is a similar option.
I'd wager hundreds of millions of dollars were spent on patching computers and fixing code. So Fing stupid.
Yeah, but how do you actually SAY that? p0wned. Is it like pohned? Or is is pee-owned? Or maybe P, zero, wned! Could it be like POW...ned? Or, keeping with the zero theme, is it peezowned?
I think we have to sort out the taunt before we really embarrass ourselves.