Were this a true representation, linux companies would account for 60%+ of the tech companies listed in the index.
Well, it isn't necessarily just tech companies that make money. And plenty of tech companies have a whole host of Windows machines, and maybe a few Linux servers.
Also, I'd be interested to see if it really is 60%+ running off of Linux. A lot of companies use a little thing called Solaris, you know. Unfortunately, I doubt the BSDs make much of a dent...
This is arguably more of an issue in the compiler than in the kernel,
Not completely... from the SANS Storm Center, the code was as follows:
struct sock *sk = tun->sk;// initialize sk with tun->sk
if (!tun)
return POLLERR;// if tun is NULL return error
The error was that the compiler optimized away the if statement, assuming that tun had already been initialized. The check should have been placed before the sock variable referenced it. Not entirely obvious maybe, but then again, it should have been checked before the assignment.
The check should have been placed before the sock variable referenced it. Not entirely obvious maybe, but then again, it should have been checked before the assignment.
Well, had the check been done first that would be a more reasonable program. But whose to say there isnt a line directly above this that assigns, invariably, a known memory access. Then, say this is a multi-threaded application, and there is a possibility that memory area has been deleted, and if so, you want to take a certain action.
I don't see how this isn't absolutely a compiler issue. There is no way that an if statement that does an error check should be optimized out in this situation, if any.
As previously mentioned, the right behavior would be to warn about this. And to leave the if statement in.
If this had been Windows, the article would have been tagged defectivebydesign.
Well, that's because Windows is--undebatably--defective by design. Not to say that the Linux kernel release model doesn't have its issues. But come on, we all know that the design underlying Windows has been bogus since the start.
Re:Blocks by indentation
on
Hello World!
·
· Score: 2, Insightful
In fact, if you do this to C code, you can run it through "indent" and it will come out clearly indented for you. It sounds like such a program is impossible for python because it depends so much on how things are indented to start with.
Yes, it's impossible in Python. And also unneccessary.
Let's see how smart you are when you get someone's code that isn't so clean in the whitespace department, and won't run anymore once you've opened it and saved it...
The whitespace requirement of Python sucks. I don't like programs whose behaviors are dictated by characters that I can't see and that aren't standard across editors.
If you're so into white space, be a man and use Whitespace.
I'm a fan of perl, Ruby, and bash when it comes to scripting.
I've found this is a nice way to create complicated passwords that are immune to dictionary attacks. Choose a pattern of shift on/off and draw a nice little picture. It's fun and easy. And you could probably write down what the picture is without arousing suspicion, if necessary.
Stop right there. This is probably some of the best advice you'll get.
Of course, it depends on what you want to do. But for the standard, current-track Internet/Cloud/Distributed blah blah blah, many people are dreadfully bad at SQL for how much it applies to their job.
That said, haven't we had enough of these language posts? You can google this and you'll see the same arguments spread out since the birth of the Intarwebs. Everyone has doubts about the language that their using when they don't know many, and want to know what to use.
Just be glad that you didn't attend a program that only taught you Java and never showed you how operating systems really work or what a pointer is. That is a great start.
As someone whose worked in a few of the largest software companies, I can tell you that this really isn't a big concern. You won't get tested on the vagaries of a programming language in an interview. They want to know exactly what you're being taught: that you understand the theories and concepts underlying what you are doing. Projects never use only one language. You often need some glue (Perl, Python, Ruby, etc) and some 'lower-level' code (C++, Java), some data storage (SQL), and maybe a dynamic web page or two (PHP).
Get an internship. This was the best way for me to learn where I fit in on a development team, what sort of thing I felt inadequate at compared to my co-workers, and learned the place of programming language in the work environment. By the time you've gotten your second or third job, most people don't list languages on their resumes anymore.
Once you know a few languages, it shouldn't take you more than a week or two to pick up a new language. On the topic of being an 'expert' at a language, that probably isn't important for your first job. What you need is strong foundations, a good attitude, and hopefully avoiding a tendency to break all the existing code.
If you're really passionate about programming, you'll probably pick up a few languages and be enthusiastic about one or another at a time. I'm currently on a big C++ and Perl kick, as well as loving debuggers in lieu of print statements.
If you're not passionate about this and you want a good 40 hour a week job where you only need to know a thing or two, I don't know what to tell you. I've found this field rewarding because the limit is only how much I'm able to learn and apply. And I've found my employers have recognized that.
Use the right tool for the job. Write readable code in whatever language you write in. Good code is easy to understand, efficient, and concise.
Put on your flame-retardant mecha-suits, this thread is about to get spicy.
Final note: Do everyone a favor and learn how to use grep and other Unix tools to do simple data transformation tasks.
Slashdot Mirror
Were this a true representation, linux companies would account for 60%+ of the tech companies listed in the index.
Well, it isn't necessarily just tech companies that make money. And plenty of tech companies have a whole host of Windows machines, and maybe a few Linux servers.
Also, I'd be interested to see if it really is 60%+ running off of Linux. A lot of companies use a little thing called Solaris, you know. Unfortunately, I doubt the BSDs make much of a dent...
This is arguably more of an issue in the compiler than in the kernel,
Not completely... from the SANS Storm Center, the code was as follows:
struct sock *sk = tun->sk; // initialize sk with tun->sk
if (!tun) return POLLERR; // if tun is NULL return error
The error was that the compiler optimized away the if statement, assuming that tun had already been initialized. The check should have been placed before the sock variable referenced it. Not entirely obvious maybe, but then again, it should have been checked before the assignment.
The check should have been placed before the sock variable referenced it. Not entirely obvious maybe, but then again, it should have been checked before the assignment.
Well, had the check been done first that would be a more reasonable program. But whose to say there isnt a line directly above this that assigns, invariably, a known memory access. Then, say this is a multi-threaded application, and there is a possibility that memory area has been deleted, and if so, you want to take a certain action.
I don't see how this isn't absolutely a compiler issue. There is no way that an if statement that does an error check should be optimized out in this situation, if any.
As previously mentioned, the right behavior would be to warn about this. And to leave the if statement in.
If this had been Windows, the article would have been tagged defectivebydesign.
Well, that's because Windows is--undebatably--defective by design. Not to say that the Linux kernel release model doesn't have its issues. But come on, we all know that the design underlying Windows has been bogus since the start.
In fact, if you do this to C code, you can run it through "indent" and it will come out clearly indented for you. It sounds like such a program is impossible for python because it depends so much on how things are indented to start with.
Yes, it's impossible in Python. And also unneccessary.
Let's see how smart you are when you get someone's code that isn't so clean in the whitespace department, and won't run anymore once you've opened it and saved it...
The whitespace requirement of Python sucks. I don't like programs whose behaviors are dictated by characters that I can't see and that aren't standard across editors.
If you're so into white space, be a man and use Whitespace.
I'm a fan of perl, Ruby, and bash when it comes to scripting.
I've found this is a nice way to create complicated passwords that are immune to dictionary attacks. Choose a pattern of shift on/off and draw a nice little picture. It's fun and easy. And you could probably write down what the picture is without arousing suspicion, if necessary.
I've been a SQL
Stop right there. This is probably some of the best advice you'll get.
Of course, it depends on what you want to do. But for the standard, current-track Internet/Cloud/Distributed blah blah blah, many people are dreadfully bad at SQL for how much it applies to their job.
That said, haven't we had enough of these language posts? You can google this and you'll see the same arguments spread out since the birth of the Intarwebs. Everyone has doubts about the language that their using when they don't know many, and want to know what to use.
Just be glad that you didn't attend a program that only taught you Java and never showed you how operating systems really work or what a pointer is. That is a great start.
As someone whose worked in a few of the largest software companies, I can tell you that this really isn't a big concern. You won't get tested on the vagaries of a programming language in an interview. They want to know exactly what you're being taught: that you understand the theories and concepts underlying what you are doing. Projects never use only one language. You often need some glue (Perl, Python, Ruby, etc) and some 'lower-level' code (C++, Java), some data storage (SQL), and maybe a dynamic web page or two (PHP).
Get an internship. This was the best way for me to learn where I fit in on a development team, what sort of thing I felt inadequate at compared to my co-workers, and learned the place of programming language in the work environment. By the time you've gotten your second or third job, most people don't list languages on their resumes anymore.
Once you know a few languages, it shouldn't take you more than a week or two to pick up a new language. On the topic of being an 'expert' at a language, that probably isn't important for your first job. What you need is strong foundations, a good attitude, and hopefully avoiding a tendency to break all the existing code.
If you're really passionate about programming, you'll probably pick up a few languages and be enthusiastic about one or another at a time. I'm currently on a big C++ and Perl kick, as well as loving debuggers in lieu of print statements.
If you're not passionate about this and you want a good 40 hour a week job where you only need to know a thing or two, I don't know what to tell you. I've found this field rewarding because the limit is only how much I'm able to learn and apply. And I've found my employers have recognized that.
Use the right tool for the job. Write readable code in whatever language you write in. Good code is easy to understand, efficient, and concise.
Put on your flame-retardant mecha-suits, this thread is about to get spicy.
Final note: Do everyone a favor and learn how to use grep and other Unix tools to do simple data transformation tasks.
That's what happens when there's no real world consequences for your behavior (or you think you can avoid them).
Everyone forgetting how often this happens in real life suddenly?
Anyone with a deeper knowledge about IBM's offering know how it compares to clang, or whether there might be a synergy between the two?
We're like our own miniature, awesome country.
If they're only former hackers, then they're useless as security consultants.
well, most people choose to avoid divulging that theyre high tech criminals on a television show. just an idea...