Ruby on Rails has a mapping layer. It's just not used by default ("convention over configuration"). You can specify that an ActiveRecord is made up of all sorts of different non-default things. It's just rare at this point, because people are mostly using it for "green field," from-scratch, new project development.
Now you can argue that since the mapping layer is in the code (with statements like "set_table_name:some_table"), that you lose the flexibility of having everything abstracted out in an XML file.
I prefer to look at it as: 1. I don't have to edit a bunch of XML files. 2. It's not like i have to recompile after editing a source file, so who cares?
The real statistical argument is the one based on conditional probability: if intelligent life had not evolved, we would not be here to ask these questions. The probability of intelligent life evolving, given that we are here, is 1.
That only holds if evolution is the only method by which life may arise. If there are other methods, then you must use relative conditional probabilities. If you know that there is another method, but you cannot reasonably assign a probability to it, then that throws a monkey wrench in the whole works. The probability of intellegent life evolving is then *undefined.*
ASP.net -- Some good ideas, but I like the OSS paradigm too much to go back to proprietary stuff.
perl, PHP -- Great for small to mid-range stuff. Both excel at library support. Perl with CPAN, PHP with the many built-in functions (yes, they're unorganized, get over it) and third-party modules available. But they don't naturally lend themselves to disciplined structure that a large app requires. I started to feel the stress at around 20k lines in my last web app.
I'm not sure I can put C and agile in the same sentence. Wow, I just did.
Java -- All around great once you get up to speed, but man do you have to learn a lot. If you're using a pretty standard "lightweight" stack, you might have to be intimately familiar with Hibernate, Spring, and Struts, all of which have a huge variety of configuration options, gotchas, etc. You try to simplify with AOP tools, and more gotchas. It feels like there's too much software to keep track of.
Ruby on Rails -- feels halfway between Java and PHP. You get the benefits of that huge Java stack, with more unity and cooperation (and all of the docs in the same place!). The language is very flexible. I'm definitely working it into my smaller web projects, and every time it works, then I feel comfortable using it on a bit larger project. Once I got past the gotchas, I became about 50-100% more productive than with PHP.
Downside to Rails is the lack of thrid-party libraries, when compared to perl, PHP, or Java. And since we're talking about large projects, its unproven when it comes to scaling. DHH argues that it's boring to scale with rails.
I have a large web project coming up, and at this point I intend to use Rails for it. I'm going to have to drop out into C, or maybe use web-services RPCs for some of the heavy stuff (notably PDF generation). But I anticipate that the productivity will outweigh the cons.
Re:I argued about increased business and royalty
on
The Case for Free WiFi?
·
· Score: 5, Informative
That's why my favorite coffee shop has some couches and tables designated as study-free zones. If an employee walks by and you have a laptop or textbook out, you'll be kindly asked to move.
The exploit was not in PHP, it was in some software that's coded in PHP. Using your thinking, that's like saying C is a horrible language because if you don't know what you're doing, there's a chance of a buffer overflow.
People criticize C all the time for not protecting from buffer overflows. There are libraries dedicated to wrapping string handling in a way that doesn't allow buffer overflows.
You could apply the same criticism to PHP for allowing SQL injection attacks. PHP lets you input any old SQL, without prepared statements.
There's some good in having a language that protects you from yourself. I don't think protection always needs to be in the language core, but it can be a good thing.
I use BT to download the Fedora ISOs that are currently taking forever on my 2-bit DSL connection? Nah, what am I talking about? Bandwidth wouldn't help.
or does the patent seem to emphasize that the mount takes place in a "cavity." All potential puns aside, the PodBuddy does not has said cavity, from which all other claims derive. It should be open and shut.
While the search space may branch more quickly in Go, relative to chess, this is not the primary source of the difficulty of Go. The primary reason why Go is hard is that the results of any move are not fully apparent until the distant future.
A blunder in chess will typically result in a loss of material or a significant measurable disadvantage within five moves or less, and often on the very next move. A blunder in Go may only become apparent forty moves later. Forty moves is well beyond the limits of current technology.
A possible side effect of this (just conjecture), is that it is also much harder to measure the effects of sacrificial moves in Go.
Re:The end of Standardization = good?
on
Fab
·
· Score: 1
Do you think anyone would actually repair anything? I would hope that there's a universal garbage disposal that disassembles whatever you've fabbed into raw materials, and then you'd start over.
If things went to court, it should be fairly easy to obtain a copy of the forged electronic document and look for added junk.
Lets imagine a more devious employer. What if the junk was on the legitimate document? The employer has you sign the one with junk, and then when it goes to court, the employer claims that YOU generated a hash collision to write yourself an easier/better contract.
It works both ways. The junk could be on either document, and both parties have motives to forge a document.
Slashdot Mirror
Ruby on Rails has a mapping layer. It's just not used by default ("convention over configuration").
:some_table"), that you lose the flexibility of having everything abstracted out in an XML file.
You can specify that an ActiveRecord is made up of all sorts of different non-default things. It's just rare at this point, because people are mostly using it for "green field," from-scratch, new project development.
Now you can argue that since the mapping layer is in the code (with statements like "set_table_name
I prefer to look at it as:
1. I don't have to edit a bunch of XML files.
2. It's not like i have to recompile after editing a source file, so who cares?
The real statistical argument is the one based on conditional probability: if intelligent life had not evolved, we would not be here to ask these questions. The probability of intelligent life evolving, given that we are here, is 1.
That only holds if evolution is the only method by which life may arise. If there are other methods, then you must use relative conditional probabilities. If you know that there is another method, but you cannot reasonably assign a probability to it, then that throws a monkey wrench in the whole works. The probability of intellegent life evolving is then *undefined.*
That *might* work to reduce rendering time depending on the engine. Some engines are slow with innerHTML calls, so it could be a wash.
Most of the slowness with a page refresh is typically network latency and bandwidth bottlenecks. Browser tricks won't help with that.
Maybe someone will enlighten me.
ASP.net -- Some good ideas, but I like the OSS paradigm too much to go back to proprietary stuff.
perl, PHP -- Great for small to mid-range stuff. Both excel at library support. Perl with CPAN, PHP with the many built-in functions (yes, they're unorganized, get over it) and third-party modules available. But they don't naturally lend themselves to disciplined structure that a large app requires. I started to feel the stress at around 20k lines in my last web app.
I'm not sure I can put C and agile in the same sentence. Wow, I just did.
Java -- All around great once you get up to speed, but man do you have to learn a lot. If you're using a pretty standard "lightweight" stack, you might have to be intimately familiar with Hibernate, Spring, and Struts, all of which have a huge variety of configuration options, gotchas, etc. You try to simplify with AOP tools, and more gotchas. It feels like there's too much software to keep track of.
Ruby on Rails -- feels halfway between Java and PHP. You get the benefits of that huge Java stack, with more unity and cooperation (and all of the docs in the same place!). The language is very flexible. I'm definitely working it into my smaller web projects, and every time it works, then I feel comfortable using it on a bit larger project. Once I got past the gotchas, I became about 50-100% more productive than with PHP.
Downside to Rails is the lack of thrid-party libraries, when compared to perl, PHP, or Java. And since we're talking about large projects, its unproven when it comes to scaling. DHH argues that it's boring to scale with rails.
I have a large web project coming up, and at this point I intend to use Rails for it. I'm going to have to drop out into C, or maybe use web-services RPCs for some of the heavy stuff (notably PDF generation). But I anticipate that the productivity will outweigh the cons.
That's why my favorite coffee shop has some couches and tables designated as study-free zones. If an employee walks by and you have a laptop or textbook out, you'll be kindly asked to move.
I think this works out well for everyone.
I'd be pissed if someone came into my house and used my wireless.
Oh wait... He didn't go into the house.
in Libraries of Congress?
Is "grizzly bear" the future of arbitrary units? Live at 10: Netcraft confirms Libraries of Congress is dead!
So, what you are saying is that English is like PHP....
*zing*
The exploit was not in PHP, it was in some software that's coded in PHP. Using your thinking, that's like saying C is a horrible language because if you don't know what you're doing, there's a chance of a buffer overflow.
People criticize C all the time for not protecting from buffer overflows. There are libraries dedicated to wrapping string handling in a way that doesn't allow buffer overflows.
You could apply the same criticism to PHP for allowing SQL injection attacks. PHP lets you input any old SQL, without prepared statements.
There's some good in having a language that protects you from yourself. I don't think protection always needs to be in the language core, but it can be a good thing.
I use BT to download the Fedora ISOs that are currently taking forever on my 2-bit DSL connection? Nah, what am I talking about? Bandwidth wouldn't help.
or does the patent seem to emphasize that the mount takes place in a "cavity." All potential puns aside, the PodBuddy does not has said cavity, from which all other claims derive. It should be open and shut.
While the search space may branch more quickly in Go, relative to chess, this is not the primary source of the difficulty of Go. The primary reason why Go is hard is that the results of any move are not fully apparent until the distant future.
A blunder in chess will typically result in a loss of material or a significant measurable disadvantage within five moves or less, and often on the very next move. A blunder in Go may only become apparent forty moves later. Forty moves is well beyond the limits of current technology.
A possible side effect of this (just conjecture), is that it is also much harder to measure the effects of sacrificial moves in Go.
"look into the matter" ... I get it!!
> particular combination of all of them
So if you have 19 of 20 features, then you aren't copying the invention? Surely Apple missed a feature somewhere.
You can use YubNub directly!
a llation
Add YubNub to your Firefox address bar by going to about:config and changing keyword.URL to http://yubnub.org/parser/parse?command=
Plugin/toolbar info here:
http://www.yubnub.org/documentation/describe_inst
Do you think anyone would actually repair anything? I would hope that there's a universal garbage disposal that disassembles whatever you've fabbed into raw materials, and then you'd start over.
There are companies selling software that let you use webcams as barcode readers.
Wait, how did the current Chinese government get into power?
Radio waves were not invented, they were predicted by Maxwell and discovered by Hertz.
Let's see.
American Revolution
French Revolution
Mexican Revolution
Russion Revolution
umm...
Pick a country, and they've had a revolution or several.
If things went to court, it should be fairly easy to obtain a copy of the forged electronic document and look for added junk.
Lets imagine a more devious employer. What if the junk was on the legitimate document? The employer has you sign the one with junk, and then when it goes to court, the employer claims that YOU generated a hash collision to write yourself an easier/better contract.
It works both ways. The junk could be on either document, and both parties have motives to forge a document.
SELECT * FROM files WHERE label=null
There is more to radio astronomy than the search for other life in the universe. There is more to..
What's your market capitalization? ...That's what I thought.
Apparently you've never heard of the Golden Rule: "He who has the gold, makes the rules."