Why the hell would a bunch of house robbers chase you, and risk getting into more trouble? They will leave as quickly as possible in the other direction from where you were heading to.
That's not JavaScript errors, but DOM errors. Trying to access document.layers won't work on Mozilla. Using the standards compliant domcument.getElementById() works great.
I don't recall my phone ceasing to work when I arrived in Las Vegas waiting for my flight into Los Angeles, nor when I was traveling down to San Diego
But can you drive straight through USA, from west coast to east coast, and still be able to use your phone during the entire journey? That is, full cell phone coverage not only in cities.
Now, with the overhaul and the complete switch to C++, I spend hours grovelling through the thing, usually without coming up with an answer.
I don't follow you here. Why would a switch from using a thousand separate C functions to a hundred C++ classes make things harder to read and understand? Or is it just that you haven't learned how to properly use OO code?
KDE started out as a project to make Linux easier to use, and was aimed primarily at the Windows crowd. Since the KDE project used a not fully free toolkit, a new project named Gnome started. It used the GTK+ toolkit and basically had the same goal as KDE: give Linux an interface that simplified usage. Unfortunately, none of these apps really make Linux any easier to use, since it is broken from the start.
Most of Slashdot readers say that we shouldn't try to make GUI:s with lots of bells and whistles. That is incredibly correct, mostly because everything below the GUI is strange or just plain wrong. Let's start with/etc. What the heck does it mean, and why not give it a logical name like/Settings instead? Same thing with/home and/bin, which should be/Users and/Applications. Also, take a look at the myriad of settings files in/etc, why not smb.conf. This file would be much better represented using XML and tree-structured settings, and so would most of the other files.
Documentation in Unix is incredibly bad - the man pages are incredibly complex. When the user wants to know what 'ls' does and how to use it, he/she should be able to type "help ls" and recieve at most a screenful of information about the command, what it does and how to do the most important things with it.
What I propose is a project where the focus is on removing all of the Unix strangeness and replace it with common sense. No care should be taken to "preserve the Unix tradition" nonsense. In the end, all GNU apps should be able to compile with -DCOMMON_SENSE to create the user-friendly version and without any flags to create the guru-friendly version.
Windows doesn't include IE. I have a Win98 installation with IE removed, and it occupies 60-70 MB. You can also create a fully working copy of OS/2 Warp in a very compact space (about 40MB or less). I would like to see an installed Linux distro with X and KDE occupying 60MB.
I rarely use my alarm clock. Infernal machine! This makes me happier, healthier.
Absolutely. It is a wonderful feeling to fall asleep and wake up because you're not tired anymore. The angry, beeping thing next to my bed now only shows what time it is, no more waking people up.
You don't. Actually, the whole concept of X is not to get work done, but to create hundreds of toolkits, window managers and applications that all look and behave like no other.
How I hate it. Is it so god damn hard to copy the OS/2 WPS, one of the few UI:s made for usage?
...why not start posting on Slashdot in our native languages, like swedish or french? Ärligt talat så vore det ganska skoj att se fler kommentarer skrivna på svenska. Dessutom så kan vi häckla personerna på andra sidan pölen utan att de förstår alldeles för mycket av det vi skriver.;-)
I am getting tired of all these new music file formats that won't allow me to make a copy of music that I have bought and bring it to work. You can, however, convert these foul beasts to something more usable like Ogg or Mp3. The solution is simple: fake the sound card. In Windows, you write a device driver that acts just like a sound card, but sends the wave information to a file. Unix makes it even simpler for root users: sound will be sent to/dev/dsp, so you just capture it there.
Now, doesn't this make the copy-limiting attemps a little... Stupid?
Tried oversea outsorcing. What we wanted was a solution in C++ written to conform to our specs, complete with UML notations and a spec that had been polished for two months. All they had to do was look at the documentation and write the classes according to the specification. The result? A C-based solution that was slow, poorly documented and generally an incredible pile of crap code.
Or, we create a working text editors for people who wants to have something that is easy to use with a consistent interface, and let all of the old goofs just open an XTerm and run vi, grep, sed and all of the others. That would be a much better solution in my opinion.
emacs httpd.conf
cvs ci -m "Fixed the problem with the foo.bar.com virtual server." httpd.conf
Because there is no "Incorrect" moderation option
on
Mozilla M17 Is Out
·
· Score: 1
The reason that Moz seems to gulp such enormous amounts of memory is the stupidity of some Linux tools. Moz uses threads. If an application uses 4MB in total and has 40 threads, top will report a mem usage of 160MB.
Why couldn't Apple just stick with the old case designs and OS from 1990? With a computer like this and the simply brilliant MacOS X, I just have to get one of these. Damn you, Apple, for making such an attractive computer! You have just got yourself another customer!
Unix programmers seems to dislike using threads in their applications. After all, they can just fork(); and run along instead of using the thread functions. But, that's not important right now.
What is your opinion on the current thread implementation in the Linux kernel compared to systems designed from the ground up to support threads (like BeOS, OS/2 and Windows NT)? In which way could the kernel developers make the threads work better?
Open source programmers are very often from a Unix background. Actually, most Unix users know at least a little about programming. Mac users, on the other hand, often don't care how the programs work. They expect them to carry on working forever without a hitch.
Now, sit down and think about this sentence for a while: open source programmers make user interfaces for other programmers. Look at X and the bazillion of different toolkits, skins, themes and general crap. Compare that to the simple elegancy of MacOS where every app behaves the same way. Just throwing in Emacs or another similar application to a Mac user is likely to give a hurl of dislike, since it doesn't follow any Mac user interface guidelines at all.
Making Mac users enjoy open source software is therefore easy: make a user interface that is aimed at the user, not the underlying program model. That is - make applications that don't suck.
Security: Again, tests have proved that Windows is far more secure. I even remember one being posted here on Slashdot some time ago (btw congrats to the Slashdot editors for posting this one - until then I had thought that Slashdot was a very biased site)
I have always said the same about Slackware. A fast, stable distro with none of the "everything must be free" crap that Debian has and that I don't care about.
Let me guess: you run Linux, right? The 'top' utility (and many others) become greatly confused when an application uses threads (like Mozilla do). If the application uses 10MB and uses 14 threads, you get a calculated memory usage of 140MB.
Slashdot Mirror
Why the hell would a bunch of house robbers chase you, and risk getting into more trouble? They will leave as quickly as possible in the other direction from where you were heading to.
Easy - set the speed limit to 32000 km/h at those areas. If you break that limit with an ordinary car...
That's not JavaScript errors, but DOM errors. Trying to access document.layers won't work on Mozilla. Using the standards compliant domcument.getElementById() works great.
If anyone manages to replace an entire operating system, capable of running on a humble 8088, with a Unix shell... THAT would be unbelievable.
But can you drive straight through USA, from west coast to east coast, and still be able to use your phone during the entire journey? That is, full cell phone coverage not only in cities.
I don't follow you here. Why would a switch from using a thousand separate C functions to a hundred C++ classes make things harder to read and understand? Or is it just that you haven't learned how to properly use OO code?
KDE started out as a project to make Linux easier to use, and was aimed primarily at the Windows crowd. Since the KDE project used a not fully free toolkit, a new project named Gnome started. It used the GTK+ toolkit and basically had the same goal as KDE: give Linux an interface that simplified usage. Unfortunately, none of these apps really make Linux any easier to use, since it is broken from the start.
/etc. What the heck does it mean, and why not give it a logical name like /Settings instead? Same thing with /home and /bin, which should be /Users and /Applications. Also, take a look at the myriad of settings files in /etc, why not smb.conf. This file would be much better represented using XML and tree-structured settings, and so would most of the other files.
Most of Slashdot readers say that we shouldn't try to make GUI:s with lots of bells and whistles. That is incredibly correct, mostly because everything below the GUI is strange or just plain wrong. Let's start with
Documentation in Unix is incredibly bad - the man pages are incredibly complex. When the user wants to know what 'ls' does and how to use it, he/she should be able to type "help ls" and recieve at most a screenful of information about the command, what it does and how to do the most important things with it.
What I propose is a project where the focus is on removing all of the Unix strangeness and replace it with common sense. No care should be taken to "preserve the Unix tradition" nonsense. In the end, all GNU apps should be able to compile with -DCOMMON_SENSE to create the user-friendly version and without any flags to create the guru-friendly version.
Windows doesn't include IE. I have a Win98 installation with IE removed, and it occupies 60-70 MB. You can also create a fully working copy of OS/2 Warp in a very compact space (about 40MB or less). I would like to see an installed Linux distro with X and KDE occupying 60MB.
Of course, 35MB is nothing compared to the enormous size of one Linux distro, KDE and finally Konqueror.
Absolutely. It is a wonderful feeling to fall asleep and wake up because you're not tired anymore. The angry, beeping thing next to my bed now only shows what time it is, no more waking people up.
You don't. Actually, the whole concept of X is not to get work done, but to create hundreds of toolkits, window managers and applications that all look and behave like no other.
How I hate it. Is it so god damn hard to copy the OS/2 WPS, one of the few UI:s made for usage?
Whistler does have built-in Voice Recognition...this is pretty cool.
Damn, I have had voice recognition installed with my OS for about five years now. Innovations from Microsoft? Nope.
...why not start posting on Slashdot in our native languages, like swedish or french? Ärligt talat så vore det ganska skoj att se fler kommentarer skrivna på svenska. Dessutom så kan vi häckla personerna på andra sidan pölen utan att de förstår alldeles för mycket av det vi skriver. ;-)
I am getting tired of all these new music file formats that won't allow me to make a copy of music that I have bought and bring it to work. You can, however, convert these foul beasts to something more usable like Ogg or Mp3. The solution is simple: fake the sound card. In Windows, you write a device driver that acts just like a sound card, but sends the wave information to a file. Unix makes it even simpler for root users: sound will be sent to /dev/dsp, so you just capture it there.
Now, doesn't this make the copy-limiting attemps a little... Stupid?
Tried oversea outsorcing. What we wanted was a solution in C++ written to conform to our specs, complete with UML notations and a spec that had been polished for two months. All they had to do was look at the documentation and write the classes according to the specification. The result? A C-based solution that was slow, poorly documented and generally an incredible pile of crap code.
No more american companies writing my code.
Or, we create a working text editors for people who wants to have something that is easy to use with a consistent interface, and let all of the old goofs just open an XTerm and run vi, grep, sed and all of the others. That would be a much better solution in my opinion.
Have you tried something like this?
emacs httpd.conf
cvs ci -m "Fixed the problem with the foo.bar.com virtual server." httpd.conf
The reason that Moz seems to gulp such enormous amounts of memory is the stupidity of some Linux tools. Moz uses threads. If an application uses 4MB in total and has 40 threads, top will report a mem usage of 160MB.
Why couldn't Apple just stick with the old case designs and OS from 1990? With a computer like this and the simply brilliant MacOS X, I just have to get one of these. Damn you, Apple, for making such an attractive computer! You have just got yourself another customer!
What is your opinion on the current thread implementation in the Linux kernel compared to systems designed from the ground up to support threads (like BeOS, OS/2 and Windows NT)? In which way could the kernel developers make the threads work better?
Now, sit down and think about this sentence for a while: open source programmers make user interfaces for other programmers. Look at X and the bazillion of different toolkits, skins, themes and general crap. Compare that to the simple elegancy of MacOS where every app behaves the same way. Just throwing in Emacs or another similar application to a Mac user is likely to give a hurl of dislike, since it doesn't follow any Mac user interface guidelines at all.
Making Mac users enjoy open source software is therefore easy: make a user interface that is aimed at the user, not the underlying program model. That is - make applications that don't suck.
NT and security are two things that don't match. http://www.securityfocus.com/vdb/stats. html
I have always said the same about Slackware. A fast, stable distro with none of the "everything must be free" crap that Debian has and that I don't care about.
Let me guess: you run Linux, right? The 'top' utility (and many others) become greatly confused when an application uses threads (like Mozilla do). If the application uses 10MB and uses 14 threads, you get a calculated memory usage of 140MB.
Nanotech anti-heart attack prevention
Excuse me, but wouldn't it be better to have a heart attack prevention device?