Compare cert salaries and plan your next career move
Asif Dasl wrote: » I have to say, if I ever meet someone who does Assembly I'll have to shake their hand and congratulate them and wonder how they stop themselves going postal... lovely example code here.
paul78 wrote: » The first language I ever learned was Applesoft Basic, followed by Pascal, and then Fortran.
erpadmin wrote: » In terms of programming languages where you compile something into an executable (which I believe this thread is about) then no, SQL does not qualify. Yes it is a "language," smarty-pants [smile], but if all you knew was SQL, then you'd have a hard time printing "Hello World" if you were not familiar with any other OOL languages.
paul78 wrote: » Whew... glad I'm not the only one. I consider Java, c#, and VB.net scripting languages too They are technically intepreted languages. I also think that any language with a garbage collector which is pretty much most intepreted languages is a scripting language.
erpadmin wrote: » SQL really isn't a programming language. When you look at what SQL is, you'll find that it's really not as a complex as Java or any other Object-Oriented Language. SQL is terribly easy, believe it or not.
TheShadow wrote: » Real programmers learned 8080/8086 assembly and used MASM or TASM to assemble it on an IBM AT or an Apple II with a CPM card for 8080 only. They learned C by reading K&R 1 and nothing else, then learned C++ using Cfront . All other languages are simply details except COBOL and maybe APL which one normally refuses to admit to. Remembering the time when most users knew how to use debug to write code. Grabs coat and hat and heads for the door with evil grin
paul78 wrote: » LOL -I thought real programmers hand-assemble 6502 code. Hides under desk to avoid the projectiles.
RobertKaucher wrote: » This is inaccurate. C# is compiled into Intermediate Language (which makes them cross platform) and JIT'ed into machine specific code when they are run. C# is not interpreted, regardless of what WikiPedia might say. The .NET specification is very clear about how this occurs (I cannot comment on Java as I have only a general knowledge of it).
RobertKaucher wrote: » I believe the same is true for all the .NET languages like VB.NET, Visual C++, and F#.
RobertKaucher wrote: » Regardless, in this case you are using the word "interpreted" where you should be using "managed". And to say that managed languages are nothing more than scripting languages is a gross oversimplification.
RobertKaucher wrote: » Either way this is simply a matter of implementation and there have been interpreted versions of C. Any language can be run on the interpreted model.
paul78 wrote: » Interesting. I did not realize there was a JIT compiler involved. That would certainly explain the comments that I've heard from colleagues regarding the performance characteristics of .Net. I assumed incorrectly that it was purely interpreted based on the tidbits that I read about .Net reflection. Java can utilize something similar.
paul78 wrote: » I am curious if you have seen any adoption of f# - I found it fascinating that Microsoft was developing a functional language. Is it really a functional language like John Backus envisioned. I often wonder if functional languages will really find widespread adoption other than as a niche.
paul78 wrote: » ... Developing a Windows desktop application in unmanaged C or Assembly is probably not a good idea. Similarly, it’s a bad idea to write an operating system kernel in a high-level language. One pet-peeve that I do have is when applications are developed using high-level languages like Java or a .Net language and then the developer tightly couples code into the operating system. Right – I have seen interpreted versions of C and it still eludes me on its utility other than an academic novelty, learning tool, or embedded application macro language.
N2IT wrote: » I edited this ABAP SAP development
vCole wrote: » $beer | %{$_.Drink()}
RobertKaucher wrote: » I'll leave the semantics of what people believe a programming vs. a scripting language is and I'll just say that SQL, especially when you consider a variant like T-SQL or Postgresql, can be exceptionally complex and the deeper you go into relational algebra and relational calculus the more you understand that. If all you are really working with is basic CRUD operations and a few JOINS it's not that bad. But the concepts of the relational model that SQL implements are not very intuitive and even seasoned developers trip up on them all the time because they can't understand how to think in a set-based, relational model.
RobertKaucher wrote: » Sooooo... Have you heard of Singularity? Can't get more academic than that! Oh yes, the Kernel is written in a variant of C#.
erpadmin wrote: » I think it is awesome that you have really gotten that deep with SQL. Perhaps one really should consider taking up calculus so that one can take one of those CS courses that deal with relational database theory (be it at an undergraduate or graduate level, though calc should undoubtedly be taken at an undergrad level.) Thankfully, for most day-to-day operations a DBA has to deal with, it really doesn't have to be that deep. But I will qualify that with saying it would not be a bad idea for it to get that deep. CRUD has always been good enough for a lot of DBAs (and I dare say, most developers I've worked with.)
Compare salaries for top cybersecurity certifications. Free download for TechExams community.