"Well I don't give a damn about my bad reputation." - Printable Version +- QB64 Phoenix Edition (https://qb64phoenix.com/forum) +-- Forum: Chatting and Socializing (https://qb64phoenix.com/forum/forumdisplay.php?fid=11) +--- Forum: General Discussion (https://qb64phoenix.com/forum/forumdisplay.php?fid=2) +--- Thread: "Well I don't give a damn about my bad reputation." (/showthread.php?tid=842) Pages:
1
2
|
"Well I don't give a damn about my bad reputation." - TDarcos - 09-02-2022 "Well I don't give a damn about my bad reputation." - Joan Jett, Bad Reputation Basic has gotten a bad reputation, some of it deserved, some of it "sneering" by people who use "real" programming languages. Or they don't know, or don't realize, the Basic languages of today "are not your father's Basic." Let's look at some of the criticisms people have of basic.
RE: "Well I don't give a damn about my bad reputation." - mnrvovrfc - 09-02-2022 Sadly a lot of it was brought about by M$. A lot of it was going from BASCOM to QuickBASIC/BASIC PDS to VBDOS to VB for Windows. There are a lot of folks around who remember how it was like to do stuff on an 8-bit computer which help maintain the "bad reputation" in the opinion of others who want it to run fast, who want to be seduced by the eye, who needs to get the latest technology... for bragging or anything else. It's not just BASIC, it's other programming languages. There must have been a lot of resistance to what was added to C in particular, according to the "gcc" manual on chapter 5 or 6 "Extensions to the C language". Defending C code in K&R style could be as ornerous as trying to run BASIC code, which has not much more than "INPUT", "PRINT" and "GOTO", anyhow on 64-bit systems. BASIC PDS v7.1 had ISAM built in but didn't go anywhere. It was one attempt for in-house support for databases or something else for office. It must have lost favor to Word Basic, something I suddenly discovered reading PC MAGAZINE in the late 1990's... I program in Lua a few times. A lot of code written for v5.1 and earlier has to be rewritten for the latest v5.4 if it must do heavy processing with integers such as checking out bits or creating WAV files. In the earlier release had to use "bit32" module, but in v5.4 must mess around with: https://www.lua.org/manual/5.4/manual.html#pdf-string.unpack P.S. There is an awful lot of hating on "LET". On Timex Sinclair you had to use "LET", there was no other choice. It was how the computer worked. No I didn't actually have one, I discovered this in a BASIC programming book for children. I didn't like the "joke" offered about it by the previous maintainer of the QB64 wiki... he could have at least offered a link to Wikipedia about the British computer. RE: "Well I don't give a damn about my bad reputation." - bplus - 09-02-2022 Quote:Is trivially easy to learn. ... What idjet bitches about that? RE: "Well I don't give a damn about my bad reputation." - CharlieJV - 09-02-2022 (09-02-2022, 04:44 PM)TDarcos Wrote: "Well I don't give a damn about my bad reputation." I enjoyed reading that. Thanks for taking the time! RE: "Well I don't give a damn about my bad reputation." - Kernelpanic - 09-03-2022 Quote:"Well I don't give a damn about my bad reputation." Yeah! I see it! I read and heard such profound reflections more than 20 years ago. And what did it do? Microsoft has driven the development of programming and website design. In IE from 4.01 onwards, you could click on individual points in an image for the first time to go to a corresponding website. And so forth . . . Microsoft revolutionized the web and it normalized the computer like the phone. Who knows where one would be today without Microsoft - maybe with the rip-off Apple, or with the Frickel-Linux? Your claims about C and Cobol are not correct. And anyway, what's the point, if I know one programming language, I don't have a problem with others? Really? What does Basic have to do with C, and C with Cobol, and all three with Java? Nothing, absolutely nothing, to do with each other. Except something like For, If, While, and so on. Well, the usual phrases I've known for over 20 years. Nothing News! RE: "Well I don't give a damn about my bad reputation." - TerryRitchie - 09-03-2022 I know quite a few other languages, some well, others I would need a refresher on (like Assembler, yikes) but I like programming in BASIC (QB64 to be exact) because it's fun. I actually like creating everything from scratch and maintaining my own libraries of utilities. QB64 is nothing like the BASIC of the 80's because of the power and new features, but it can be if you want, and that's amazing too. BASIC was designed to be a tool to let people enter programming quickly. The same for PASCAL. It's a shame languages like these aren't revered more. BASIC has been around now since 1965 and still widely used. That tells you something. Hell, I even enjoyed VisualBasic (well, until .NET came along). Someone mentioned ISAM too. VisualBasic for DOS had ISAM as well and I wrote many database programs back in the early to mid 90's for a company I was with. It's a shame that wasn't developed further. RE: "Well I don't give a damn about my bad reputation." - OldMoses - 09-03-2022 Any time I've attempted to learn a new language, I've noticed that they inevitably use the same root concepts of iteration, logical branching, variable assignment, etc. Well a programming language is for talking to a computer, and unless you're flipping bit switches, you're doing that through an interpreter. So maybe someone could enlighten me... if I wished to speak to a Russian gentleman, and there was an English speaking interpreter and a French speaking interpreter in the room, why should I learn French in lieu of employing the English interpreter? All that trouble for a few nuanced bits of vocabulary? So meanwhile, QB64 enables me to do stuff that I never dreamed of doing 20 years ago with QBasic on a 386. Certainly there are differences in capabilities, but there are workarounds for those and I suspect that a well crafted program in BASIC will perform as well or better than a poorly coded one in some other language, even one coded "close to the metal". RE: "Well I don't give a damn about my bad reputation." - TDarcos - 09-03-2022 (09-02-2022, 06:41 PM)mnrvovrfc Wrote: P.S. There is an awful lot of hating on "LET". On Timex Sinclair you had to use "LET", there was no other choice. It was how the computer worked. The reason for the "LET" statement was when Basic was invented in 1965, there wasn't much work on things like parsing, and also, these people were working in systems sometimes only having 8L - 4K of ROM, 4K of RAM. Requiring every line start with a keyword makes the job of writing a compiler or interpreter easier. Later people figured how to get around this restriction. I mean, I think there is a correlation between language capability and compiler complexity. The fewer things the person has to do in writing code, the easier it makes their job, and the more complex the compiler has to become. I can obviously say that the more things you require the programmer to do, the simpler your language processor can be. It's a choice of who does the work, the compiler writer or the application programmer. The difference being the application programmer's workspace is "where the rubber meets the road." The compiler user (programmer) is the one that, in the end, who has to use the language to write their application. Application programmers, unlike compiler writers, can't push their work onto the user of their program. RE: "Well I don't give a damn about my bad reputation." - TDarcos - 09-03-2022 (09-02-2022, 07:16 PM)bplus Wrote:Quote:Is trivially easy to learn. ... The ones that declare, without ever having learned a language, that it's no good for certain types of applications. I mean, there are some features that are in certain languages that are brilliant, and others that are brain-dead moronic. Let's look at C. Absolutely brilliant: the "symbol =" notation, e,g. a +=5 instead of a = a+5; a *= b instead of a= a*b etc. Brain dead moronic: case sensitivity of identifiers. It's hard enough keeping all the variables and manifest constants in a program in your head, now you also have to remember the capitalization of them. It also increases the possibility of confusion, if you have multiple variables with the same spelling. I mean, I am neither a language bigot nor a word processor bigot. I use both Word Perfect and Open Office/Libre office. I also use QB64, QB64 PE, wxBasic, Free Basic, Free Pascal, and when necessary, C and C++. Each has strengths and weaknesses. RE: "Well I don't give a damn about my bad reputation." - mnrvovrfc - 09-03-2022 (09-03-2022, 09:30 PM)TDarcos Wrote: Let's look at C. Absolutely brilliant: the "symbol =" notation, e,g. a +=5 instead of a = a+5; a *= b instead of a= a*b etc. Brain dead moronic: case sensitivity of identifiers. It's hard enough keeping all the variables and manifest constants in a program in your head, now you also have to remember the capitalization of them. It also increases the possibility of confusion, if you have multiple variables with the same spelling.Say to the people that brought us both C and Unix they created a few things which are "brain dead moronic". Also some companies depend on obfuscation for "defending" their "property": I saw an example of working C++ code which was nothing but "A", "a", "B" and "b" -- advertising on M$DN if I'm not mistaken long ago. :/ |