Hey wait doesnt Runescape run on Java?
Actually it runs on
"computers".
"java" is a
"programming" language.
well, to correct myself, it technically runs on a JVM which runs on computers...
I searched the 'net for asm and got this mess.
I do see one reference, further down, for assembly language. I looked a little closer at the Java references, and one talks about manipulating bytecodes. Perhaps that is a reference to assembly language...hey, the poll says Asm. No capitals...is it an acronym? Wasn't sure what to think, so I searched asm, and got the previously mentioned results. If assembly language was meant, then it ought have been specified. I found more references to Oracle than Java when I searched.
I threw in FORTRAN in my prior post as a salute to an oldie-but-goody. What about Perl, Python, Ruby, and Ruby on Rails?
Just some more examples...
well, I assumed ASM, I don't think I'd call it an acronym... I think it got the name simply from the file extension (*.ASM).
And now, a brief opinion on some programming languages:
HTML:
I swear to god if I hear another person call this a
programming language... and NO it is NOT a technicality! it's like calling a cheap reliant a corvette! complete misinformation! I mean if you tell somebody your a "programmer" and they subsequently discover that you really are just a markupper, whose going to look silly then? Huh? I can assure you, it won't be your neighbors dog. or his cat, for that matter.
BASICA:
The IBM Personal Computer Basic
Version A2.10 Copyright IBM Corp. 1981, 1982, 1983
60455 Bytes free
Ok
I have to say, my favorite thing about BASICA and GWBASIC (it's younger sibling) is that it's fun to start it on other peoples computers, just to challenge them to get out! "exit" Nope. "quit". Nope. Yes, for some reason the command to quit is "SYSTEM". how intuitive.
QBASIC:
If anybody programs in this- good for them. stick it to Microsoft! "yes, I know you guys have the .NET framework and the windows API and all that, but I prefer to use a 20 year old programming tool that was included on DOS 5 and 6 as a crappy (although effective) substitute for REXX in IBM's PC-DOS. Also I hate compiling programs, so I'll just keep them in BAS format and CHAIN them together into 5 separate modules containing code that is completely unrelated."
My advice for anybody stumbling upon this program, is to quickly (and I can't stress that enough, is to type Alt+F, X. You're safe. And then get...
QuickBasic 4.5
I am still amazed at the people who actually write programs in this language and think that they are financially viable. I mean, sure, they may be viable to do what you intend, but there is no way a company that runs Windows is ever going to invest in a 16-bit DOS executable for mission-critical tasks. On the bright side, what used to cost a goodly sum in the old days, can now be had for free on abandonware sites, because apparently after a software developer stops working on a product for a specified period of time, it becomes free!
QuickBasic PDS 7.1:
Much better. Much Better. 4.5 is childs play compared to QBX. ROCK ON QBX! I love you!
VB-DOS:
whats better then QuickBasic PDS 7.1? a more expensive version with little text windows that capitalize on the success of Windows 3.1 without even having to commit to actually running on it!
Turbo Pascal:
a good language, I just never got into using it seriously *censored* shame too, it's a great language. I think I was put off by it's lack of an exponentiation operator. I mean, it has no exponentiation operator, but it has a IN operator for it's "set" types?
Perl:
a great language, but anybody has to admit that it is definitely the ASCII equivalent of vomit. I mean, it's alright right after it comes out of you, but come back after a few months, and it'll be unrecognizable (not to mention quite putrid). You heard me, Larry Wall.
Visual Basic
I've used Visual Basic version 2 and 6, and have also messed around in the others (VB1 humours me to no end), and I find that although it lacks a lot of what other languages offer, it makes up for it in learning curve. Given, I probably could have learned Microsoft QuickC instead of QuickBasic, and thus moved on to Visual C++ 6.0 and then C#, but then I'd have a high-paying job, a corvette, a hot wife, and three kids, but no time to visit computerhope. I think I'll stick with my Visual Basic.
C++
oh wait, I know C++, sort of. only enough to know I don't want to know the rest. Any language verbose enough to include templates as part of a language definition doesn't garner further attention from me then a theoretical analysis.
C#,Visual Fred, and .NET
I don't think I could loathe anything anymore then I do the .NET framework. I really don't. All I know is that Microsoft has this Vendetta against Sun Microsystems for cancelling their license agreement that let Microsoft develop J++, because they kept adding "Microsoft Only" extensions to it. So now Microsoft is dedicated to creating it's own JVM that it calls the CLR, and then spends the rest of it's time trying to cover it up. It's really great, because just like java, the simplest program's memory requirements skyrocket with the price of gas. Difference being they won't come down, because you also have this memory leak called "garbage collection". Did I mention I hate garbage collection? Reference counting may require programmer attention but it's a *censored* of a lot better to code properly first off then to have your objects sitting idle taking up god knows how much memory until the garbage truck rolls by that week to take out the trash. Of course the irony is that Garbage collection essentially needs reference counting anyway, so why not just delete the object when it is... deleted, rather then wait some arbitrary period of time to delete a bunch of different objects? My theory is that doing that prevents the creation of new algorithms, like "Stop and Copy" which means the program stops and you need to copy your OS system files back onto your system drive because they got corrupted, or "Mark And sweep", which means that all the objects get deleted at once leaving the allocated memory a hideous fragmented mess. (OK, so I don't have a good wordplay joke for the second one, so sue me).
The closest thing to .NET that I like would have to be P-code, simply because it isn't completely retarded, and actually has benefits.
Wow, that is probably my longest post ever. oh well.