Super Glue has the same ingredients are "Tissue Glue" they use after surgery instead of external stitches to close the skin.
I've had an accident with some quantity of super glue poured on my leg (don't ask). It hurted like pain and caused bad chemical burns, not exactly something you'd wanna pour into an open wound.
If is funny. The question now is where do we go from here? Continue to be ashamed of our intrinsic natures and stick to faulty societal models (socialism) or accept ourselves as the selfish beings that we are and finally become comfortable with capitalism?
You see, both models are actually part of our intrinsic nature. As separate beings, capitalism makes sense. As cogs in a large system (or cells in an organism if you will), socialism makes sense.
Since we're currently on the borderline between separate beings, and part of one "uber-being" (society), such conflicts will always arise again and again.
Sony's running on fumes. Their marketing team STILL not fired and STILL making the same mistakes as with the PSP fake site and grafitti.
Sony: you're selling to the techy early adopters. Don't sell is shit, because we don't buy shit. I wonder if they even have a honest good thing to say about their products, if they come up with so much non-sense.
And no, nested DIVs are NOT the same as nested tables, because tables have rows and columns and are meant for TABULAR DATA
You know, no one can help you if you don't see the irony in your own statements. And TYPING IN ALL CAPS doesn't help get your supposed point across either.
Check the CSS3 Layout module proposal: it has rows and columns. Because this is what layouts are. Until CSS gains back this ability, tables will have plenty of cases where they have edge on CSS hacks.
Not many were the people that appreciated SOAP before "Google did it" (tm).
After "Google did it" (tm), SOAP is suddenly a good thing. Now that they drop it, peple are discussing if it's again a bad thing. Google is not the whole of Internet though. People will use SOAP if it's better than other solutions for a given tasks.
And if it isn't, then it was a fad all along.
Same with "AJAX" by the way. JavaScript was out there for years before "Google did it" (tm) but there were not many people appreciating it. If Google drops JavaScript tomorrow, would this spell the end of AJAX?
Hey Sony, Nintendo, and Apple, Listen Up! This is your wake up call. MS intends to leverage their OS monopoly to give themselves and advantage in the gaming console market.
Oh no! Microsoft intends to leverage their OS monopoly in the game market, by introducing consistent labeling and experience for Windows games in Vista! Shit! The world's lost!
In terms of the European online store, while still being extremely vague, a spokesman for SCE Europe was able to explain that Sony would have no defense if they were to charge the European consumer more than in other regions as there are no extra costs on digital distribution as apposed to a product with packaging etc.
That's quite naive. There can always be reasons. I'm only purchasing serial numbers (licenses...) from Adobe/Macromedia, but they've always charged me almost double since I'm in EU. I always envied my US colleagues which get to buy the same software so much cheaper:(
The excuses: exchange rates, VAT taxes, other electronic taxes, [insert other vague reasons], [insert lock of shopping region per your credit card country origin]
Yes, in my mind even I associate the color brown with shit
Well, depending on the biological species and their momentary health condition, as a matter of fact shit can be yellow, red, or so dark that it looks black. It's also often green, sometimes yellow, and in rare cases white.
In fact the only truly "shit safe" color is blue, and its derivatives, like purple or cyan.
So to be Slashdot compliant, MP3 manufacturers will abandon selling red, white and black iPods, and starting next year begin the new series of exclusive blue, purple and cyan mp3 players.
Some industry analysts are hoping this will have the desired effect of Slashdot no longer qualifying said mp3 players as "shit". Other analysts however hope that Slashdot users will just suddenly, you know, grow up, and stop being so interested in elementary toilet humor jokes and reducing everything they see to references to various bodily functions and byproducts.
Difficulty of a mission isn't perfectly proportional to the distance from the center of Earth to the spot of colonization.
Let NASA know a little bit about space missions than bloggers do, but even without this, common sense says that's easier to establish a colony on a solid surface, and with some gravity (much easier to build tools, handle daily activities and so on, even the safety of having some ground below your feet), versus a colony in a ship in open space.
But you know, universe has its ways... , I mean, if it didn't, bloggers would by making colonies in space and NASA would be teaching them how to write articles.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
Would you agree you are more productive working with cleaner code?
Would you agree you are more productive working on something intuitive?
Would you agree you are more productive with less redundant code?
Do you agree 1+1 = 2? Now, does this mean PHP is better? You're asking the wrong questions.
In my eye Ruby fails on all of those. Cleaner code doesn't mean randomly dropping various characters and claiming them redundant.
Unlike Ruby, PHP doesn't have hard time differentiating function from a non-function, and neither do I. In my day to day work, the "C++" style syntax has proven most productive and clear.
PS: For type conversion in PHP, look for "magic functions" and especially __toString, next, isValid and so on.
Please hit "preview" before submitting. It provides instant feedback.
I'm sorry I was busy because of the deficiencies non-Ruby languages burden my workday with.
I never read of anyone having suffered consequences as a result of someone losing their data. Why is that?
Doesn't it seem as if there would be a few major class action lawsuits, at the very least? You'd think every time data loss occurs on this large a scale, it would be followed by droves of people suffering from identity theft or fraud
You're correct: theft or loss of a machine doesn't automatically mean identity theft.
First, the machine should be in a working state which is sometimes not the case. Then, the criminal should realize there may be interesting info on the laptop (most would just format the drive and reinstall OS). Then he should find it on the disk. Then know what to do with it or who would be interested in buying it.
As you may suspect, this quickly limits the potential damage from such mishaps.
But there's the other side of the coin: the fact you don't hear of consequences may be a result of too delayed or still undiscovered frauds.
It's like bad food additives (like aspartam): they are deemed safe, simply because by the time damage occurs, noone can link the damage to the cause.
It's possible that people suffered but they either didn't know they data was stolen, how it was stolen, or that their problems are caused by identity theft.
It's also possible that the info is collected somewhere, ready to be abused, but the would-be-criminals are waiting for things to "settle" so they have greater chances of success with their activities.
So it's all very complex, but one thing is simple: keeping unencrypted critical info on portable machines you can easily lose possession of, is terribly bad. It's pure laziness and ignorance, and the solutions to this very basic layer of data protection, are simple and "there", ready for someone to realize they are needed.
I'm not very happy to see the government trying to react in "pieces" by demanding that veteral info breaches are reported.. Why just veteran breaches? I'm not a veteran from any war, is theft of my data less critical? It can be the place where I work, the site I shopped from or my bank: it really should be approached with a generic solution and not a bunch of untimely exceptions to an absurd status quo.
If our universe resembles a video game, could it actually be a video game?
That logic is fallacious, even if the observable universe is a "simulation", then this simulation runs inside a real universe, and we're at the start again figuring out what the universe is.
Plus I subscribe to another logic: if the universe is similar to a video game, then it's because as video games increase in complexity they start to approach the model of a little universe:D
And ask anyone what they remember from the first, and it'll be Johnny Depp's character and the humour, not the special effects.
That's funny since I also remember the effects AND Johny Depp's performance AND the humor.
You guys are oversimplifying everything. "It's not about the effects!", breaking news: it's ALSO about the effects, it's about everything in a careful balance, that, if done properly is called "a good movie".
It's not as if they had effects, they had to have crappy script, it just happens so that when movies get involved, they try to stick everything to simple "secure" models just like you're doing here in your reviews.
Now this site in particular, is on ILM's site. ILM don't make movie scripts, they make effects. Don't bash them for showcasing their (amazing, in my opinion) work and willing to market themselves and their incredible skills in this area.
Look at the site as an achievement of arts and technology and forget the script.
I for one, really respect ILM for their hard work on this movie and just consider how fast CGI technologies are evolving: I mean they did THIS all with the raw footage from the film (mocap, camera tracking: all done on the spot, no additional footage).
Also managing all those little details in the character models looks like a hyper impossible tasks to me: but they pulled it off and pulled it off for an incredible amount of shots in the movie with consistent success. I applaud them for their participation in this project.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
Dynamic, arbitrary conversion: I can declare an object's conversion to another format that is automatically called when it is needed in that context. I can create a number subclass that will know to call itself "4" in a numeric context and "IV" in a string context.
PHP has the same so you can make a class "visible" as string, iterator etc.
Optional parenthesis: "has_many(:colors)" is equivalent to "has_many:colors".
Uhmm.. I'm missing your point here. Does optional parens make a huge difference in your life as a developer?
There you go: $a = (2+3); the parens are optional!:P
Functions with arbitrary parameter length: "has_many [:colors,:shapes]" is equivalent to "has_many:colors,:shapes"
PHP has that too. You can get arbitrary (unknown in advance) number of arguments inside the function and process them. I'm not a fan of that feature however.
People overuse this functionality to create a complete mess of "arbitrary parameters", when all they want is signature overloading.
Iterators and Blocks: Rather than "for( i =0; i
Gee, Ruby has invented iterators!
In PHP this is: foreach ($members as $x)... In JavaScript even, it is: for (x in members)...
Does it hurt knowing you rediscovered hot water there?
Messages: Rather than call a function to send a message. This allows Duck Typing,which allows refactoring impossible in other languages.
Hehehe, you know I've heard and seen lots of stories about Ruby refactoring. I have a friend, who after lots of fight confessed that Ruby encourages refactoring for refactoring's sake: just to make your incredible syntax look a bit tiny easier and more "natural"..
Well here's what: why Ruby devs are busy molding their own "languages" we've decided on a language and and use OOP features to mold our natural interfaces to the systems we create.
Ruby is trying to go that extra step of reinventing its own syntax for every project, and that's a step noone needs.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
class User extends AppModel
{
var $name = "User";
var $hasMany = array('Membership');
}
That is as concise as PHP will allow. It is a limit of the language.
Actually the "$name" is optional, PHP classes know very well what they are named.
Ruby's syntax makes it easy to construct domain specific languages.
var $hasMany = array('Membership');
will never feel as natural as:
has_many:memberships
Oh I see, you're afraid of language syntax. The "array" bit is a framework oddity of the sample you used. So we arrive at the core of the issue: The quotes! 'Membership' will NEVER feel as natural as memberships!
What was I thinking, I drop everything and become a Rails developer. Never mind all the "side effects" and global crap Ruby has to support its "magic", all it matters is we avoid those quotes and dollar signs with the cost of our lives.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
You have Java,.NET, and PHP. I make more money. Enjoy them.
This, just like everything you said is a bunch of unsubstantiated assumptions you spew left and right in attempt to hit a weak spot.
I don't expect different from a Rails fan. You're all blind.
The answer is so simple: because it's fashionable.
How does a fashion start? That's a tough question. For the first this, you gotta be everywhere, in the face of people every day. Microsoft is.
They are a commercial company and free software is mostly supported by young idealists (yes, I'll completely ignore the commercialization of OSS for this example), which are naturally opposed to a leading commercial company competing with their work.
Around the antitrust cases, the OSS community, the forums, the mishaps: a seed forms that quickly grows into a subculture where it's fashionable to loudly demonstrate how and why you hate Microsoft.
Of course there are legitimate reasons to not like Microsoft, but there are legitimate reasons to not like anything at all.
To end how I started, the verdict why people hate Microsoft: because it's fashionable.
Seriously, any employer that asks for a code sample has no clue what they're doing. They should put you at a whiteboard with a pen and have you write something on the fly.
You know, after so much typing, I don't know how to write:(
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
So has a popular web comic. [penny-arcade.com]
In fact one of the cases I've looked into was penny arcade, which after switching to Rails were plagued by performance issues.
And with Rails, I don't need an IDE. For a while, I developed in vi.
You know that basically says it all. You develop in vi. How marvelous. You can develop anything in vi, but when your project grows and you work in a team, you suddenly appreciate the myriad of (probably irrelevant for you) features that makes your life easier:
- integration with version control systems (SVN for me), for updating, committing, resolving conflicts and so on directly from the editor - interactive debugging (breakpoints, step in/over/out etc, watches) - "intellisense" or "autocomplete" so that you see instant feedback for the classes, methods and arguments that you have to use, which your team mates created as a part of a larger ecosystems (of course maybe switching out of vi and constantly consulting the source code of the entire repo for API specifics is much easier than instant feedback?) - instant feedback on syntax and logical errors while you're typing the code (so you don't have to keep refreshing a browser only to see a basic error, like a syntax error)
I use this when I code in Java,.NET or PHP. And you have vi. Enjoy it.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
Oh, it's *opinionated*, certainly.
It does NOT appreciate you trying to do anything but a Web2.0 app, with forward generation of a db schema on MySQL. It absolutely, positively despises you trying to use an existing db schema, or to interoperate with anything resembling a J2EE app.
However, if you are willing to play by its rules, it rewards the novice. I say "Rails", and not "RoR" and not "Ruby", because I consider "Rails" to be an entirely distinct idiom from Ruby. Ruby is a language for Computer Scientists, in the sense that ML, Lisp, and Prolog are.
Rails is something different. I don't like arguing about it though. There's not a developer who I would consider competent, who could not produce a webapp within, say, four hours of working through the first demo.
Congratulations, you've been brainwashed. No you successfully apply cliche excuses when confronted with Rails disadvantages (hey it doesn't work with anything since it's *opinionated*! yei!), and ignore the tens of other frameworks which have the same features Rails has (and more), like CakePHP on PHP, Django on Python and so on. They have the SAME features and approach dude. Sorry to burst your bubble, Rails is just a lot of hype and a bunch of brainwashed fans defending it on the various forums.
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
A technology like Rails threatens to make "programmers" obsolete, at least in certain segments of the killer-app domain that is "webapps."
I feel as threatened by Rails making me obsolete, as I do feel threatened by Lego Logo.
People who were never able to write programs in, say, CGI, PHP, or servlets/JSP, are writing Rails apps without much difficulty.
Thanks for the propaganda, but I'd like to see actual examples to acknowledge this as anything other than completley disconnected from reality BS.
It's a lot easier to start with PHP, especially for people who never coded before, or you think MVC, ActiveRecord, routing, scaffolding and so on is far easier than the learning curve PHP offers.
Rails enables this, and it is doing so rather effectively, for those who discover it. That's a pretty scary thing for a J2EE developer to witness.
Hahahaha! Dude, how can you compare J2EE development with home-made Rails applications!? Are you from this planet?
Jesus, well let's hope those "enabled" by Rails people never have to suffer more than mild traffic to their sites, since it's about what RoR can handle anyways.
Your post is full of the same kind of hype propaganda that completely surrounds Ruby on Rails. One reason I hate it so much: don't mislead people about what RoR is, it'll all bite you back so hard you won't have time to react.
Slashdot Mirror
It hurted like pain
Nice, another gem from the "don't post while still sleeping department"
Super Glue has the same ingredients are "Tissue Glue" they use after surgery instead of external stitches to close the skin.
I've had an accident with some quantity of super glue poured on my leg (don't ask). It hurted like pain and caused bad chemical burns, not exactly something you'd wanna pour into an open wound.
If is funny. The question now is where do we go from here? Continue to be ashamed of our intrinsic natures and stick to faulty societal models (socialism) or accept ourselves as the selfish beings that we are and finally become comfortable with capitalism?
You see, both models are actually part of our intrinsic nature. As separate beings, capitalism makes sense. As cogs in a large system (or cells in an organism if you will), socialism makes sense.
Since we're currently on the borderline between separate beings, and part of one "uber-being" (society), such conflicts will always arise again and again.
Sony's running on fumes. Their marketing team STILL not fired and STILL making the same mistakes as with the PSP fake site and grafitti.
Sony: you're selling to the techy early adopters. Don't sell is shit, because we don't buy shit. I wonder if they even have a honest good thing to say about their products, if they come up with so much non-sense.
And no, nested DIVs are NOT the same as nested tables, because tables have rows and columns and are meant for TABULAR DATA
You know, no one can help you if you don't see the irony in your own statements.
And TYPING IN ALL CAPS doesn't help get your supposed point across either.
Check the CSS3 Layout module proposal: it has rows and columns. Because this is what layouts are. Until CSS gains back this ability, tables will have plenty of cases where they have edge on CSS hacks.
Not many were the people that appreciated SOAP before "Google did it" (tm).
After "Google did it" (tm), SOAP is suddenly a good thing. Now that they drop it, peple are discussing if it's again a bad thing. Google is not the whole of Internet though. People will use SOAP if it's better than other solutions for a given tasks.
And if it isn't, then it was a fad all along.
Same with "AJAX" by the way. JavaScript was out there for years before "Google did it" (tm) but there were not many people appreciating it. If Google drops JavaScript tomorrow, would this spell the end of AJAX?
Same logic applies.
Isn't this like preventing a news reporter from referring to a book, because someone might go out and photocopy it illegally?
:P ...
Nope. Keep trying though
Hey Sony, Nintendo, and Apple, Listen Up! This is your wake up call. MS intends to leverage their OS monopoly to give themselves and advantage in the gaming console market.
Oh no! Microsoft intends to leverage their OS monopoly in the game market, by introducing consistent labeling and experience for Windows games in Vista! Shit! The world's lost!
In terms of the European online store, while still being extremely vague, a spokesman for SCE Europe was able to explain that Sony would have no defense if they were to charge the European consumer more than in other regions as there are no extra costs on digital distribution as apposed to a product with packaging etc.
:(
That's quite naive. There can always be reasons. I'm only purchasing serial numbers (licenses...) from Adobe/Macromedia, but they've always charged me almost double since I'm in EU. I always envied my US colleagues which get to buy the same software so much cheaper
The excuses: exchange rates, VAT taxes, other electronic taxes, [insert other vague reasons], [insert lock of shopping region per your credit card country origin]
There are way more subtle ways to misuse cookies than demonstrated here.
This article shows us that you shouldn't let people in only by username without their password. Well duh.
Yes, in my mind even I associate the color brown with shit
Well, depending on the biological species and their momentary health condition, as a matter of fact shit can be yellow, red, or so dark that it looks black. It's also often green, sometimes yellow, and in rare cases white.
In fact the only truly "shit safe" color is blue, and its derivatives, like purple or cyan.
So to be Slashdot compliant, MP3 manufacturers will abandon selling red, white and black iPods, and starting next year begin the new series of exclusive blue, purple and cyan mp3 players.
Some industry analysts are hoping this will have the desired effect of Slashdot no longer qualifying said mp3 players as "shit". Other analysts however hope that Slashdot users will just suddenly, you know, grow up, and stop being so interested in elementary toilet humor jokes and reducing everything they see to references to various bodily functions and byproducts.
Hehe, I said "shit". Hehe.
Difficulty of a mission isn't perfectly proportional to the distance from the center of Earth to the spot of colonization.
Let NASA know a little bit about space missions than bloggers do, but even without this, common sense says that's easier to establish a colony on a solid surface, and with some gravity (much easier to build tools, handle daily activities and so on, even the safety of having some ground below your feet), versus a colony in a ship in open space.
But you know, universe has its ways... , I mean, if it didn't, bloggers would by making colonies in space and NASA would be teaching them how to write articles.
Next article on Slashdot: 486 SX vs 486 DX
Would you agree you are more productive working with cleaner code?
Would you agree you are more productive working on something intuitive?
Would you agree you are more productive with less redundant code?
Do you agree 1+1 = 2? Now, does this mean PHP is better? You're asking the wrong questions.
In my eye Ruby fails on all of those. Cleaner code doesn't mean randomly dropping various characters and claiming them redundant.
Unlike Ruby, PHP doesn't have hard time differentiating function from a non-function, and neither do I. In my day to day work, the "C++" style syntax has proven most productive and clear.
PS: For type conversion in PHP, look for "magic functions" and especially __toString, next, isValid and so on.
Please hit "preview" before submitting. It provides instant feedback.
I'm sorry I was busy because of the deficiencies non-Ruby languages burden my workday with.
I never read of anyone having suffered consequences as a result of someone losing their data. Why is that?
Doesn't it seem as if there would be a few major class action lawsuits, at the very least? You'd think every time data loss occurs on this large a scale, it would be followed by droves of people suffering from identity theft or fraud
You're correct: theft or loss of a machine doesn't automatically mean identity theft.
First, the machine should be in a working state which is sometimes not the case.
Then, the criminal should realize there may be interesting info on the laptop (most would just format the drive and reinstall OS).
Then he should find it on the disk.
Then know what to do with it or who would be interested in buying it.
As you may suspect, this quickly limits the potential damage from such mishaps.
But there's the other side of the coin: the fact you don't hear of consequences may be a result of too delayed or still undiscovered frauds.
It's like bad food additives (like aspartam): they are deemed safe, simply because by the time damage occurs, noone can link the damage to the cause.
It's possible that people suffered but they either didn't know they data was stolen, how it was stolen, or that their problems are caused by identity theft.
It's also possible that the info is collected somewhere, ready to be abused, but the would-be-criminals are waiting for things to "settle" so they have greater chances of success with their activities.
So it's all very complex, but one thing is simple: keeping unencrypted critical info on portable machines you can easily lose possession of, is terribly bad. It's pure laziness and ignorance, and the solutions to this very basic layer of data protection, are simple and "there", ready for someone to realize they are needed.
I'm not very happy to see the government trying to react in "pieces" by demanding that veteral info breaches are reported.. Why just veteran breaches? I'm not a veteran from any war, is theft of my data less critical? It can be the place where I work, the site I shopped from or my bank: it really should be approached with a generic solution and not a bunch of untimely exceptions to an absurd status quo.
If our universe resembles a video game, could it actually be a video game?
:D
That logic is fallacious, even if the observable universe is a "simulation", then this simulation runs inside a real universe, and we're at the start again figuring out what the universe is.
Plus I subscribe to another logic: if the universe is similar to a video game, then it's because as video games increase in complexity they start to approach the model of a little universe
And ask anyone what they remember from the first, and it'll be Johnny Depp's character and the humour, not the special effects.
That's funny since I also remember the effects AND Johny Depp's performance AND the humor.
You guys are oversimplifying everything. "It's not about the effects!", breaking news: it's ALSO about the effects, it's about everything in a careful balance, that, if done properly is called "a good movie".
It's not as if they had effects, they had to have crappy script, it just happens so that when movies get involved, they try to stick everything to simple "secure" models just like you're doing here in your reviews.
Now this site in particular, is on ILM's site. ILM don't make movie scripts, they make effects. Don't bash them for showcasing their (amazing, in my opinion) work and willing to market themselves and their incredible skills in this area.
Look at the site as an achievement of arts and technology and forget the script.
I for one, really respect ILM for their hard work on this movie and just consider how fast CGI technologies are evolving: I mean they did THIS all with the raw footage from the film (mocap, camera tracking: all done on the spot, no additional footage).
Also managing all those little details in the character models looks like a hyper impossible tasks to me: but they pulled it off and pulled it off for an incredible amount of shots in the movie with consistent success. I applaud them for their participation in this project.
Dynamic, arbitrary conversion: I can declare an object's conversion to another format that is automatically called when it is needed in that context. I can create a number subclass that will know to call itself "4" in a numeric context and "IV" in a string context.
:colors".
:P
:shapes]" is equivalent to "has_many :colors, :shapes"
... ...
PHP has the same so you can make a class "visible" as string, iterator etc.
Optional parenthesis: "has_many(:colors)" is equivalent to "has_many
Uhmm.. I'm missing your point here. Does optional parens make a huge difference in your life as a developer?
There you go: $a = (2+3); the parens are optional!
Functions with arbitrary parameter length: "has_many [:colors,
PHP has that too. You can get arbitrary (unknown in advance) number of arguments inside the function and process them. I'm not a fan of that feature however.
People overuse this functionality to create a complete mess of "arbitrary parameters", when all they want is signature overloading.
Iterators and Blocks: Rather than "for( i =0; i
Gee, Ruby has invented iterators!
In PHP this is: foreach ($members as $x)
In JavaScript even, it is: for (x in members)
Does it hurt knowing you rediscovered hot water there?
Messages: Rather than call a function to send a message. This allows Duck Typing,which allows refactoring impossible in other languages.
Hehehe, you know I've heard and seen lots of stories about Ruby refactoring. I have a friend, who after lots of fight confessed that Ruby encourages refactoring for refactoring's sake: just to make your incredible syntax look a bit tiny easier and more "natural"..
Well here's what: why Ruby devs are busy molding their own "languages" we've decided on a language and and use OOP features to mold our natural interfaces to the systems we create.
Ruby is trying to go that extra step of reinventing its own syntax for every project, and that's a step noone needs.
Actually the "$name" is optional, PHP classes know very well what they are named.
Oh I see, you're afraid of language syntax. The "array" bit is a framework oddity of the sample you used. So we arrive at the core of the issue: The quotes! 'Membership' will NEVER feel as natural as memberships!
What was I thinking, I drop everything and become a Rails developer. Never mind all the "side effects" and global crap Ruby has to support its "magic", all it matters is we avoid those quotes and dollar signs with the cost of our lives.
You have Java, .NET, and PHP. I make more money. Enjoy them.
This, just like everything you said is a bunch of unsubstantiated assumptions you spew left and right in attempt to hit a weak spot.
I don't expect different from a Rails fan. You're all blind.
The answer is so simple: because it's fashionable.
How does a fashion start? That's a tough question. For the first this, you gotta be everywhere, in the face of people every day. Microsoft is.
They are a commercial company and free software is mostly supported by young idealists (yes, I'll completely ignore the commercialization of OSS for this example), which are naturally opposed to a leading commercial company competing with their work.
Around the antitrust cases, the OSS community, the forums, the mishaps: a seed forms that quickly grows into a subculture where it's fashionable to loudly demonstrate how and why you hate Microsoft.
Of course there are legitimate reasons to not like Microsoft, but there are legitimate reasons to not like anything at all.
To end how I started, the verdict why people hate Microsoft: because it's fashionable.
Seriously, any employer that asks for a code sample has no clue what they're doing. They should put you at a whiteboard with a pen and have you write something on the fly.
:(
You know, after so much typing, I don't know how to write
So has a popular web comic. [penny-arcade.com]
.NET or PHP. And you have vi. Enjoy it.
In fact one of the cases I've looked into was penny arcade, which after switching to Rails were plagued by performance issues.
And with Rails, I don't need an IDE. For a while, I developed in vi.
You know that basically says it all. You develop in vi. How marvelous. You can develop anything in vi, but when your project grows and you work in a team, you suddenly appreciate the myriad of (probably irrelevant for you) features that makes your life easier:
- integration with version control systems (SVN for me), for updating, committing, resolving conflicts and so on directly from the editor
- interactive debugging (breakpoints, step in/over/out etc, watches)
- "intellisense" or "autocomplete" so that you see instant feedback for the classes, methods and arguments that you have to use, which your team mates created as a part of a larger ecosystems (of course maybe switching out of vi and constantly consulting the source code of the entire repo for API specifics is much easier than instant feedback?)
- instant feedback on syntax and logical errors while you're typing the code (so you don't have to keep refreshing a browser only to see a basic error, like a syntax error)
I use this when I code in Java,
Oh, it's *opinionated*, certainly.
It does NOT appreciate you trying to do anything but a Web2.0 app, with forward generation of a db schema on MySQL. It absolutely, positively despises you trying to use an existing db schema, or to interoperate with anything resembling a J2EE app.
However, if you are willing to play by its rules, it rewards the novice. I say "Rails", and not "RoR" and not "Ruby", because I consider "Rails" to be an entirely distinct idiom from Ruby. Ruby is a language for Computer Scientists, in the sense that ML, Lisp, and Prolog are.
Rails is something different. I don't like arguing about it though. There's not a developer who I would consider competent, who could not produce a webapp within, say, four hours of working through the first demo.
Congratulations, you've been brainwashed. No you successfully apply cliche excuses when confronted with Rails disadvantages (hey it doesn't work with anything since it's *opinionated*! yei!), and ignore the tens of other frameworks which have the same features Rails has (and more), like CakePHP on PHP, Django on Python and so on. They have the SAME features and approach dude. Sorry to burst your bubble, Rails is just a lot of hype and a bunch of brainwashed fans defending it on the various forums.
A technology like Rails threatens to make "programmers" obsolete, at least in certain segments of the killer-app domain that is "webapps."
I feel as threatened by Rails making me obsolete, as I do feel threatened by Lego Logo.
People who were never able to write programs in, say, CGI, PHP, or servlets/JSP, are writing Rails apps without much difficulty.
Thanks for the propaganda, but I'd like to see actual examples to acknowledge this as anything other than completley disconnected from reality BS.
It's a lot easier to start with PHP, especially for people who never coded before, or you think MVC, ActiveRecord, routing, scaffolding and so on is far easier than the learning curve PHP offers.
Rails enables this, and it is doing so rather effectively, for those who discover it. That's a pretty scary thing for a J2EE developer to witness.
Hahahaha! Dude, how can you compare J2EE development with home-made Rails applications!? Are you from this planet?
Jesus, well let's hope those "enabled" by Rails people never have to suffer more than mild traffic to their sites, since it's about what RoR can handle anyways.
Your post is full of the same kind of hype propaganda that completely surrounds Ruby on Rails. One reason I hate it so much: don't mislead people about what RoR is, it'll all bite you back so hard you won't have time to react.