The creator of Rails has expressed regret for that video, because it gives people the impression that CRUD generation is the most important feature of RoR.
99% of the J2EE work I've seen doesn't require high-performance, low latency distributed messaging engines. That's the edge case that Rails doesn't and can't handle right now. If JRuby ever progresses, it will get that. (I wonder if we could bolt a messenger framework to a Rails app, open sockets maybe?)
Speaking of edge cases, Hibernate still kicks ActiveRecord's ass.
For those of us who live in that 99% of projects that don't require those edge cases (or can drop down to SQL when AR doesn't hold up), there's a lot of productivity and elegance to the Rails community's projects.
Have you seen Migrations? Things like that are a delight to code with. In the same vein, check out the config for URL mapping if you've ever been frustrated by web.xml. Tag libs and filters, features I appreciated when going from PHP to Java in 2001 are more straightforward in Rails.
In the Java world I was already convinced that Hibernate/Spring was the way to go, and wanted to avoid EJB's as much as I could. I've worked with them, and they're f&*()g messy, barely testable, slow abominations. In Rails, I've got all the features I wanted to deal with in J2EE... so far, no regrets.
But speaking of edge cases and awesomeness... have you played at all with Ruby (not Rails)? There's been a few times I've done thing in Ruby I simply couldn't have in Java, thinking "Fuck, I always wondered why it was so complicated".
Again, please keep in mind that rails is a lot more than CRUD generation. That's only a tiny part of it!
I'm well aware of efforts to get Ruby running on the JVM, and the capacities of the J2EE stack. But you can go on ignoring what Rails really is about, that's just fewer of us working with productive tools;)
Considering I have fewer lines of code than I had configuration files, I'd say this is way more maintainable. And fewer LOC's usually means fewer bugs, therefore less maintenance.
Oh, and Rails is about much more than rapid CRUD. Although scaffolding (the automatic generation of CRUD pages for a table) is damned handy in some cases, it's expected you'll replace most of it for any non-trivial application.
But as for TCO, and startup costs. If you're starting a company based on software, would you rather
A: Spend 1-200 hours building something to see if there's a market knowing you'll have to rewrite the whole thing B: Spend 500 hours doing it "right" and then realizing you either have no demand, or people didn't want the features you put in
Ok, that's not much of a choice is it? All that pre-planning stuff is premature optimization. If you can build it fast AND CLEAN, you'll be able to fix it. Most importantly, you'll still be in the game.
The traditional role was selling products and/or services. If branding was the entire value of advertising, no one would advertise. "Hey, everyone knows who we are, and no one wants to buy!"
This will even out. If your conversion rate was 2%, you should be willing to spend 50 times more in CPA. If you're not, your competitor will.
Bottom line: this should help boost confidence amongst advertisers, and result in more, not less revenues for most. The spammers and click-frauders will lose.
RTFA already. We're talking 7 tumours with 2 that were not benign. Not exactly little ailments.
Australian Medical Association president Mukesh Haikerwal said there was no proof of a connection but "if you get clusters of disease it's sensible to investigate."
Maybe these people's cancers are psychological in origin, maybe it's the radiation - was the tower's radiation level too high!? - or maybe it's the building off-gasing, or maybe they all do drugs in that faculty. But hey mate, jumping to conclusions to suggest the first is a fun way to show your techo-elitism.
Googling "PHP JVM", my second hit was Caucho Resin adds PHP: "Caucho, the company behind the open source application server Resin and the open Web Services protocols Burlap and Hessian, has recently added PHP to its list of supported features. Apparently, the PHP pages are compiled in the background to byte-code, and the resulting performance is six times that of Apache mod_php!"
Being able to call some of the Java libraries from PHP or even Ruby would be pretty nifty; there's some really top-notch stuff that has been developed in Java.
See, the thing that bugs me is that every time Google modifies its logo, you can click on it to get to a search page- and the folks who are at the top of that page tend to deal with a google-dot effect that makes slashdot look puny.
It's free publicity on a massive scale. So if they were selfish or greedy, they'd just accept it. But they're fuckwits who can't understand someone just offered them a huge gift, and they threaten to sue instead.
I wish they were selfish, because they'd be far more predictable. This is just utterly stupid.
Wow, if Greenpeace is receiving some cash from the Oil industry, all greens must obviously be doing the petro-elite's bidding when they blabber on about climate change.
It is such a shame that not only nuclear doesn't receive any funding at ALL from the government, they also have to contend with onerous rules. When will we finally give nuclear an equal footing with say, wind? Right now, wind is growing steadily, with the same market-distorting subsidies as the government gives to oil and gas. Nuclear could be growing 20 or 30% a year too!
As it is, our landscapes will be blighted with turbines as wind goes down in price to 2 or 3 cents per kWh. We could have done better 50 years ago if it weren't for the NIMBY grannies and Luddites of this world.
Well, isn't it it great to see brilliant scientists like that attempt to do the cautious thing and save lives in the process.
Of course, if they're wrong, they'll have the satisfaction of knowing they were doing their scientific duty. If they're right it won't matter anyways, because the rest of the world will have found profitable ways to make our economies less carbon-intensive.
That's $6 Billion saved per aircraft carrier, over a supposed 50 year lifetime. These people obviously haven't heard of accounting concepts such as net present value, so for the sake of the argument, let's see how much we'd save by not building these.
Carrier: $4 Billion Cost of 1200 staff saved over 50 years: $6 Billion Cost of remaining 800 staff in same period: $4 Billion.
So, scrapping the program saves $8 Billion *per* carrier. 8 * 3 carriers = $24 Billion. Still a bargain compared to the $42 Billion it would have cost.
But dear God/Allah/Thor, we could buy a whole lot more security for $24 Billion.
Yeah, I really see no difference between the good ol' pico and this newfangled gmail.
Check the Web 2.0 DNA stuff. There's a lot of hype, but some real advances in there as well. two-point-oh is cringe-worthy, but we need some way to label all this newish stuff.
A CRITICAL piece of this is whether they will also roll out free wifi access to the internet. Without that I'll go ahead and predict dismal failure right now. The only way this could become a world changing phenomenon if if they also come with free internet access.
Even better: the plan is for them to become nodes of a wireless mesh network.
The first countries to have more cellphones than landlines were African. I don't for a second doubt that wireless is going to be the cheapest way to deliver internet connectivity too.
Rails is a web framework. Ruby is a solid choice for scripting, with less of a wonky syntax than Perl.
I haven't done much desktop GUI work to say much of worth in that area, but Tk is included with the main Ruby distribution, and there are other bindings available. In any case, Ruby is bound to be far more productive than C.
So basically, in your position it would boil down to the engineers I could attract. How about you just try posting an ad on Craigslist for an engineer with Ruby (and GUI experience specifically), and see if you are more satisfied with the responses? Check out Paul Graham's essays The Python Paradox and Revenge of the Nerds. Do tell me how your experiment goes if you decide to try it:)
"Candidates should be highly motivated, possess strong development skills, follow design trends, and keep updated and aware of ways to improve your skill set."
You want amazing, ridiculously overqualified programmers? Advertise you are hiring a Ruby/Rails programmer instead.
And yes, convert your shop. Get a great engineer with Rails experience, and transform your shop.
Or maybe you just want to be a PHB that asks their staff follow trends without actually letting them use all that new technology they learn about? That's how your ad reads to me.
BusinessWeek is so last year, so, so... so one-point-oh. (I kid, I kid!)
The "hip" thing for ex-Java folks is not LAMP but Ruby on Rails. When Bruce Tate wrote Beyond Java, it seemed it was time to check it out- and after doing so I have to say he's on to something.
Seriously, if you like the whole direction of Spring / Hibernate / JUnit, you owe it to yourself to check out RoR. The speed and joy of LAMP with the architecture and cleanliness of the best Java solutions.
What I find ironic is how often people who don't trust the fossil fuel industry, and claim not to believe anything they say, etc. have been taken in by the anti-nuclear FUD spread by the very people they claim to distrust.
It's like some bad comedy routine.
What I find ironic is every time there's a global warming story we hear the same refrain about nukes and how they can save us. And that so many assume we're complete morons if we don't agree.
I've got news for you: I don't trust the oil and gas crowd, and I don't trust the "too cheap to meter" promises either. We have cheaper, better alternatives.
But that's OK, you can go on with the ad-hominem- implying we're too stupid and/or naive- and skirt the real issues with nuclear energy as well as ignore the alternatives.
Facts don't need to bother you. This is/. after all.
"Besides sending this to my supervisor, is there anything else I can do for you?"
"I want this problem dealt with NOW."
Let me be clear: I hear that ALL the time. I deal with everything from account inquiries / trouble shooting to life-critical apps. For the record, I do level I work but unsupervised night-shift (some L2 responsibilties) and deal with fuels. Yeah, explosive stuff.
If you have a dangerous situation, I have full authority to do whatever it takes to get you help. If you're arguing, it's because you either want to stop help from getting there ASAP or that you really think I have the authority to do the accounting department's work (refund / rebilling), or can authorize a change in price (supervisor).
Seriously, if a level I rep can't help you, you're just being obnoxious by staying on the line. There's efficient ways to get much better deals out of most corporations, but alienating L1 reps is not one of them. And we get in trouble if we hang up first. So quit doing it.
Pergatory? There's another obviously horrid mistake in the blurb, which was supposedly edited by a human. [Did the editing get outsourced or something? No can't be india... I guess none of it is actually done.]
And that is one reason I am starting to dislike "customer service". You get lots of utterly ignorant people, and the ones that can't read or write are often the ones that can't understand the spoken word. "I can't help you right now, I will have to ask my supervisor to look at your situation and call you back in the morning" Conversation should be OVER, save a few niceties. Quit arguing with me, it's just killing my stats. I can't help you, bitch/fuckwit.
So I just imagine the pain of those in their organizational silos, getting people that insisted on talking to the wrong person. It's their job performance that suffers- all the stats for incoming and outgoing calls are recorded. The more out calls, and the longer the calls, the more likely you are to get canned. Plus, I get to have a person on hold while I'm on hold with another department. WTF? Misery insists on having company to listen to elevator music.
If you're pissed off about a phone menu, don't make the reps suffer. Tell them politely, or better yet, write a letter about it. Take your business elsewhere if you hear of better service.
But for the love of #random deity# just press the buttons and be nice to the rep.
Slashdot Mirror
The creator of Rails has expressed regret for that video, because it gives people the impression that CRUD generation is the most important feature of RoR. 99% of the J2EE work I've seen doesn't require high-performance, low latency distributed messaging engines. That's the edge case that Rails doesn't and can't handle right now. If JRuby ever progresses, it will get that. (I wonder if we could bolt a messenger framework to a Rails app, open sockets maybe?) Speaking of edge cases, Hibernate still kicks ActiveRecord's ass. For those of us who live in that 99% of projects that don't require those edge cases (or can drop down to SQL when AR doesn't hold up), there's a lot of productivity and elegance to the Rails community's projects. Have you seen Migrations? Things like that are a delight to code with. In the same vein, check out the config for URL mapping if you've ever been frustrated by web.xml. Tag libs and filters, features I appreciated when going from PHP to Java in 2001 are more straightforward in Rails. In the Java world I was already convinced that Hibernate/Spring was the way to go, and wanted to avoid EJB's as much as I could. I've worked with them, and they're f&*()g messy, barely testable, slow abominations. In Rails, I've got all the features I wanted to deal with in J2EE... so far, no regrets. But speaking of edge cases and awesomeness... have you played at all with Ruby (not Rails)? There's been a few times I've done thing in Ruby I simply couldn't have in Java, thinking "Fuck, I always wondered why it was so complicated".
Again, please keep in mind that rails is a lot more than CRUD generation. That's only a tiny part of it! I'm well aware of efforts to get Ruby running on the JVM, and the capacities of the J2EE stack. But you can go on ignoring what Rails really is about, that's just fewer of us working with productive tools ;)
Considering I have fewer lines of code than I had configuration files, I'd say this is way more maintainable. And fewer LOC's usually means fewer bugs, therefore less maintenance.
Oh, and Rails is about much more than rapid CRUD. Although scaffolding (the automatic generation of CRUD pages for a table) is damned handy in some cases, it's expected you'll replace most of it for any non-trivial application.
But as for TCO, and startup costs. If you're starting a company based on software, would you rather
A: Spend 1-200 hours building something to see if there's a market knowing you'll have to rewrite the whole thing
B: Spend 500 hours doing it "right" and then realizing you either have no demand, or people didn't want the features you put in
Ok, that's not much of a choice is it? All that pre-planning stuff is premature optimization. If you can build it fast AND CLEAN, you'll be able to fix it. Most importantly, you'll still be in the game.
The traditional role was selling products and/or services. If branding was the entire value of advertising, no one would advertise. "Hey, everyone knows who we are, and no one wants to buy!" This will even out. If your conversion rate was 2%, you should be willing to spend 50 times more in CPA. If you're not, your competitor will. Bottom line: this should help boost confidence amongst advertisers, and result in more, not less revenues for most. The spammers and click-frauders will lose.
If you under-report your conversion rate, Google makes less money and shows fewer of your ads. A pretty silly way to save money.
the French probably covered it up.Learn to use Google or STFU, connard.
Googling "PHP JVM", my second hit was Caucho Resin adds PHP: "Caucho, the company behind the open source application server Resin and the open Web Services protocols Burlap and Hessian, has recently added PHP to its list of supported features. Apparently, the PHP pages are compiled in the background to byte-code, and the resulting performance is six times that of Apache mod_php!"
Being able to call some of the Java libraries from PHP or even Ruby would be pretty nifty; there's some really top-notch stuff that has been developed in Java.
See, the thing that bugs me is that every time Google modifies its logo, you can click on it to get to a search page- and the folks who are at the top of that page tend to deal with a google-dot effect that makes slashdot look puny.
It's free publicity on a massive scale. So if they were selfish or greedy, they'd just accept it. But they're fuckwits who can't understand someone just offered them a huge gift, and they threaten to sue instead.
I wish they were selfish, because they'd be far more predictable. This is just utterly stupid.
Wow, if Greenpeace is receiving some cash from the Oil industry, all greens must obviously be doing the petro-elite's bidding when they blabber on about climate change.
It is such a shame that not only nuclear doesn't receive any funding at ALL from the government, they also have to contend with onerous rules. When will we finally give nuclear an equal footing with say, wind? Right now, wind is growing steadily, with the same market-distorting subsidies as the government gives to oil and gas. Nuclear could be growing 20 or 30% a year too!
As it is, our landscapes will be blighted with turbines as wind goes down in price to 2 or 3 cents per kWh. We could have done better 50 years ago if it weren't for the NIMBY grannies and Luddites of this world.
Well, isn't it it great to see brilliant scientists like that attempt to do the cautious thing and save lives in the process.
Of course, if they're wrong, they'll have the satisfaction of knowing they were doing their scientific duty. If they're right it won't matter anyways, because the rest of the world will have found profitable ways to make our economies less carbon-intensive.
"We have had efficent and safe nuclear power since the 1950s"
And too cheap to meter too. Construction always on schedule and under budget, vastly cheaper than any other type of type of power generation.
Unlike coal, oil and natural gas, nuclear hasn't even benefited from state subsidies.
Those environmentalists are some strong, they must be in it with the Freemasons.
That's $6 Billion saved per aircraft carrier, over a supposed 50 year lifetime. These people obviously haven't heard of accounting concepts such as net present value, so for the sake of the argument, let's see how much we'd save by not building these.
Carrier: $4 Billion
Cost of 1200 staff saved over 50 years: $6 Billion
Cost of remaining 800 staff in same period: $4 Billion.
So, scrapping the program saves $8 Billion *per* carrier. 8 * 3 carriers = $24 Billion. Still a bargain compared to the $42 Billion it would have cost.
But dear God/Allah/Thor, we could buy a whole lot more security for $24 Billion.
A few people felt the same way, and would pay $300 for it
Yeah, I really see no difference between the good ol' pico and this newfangled gmail.
Check the Web 2.0 DNA stuff. There's a lot of hype, but some real advances in there as well. two-point-oh is cringe-worthy, but we need some way to label all this newish stuff.
That must have been heavy as hell... and were if the bullet ever went through, would it carry bits of glass with it?
Sure, people could share files, and email the link.
In practice, offices don't do that. It'll be easier for the PHB to have it explained that you can do this in a browser than how to turn on sharing.
The first countries to have more cellphones than landlines were African. I don't for a second doubt that wireless is going to be the cheapest way to deliver internet connectivity too.
Please take a second to sign the pledge to buy one of these laptops at $300. Thanks!
There are a lot more Ruby developers than Ruby jobs.
And they tend to be better developers too, those that enjoy hacking and being productive.
Rails is a web framework. Ruby is a solid choice for scripting, with less of a wonky syntax than Perl.
:)
I haven't done much desktop GUI work to say much of worth in that area, but Tk is included with the main Ruby distribution, and there are other bindings available. In any case, Ruby is bound to be far more productive than C.
So basically, in your position it would boil down to the engineers I could attract. How about you just try posting an ad on Craigslist for an engineer with Ruby (and GUI experience specifically), and see if you are more satisfied with the responses? Check out Paul Graham's essays The Python Paradox and Revenge of the Nerds. Do tell me how your experiment goes if you decide to try it
From the job description:
"Candidates should be highly motivated, possess strong development skills, follow design trends, and keep updated and aware of ways to improve your skill set."
You want amazing, ridiculously overqualified programmers? Advertise you are hiring a Ruby/Rails programmer instead.
And yes, convert your shop. Get a great engineer with Rails experience, and transform your shop.
Or maybe you just want to be a PHB that asks their staff follow trends without actually letting them use all that new technology they learn about? That's how your ad reads to me.
BusinessWeek is so last year, so, so... so one-point-oh. (I kid, I kid!)
The "hip" thing for ex-Java folks is not LAMP but Ruby on Rails. When Bruce Tate wrote Beyond Java, it seemed it was time to check it out- and after doing so I have to say he's on to something.
Seriously, if you like the whole direction of Spring / Hibernate / JUnit, you owe it to yourself to check out RoR. The speed and joy of LAMP with the architecture and cleanliness of the best Java solutions.
I've got news for you: I don't trust the oil and gas crowd, and I don't trust the "too cheap to meter" promises either. We have cheaper, better alternatives.
But that's OK, you can go on with the ad-hominem- implying we're too stupid and/or naive- and skirt the real issues with nuclear energy as well as ignore the alternatives.
Facts don't need to bother you. This is
"Besides sending this to my supervisor, is there anything else I can do for you?"
"I want this problem dealt with NOW."
Let me be clear: I hear that ALL the time. I deal with everything from account inquiries / trouble shooting to life-critical apps. For the record, I do level I work but unsupervised night-shift (some L2 responsibilties) and deal with fuels. Yeah, explosive stuff.
If you have a dangerous situation, I have full authority to do whatever it takes to get you help. If you're arguing, it's because you either want to stop help from getting there ASAP or that you really think I have the authority to do the accounting department's work (refund / rebilling), or can authorize a change in price (supervisor).
Seriously, if a level I rep can't help you, you're just being obnoxious by staying on the line. There's efficient ways to get much better deals out of most corporations, but alienating L1 reps is not one of them. And we get in trouble if we hang up first. So quit doing it.
Pergatory? There's another obviously horrid mistake in the blurb, which was supposedly edited by a human. [Did the editing get outsourced or something? No can't be india... I guess none of it is actually done.]
And that is one reason I am starting to dislike "customer service". You get lots of utterly ignorant people, and the ones that can't read or write are often the ones that can't understand the spoken word. "I can't help you right now, I will have to ask my supervisor to look at your situation and call you back in the morning" Conversation should be OVER, save a few niceties. Quit arguing with me, it's just killing my stats. I can't help you, bitch/fuckwit.
So I just imagine the pain of those in their organizational silos, getting people that insisted on talking to the wrong person. It's their job performance that suffers- all the stats for incoming and outgoing calls are recorded. The more out calls, and the longer the calls, the more likely you are to get canned. Plus, I get to have a person on hold while I'm on hold with another department. WTF? Misery insists on having company to listen to elevator music.
If you're pissed off about a phone menu, don't make the reps suffer. Tell them politely, or better yet, write a letter about it. Take your business elsewhere if you hear of better service.
But for the love of #random deity# just press the buttons and be nice to the rep.