Why does Asia get all of this Linux mobile technology first? It seems as if most Linux embedded technology either fails to hit the Western world or else it gets withdrawn. Case in point the Sharp Zaurus line of handhelds. cooler than anything, but the only way you can get one in the U.S. is to import one from a company that reprograms them for Western keyboard functions and whatnot.
I know that there have been more than a few bashing threads, so I won't add any fuel to them. Props to the mySQL team for adding significant functionality to their software. Triggers and stored procedures are components that are important in making mySQL a production worthy enterprise level product. The big name companies who have been using mySQL likely were using it for basic heavy select statement stuff where inserting or updating recordsets wasn't part of the equation.
If most of the documented gotchas are addressed in the 5.0 RC then all the more I applaud their efforts. Once serious referential/data integrity is fully delivered I will plan to seriously consider mySQL for my next project. Until then it's PostgreSQL for FOSS and MSSQL Server for other stuff...
I had read somewhere that the PalmOS might move to a Linux base. That would be great since I'm currently working on some Linux-based Qt GUI projects that run on the Sharp Zaurus. If I could port these over to a Tungsten so much the better for getting my sales force to adopt it!
What was the source of this information you "heard?" Also a point of clarification. The Bush policy doesn't approve of embryonic stem cell research, not stem cell research as a whole. Everyone gets so torqued up about this subject they fail to differentiate. There are other areas of stem cell research just as promising that don't involve an embryo...
I know that's a relatively intangible question to quantify but I did find a survey that lists different programming languages used in the workplace. Seems as if C++ definitely isn't dying just yet. I found another seemingly google-based article on the popularity of various programming languages. Sure Java and C# are up there with PHP thrown in as well, but C++ still has lots of current uses. Seeing I am hooked on Ruby in my workplace I am one of the few according to all of these figures:-)
I have read a decent number of articles about cities choosing to adopt Linux but would be more curious to read a follow up story of how the transition went using hindsight, say a month later, a year later, etc. What were the major obstacles and how were they overcome? After the dust settled how does worker productivity and cost effectiveness stand? These sort of facts could help start a domino effect where other IT execs could build cases to present to their respective PHB's in order to make the switch.
Kind of like some of the countless U.S. reality shows where people and houses are made over (e.g. - The Swan, The Biggest Loser, Extreme Home Makeover). Rather than short term focus I'd love to see the shows check in a year later to see how things look. That's more indicative of true success and failure.
a much better database than sql server. Perhaps define "better" so we have an idea of your criteria. In terms of features and functionality SQL Server is light years beyond mySQL. The list of mySQL gotchas is pretty lengthy and the main gotcha I see regarding SQL Server is the fact that it's produced by Microsoft and lots of folks love to hate on them. Maybe morons having a blank sa password leading to the Slammer exploit, but that's hardly a gotcha for a halfwitted DBA...
Check here for a list of groups actively using RoR in production or developing with RoR. I know there are no Yahoo!s, Googles, or Amazons on the list.
As for Ruby offering you nothing that you can't do with Python I would argue that you can do things simpler, more concise, and more logically in Ruby. The code is cleaner so if you are picking up the code for something you developed six months ago things should fall into place easier.
IMHO Ruby == Prettier and more OO than Perl and Ruby == More powerful than Python
I agree with most of these assertions, although I actively use Ruby for more and more of my development code and have moved over several application to Ruby on Rails. There is a "not ready for primetime" feel to it, but it is because it's still an immature product. After all it still hasn't surpassed 1.0 revision status!
For IDE choices I personally use Eclipse with the Ruby plug-in now, although I have used FreeRIDE in the past and some other alternatives (like WideStudio, which is an IDE that is distributed alongside full installations of Ruby, Python, and Perl). If FreeRIDE isn't your cup of tea check out Eclipse. It works for me at least.
And as for the database driver issues there are likely some problems resident in the DBI version that's being used. I personally connect to MSDE and MSSQL instances without issue using RoR 0.9.1.
Let's check in with RoR a year later and see where things stand. I think people are excited but a little prematurely so...
Re:Thanks for the career, PHP!!
on
A Decade of PHP
·
· Score: 1
I have been using Ruby for everything from admin scripts to SQL data transformation/importing to Tk GUI apps. After working with everything from Perl to C++ to Java to VB it was a pleasure to switch over to Ruby. There are lots of bindings available for it and the community is strong. Started using it last November and can't imagine switching back to another language.
Just a month and a half ago I picked up Ruby on Rails and haven't looked back. I haven't used PHP in production apps but have used ASP with VBScript and Javascript. Coming from that background Ruby on Rails is a welcome departure. The MVC concept is great and I was building relatively complex web apps with relative ease. I created an internal purchase order application that integrates with a central fax server, e-mail notification, etc. and can't imagine the pain that I would've endured doing it with ASP.
If you get a chance, read through the Practical Programmer's Guide to Ruby (Second Edition) and The Ruby Way. Those two books will sell you on what Ruby has to offer. It's powerful as Perl but pretty to look at and read through:-)
I wouldn't get on the hatewagon that that degree. As long as they have schema reference documents available your bet would be a losing one. My bet is that certain documents are encoded using technology similar to this. One of my company's software products has file documents based on encoded XML and for certain situations Microsoft could employ something similar.
Ummm, check out the real deal. These are their supposedly "closed API's." The fact that the source code used to build their OS is closed doesn't mean that the programming interfaces to work with their OS are as well. Big difference.
I'm not getting into the fact that Microsoft can/has purposely changed their software in order to break competitor products (or at the least make them look subpar). But it's not like these companies have sat in a dark, closed room for almost a year being totally unable to bring their products up to speed.
Check out a comprehensive listing of third-party products that might have compatibility issues under XPSP2. "Breaking critical software?" Hardly. Almost a full year has gone by to allow the third-party companies time to being their products up to speed so they will function correctly under XPSP2. IMHO that's enough time.
Most of the posts I am reading are contradictory to most the posts I read right after XPSP2 was released. Then the general sentiment was that Microsoft was finally taking steps to secure their OS and sometimes breaking third-party compatibility was a necessary means to that end. Sooner or later a line had to be drawn in the sand and generally folks agreed that it was past due.
Since XPSP2 was released the third-party companies have had adequate time to revise their products to be compatible with XPSP2. And, as I have read on a couple of posts, some of the apparent compatibility issues are resolved by allowing the program executable access through the Windows Firewall. The ones that aren't this simple have had time to bring their products up to speed.
Look how long it's been since XPSP2 has been released for downloading. It's about time it's automatically prompted as a Windows Automatic Update option isn't it? What's the big deal? I support a Windows corporate environment and haven't encountered any BSOD's where the PC's won't even boot up due to installing XPSP2. Methinks a bit of extra FUD on the fire...
Since Ruby is an interpreted language and Java is typically JIT compiled I don't think certain studies stating ROR is faster is a totally resounding victory. But in terms of code being concise, readable, totally OO, etc. I choose Ruby hands-down.
Just check out a handful of the Ruby tutorials and compare the code with Java. I wouldn't use anything else but Ruby now that I've discovered it and have gotten into it...
For anyone interested here are the links to Iomega, to QEMU, and to Damn Small Linux. I got the Iomega used so all of this did wind up costing around $50.
Is an Iomega mini flash USB unit. It's about an inch long, holds 512 MB and is on my keychain. I have QEMU loaded on it so I can run any OS I want as an ISO. For example I have a DamnSmallLinux ISO that I can use to pop right into a Windows box and start up a Linux session without having to reboot the PC. All of this costs about $50.
This line of thinking is (sadly perhaps) dated. I am thinking back in the day when code had to be painstakingly optimized to be stored and executed with minimal hardware resources. Like those video games squeezed into 4 KB of ROM.
Nowadays most of the languages folks use are high level programming types. Newer programmers hardly worry about malloc types of things and the nittty gritty.
This might not be the best way things are evolving, but with the hardware power and resources that are out there it's true.
There is this. I am a Ruby convert as well. I think it's so much cleaner than other scripting languages. Most of it "just makes sense." I personally am not using it not so much as a web app framework as a replacement for my company's plethora of ASP work. Using eRuby on Apache I hope to keep things moving along...
Slashdot Mirror
Why does Asia get all of this Linux mobile technology first? It seems as if most Linux embedded technology either fails to hit the Western world or else it gets withdrawn. Case in point the Sharp Zaurus line of handhelds. cooler than anything, but the only way you can get one in the U.S. is to import one from a company that reprograms them for Western keyboard functions and whatnot.
I know that there have been more than a few bashing threads, so I won't add any fuel to them. Props to the mySQL team for adding significant functionality to their software. Triggers and stored procedures are components that are important in making mySQL a production worthy enterprise level product. The big name companies who have been using mySQL likely were using it for basic heavy select statement stuff where inserting or updating recordsets wasn't part of the equation.
If most of the documented gotchas are addressed in the 5.0 RC then all the more I applaud their efforts. Once serious referential/data integrity is fully delivered I will plan to seriously consider mySQL for my next project. Until then it's PostgreSQL for FOSS and MSSQL Server for other stuff...
I had read somewhere that the PalmOS might move to a Linux base. That would be great since I'm currently working on some Linux-based Qt GUI projects that run on the Sharp Zaurus. If I could port these over to a Tungsten so much the better for getting my sales force to adopt it!
What was the source of this information you "heard?" Also a point of clarification. The Bush policy doesn't approve of embryonic stem cell research, not stem cell research as a whole. Everyone gets so torqued up about this subject they fail to differentiate. There are other areas of stem cell research just as promising that don't involve an embryo...
dammit. :-) J/K
Dear Editors,
The hell what say you? Tell me you will.
Signed,
Yoda
click me FFS!!!
I know that's a relatively intangible question to quantify but I did find a survey that lists different programming languages used in the workplace. Seems as if C++ definitely isn't dying just yet. I found another seemingly google-based article on the popularity of various programming languages. Sure Java and C# are up there with PHP thrown in as well, but C++ still has lots of current uses. Seeing I am hooked on Ruby in my workplace I am one of the few according to all of these figures :-)
Kind of like some of the countless U.S. reality shows where people and houses are made over (e.g. - The Swan, The Biggest Loser, Extreme Home Makeover). Rather than short term focus I'd love to see the shows check in a year later to see how things look. That's more indicative of true success and failure.
a much better database than sql server. Perhaps define "better" so we have an idea of your criteria. In terms of features and functionality SQL Server is light years beyond mySQL. The list of mySQL gotchas is pretty lengthy and the main gotcha I see regarding SQL Server is the fact that it's produced by Microsoft and lots of folks love to hate on them. Maybe morons having a blank sa password leading to the Slammer exploit, but that's hardly a gotcha for a halfwitted DBA...
As for Ruby offering you nothing that you can't do with Python I would argue that you can do things simpler, more concise, and more logically in Ruby. The code is cleaner so if you are picking up the code for something you developed six months ago things should fall into place easier.
IMHO Ruby == Prettier and more OO than Perl and Ruby == More powerful than Python
I agree with most of these assertions, although I actively use Ruby for more and more of my development code and have moved over several application to Ruby on Rails. There is a "not ready for primetime" feel to it, but it is because it's still an immature product. After all it still hasn't surpassed 1.0 revision status!
For IDE choices I personally use Eclipse with the Ruby plug-in now, although I have used FreeRIDE in the past and some other alternatives (like WideStudio, which is an IDE that is distributed alongside full installations of Ruby, Python, and Perl). If FreeRIDE isn't your cup of tea check out Eclipse. It works for me at least.
And as for the database driver issues there are likely some problems resident in the DBI version that's being used. I personally connect to MSDE and MSSQL instances without issue using RoR 0.9.1.
Let's check in with RoR a year later and see where things stand. I think people are excited but a little prematurely so...
I have been using Ruby for everything from admin scripts to SQL data transformation/importing to Tk GUI apps. After working with everything from Perl to C++ to Java to VB it was a pleasure to switch over to Ruby. There are lots of bindings available for it and the community is strong. Started using it last November and can't imagine switching back to another language.
:-)
Just a month and a half ago I picked up Ruby on Rails and haven't looked back. I haven't used PHP in production apps but have used ASP with VBScript and Javascript. Coming from that background Ruby on Rails is a welcome departure. The MVC concept is great and I was building relatively complex web apps with relative ease. I created an internal purchase order application that integrates with a central fax server, e-mail notification, etc. and can't imagine the pain that I would've endured doing it with ASP.
If you get a chance, read through the Practical Programmer's Guide to Ruby (Second Edition) and The Ruby Way. Those two books will sell you on what Ruby has to offer. It's powerful as Perl but pretty to look at and read through
I wouldn't get on the hatewagon that that degree. As long as they have schema reference documents available your bet would be a losing one. My bet is that certain documents are encoded using technology similar to this. One of my company's software products has file documents based on encoded XML and for certain situations Microsoft could employ something similar.
Ummm, check out the real deal. These are their supposedly "closed API's." The fact that the source code used to build their OS is closed doesn't mean that the programming interfaces to work with their OS are as well. Big difference. I'm not getting into the fact that Microsoft can/has purposely changed their software in order to break competitor products (or at the least make them look subpar). But it's not like these companies have sat in a dark, closed room for almost a year being totally unable to bring their products up to speed.
Looking at their documentation it seems in order to me. It clearly states 64-bit Photoshop CS clients.
Check out a comprehensive listing of third-party products that might have compatibility issues under XPSP2. "Breaking critical software?" Hardly. Almost a full year has gone by to allow the third-party companies time to being their products up to speed so they will function correctly under XPSP2. IMHO that's enough time.
Most of the posts I am reading are contradictory to most the posts I read right after XPSP2 was released. Then the general sentiment was that Microsoft was finally taking steps to secure their OS and sometimes breaking third-party compatibility was a necessary means to that end. Sooner or later a line had to be drawn in the sand and generally folks agreed that it was past due.
Since XPSP2 was released the third-party companies have had adequate time to revise their products to be compatible with XPSP2. And, as I have read on a couple of posts, some of the apparent compatibility issues are resolved by allowing the program executable access through the Windows Firewall. The ones that aren't this simple have had time to bring their products up to speed.
Look how long it's been since XPSP2 has been released for downloading. It's about time it's automatically prompted as a Windows Automatic Update option isn't it? What's the big deal? I support a Windows corporate environment and haven't encountered any BSOD's where the PC's won't even boot up due to installing XPSP2. Methinks a bit of extra FUD on the fire...
Since Ruby is an interpreted language and Java is typically JIT compiled I don't think certain studies stating ROR is faster is a totally resounding victory. But in terms of code being concise, readable, totally OO, etc. I choose Ruby hands-down. Just check out a handful of the Ruby tutorials and compare the code with Java. I wouldn't use anything else but Ruby now that I've discovered it and have gotten into it...
I thought using the InnoDB version of mySQL row-level locking is indeed available. This has been the case for awhile IIRC.
Why was this modded down? Certainly not offtopic. And not too much of a troll or flamebait since it's pretty on target (even if a bit abrupt).
For anyone interested here are the links to Iomega, to QEMU, and to Damn Small Linux. I got the Iomega used so all of this did wind up costing around $50.
Is an Iomega mini flash USB unit. It's about an inch long, holds 512 MB and is on my keychain. I have QEMU loaded on it so I can run any OS I want as an ISO. For example I have a DamnSmallLinux ISO that I can use to pop right into a Windows box and start up a Linux session without having to reboot the PC. All of this costs about $50.
This line of thinking is (sadly perhaps) dated. I am thinking back in the day when code had to be painstakingly optimized to be stored and executed with minimal hardware resources. Like those video games squeezed into 4 KB of ROM. Nowadays most of the languages folks use are high level programming types. Newer programmers hardly worry about malloc types of things and the nittty gritty. This might not be the best way things are evolving, but with the hardware power and resources that are out there it's true.
There is this. I am a Ruby convert as well. I think it's so much cleaner than other scripting languages. Most of it "just makes sense." I personally am not using it not so much as a web app framework as a replacement for my company's plethora of ASP work. Using eRuby on Apache I hope to keep things moving along...