With mobile provider of Ontario, that's a pain in the ass, when your cellular Caller ID recognized 10-digit (or worse - 7-digit) local number from the incoming call and you stored it in your device. Then you movde temporary out of your local area and decided to call that number. Your provider would immidiately complain that you missed "1". Some provider would complete the call anyway after that, some - not. It really sucks.
Instead, why not all of North America go to 11 digits? At least, let all Caller ID services recognize 11-digits and let all provider accept 11-digits even for local calls.
There is also a bit of a seeding problem. How do you establish a large enough trusted community in the beginning, so that sufficient signings can be made on new certs.
Then use already existing community. Like Slashdot:)
Seriously,./ mechanism controling moderators can be used to sign certs of authors and moderators - just as a side effect of authoring and moderating activity.
You've got "Fair" and your cert is signed by one more signer. You've got "Unfair" and your cert marked bad by one more signer. Keep your balance as high as possoble if you want people to trust your cert!
Same way, just with lower rate of signature, can be used against authors - keep your Karma high and your cert will be trusted more.
More generally, that way can be used on many other forums and you can collect trusts from forum to forum using the same cert.
Do you use GOTO? No? Why? Because it's unsafe and it is not really unnecessary. However, it is still used somewhere hiddenly in the compiled binary code - programmers just don't manipulate it manually.
Same way, manual operations with memory ponters must be prohibited. And they are prohibited in languages with garbage collectors and automatic memory allocation: Java, Python, Perl, Ruby.
GC, automatic memory allocation and disabled GOTO, such methods limit programmers (in a positive way) and help to avoid very critical mistakes. But not all mistakes. Changing the variable (object) value is another source of common mistakes, which must be eliminated. It's solved in Functional Programming languages, such as Lisp, Haskell, ML, Oz, Mercury and Erlang.
sending spam would be just as illegal, no matter where the server is
So, what are you gonna do? Send the bill to many goverments? Say they are parts of "the evil axe" and apply sacntions to them? Disconnect many countries from USA (in other words, disconnect USA from the rest of the world)? Send CIA agents to find those servers and shut them down with a not-really-intelligent force (blow the server up)?
You leave in the real world, which is not perfect. If you don't like it - close the door. Applying to email - use certificates and PKI to accept only email from people you want to accept. Or use AI to do the filtering job instead of you. Nothing really else you can do. Today.
if journalling is just a hack, why IBMuse it instead of UFS? I don't believe that journalling is just a hack. It's reliability has been proven by several new-designed open source and commercial filesystems: ReiserFS, XFS, JFS.
As for Ext3, it's been improved, not hacked. And counting its age it's already reliable. Compare to UFS back to the same age.
As for scaling, I doubt that IBM made a mistake choosing Linux as a replacement for AIX. Otherwise, why IBM did not do the same or similar step as Apple did? The answer is simple: IBM doesn't trust to non-scalable design of BSD.
Recent news from SGI (Linux on new SGI servers) just proves it.
Re:Why can't they arleady do this?
on
SVG On the Rise
·
· Score: 1
I think it's more about politics than real license issue.
Mozilla team rejects libart (LGPL) and at the same time includes GTK (also LGPL). Strange, isn't it? But it doesn't look strange if you'll try to read some discussions in their bugzilla, like this one, where they buried out XFORMS b/c Why not just do it all in html and keep extending html. Basically, "we don't need any new standards, we need just some bugs to be fixed".
Look at other Mozilla projects having been promising and now dead. Look at their Roadmap - only version numbers, no info about any planned features (compare it with, for example PostgreSQL TODO list).
Gecko is (or was?) the most promising GUI technology I see today. It allows much more than HTML browsing - it allows to build real applications on the web. And several non-browser projects have been developed (i.e. mail). But tell me the name of any Gecko project newborn in last 6 months? Or old one riched its v1.0 quality in last 12 months? Did I miss something or nobody cares about Gecko anymore?
I think that for a long term Mozilla as project is slowing down and it may eventually die. At least with its current development team.
Correction: No single Linux server would be able to handle the Slashdot crowd. A single FreeBSD server can do it easily.
For business it doesn't matter single or cluster. For business the keyword is scalability.
Linux have much more than BSD ways for scaling up. BSD was designed to work as a single server (with single CPU).
Besides, I wanna ask: how is BSD good with journalling and RAIDs on that sinlge server?
The only way for Microsoft to win in the buttle with Linux is to stop the buttle and to begin cooperation. If you cannot win - live with it and use it for your own benefit.
There is no such company as Linux - there are dozen of vendors, handreds of support centers and thousands of independent developers. You cannot buy ALL of them. You cannot force ALL of them out of business. This is the new life, new objective reality. You cannot compete with the life itself.
Microsoft is not a church or any religion organization. Instead, Microsoft is the most successful software-related business. When Microsoft is using some propaganda - it's to make new money, nothing else. If (or when) strategic planners in the giant discover that Windows on a top of Linux is a good idea - they will command to do it without any hesitation.
Linux community won't be really hurt - more drivers etc etc. The life won't be the same
as we know it, but that won't be the death for the Linux community. I am positive.
There won't be the war between OSes. Instead, there will be wars between architecture and design ideas. Users won't choose between Windows and
Linux. They will be choosing between diffirent implementations and distros.
I guess, Microsoft will shift their main profit source from OS licensing to application licensing and even more - to support.
If (actually - when) Microsoft will build new Windows on a top of Linux, the users will win. That's for sure.
Now, why linux and why not BSD? If Microsoft will adopt BSD then it will play well for its strong potential competitor - Apple. If Apple will deliver MacOSX for x86 - Microsoft market share will collapse and it would happen rapidly - MSFT stock may collapse.
How Linux may help? It's very simple. Just count how many Linux users are out there. Add how many corps have already considered Linux (just not migrated yet). If Microsoft will declare that new Windows will be on the top of Linux then Apple can forget about x86 forever.
Speaking about GPL, it's a matter of time that Microsoft will agree with logic of IBM: GPL is compatible with profitable business models. There is nothing wrong of including GPL kernel and uilities into your OS. And that there are much more good GPL software out there than BSDL.
Besides, if you agree to include GPL into your product, its more likely you agree with BSDL as well. If don't - then you are limited only to BSDL subset of OSS. So, your agreement to include GPL gives you all OSS instead of just small portion of it. Just make sure your lawers are OK with GPL and your business model is OK with GPL. And that what's gonna happen to Microsoft soon, I believe.
Where are all those cool systems, like BeOS, Amiga and others?
LISP was the cool language and interpreter since 1957 and stays cool here. TCL, Perl, Python, Ruby, Scheme, Haskell and OCAML are cools languages and interpreters. Linux and BSD are cool systems. PostgreSQL is a cool database. And they stay cool without any commercial support.
But all those "cool" languages and systems, which are failed and forgottent immidiately after dropping of their commercial support, they are not cool. And never been.
What will happen to Java if Sun will drop its support? Same questions about Erlang, MySQL and MacOSX. Noone will remember them.
yeah, right. let's also integrate to the kernel Perl, Python, Tcl, Lua, Emacs (for Elisp), Guile, Hugs, OCAML, Bash, Apache (for PHP) and Gecko (I want my Mozilla to work faster too!). I wonder, why is X server still not there? And don't forget about at least two CORBA brokers: Gnorba (everyone would love faster Gnome) and OmniOrb (just for a case). Hey, let's put everything into the kernel! Ooops... It's not kernel anymore and it doesn't want to run either. What was the mistake?
That fact is less important for Apple comparing to the fact that KHTML doesn't work on Windows like Gecko does. Helping (contributing?) to KHTML could be a part of the war against Windows.
The only way to avoid buffer overflow problem by application programmers is to use languages where buffer overflow is not possible at all. The only category of such languages I know is pure functional programming languages. All variables/objects must be immature. There should be no way to change the value of any variable/object.
I've been using J2EE on winNT/2k, Solaris and linux and i would tell that Linux was the worst case of scenario counting slow performance and amount of bugs.
I am not fun of Java after all, but if you want to (have to, are forced to) use Java, take either Solaris or Windows, depends on your hardware budget.
Personally, I prefer to develop Python based web applications with Zope. But that is off-topic.
what specifically makes it different?
on
Ark Linux
·
· Score: 2
The web site claims that There are already plenty of good Linux distributions for servers and for advanaced users out there - but so far, nobody has tried making an easy to use version of Linux for the masses, even though the KDE user interface makes Linux very easy to use. It is not our intent to take users away from other Linux distributions. It is our goal to provide a good desktop operating system.
But neither the article or the original project site do not disclose by which means the new distro will make Linux easy to use comparing to other linux distros.
Is it just new set of very well debugged installation programs very well integrated with GUI based wizards? If so, what's the difference with Mandrake, Lindows, SCO and Redhat?
Or it integrates some new end-user applications (like ximian evolution)?
Especially I wonder, what is done or is going to be done to improve the user experience from usability prospective? For example, what specifically is done to explain the user what makes this distro so easy to use?
Could it be a point of argument that removing pay phones reduces access to 911 emergency services for those economically disadvantaged who don't have cell phones?
That nothing to do with Bells. Telcos originally started the payphone business with the only goal to make money, not because the govt ordered them to do so. Therefore, if this business is not working anymore let them get phones out of the street.
And if the safity of citizens is any concern of the govt then the govt must compensate telco all TCO they have plus prenegotiated profit minus total revenue. Otherwise, let the govt to buy out the payphone business from telcos and run it on their own for the money of tax payers if the tax payers agree to pay such a price for very doubtful benefit in their security.
Slashdot Mirror
Instead, why not all of North America go to 11 digits? At least, let all Caller ID services recognize 11-digits and let all provider accept 11-digits even for local calls.
Then use already existing community. Like Slashdot :)
Seriously, ./ mechanism controling moderators can be used to sign certs of authors and moderators - just as a side effect of authoring and moderating activity.
You've got "Fair" and your cert is signed by one more signer. You've got "Unfair" and your cert marked bad by one more signer. Keep your balance as high as possoble if you want people to trust your cert!
Same way, just with lower rate of signature, can be used against authors - keep your Karma high and your cert will be trusted more.
More generally, that way can be used on many other forums and you can collect trusts from forum to forum using the same cert.
Let your Karma sign your cert!
Same way, manual operations with memory ponters must be prohibited. And they are prohibited in languages with garbage collectors and automatic memory allocation: Java, Python, Perl, Ruby.
GC, automatic memory allocation and disabled GOTO, such methods limit programmers (in a positive way) and help to avoid very critical mistakes. But not all mistakes. Changing the variable (object) value is another source of common mistakes, which must be eliminated. It's solved in Functional Programming languages, such as Lisp, Haskell, ML, Oz, Mercury and Erlang.
Another alternative is RCS written on shell: Arch.
Wait, both Scheme and Shell are written on C, so you can't use them either. You may try to find someting written directly on Asm.
I don't see any "BSD World" exhibition around? Is it because of BSD architecture or BSD license?
So, what are you gonna do? Send the bill to many goverments? Say they are parts of "the evil axe" and apply sacntions to them? Disconnect many countries from USA (in other words, disconnect USA from the rest of the world)? Send CIA agents to find those servers and shut them down with a not-really-intelligent force (blow the server up)?
You leave in the real world, which is not perfect. If you don't like it - close the door. Applying to email - use certificates and PKI to accept only email from people you want to accept. Or use AI to do the filtering job instead of you. Nothing really else you can do. Today.
Now, try to stick in China with Chineese keyboard. Got a difference?
I believe that South-East Asia has the biggest motivation in morphiing keyboards.
However, let's keep watching the Moore's law. If it will hold in ~7 years, than we'll get 5GB flash memory in one piece for the sime price, probably :)
I wonder what's happened to original implementation of roaming profiles of Netscape Communicator?
As for Ext3, it's been improved, not hacked. And counting its age it's already reliable. Compare to UFS back to the same age.
As for scaling, I doubt that IBM made a mistake choosing Linux as a replacement for AIX. Otherwise, why IBM did not do the same or similar step as Apple did? The answer is simple: IBM doesn't trust to non-scalable design of BSD.
Recent news from SGI (Linux on new SGI servers) just proves it.
Mozilla team rejects libart (LGPL) and at the same time includes GTK (also LGPL). Strange, isn't it? But it doesn't look strange if you'll try to read some discussions in their bugzilla, like this one, where they buried out XFORMS b/c Why not just do it all in html and keep extending html. Basically, "we don't need any new standards, we need just some bugs to be fixed".
Look at other Mozilla projects having been promising and now dead. Look at their Roadmap - only version numbers, no info about any planned features (compare it with, for example PostgreSQL TODO list).
Gecko is (or was?) the most promising GUI technology I see today. It allows much more than HTML browsing - it allows to build real applications on the web. And several non-browser projects have been developed (i.e. mail). But tell me the name of any Gecko project newborn in last 6 months? Or old one riched its v1.0 quality in last 12 months? Did I miss something or nobody cares about Gecko anymore?
I think that for a long term Mozilla as project is slowing down and it may eventually die. At least with its current development team.
For business it doesn't matter single or cluster. For business the keyword is scalability.
Linux have much more than BSD ways for scaling up. BSD was designed to work as a single server (with single CPU). Besides, I wanna ask: how is BSD good with journalling and RAIDs on that sinlge server?
There is no such company as Linux - there are dozen of vendors, handreds of support centers and thousands of independent developers. You cannot buy ALL of them. You cannot force ALL of them out of business. This is the new life, new objective reality. You cannot compete with the life itself.
Microsoft is not a church or any religion organization. Instead, Microsoft is the most successful software-related business. When Microsoft is using some propaganda - it's to make new money, nothing else. If (or when) strategic planners in the giant discover that Windows on a top of Linux is a good idea - they will command to do it without any hesitation.
Linux community won't be really hurt - more drivers etc etc. The life won't be the same as we know it, but that won't be the death for the Linux community. I am positive.
There won't be the war between OSes. Instead, there will be wars between architecture and design ideas. Users won't choose between Windows and Linux. They will be choosing between diffirent implementations and distros.
I guess, Microsoft will shift their main profit source from OS licensing to application licensing and even more - to support.
If (actually - when) Microsoft will build new Windows on a top of Linux, the users will win. That's for sure.
Now, why linux and why not BSD? If Microsoft will adopt BSD then it will play well for its strong potential competitor - Apple. If Apple will deliver MacOSX for x86 - Microsoft market share will collapse and it would happen rapidly - MSFT stock may collapse.
How Linux may help? It's very simple. Just count how many Linux users are out there. Add how many corps have already considered Linux (just not migrated yet). If Microsoft will declare that new Windows will be on the top of Linux then Apple can forget about x86 forever.
Speaking about GPL, it's a matter of time that Microsoft will agree with logic of IBM: GPL is compatible with profitable business models. There is nothing wrong of including GPL kernel and uilities into your OS. And that there are much more good GPL software out there than BSDL.
Besides, if you agree to include GPL into your product, its more likely you agree with BSDL as well. If don't - then you are limited only to BSDL subset of OSS. So, your agreement to include GPL gives you all OSS instead of just small portion of it. Just make sure your lawers are OK with GPL and your business model is OK with GPL. And that what's gonna happen to Microsoft soon, I believe.
Well, if Erlang will stay without Ericson and Nokia support than it's a cool language. Otherwise it was not. Simple.
No, it wasn't. Otherwise, where is it now?
Where are all those cool systems, like BeOS, Amiga and others?
LISP was the cool language and interpreter since 1957 and stays cool here. TCL, Perl, Python, Ruby, Scheme, Haskell and OCAML are cools languages and interpreters. Linux and BSD are cool systems. PostgreSQL is a cool database. And they stay cool without any commercial support.
But all those "cool" languages and systems, which are failed and forgottent immidiately after dropping of their commercial support, they are not cool. And never been.
What will happen to Java if Sun will drop its support? Same questions about Erlang, MySQL and MacOSX. Noone will remember them.
It would be much simpler to write Smalltalk on Scheme or Lisp, than Lisp (or even Scheme) on Smalltalk.
yeah, right. let's also integrate to the kernel Perl, Python, Tcl, Lua, Emacs (for Elisp), Guile, Hugs, OCAML, Bash, Apache (for PHP) and Gecko (I want my Mozilla to work faster too!). I wonder, why is X server still not there? And don't forget about at least two CORBA brokers: Gnorba (everyone would love faster Gnome) and OmniOrb (just for a case). Hey, let's put everything into the kernel! Ooops... It's not kernel anymore and it doesn't want to run either. What was the mistake?
That fact is less important for Apple comparing to the fact that KHTML doesn't work on Windows like Gecko does. Helping (contributing?) to KHTML could be a part of the war against Windows.
The only way to avoid buffer overflow problem by application programmers is to use languages where buffer overflow is not possible at all. The only category of such languages I know is pure functional programming languages. All variables/objects must be immature. There should be no way to change the value of any variable/object.
I've been using J2EE on winNT/2k, Solaris and linux and i would tell that Linux was the worst case of scenario counting slow performance and amount of bugs.
I am not fun of Java after all, but if you want to (have to, are forced to) use Java, take either Solaris or Windows, depends on your hardware budget.
Personally, I prefer to develop Python based web applications with Zope. But that is off-topic.
You mean xnu as in Xnu's Not Unix?
But neither the article or the original project site do not disclose by which means the new distro will make Linux easy to use comparing to other linux distros.
Is it just new set of very well debugged installation programs very well integrated with GUI based wizards? If so, what's the difference with Mandrake, Lindows, SCO and Redhat?
Or it integrates some new end-user applications (like ximian evolution)?
Especially I wonder, what is done or is going to be done to improve the user experience from usability prospective? For example, what specifically is done to explain the user what makes this distro so easy to use?
That nothing to do with Bells. Telcos originally started the payphone business with the only goal to make money, not because the govt ordered them to do so. Therefore, if this business is not working anymore let them get phones out of the street.
And if the safity of citizens is any concern of the govt then the govt must compensate telco all TCO they have plus prenegotiated profit minus total revenue. Otherwise, let the govt to buy out the payphone business from telcos and run it on their own for the money of tax payers if the tax payers agree to pay such a price for very doubtful benefit in their security.
Some similar ideas I remember from my experience also with Compaq and IBM.