You and everybody else can try to rationilze using port 80 and HTTP for all types of reasons, but the moral of the story is because people are trying to get around firewalls. Why you ask? Well because SysAdmins open up port 80 for obvious reasons, but have other ports shutdown for more obvious reasons (good or bad).
You can sit there and tell me till the sky is green that you are just reusing code/technology/methodolgy/voodoo/karma, but the moral of the story is people are trying to be slick and get around their SysAdmins!!!!
Okay, I finally found an article that I feel the need to reply too.
Writing good code is art-work, but it is not a black-art. If you spend some time upfront to design the system, you should be able to give a good estimate. Don't give me that "but its new technology" bullshit either. Then in your schedule you put a prototyping period in where all you do is write scrapable code (did you happen to catch the word "schedule" in that sentence).
That being said, Yes, I realize that sometimes manangement doesn't/won't give you that time upfront for which you will pay 10-fold in a piss-pour design. I might not be the sharpest knife in the ol drawer, but even I know that.
Basically, the moral of this rant is, just apply good engineering principles and you should be able to create a schedule (ah there is that word again) that you should be able to track reasonably close.
Praise the freakin' (insert your deity here)!!
I finally found someone who I can agree with on Slashdot!!!
My thoughts exactly. A computer is a computer, not a damn religion. I use Linux for my workstation because I feel that it is the best match. I use OpenBSD for my firewall because it is the best OS for that role.
Well, I guess I will throw my $0.02 into the ring.
As the subject says, I would recommend OpenBSD all the way. Granted, it is not really for my Gramps, but Gramps shouldn't be hooking up a box to the Net that is readily available for hacks to become based for attacks:-) This really should be left to people who understand the basics of security.
Now, granted you will need slightly more hardware (2 NICS's plus an old PC), but the flexibility that you get far out weights the hassles of the "extra" computer floating around under the desk.
I have my old 133 A) keeping all of the bad people out (occasionally I turn on the logging to just see what is going on and I am always amazed to see just how many "attacks" I see on my box) B) NAT'ing because I have several boxes behind the Wall C) file sharing via Samba because some of the boxes behind the Wall are Windows D) printer sharing via Samba as well
I am relativly new to *NIX OS's, and I thought the install and configuring was quite simple. Just print out the FAQ pages, and follow them. Voila, your system will be up and running.
For firwalling, IP forwarding and such activity, I can't imagine using anything other that Open
BSD, but like I said, just my $0.02.
Bullshit. I write system services and plenty of system-privilege apps that don't crash Windows. The *app* may crash until I get it finished, but that's not what you said. Anyone writing code that depends on wininet or the MSVC runtime and MFC dlls, frankly, is asking for what they get.
Lets take a look at your statement for a moment. You say that if you use MFC any of that _SYSTEM_ provided resources, that you asking for it. Whhhoooaaa, aren't those and I say again _SYSTEM_ provide resources. Hmmmmm.
But if you use the interfaces correctly, these don't crash Windows either.
So now how do you get to the interface without MFC. Hmmm, wait that would be the Win32 API's. Who in the hell really wants to use OO languages anyway when doing UI's. I guess I am just in the minority
Yep, it is your fault. All that shit is not necessary to work with XML. There are some reasonably good third-party libs that don't require all that crap. You apparently know as well as I do that developers using all that crap (besides the existence of that crap itself) are the cause of the problem. The most useful frame of mind I've found for writing Windows apps is "think small". Write with the fewest dependencies and libs possible. That pretty much leaves out developing in VB or using MFC, and avoiding the C runtime if possible. ATL is an excellent library, though, and there are some outstanding compilers out there if you prefer BASIC (check out http://www.powerbasic.com".
Again I say, arent' these _SYSTEM_ resources that are causing the stability issues? Okay, so they had to be installed, but they did come from the OS vendor directly, and they caused stability issues. Again I say Hmmmmmmmmmmm.
You sound like a Windows user who just does not have a clue about what a real operating system should be like, and YES I do realize that you are little troll who just learned just what the Internet is!!!!
One part of trusted is that a system _MUST NOT_ have any underlying bugs. Don't forget that and just go away.
No. Freebsd is just another free Unix. It may be used more as a server OS (IMHO because there is less hand-holding for newbies)
And this is why your OS will _NEVER_ get into the mainstream. If you want people to try your OS, guess what jackass, they have to atleast get in installed. Yes, some of the Linux distro's install's aren't the best, but they sure as hell are better than the FreeBSD install.
The biggest problem that companies have is that they do not understand the difference between an Engineer and a programmer. Well guess what, there is one hellva big difference, and anybody that says other wise is a lying. I do not mean to insult people who do not have any formal training, but yes the formal training is important. Most software sucks is because you did not have anybody clearly understanding the problem and laying the direction with the correct technology.
I am sorry to say, but that is what I was taught in school. Sit back and evaluation the situation as a whole. Most programmers can't/won't think big about the solution as a whole; they just want to jump in and start writing code.
But your "changes" go against all that has made this country great. You need to reeeeaallllyyyy think about just what the changes you want will affect the country. Socialism means you are willing to accept nothing more than average.
Show me one country that is either socalistic or communistic that can equal our country....I dare you!!! You can't can you!!!!
The reason you can't is because our system works the best that is out there, and you feel that you have the brains to change what has made this countery great!!!!!
Just shut the hell up and continue asking your familiar work phrase: "Would you like that super-sized for $.39" because obviously that is all that you are capable of and let us who have potential move forward!!!
At this point, you are a fork just renamed. Anything that is added to 'foo.c' would then have to be merged into 'foo-garbage.c' or 'foo-bigiron.c'. Soooo what have you gained? Nothing.
There is absolutely nothing wrong with a fork if whoever forks takes on the responsibility of forever merging the tip changes onto the fork.
On a personal note, it is nice to see you GPL boys now possibly having to code with real-world issues like forks and specials. I don't mean it as a slam, just an observation.
I really feel sorry for your company that employes developers that have a hard-time understanding a mult-threaded design. I have a degree in Electrical Engineering and now work as a software designer/programmer. Notice that I make a distinction!!! Obviously you were talking about "programmers" right?
My guess is the person who did the design AND DOCS was a programmer because if he had been a TRUE designer, most of your problems would have just disappeared.
You have a problem with multi-threaded designs? You need to seriously come to grips with where the world is going. They are vastly superior to the old Unix way of everything is a "process".
Normally I would agree with you, but the PIII is going to be around for quite some time. In addition, I don't think you will be seeing the PIV around for quite some time regardless of what Intel says (something about not being able to actually make a product in use quantity!!).
So my 2sense is that this is quite important because anybody upgrading their system should take note of this if performance is an issue.
Re:There's really not much difference between the
on
GPG vs. PGP?
·
· Score: 1
Thanks for your input. It was simple and useful, but I have to tell you: Mutt ain't that great!!!!
Soooo what you are trying to say is that when you sell your software, you want the whole pot versus having to dole out some to a third party.
My guess is that your concept of how business's really work is slightly skewed to the loopy side: I am sorry to say.
You say "swallow some pride and work on a good C++ interface for GTK and Gnome!". Great add just one more layer onto a system that is already overloaded (Sorry no pun intended!!!).
Damn, I knew I should have gone into CS program. I stayed in the EE program, and man let me tell you what the chicks looked like in there!!
Woof woof, bow bow and it goes on from there. Not to be shallow...hell what I saying..they were dogs!!!!
To sum up, I am quite envious !!!!!
Re:This *should* be a position at every University
on
Computer Historian?
·
· Score: 1
So what you are telling me is that you:
a) don't work in a technical field
b) you have no grasp of the "bigger picture"
c) you just squeeked by getting that finance degree
d) the bubble you call 'the world' is a 'happy place' for you
If you were a technically based person, you would realize that 70% of all problems were already solved, 20% just can't be solved currently and the last 10% set us who have a clue apart from those like you who don't have a clue.
Re:Use for multitaasking, multiuser, networked box
on
A Praise To Unix
·
· Score: 1
The new paradigm should be "I am so fricken tired of reinstalling Windows because the stupid user keeps deleting files that they shouldn't".
You need the multi-user ability to keep the normal user from roaching the system because they were click-happy!
Slashdot Mirror
Bzzzt...wrong answer
You and everybody else can try to rationilze using port 80 and HTTP for all types of reasons, but the moral of the story is because people are trying to get around firewalls. Why you ask? Well because SysAdmins open up port 80 for obvious reasons, but have other ports shutdown for more obvious reasons (good or bad).
You can sit there and tell me till the sky is green that you are just reusing code/technology/methodolgy/voodoo/karma, but the moral of the story is people are trying to be slick and get around their SysAdmins!!!!
SeeYa
Okay, I finally found an article that I feel the need to reply too.
Writing good code is art-work, but it is not a black-art. If you spend some time upfront to design the system, you should be able to give a good estimate. Don't give me that "but its new technology" bullshit either. Then in your schedule you put a prototyping period in where all you do is write scrapable code (did you happen to catch the word "schedule" in that sentence).
That being said, Yes, I realize that sometimes manangement doesn't/won't give you that time upfront for which you will pay 10-fold in a piss-pour design. I might not be the sharpest knife in the ol drawer, but even I know that.
Basically, the moral of this rant is, just apply good engineering principles and you should be able to create a schedule (ah there is that word again) that you should be able to track reasonably close.
Hey,
You must be the guy who sits next to me because you just described my day to a tee!!!
Praise the freakin' (insert your deity here)!!
I finally found someone who I can agree with on Slashdot!!!
My thoughts exactly. A computer is a computer, not a damn religion. I use Linux for my workstation because I feel that it is the best match. I use OpenBSD for my firewall because it is the best OS for that role.
Well, I guess I will throw my $0.02 into the ring.
:-) This really should be left to people who understand the basics of security.
As the subject says, I would recommend OpenBSD all the way. Granted, it is not really for my Gramps, but Gramps shouldn't be hooking up a box to the Net that is readily available for hacks to become based for attacks
Now, granted you will need slightly more hardware (2 NICS's plus an old PC), but the flexibility that you get far out weights the hassles of the "extra" computer floating around under the desk.
I have my old 133 A) keeping all of the bad people out (occasionally I turn on the logging to just see what is going on and I am always amazed to see just how many "attacks" I see on my box) B) NAT'ing because I have several boxes behind the Wall C) file sharing via Samba because some of the boxes behind the Wall are Windows D) printer sharing via Samba as well
I am relativly new to *NIX OS's, and I thought the install and configuring was quite simple. Just print out the FAQ pages, and follow them. Voila, your system will be up and running.
For firwalling, IP forwarding and such activity, I can't imagine using anything other that Open
BSD, but like I said, just my $0.02.
Well, currently I am running XP Professional with IE 6.0 and guess what, it doesn't load. Sorry, it just sits there.
Dude, you just made my day by making me laugh real hard.
Thanks. I appreaciate the humor.
Bullshit. I write system services and plenty of system-privilege apps that don't crash Windows. The *app* may crash until I get it finished, but that's not what you said. Anyone writing code that depends on wininet or the MSVC runtime and MFC dlls, frankly, is asking for what they get.
Lets take a look at your statement for a moment. You say that if you use MFC any of that _SYSTEM_ provided resources, that you asking for it. Whhhoooaaa, aren't those and I say again _SYSTEM_ provide resources. Hmmmmm.
But if you use the interfaces correctly, these don't crash Windows either.
So now how do you get to the interface without MFC. Hmmm, wait that would be the Win32 API's. Who in the hell really wants to use OO languages anyway when doing UI's. I guess I am just in the minority
Yep, it is your fault. All that shit is not necessary to work with XML. There are some reasonably good third-party libs that don't require all that crap. You apparently know as well as I do that developers using all that crap (besides the existence of that crap itself) are the cause of the problem. The most useful frame of mind I've found for writing Windows apps is "think small". Write with the fewest dependencies and libs possible. That pretty much leaves out developing in VB or using MFC, and avoiding the C runtime if possible. ATL is an excellent library, though, and there are some outstanding compilers out there if you prefer BASIC (check out http://www.powerbasic.com".
Again I say, arent' these _SYSTEM_ resources that are causing the stability issues? Okay, so they had to be installed, but they did come from the OS vendor directly, and they caused stability issues. Again I say Hmmmmmmmmmmm.
At what point do you open that bag of bad weed?
You sound like a Windows user who just does not have a clue about what a real operating system should be like, and YES I do realize that you are little troll who just learned just what the Internet is!!!!
One part of trusted is that a system _MUST NOT_ have any underlying bugs. Don't forget that and just go away.
No. Freebsd is just another free Unix. It may be used more as a server OS (IMHO because there is less hand-holding for newbies)
And this is why your OS will _NEVER_ get into the mainstream. If you want people to try your OS, guess what jackass, they have to atleast get in installed. Yes, some of the Linux distro's install's aren't the best, but they sure as hell are better than the FreeBSD install.
The biggest problem that companies have is that they do not understand the difference between an Engineer and a programmer. Well guess what, there is one hellva big difference, and anybody that says other wise is a lying. I do not mean to insult people who do not have any formal training, but yes the formal training is important. Most software sucks is because you did not have anybody clearly understanding the problem and laying the direction with the correct technology.
I am sorry to say, but that is what I was taught in school. Sit back and evaluation the situation as a whole. Most programmers can't/won't think big about the solution as a whole; they just want to jump in and start writing code.
Just my $0.0000000002
"cumbersome BSD licensing ponzi scheme.." ????
Exactly what orifice is your head in? I am just curious? Last time I checked, the BSD license is much less restrictive.
Very well put.
But your "changes" go against all that has made this country great. You need to reeeeaallllyyyy think about just what the changes you want will affect the country. Socialism means you are willing to accept nothing more than average.
Show me one country that is either socalistic or communistic that can equal our country....I dare you!!! You can't can you!!!!
The reason you can't is because our system works the best that is out there, and you feel that you have the brains to change what has made this countery great!!!!!
Just shut the hell up and continue asking your familiar work phrase: "Would you like that super-sized for $.39" because obviously that is all that you are capable of and let us who have potential move forward!!!
Dude, I am not sure where you got that info from, but you rrreeeeaaallllyyyyy need to recheck that one out.
At this point, you are a fork just renamed. Anything that is added to 'foo.c' would then have to be merged into 'foo-garbage.c' or 'foo-bigiron.c'. Soooo what have you gained? Nothing.
There is absolutely nothing wrong with a fork if whoever forks takes on the responsibility of forever merging the tip changes onto the fork.
On a personal note, it is nice to see you GPL boys now possibly having to code with real-world issues like forks and specials. I don't mean it as a slam, just an observation.
I really feel sorry for your company that employes developers that have a hard-time understanding a mult-threaded design. I have a degree in Electrical Engineering and now work as a software designer/programmer. Notice that I make a distinction!!! Obviously you were talking about "programmers" right?
My guess is the person who did the design AND DOCS was a programmer because if he had been a TRUE designer, most of your problems would have just disappeared.
You have a problem with multi-threaded designs? You need to seriously come to grips with where the world is going. They are vastly superior to the old Unix way of everything is a "process".
Normally I would agree with you, but the PIII is going to be around for quite some time. In addition, I don't think you will be seeing the PIV around for quite some time regardless of what Intel says (something about not being able to actually make a product in use quantity!!).
So my 2sense is that this is quite important because anybody upgrading their system should take note of this if performance is an issue.
Thanks for your input. It was simple and useful, but I have to tell you: Mutt ain't that great!!!!
Soooo what you are trying to say is that when you sell your software, you want the whole pot versus having to dole out some to a third party.
My guess is that your concept of how business's really work is slightly skewed to the loopy side: I am sorry to say.
You say "swallow some pride and work on a good C++ interface for GTK and Gnome!". Great add just one more layer onto a system that is already overloaded (Sorry no pun intended!!!).
Get a grip and move on.
Ouch, that was not very nice!!!
Damn, I knew I should have gone into CS program. I stayed in the EE program, and man let me tell you what the chicks looked like in there!!
Woof woof, bow bow and it goes on from there. Not to be shallow...hell what I saying..they were dogs!!!!
To sum up, I am quite envious !!!!!
So what you are telling me is that you:
a) don't work in a technical field
b) you have no grasp of the "bigger picture"
c) you just squeeked by getting that finance degree
d) the bubble you call 'the world' is a 'happy place' for you
If you were a technically based person, you would realize that 70% of all problems were already solved, 20% just can't be solved currently and the last 10% set us who have a clue apart from those like you who don't have a clue.
The new paradigm should be "I am so fricken tired of reinstalling Windows because the stupid user keeps deleting files that they shouldn't".
You need the multi-user ability to keep the normal user from roaching the system because they were click-happy!
Dude, notice any sarcasm???