but instead of that, you are just hitting others who are giving their own opinion according to the best of their knowledge |
If I consider your opinion to be contrary to mine, I can opt to challenge it. What, I can transmit my opinion about X, but not my opinion about your opinion about X?
I never STATED that its the ONLY possible method... [...] It was my opinion... |
That's true in the sense that you didn't explicitly say "the only way you can ...", but it's implied by your phrasing, so you might as well have.
See, the thing is, something doesn't become opinion until you define it as such. If I say, "the Sun orbits the Earth", what a rational person would do is ask me for evidence of my claim. He can also add "you're full of ****". Now, I can either try to back up my claim with hard evidence, or say "**** you, it's my opinion". This has a name in debate, but I can't remember it ATM. Basically, I'd be trying to win by refusing to debate with him (since opinions are unfalsifiable, any debate on whether the Sun indeed orbits the Earth is pointless).
Now, if I say "
I think the Sun orbits the Earth", that starts out as an opinion, and someone else could either ignore me, or try to share their own thoughts.
And perhaps you didn't read further about the use of gcc in linux for compiling from command line which would prompt him to probe more about compilation options and methods |
You may be right about that. However, many if not all other compilers offer a command line to compile from.
I did not advocate in favor of gcc providing any kind of superior insights into the compilation process, but it does give some insight |
Same as any other compiler.
You are welcome to suggest him another path you think may be good for him, |
There's paths not to take, but there's no reason to pick any single of the other ones.
rather than questioning others. |
See, there you go again. When you make any kind of statement, you leave yourself open to being questioned. If you don't like that, all you have to do is not say anything. Easy, right?
And? What conclusion are you drawing from that? |
Well, that's not really the same. For one,
Writing in a very high level language/a high level language/Assembly/hex/punch cards makes you lazy. Back in the day, we had to manage our own memory/use CPU registers/memorize opcodes/spend all the bleeping day making holes into cards/walk ten miles in the snow carrying vacuum tubes the size of your cat and fish moths out of relays. |
wasn't intended to be taken seriously. It was an ironic way of showing how things in CS have gotten more abstract and
simpler easier over the years, and how there's always people who like the old ways better.
Now,
as i can imagine from where he is doing engineering, most of his teachers wont have much idea abt linking apart from theoretical knowledge abt compilation... and the only IDE installed on the computers in the college labs may be Turbo C++... they wont even tell the class about using its debugging features... |
seemed to me like it was an incomplete thought. Sure, it doesn't have to be. Maybe I read it wrong and you weren't trying to reach any conclusion, but that's what it seemed to me, which is why I asked.