.NET is killing natural of programming from inside !?
-
a problem with .net is that it's almost a complete duplicate of java from top to toe, with some difference, which of course did reduce the java code out there - but now you have two code bases that are only slightly different. real men only code in lisp or haskell, anyway. and real women always use (obj c?) - well, cobol was developed by a woman. if some one ( like oracle ) developed a vm that ran java and c#, that would be an interesting development/but microsoft would sue for $1,000,000,000.00 or maybe 1.5/!/!/!/ Google could buy microsoft and do it, but they are too busy these days making cell phones and they could never merge that culture which would throw a lot of people back into the job market. intel could build a processor that would run c# or java, but only the defense dept would buy it. However, the sad story is that java guys write java, and c# guys write c# and they hardly ever write to each other. actually i don't think .net will kill i.t. we can still find some paper tape readers if we need, too. what could kill i.t. is really good cheap scotch, but that most likely would end badly.
From what I gathered from that ridiculous post is that you now nothing about either java or .net.
-
its just a private idea , really .net is not killing natural of programming? i mean in .net sometimes with one line you can do something wich needs more than 10 lines! it makes programming so simple and faster but in this situations i dnt feel im programming really ! maybe because my codes complete so fast :laugh: ! whats your idea? agree or not?
-
i just ask a question from experts !
-
No - it's just moving the "grunt work" into a tested, reliable code base. Just as we all used to do ourselves, but with that code base being consistent and shared among a huge number of users instead of different for each company or even programmer. All .NET does is let us concentrate on the application instead of getting bogged down by the details of the low level stuff we have written so many times before.
If you get an email telling you that you can catch Swine Flu from tinned pork then just delete it. It's Spam.
You know, I agree with this, but I think that therein lies a problem somewhat. For folks that have coded low level grunt work stuff lots and lots, this is really nice and is a huge help because it lets you spend your valuable time on more productive things. What about, though, people that are just starting out? By not having to do the low level stuff, they miss out on learning the foundational things that the experienced people learned cold through repetition. It seems like there's the potential for newer people to miss out on valuable experience. Before too long you get people that can do quite a bit of things with the language, yet they are confused about the difference between value types and reference types or some other foundational skill. What do you guys think?
-
You know, I agree with this, but I think that therein lies a problem somewhat. For folks that have coded low level grunt work stuff lots and lots, this is really nice and is a huge help because it lets you spend your valuable time on more productive things. What about, though, people that are just starting out? By not having to do the low level stuff, they miss out on learning the foundational things that the experienced people learned cold through repetition. It seems like there's the potential for newer people to miss out on valuable experience. Before too long you get people that can do quite a bit of things with the language, yet they are confused about the difference between value types and reference types or some other foundational skill. What do you guys think?
I can't say that you are wrong: I think people should have to do the basics first, perhaps learn to code in assembler on bare hardware, and work their way up to higher level languages so that they do know the basics. But... Computing is now a relatively "mature" field. If you look at other mature professions, they don't start with first principles either. A car designer doesn't get a blank sheet of paper and have to reinvent the ball bearing before he can start work on thinking up how to get fuel into an engine without using a carb or fuel injection. Instead, they buy in that technology from companies who specialise in that field. Doctors don't mix their own medicines - they let pharmaceutical companies do years of research, then tell them what tablet does what to whom. Bakers don't grow their own wheat, mill it, and make bread - they get farmers to do the mucky bits. I think the problem is that we aren't quite in a mature enough profession - we haven't decided how low everybody needs to know and what we can afford to "farm out" yet. But we are moving into an era when the general "jobbing" programmer knows only the high level stuff, and "experts" who know what is going on beneath that are a rare breed. Pity.
If you get an email telling you that you can catch Swine Flu from tinned pork then just delete it. It's Spam.
-
i just ask a question from experts !
-
Maybe I wasn't clear enough. People are interested in your end-product. How you do it, with how much effort or code, it's mostly irrelevant for them. dont-call-yourself-a-programmer/[^]
but it was a question, wanna say , somthing very useful can be very harmful in long time ! but i just ask a question from experts to know whats their idea about this! i dnt want indict .NET to bad thing! i am debator to .NET !
-
but it was a question, wanna say , somthing very useful can be very harmful in long time ! but i just ask a question from experts to know whats their idea about this! i dnt want indict .NET to bad thing! i am debator to .NET !
"its just a private idea , really .net is not killing natural of programming? i mean in .net sometimes with one line you can do something wich needs more than 10 lines! it makes programming so simple and faster but in this situations i dnt feel im programming really ! maybe because my codes complete so fast ! whats your idea? agree or not? " If you insist ona specific answer, then ask youself: what exactly is the "natural of programming"? Writing a lot of mumbo jumbo in another mumbo jumbo? Or maybe solving problems and making money with a product? The amount of code is relevant only to the first option.
-
"its just a private idea , really .net is not killing natural of programming? i mean in .net sometimes with one line you can do something wich needs more than 10 lines! it makes programming so simple and faster but in this situations i dnt feel im programming really ! maybe because my codes complete so fast ! whats your idea? agree or not? " If you insist ona specific answer, then ask youself: what exactly is the "natural of programming"? Writing a lot of mumbo jumbo in another mumbo jumbo? Or maybe solving problems and making money with a product? The amount of code is relevant only to the first option.
no its not any mumbo-jumbo!i asked myself what is Natural of programming ! i think its some codes with dim face, which we act with hardwares directly!
-
no its not any mumbo-jumbo!i asked myself what is Natural of programming ! i think its some codes with dim face, which we act with hardwares directly!
Unless you work in research and academia, read the link I gave you. Hope you will get it. Programming is a craft, a profession. It has tools that fit different tasks. You need to hang a picture on the wall? You need a hammer and some nails, not a microscope and scalpel.
-
Unless you work in research and academia, read the link I gave you. Hope you will get it. Programming is a craft, a profession. It has tools that fit different tasks. You need to hang a picture on the wall? You need a hammer and some nails, not a microscope and scalpel.
i read it... you are right too! but remaind i dnot want indict anything, i just tried to get others ideas!
-
a problem with .net is that it's almost a complete duplicate of java from top to toe, with some difference, which of course did reduce the java code out there - but now you have two code bases that are only slightly different. real men only code in lisp or haskell, anyway. and real women always use (obj c?) - well, cobol was developed by a woman. if some one ( like oracle ) developed a vm that ran java and c#, that would be an interesting development/but microsoft would sue for $1,000,000,000.00 or maybe 1.5/!/!/!/ Google could buy microsoft and do it, but they are too busy these days making cell phones and they could never merge that culture which would throw a lot of people back into the job market. intel could build a processor that would run c# or java, but only the defense dept would buy it. However, the sad story is that java guys write java, and c# guys write c# and they hardly ever write to each other. actually i don't think .net will kill i.t. we can still find some paper tape readers if we need, too. what could kill i.t. is really good cheap scotch, but that most likely would end badly.
