Mozilla is more than a browser. It's a development platform, a software layer that runs on top of a number of hardware/OS platforms, and masks the differences.
In this light, an essential feature of Mozilla is backward compatibility between minor revisions. So, 1.0 means: "We're done with the APIs. Please come and hack away with them, we won't break your software".
Would automakers be for it? Most likely not. They make a substantial amount of money from repairs and maintenance. And to think of the outrage from auto-repair shops, cutting their business as well.
Nope. Audi has admited publicly that they are pushing for wider maintenance intervals, as most problems with their cars arise from faulty maintenance. Current Volkswagen-Audi gasoline engines have maintenance intervals of 30 0000km, and the new 1400cc Turbodiesel goes as far as 45 000km (if you don't count oil changes).
Moderators, please read before moderating. This AC posted a bunch of uselesse links. They're either biased (from the manuals of pgsql or mysql), or zdnet-like checklists, mostly outdated.
Does anyone know of a good comparison of both databases? Not the usual "X as feature A, while Y has not. Y is faster.". These are open-source products, so there's room for design analysis, not just the ZDNet style checklists... There's room to review the design and implementation decisions. This would ideally involve established members of both dev communities.
What I'd like to see is a profound comparison of mysql and postgresql. I'm a happy user of both, and I currently have pgsql serving a 8 million pageviews/month site, and handling load gracefully. AFAICare, pgsql is at least fast enough. I also never had any reliability/data loss problems with mysql, despite heavy concurrent access. AFAICare, mysql is robust enough. I'd really like to find out what are the core differences in both designs to get a grasp of how fast they may evolve.
Electric motors are nowhere close to having the kind of efficiency needed for an aircraft engine.
You probably didn't mean to say this. AFAIK, electric engines are the most efficient engines known to mankind, with efficiencies above 90% in most cases, and around 98% in the best cases.
The whole question on patent usage for standards is about what might be a reasonable fee. Simple, make the fee a percentage of the software product's added value. Just like in european VAT.
This would allow for the use of standards in open source products, which is an essential requisite for a valid standard. Since they never cost anything, they would never need to pay patent fees.
Microsoft has released a completely rewritten, thoroughly and publicly tested, new release of IIS,' which they say has an 80% chance of happening by the end of next year.
Hey! Even the Mozilla team took way over one year to get a good browser out of the door. I don't see MS being 4x faster.
Not to mention "thoroughly and publicly tested". Hah! It's M$ for Christ's sake! Testing hurts the bottom line!
No. IIS is integrated into the system in such a way that it cannot be uninstalled, and it cannot be disabled.
Bottom line: you can't ditch it. It'll always be there, and since it is there it must be patched to prevent security risks.
Re:Pray Or Meditate Or Whatever For President Bush
on
Handling the Loads
·
· Score: 1
Being Portugal the first country which abolished the death penalty, I think I can shed some light.
The Justice system, around here, is not meant for punishment. If you read the laws, nowhere is there the mention to any kind of punishment.
People are encarcerated to fullfill two basic objectives:
Protect the society from them.
Rehabilitate them.
Encarceration is limited to 25 years -- you can kill 100 people, get sentenced to 2000 years, and the limit makes you go free after 25 -- because it is the established limit for rehabilitation. For someone to be removed from society longer than that, he would have to be considered insane, dangerous to other people, and then sent to a mental institution - not the prision system.
Dreamweaver has no contender in Linux, unfortunately. Frontpage is easily beat by Mozilla's HTML editor, which although unknown to most, sports a great set of features.
As for syntax highlighting, the obvious choice is (X)emacs, and it has much more than syntax highlighting.
Photoshop is arguably better than GIMP, but GIMP beats ImageReady and Fireworks.
As for FTP, linux has the upper hand, as you can mount FTP and webdav filesystems. They become seamlessly accessible, better than any FTP manager can achieve.
The bottom line is: It is not for the tools that developers don't change to Linux. I publish web sites, and I do it on Linux. I feel I do it here better than on Windows.
How US centric... I guess its the history they teach you at school.
Aircraft: The Wright brothers flew the first *motorized* aircraft, but the first heavier-than-air flying man was Otto Lilienthal (German), on whose design the Wright brothers based their own airplane. Lilienthal died unfortunately, six years before the Wright brothers began their work.
The french flew hot-air baloons decades before.
Computers: The first electromechanical binary digital computer - the Z1 - is dated 1938, and was built by Konrad Zuse (german). By 1941, his computer was programmable. Choose either one as the first computer, but Konrad was the first.
Internet: If you are talking about TCP/IP, then you are right. But TCP/IP wouldn't have half its use, if it weren't Tim Berners Lee, working at CERN - Switzerland. Playing the www a huge part on today's internet, it is unfair to classify it as a US invention.
Automobiles: The first car was driven in 1889 by Gottlieb Daimler, inventor of the gasoline engine. BTW, the diesel engine was invented in 1893 by Rudolph Diesel, also german.
6 and 8 cylinder engines are irrelevant when Japanese produce the same torque and power using variable admission and turbos on 2 liter, 4 cylinders. For real power, the real engines are Ferrari's V12 (3 liter?) powering their winner F1 car.
Space vehicles: Unfortunately, the Russians beat you there. About reusability, today's age-old Ariane design from ESA has a cost per-launch lower than space shuttles. I don't mind if they have to put it back together after each mission, as long as it is safe and cheaper.
Here, you have to trace some parallelism with what happened in the past, in different markets.
Think about agriculture. 200 years ago, over half of men on Earth worked the fields. If you had dropped current automation and bioscience on them, and shown them that only 5% of total population needed to work on the fields, they'd be asking your exact question: "what will the rest of us do?"
The fact is that human evolution tends to commoditize goods and services, to move up in the added-value chain. One current example of this is the mobile phone industry, chasing ways to add value to their services, now that mobile phones are too common to provide operators with growth.
So, on software, after commoditizing libraries, operating systems and office suites, everyone will be free to build on this on to more complicated systems and uses.
Complicated systems are less general, creating a huge market for customization services. Thats what everyone will be doing. Solving complicated problems, not reinventing the wheel because the current wheel must be rented and paid by the kilometer.
Hey, criticism isn't any good unless it is constructive. I wouldn't mod this up to 4 without a solution proposal. If open-source isn't as good as MS Windows, explain why, and explain what should be done. Just saying "I don't know my path but I know it is not that one" is not acceptable.
I feel that current distributions are not easy enough to configure to be a good alternative to a windows desktop. That is the major bad point.
However, configuration is not an issue for enterprise deployments, or any other kind of mass deployment. Here Linux is actually easier on administrators, and I think is ready for usage.
We have seen major advances in desktops (both KDE and Gnome are to congratulate on this), and major advances in Office suites. I don't believe there's a problem here, even if Office suites are not par with MS.
But still - face it: Open source and free software is hobbyists writing code for their own well-being, because they (we) think it's fun, and/or because we need the software, and feels good about letting other people use and change said software too.
Untrue. Or at least, incomplete. While there certainly are many hobbyists writing code in their spare time, a quick glance at major open-source projects will find commercial company support.
Open-source allows for small companies to enter fields held by large corporations up until now. Open source development lowers the software entry barrier, for corporations as well as individuals.
Example: Imagine a small company who realizes they need to develop a J2EE application server because of an esoteric requirement. Before open source, the cost would be prohibitive. Nowadays, they'll probably join some project like JBoss, and add the features they particularly need.
Companies also have itches, and also scratch them.
Re:Not the firsr Sotock MArker of the world with L
on
NYSE Goes To Linux
·
· Score: 1
That might explain the 25% drop of PSI-20 since January:-)
There's that fabulous story about my traffic light simulator, in college. My group had created the most super-duper traffic simulator, with a fantastic programming language for the traffic lights, and a flashy Java GUI, showing the traffic congestion in the various avenues.
So it happens, that we should have written a few different programs for the traffic lights, so we could compare the simulation results. Nope. No time. Not after working through the night on the flashy GUI (mandatory for a good grade with that teacher).
Well, needless to say that we hacked together a few, very intelligent FIXED-TIME traffic lights. Yup, those that turn green and red like a swiss clock at precise intervals. The funny part was fooling the teacher:
- "And now, we see, that the congestion levels are rising...(time goes by)..., pavement sensors signal this condition to the traffic light...(time goes by)..., and (time goes by), voilá, the traffic light reacts and turns green."
- "Compared with fixed-time traffic lights, these agent-based artificial intelligent traffic lights show an increased effectivenes of (BIG NUMBER)"
And is it just me, or are Java exceptions completely useless? ...
Actually it's worse since you don't even have the option of *not* checking it; if you don't catch (...), it won't compile, even for exceptions that will never ever happen.
Yes you have the option of not checking them. Just declare the exception on the throws clause of the method again. The method caller needs to know the exception might be coming.
Java exceptions and Java compilers' exception checking are great methods to enforce error handling. Light years from NULL return values!
From your post, I believe you have used VisualAge for Java. If it is, your opinions are unfounded, as you can customize VA to do what you say you like.
Whenever you create fields for a class, you can tell VisualAge whether you prefer them to be private or not. The data field itself is *always* private; the accessor methods (getFoo/setFoo) will be there if you choose the have the field public.
As you should know, accessor methods are a Good Thing (tm) as they allow for the class to be responsible for keeping consistency (internal and external): data hiding as you say yourself.
As for the GUI design paradigm, it is a classic, recurrent OO pattern: Event Producer / Event Listener. You probably failed to recognize it, or you wouldn't say the design methodology is horrible.
Java may have been left to the wrong hands, both comercially and engineering-wise, but as an OO language it is very, very good. Most people here rant about OO language characteristics and fail to see that if Java does have these is a result of being an OO language.
I'm a professional programmer. I work with professional programmers. I've never seen anyone use calculus, ever. I've only seen people use trig maybe twice.
You've never recognised the use of calculus on a programmer. That's a different concept altogether. Calculus can be seen as the foundation of programming. No foundation, and the whole building comes apart.
Slashdot Mirror
In this light, an essential feature of Mozilla is backward compatibility between minor revisions. So, 1.0 means: "We're done with the APIs. Please come and hack away with them, we won't break your software".
I really don't get this thing of core features being implemented in table types.
Moderators, please read before moderating. This AC posted a bunch of uselesse links. They're either biased (from the manuals of pgsql or mysql), or zdnet-like checklists, mostly outdated.
What I'd like to see is a profound comparison of mysql and postgresql. I'm a happy user of both, and I currently have pgsql serving a 8 million pageviews/month site, and handling load gracefully. AFAICare, pgsql is at least fast enough. I also never had any reliability/data loss problems with mysql, despite heavy concurrent access. AFAICare, mysql is robust enough. I'd really like to find out what are the core differences in both designs to get a grasp of how fast they may evolve.
This would allow for the use of standards in open source products, which is an essential requisite for a valid standard. Since they never cost anything, they would never need to pay patent fees.
Not to mention "thoroughly and publicly tested". Hah! It's M$ for Christ's sake! Testing hurts the bottom line!
Bottom line: you can't ditch it. It'll always be there, and since it is there it must be patched to prevent security risks.
The Justice system, around here, is not meant for punishment. If you read the laws, nowhere is there the mention to any kind of punishment. People are encarcerated to fullfill two basic objectives:
- Protect the society from them.
- Rehabilitate them.
Encarceration is limited to 25 years -- you can kill 100 people, get sentenced to 2000 years, and the limit makes you go free after 25 -- because it is the established limit for rehabilitation. For someone to be removed from society longer than that, he would have to be considered insane, dangerous to other people, and then sent to a mental institution - not the prision system.As for syntax highlighting, the obvious choice is (X)emacs, and it has much more than syntax highlighting.
Photoshop is arguably better than GIMP, but GIMP beats ImageReady and Fireworks.
As for FTP, linux has the upper hand, as you can mount FTP and webdav filesystems. They become seamlessly accessible, better than any FTP manager can achieve.
The bottom line is: It is not for the tools that developers don't change to Linux. I publish web sites, and I do it on Linux. I feel I do it here better than on Windows.
You just missed an excelent chance of keeping your wide mouth shut.
Aircraft: The Wright brothers flew the first *motorized* aircraft, but the first heavier-than-air flying man was Otto Lilienthal (German), on whose design the Wright brothers based their own airplane. Lilienthal died unfortunately, six years before the Wright brothers began their work.
The french flew hot-air baloons decades before.
Computers: The first electromechanical binary digital computer - the Z1 - is dated 1938, and was built by Konrad Zuse (german). By 1941, his computer was programmable. Choose either one as the first computer, but Konrad was the first.
Internet: If you are talking about TCP/IP, then you are right. But TCP/IP wouldn't have half its use, if it weren't Tim Berners Lee, working at CERN - Switzerland. Playing the www a huge part on today's internet, it is unfair to classify it as a US invention.
Automobiles: The first car was driven in 1889 by Gottlieb Daimler, inventor of the gasoline engine. BTW, the diesel engine was invented in 1893 by Rudolph Diesel, also german.
6 and 8 cylinder engines are irrelevant when Japanese produce the same torque and power using variable admission and turbos on 2 liter, 4 cylinders. For real power, the real engines are Ferrari's V12 (3 liter?) powering their winner F1 car.
Space vehicles: Unfortunately, the Russians beat you there. About reusability, today's age-old Ariane design from ESA has a cost per-launch lower than space shuttles. I don't mind if they have to put it back together after each mission, as long as it is safe and cheaper.
Think about agriculture. 200 years ago, over half of men on Earth worked the fields. If you had dropped current automation and bioscience on them, and shown them that only 5% of total population needed to work on the fields, they'd be asking your exact question: "what will the rest of us do?"
The fact is that human evolution tends to commoditize goods and services, to move up in the added-value chain. One current example of this is the mobile phone industry, chasing ways to add value to their services, now that mobile phones are too common to provide operators with growth.
So, on software, after commoditizing libraries, operating systems and office suites, everyone will be free to build on this on to more complicated systems and uses.
Complicated systems are less general, creating a huge market for customization services. Thats what everyone will be doing. Solving complicated problems, not reinventing the wheel because the current wheel must be rented and paid by the kilometer.
I feel that current distributions are not easy enough to configure to be a good alternative to a windows desktop. That is the major bad point.
However, configuration is not an issue for enterprise deployments, or any other kind of mass deployment. Here Linux is actually easier on administrators, and I think is ready for usage.
We have seen major advances in desktops (both KDE and Gnome are to congratulate on this), and major advances in Office suites. I don't believe there's a problem here, even if Office suites are not par with MS.
Open-source allows for small companies to enter fields held by large corporations up until now. Open source development lowers the software entry barrier, for corporations as well as individuals.
Example: Imagine a small company who realizes they need to develop a J2EE application server because of an esoteric requirement. Before open source, the cost would be prohibitive. Nowadays, they'll probably join some project like JBoss, and add the features they particularly need.
Companies also have itches, and also scratch them.
That might explain the 25% drop of PSI-20 since January :-)
What?! Slow and unresponsive? What hardware are you running on? My PII233/256Mb and a TNT show no difference between win and X.
On the other hand, I'd like you to show me how can one open an emacs window on two displays, for pair programming, using windows.
The only possible explanation would be the use of a bloated window manager, like enlightenment
Do you plan on reusing effort that was put on Linux, avoiding the rewrite of the mythical wheel?
If at first you don't succeed, skydiving is not for you
At least it bought me a good laugh...
Well, needless to say that we hacked together a few, very intelligent FIXED-TIME traffic lights. Yup, those that turn green and red like a swiss clock at precise intervals. The funny part was fooling the teacher:
- "And now, we see, that the congestion levels are rising ...(time goes by)..., pavement sensors signal this condition to the traffic light...(time goes by)..., and (time goes by), voilá, the traffic light reacts and turns green."
- "Compared with fixed-time traffic lights, these agent-based artificial intelligent traffic lights show an increased effectivenes of (BIG NUMBER)"
Greatest laugh on a professors back.
--
Try a build from late April. Mozilla is like wine. Some daily builds are 'vintage' quality, some are good for making vinager.
Best way is to keep an eye on Mozillazine's daily build comments column and grab only vintage builds:
http://www.mozillazine.org/build_comments
I've been using Mozilla's browser for a few months now and it is very fast and stable. I agree it may choke on low RAM systems (128Mb).
Actually it's worse since you don't even have the option of *not* checking it; if you don't catch (...), it won't compile, even for exceptions that will never ever happen.
Yes you have the option of not checking them. Just declare the exception on the throws clause of the method again. The method caller needs to know the exception might be coming.
Java exceptions and Java compilers' exception checking are great methods to enforce error handling. Light years from NULL return values!
Whenever you create fields for a class, you can tell VisualAge whether you prefer them to be private or not. The data field itself is *always* private; the accessor methods (getFoo/setFoo) will be there if you choose the have the field public.
As you should know, accessor methods are a Good Thing (tm) as they allow for the class to be responsible for keeping consistency (internal and external): data hiding as you say yourself.
As for the GUI design paradigm, it is a classic, recurrent OO pattern: Event Producer / Event Listener. You probably failed to recognize it, or you wouldn't say the design methodology is horrible.
Java may have been left to the wrong hands, both comercially and engineering-wise, but as an OO language it is very, very good. Most people here rant about OO language characteristics and fail to see that if Java does have these is a result of being an OO language.
You've never recognised the use of calculus on a programmer. That's a different concept altogether. Calculus can be seen as the foundation of programming. No foundation, and the whole building comes apart.