You can do anything in 11 lines of Perl.
Clearly, if HealthCare.gov had been written in Perl and still took 500,000,000 lines to do so, it would indicate that they had hired on the team responsible for building [http://www.otrs.com/ OTRS] because...OMG.
DreamWeaver is the worst. No syntax hilighting for Perl. At all.
Forces you to use tabs (instead of spaces). Attempting to choose otherwise will result in a mixture of tabs and spaces.
Even now, after nearly a decade of DreamWeaver, an FTP transfer requires 100% of my CPU. The progress meter is not a progress meter at all.
It doesn't even provide proper autocomplete for JavaScript (not even client-side). Considering how deeply tied to JavaScript the DreamWeaver UI is, this has always bothered me.
Sure, it's better than nothing. But after *this* long under development, I expect a lot more that what we have now.
Seriously, something like this would only play into the idea of "terrorists are attacking us" or "domestic combatants" or whatever.
Microsoft would have to be infiltrated by an operative - and do the evil deed (or public service?) there. I don't think it would be too hard to let just one more bug slip through (that's a joke).
Perhaps hack the Windows Update servers to automatically download the specially-crafted code.
Joomla - written in PHP - is the only item in your list with decent source code. Comments in the code and the use of CVS or SVN are some obvious good points. It still has the HTML-in-the-code problem but 2 out of 3 isn't bad.
vTiger (and SugarCRM) - also written in PHP - both have Terrible performance. Absolutely terrible. I suppose that if you use this software with a database of less than 10,000 customers you might be ok. Searching for bugs actually times out (not a good sign). Something else of note: the SugarCRM developers can't code valid HTML. See for yourself - http://validator.w3.org/check?uri=http%3A%2F%2Fwww .sugarcrm.com
LedgerSMB and SQL-Ledger are seriously some of the worst Perl I have ever seen in the last 10 years.
I wouldn't touch LedgerSMB/SQL-Ledger with a 10 foot pole.
Every Perl programmer worth his/her salt knows that any Perl program or module should begin with:
#!/your/path/to/perl -w use strict; use warnings;
I looked through the source code and although I didn't see any obvious vulnerabilities (i.e. SQL Injection or Cross-Site-Scripting) there are literally hundreds (thousands?) of lines of (poorly coded) HTML scattered throughout the Perl source.
Conventions as old as Perl5 (October of 1994) are completely ignored (clear module hierarchy, stricture, code comments, POD documentation, full test suite, etc.) and will ultimately lead any business built on such shoddy code to peril (or ruin).
The Dieter Simader (coder) and DWS Systems Inc. (company) may have made headlines with this steaming pile back in 1992. However, looking at the source code, it bears a copyright date of 2006. Mr. Dieter Simader appears to have successfully sheltered himself from learning anything new for the last 13 years (and running). Great Job!
Shitty code like *THIS* gives Perl a bad name. I would rather they simply close the download site before another hapless would-be user falls into the trap that is SQL-Ledger/LedgerSMB.
You know that's a good idea.
I know that's a good idea.
Everyone here knows that's a good idea.
Apparently the same person in Redmond responsible for the 1-inch scrollable lists of dozens (sometimes hundreds) of items is also responsible for coming up with ways to prevent viruses from infecting almost-updated Windows installs.
quote:
They just say, "We're in Iraq, we're in Baghdad, and there's a firefight going on, I'll shut up and let you watch it." And being able to see it in wide-screen high resolution with 5.1 sound, if you have a tank firing, you hear it coming out of one ear and see it leaving out of the other ear. It's just incredible. Just to be able to see it like you're actually sitting there is amazing.
----
Yeah, gee that's exactly what we all need. 84 inches of Hi-Def death and dismemberment. Death gurgles in Dolby Digital 5.1.
Wow.
I loved those books, and have been hoping someone would make a movie about them.
The story line is something like Harry Potter meets Pirates of the Carribean.
I thought the third book really tied it all together though, so I hope there are also plans to do that one as well. That one small book could fill an entire feature-length movie script though, so maybe that's why it's not on the list yet.
Though I'm sure someone has already put together such a tree model to explain how fusion creates heavier elements, it would be nice to have, especially in a classroom setting.
I've tried lots of templating schemes with perl-based web development, but Apache::ASP is my favorite so far.
With the XMLsubs, $Request, $Response, $Server, $Application and $Session objects I am able to focus on the task at hand, rather than figuring workarounds to the limitations of the language I am using.
Global variables, cached database connections & queries, shared session-state and full access to the Apache API give you the power to do anything you need to.
Hi! I found this picture that describes in some detail President Bush's plan to raise Iraqi opinion of the USA and help ease tension in the hopes of reducing terrorist threat.
I agree. If a person finds their job dull, maybe they are either:
->> not showing their employer the skills necessary for a more challenging assignment ->> upset about something else, but projecting it on work ->> jealous of a project someone else was assigned ->> the project you are working on has dragged on too long and you are anxious to start something else
->> any combination of the above
I am only speaking out of personal experience here.
Basically, you can create an object of a particular type anyplace that has access to the definition of that object.
Find a bug in that object? No problem...just update your single definition of that object ( the DLL, loadable library, module, etc ).
If every time I wanted to connect to the database or check an MD5 signature, I had to include that code into my project, that would really suck.
Instead of having 1 version of that code, I would now have as many versions as there are programs using it.
If I found a bug after using it in several places, I would have to recompile perhaps dozens of programs that use the same code.
With DLLs and libs, we can make reference to the object defined in the external library, and just use them from anything that _can_ reference them. I find this is very much my preferred method, and the reason people in general prefer to use external libraries when they can.
Imagine actually having to include all the code from CGI.pm, DBI.pm and DBD::Mysql everytime you wanted to just make a simple call to the database.
Here's an example to show how many modules you would need to copy + paste into even the most simple perl script if not for loadable libraries (you can see what I'm saying here):
To quote:
You obviously a have a feeble grasp of history that does not venture past the propoganda stuffed down your throat in high school and/or by the history channel.
If you did actually know history then you would be aware of course that the united states secretly instigated the pearl harbor attack by interfering with oil transport routes in the south pacific. Neither high command nor the most powerful ships where at pearl harbor. They knew an attack was coming eventually, and they needed it to be a slaughter so the public could never oppose entry to the war.
Like almost every war America joins or starts there has to be some kind of event to draw us in. Basically these events are always manufactured. Sinking lucitania, pearl harbor, gulf of tonkin, to name a few...
And of course nuking japan was not needed at all. Through freedom of information act requests we now know the president had agreed to an armistace and was already negotiating a surrender with japans emperor when the bombs where dropped. The mass death from the bombs was not really done to send a message to japan so much as a message to the Soviet Union. We wanted to demonstrate our new found power to completely devestate cities with atomic power in an attempt to intimidate them.
So basically pearl harbor and horishima would have been both avoidable but then again the record shows that america has never been a country that tries to avoid mass slaughter.
Should be read as: "<b>Inegrity can be exchanged for goods and services, like money. I get a lot more use out of money earned without a bit of integrity than I do from knowing I am doing the right thing."</b>
"Option B is an obvious downer, because customers give us money. Money can be exchanged for goods and services, like food... and I find food to be an important part of a nutritious breakfast."
Slashdot Mirror
You can do anything in 11 lines of Perl. Clearly, if HealthCare.gov had been written in Perl and still took 500,000,000 lines to do so, it would indicate that they had hired on the team responsible for building [http://www.otrs.com/ OTRS] because...OMG.
Link: http://www.youtube.com/watch?v... First thing I thought of.
Don't make this a racial thing.
"Ubuntu Outperforms Vista" is like saying "Ford Pinto Outperforms Amish Carriage"
DreamWeaver is the worst. No syntax hilighting for Perl. At all.
Forces you to use tabs (instead of spaces). Attempting to choose otherwise will result in a mixture of tabs and spaces.
Even now, after nearly a decade of DreamWeaver, an FTP transfer requires 100% of my CPU. The progress meter is not a progress meter at all.
It doesn't even provide proper autocomplete for JavaScript (not even client-side). Considering how deeply tied to JavaScript the DreamWeaver UI is, this has always bothered me.
Sure, it's better than nothing. But after *this* long under development, I expect a lot more that what we have now.
Adobe/Macromedia - you should be ashamed!
Great idea - I think I'll get right on that :)
Seriously, something like this would only play into the idea of "terrorists are attacking us" or "domestic combatants" or whatever.
Microsoft would have to be infiltrated by an operative - and do the evil deed (or public service?) there. I don't think it would be too hard to let just one more bug slip through (that's a joke).
Perhaps hack the Windows Update servers to automatically download the specially-crafted code.
Fun!
vTiger (and SugarCRM) - also written in PHP - both have Terrible performance. Absolutely terrible. I suppose that if you use this software with a database of less than 10,000 customers you might be ok. Searching for bugs actually times out (not a good sign). Something else of note: the SugarCRM developers can't code valid HTML. See for yourself - http://validator.w3.org/check?uri=http%3A%2F%2Fww
LedgerSMB and SQL-Ledger are seriously some of the worst Perl I have ever seen in the last 10 years.
I wouldn't touch LedgerSMB/SQL-Ledger with a 10 foot pole.
Every Perl programmer worth his/her salt knows that any Perl program or module should begin with:
I looked through the source code and although I didn't see any obvious vulnerabilities (i.e. SQL Injection or Cross-Site-Scripting) there are literally hundreds (thousands?) of lines of (poorly coded) HTML scattered throughout the Perl source.
Conventions as old as Perl5 (October of 1994) are completely ignored (clear module hierarchy, stricture, code comments, POD documentation, full test suite, etc.) and will ultimately lead any business built on such shoddy code to peril (or ruin).
The Dieter Simader (coder) and DWS Systems Inc. (company) may have made headlines with this steaming pile back in 1992. However, looking at the source code, it bears a copyright date of 2006. Mr. Dieter Simader appears to have successfully sheltered himself from learning anything new for the last 13 years (and running). Great Job!
Shitty code like *THIS* gives Perl a bad name. I would rather they simply close the download site before another hapless would-be user falls into the trap that is SQL-Ledger/LedgerSMB.
SalesForce (http://www.salesforce.com/), NetSuite (http://www.netsuite.com/) and Oracle/Siebel CRM on Demand (http://www.crmondemand.com/ are all excellent (hosted and proprietary) tools.
I know that's a good idea.
Everyone here knows that's a good idea.
Apparently the same person in Redmond responsible for the 1-inch scrollable lists of dozens (sometimes hundreds) of items is also responsible for coming up with ways to prevent viruses from infecting almost-updated Windows installs.
People like you would never have invented the wheel.
----
Yeah, gee that's exactly what we all need. 84 inches of Hi-Def death and dismemberment. Death gurgles in Dolby Digital 5.1.
Wow.
Too early for me, apparently..
You said it, brother.
The story line is something like Harry Potter meets Pirates of the Carribean.
I thought the third book really tied it all together though, so I hope there are also plans to do that one as well. That one small book could fill an entire feature-length movie script though, so maybe that's why it's not on the list yet.
Yay.
I agree.
Though I'm sure someone has already put together such a tree model to explain how fusion creates heavier elements, it would be nice to have, especially in a classroom setting.
I've tried lots of templating schemes with perl-based web development, but Apache::ASP is my favorite so far.
With the XMLsubs, $Request, $Response, $Server, $Application and $Session objects I am able to focus on the task at hand, rather than figuring workarounds to the limitations of the language I am using.
Global variables, cached database connections & queries, shared session-state and full access to the Apache API give you the power to do anything you need to.
Hi! I found this picture that describes in some detail President Bush's plan to raise Iraqi opinion of the USA and help ease tension in the hopes of reducing terrorist threat.
I agree. If a person finds their job dull, maybe they are either:
->> not showing their employer the skills necessary for a more challenging assignment->> upset about something else, but projecting it on work
->> jealous of a project someone else was assigned
->> the project you are working on has dragged on too long and you are anxious to start something else ->> any combination of the above
I am only speaking out of personal experience here.
We must do something to stop this war.
I am ashamed of my government.
Bush and his partners are criminals, not leaders.
There's this new thing called an "object".
Basically, you can create an object of a particular type anyplace that has access to the definition of that object.
Find a bug in that object? No problem...just update your single definition of that object ( the DLL, loadable library, module, etc ).
If every time I wanted to connect to the database or check an MD5 signature, I had to include that code into my project, that would really suck.
Instead of having 1 version of that code, I would now have as many versions as there are programs using it.
If I found a bug after using it in several places, I would have to recompile perhaps dozens of programs that use the same code.
With DLLs and libs, we can make reference to the object defined in the external library, and just use them from anything that _can_ reference them. I find this is very much my preferred method, and the reason people in general prefer to use external libraries when they can.
Imagine actually having to include all the code from CGI.pm, DBI.pm and DBD::Mysql everytime you wanted to just make a simple call to the database.
Here's an example to show how many modules you would need to copy + paste into even the most simple perl script if not for loadable libraries (you can see what I'm saying here):
Windows--
perl -e "use CGI;use DBI;use DBD::Mysql;use Digest::MD5;print $_. ' => ' . $INC{$_} . chr(10) foreach sort {$a cmp $b} keys %INC"
Other--
perl -e 'use CGI;use DBI;use DBD::Mysql;use Digest::MD5;print $_. " => " . $INC{$_} . chr(10) foreach sort {$a cmp $b} keys %INC'
This is the output I get from running that 1-liner on my windows box: :/perl/lib/Carp.pm .pm .pm /vars.pm
AutoLoader.pm => C:/perl/lib/AutoLoader.pm
CGI.pm => C:/perl/li b/CGI.pm
CGI/Util.pm => C:/perl/lib/CGI/Util.pm
Carp.pm => C
Config.pm => C:/perl/lib/Config.pm
DBD/Mysql. pm => C:/perl/site/lib/DBD/Mysql.pm
DBI.pm => C:/perl/site/lib/DBI
Digest/MD5.pm => C:/perl/site/lib/Digest/MD5.pm
DynaLoader.p m => C:/perl/lib/DynaLoader.pm
Exporter.pm => C:/perl/lib/Exporter
Exporter/Heavy.pm => C:/perl/lib/Exporter/Heavy.pm
constant. pm => C:/perl/lib/constant.pm
overload.pm => C:/perl/lib/overload. pm
strict.pm => C:/perl/lib/strict.pm
vars.pm => C:/perl/lib
warnings.pm => C:/perl/lib/warnings.pm
warnings/registe r.pm => C:/perl/lib/warnings/register.pm
Loadable modules are cool.
To quote: You obviously a have a feeble grasp of history that does not venture past the propoganda stuffed down your throat in high school and/or by the history channel. If you did actually know history then you would be aware of course that the united states secretly instigated the pearl harbor attack by interfering with oil transport routes in the south pacific. Neither high command nor the most powerful ships where at pearl harbor. They knew an attack was coming eventually, and they needed it to be a slaughter so the public could never oppose entry to the war. Like almost every war America joins or starts there has to be some kind of event to draw us in. Basically these events are always manufactured. Sinking lucitania, pearl harbor, gulf of tonkin, to name a few... And of course nuking japan was not needed at all. Through freedom of information act requests we now know the president had agreed to an armistace and was already negotiating a surrender with japans emperor when the bombs where dropped. The mass death from the bombs was not really done to send a message to japan so much as a message to the Soviet Union. We wanted to demonstrate our new found power to completely devestate cities with atomic power in an attempt to intimidate them. So basically pearl harbor and horishima would have been both avoidable but then again the record shows that america has never been a country that tries to avoid mass slaughter.
Weeeeeeee! It's so fun. i am lucky. Yay.
here here!
Those Germans are always behind!
Should be read as:
"<b>Inegrity can be exchanged for goods and services, like money. I get a lot more use out of money earned without a bit of integrity than I do from knowing I am doing the right thing."</b>
"Option B is an obvious downer, because customers give us money. Money can be exchanged for goods and services, like food ... and I find food to be an important part of a nutritious breakfast."
Fucking Whore
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money
MONEY money MONEY money MONEY money MONEY money v