i didnt like the bbs doc. i dont know if everyone he interviewed was THAT boring, because he would take these long trips out there and then only
show 1-2 mins of the interview on the bbs doc.
Have you watched the BBS documentary? Some of the older sysops lamented
the fact that someone could just install a BBS package and call themselves
a sysop without knowing assembler. :)
Perhaps it was because he interviewed many people, and he had to make a decision about what to include and figured it would be fair to include as ma people as possible. I enjoyed the documentary - It definitely took me back the BBS days, and it's what inspired me to start running a BBS again.
Do you agree or disagree with them, or were you just pointing it out? :)
--- NIGHTFOX wrote --
Re: Anyone With A Tandy 1000
By: Poindexter Fortran to ROB MCCART
Have you watched the BBS documentary? Some of the older sysops lamente
the fact that someone could just install a BBS package and call themsel
a sysop without knowing assembler. :
Do you agree or disagree with them, or were you just pointing it out? :
Do you agree or disagree with them, or were you just pointing it out? :
I kind of agree with them. I think that to use a computer on the Internet you should need a license, like Amateur Radio.
You should have to do something like log into a UNIX shell account and modify your .profile or something...
People can say what they want about the BBS documentary, but it documented
a period in time for many of us, and he got it out there. I've had callers cite it as a reason for calling. And, good or bad, he got out there and did it.
I liked it, personally. I think he captured a period of time but could have ended with a chapter on the current scene and had it be a bit less memoir-ish.
Perhaps it was because he interviewed many people, and he had to make a decision about what to include and figured it would be fair to include as many people as possible. I enjoyed the documentary - It definitely took me
I kind of agree with them. I think that to use a computer on the Internet you should need a license, like Amateur Radio.
You should have to do something like log into a UNIX shell account and modify your .profile or something...
but he could have done some due diligence with some research. I do
remember the documentary saying something about telnet BBSs though.
That's true. It's pretty cool that the BBS documentary has gotten users to call BBSs these days.
You should have to do something like log into a UNIX shell account and modif your .profile or something...
remember the documentary saying something about telnet BBSs though.
he said nothing about telnet bbses.
That's true. It's pretty cool that the BBS documentary has gotten users to call BBSs these days.
i think it's got old sysops to call bbses. i dont think users even know about it.
i think it's got old sysops to call bbses. i dont think users even know abou it.
--- NIGHTFOX wrote --
I can understand your thinking there, but at the same time, I think that i the same way people don't need a license to use a telephone, they shouldn' need a license to use the Internet, as it's a fairly public-domain system. don't think requiring a license to use the Internet would do much to preve abuse, either
That could be true. I wonder how many former BBS users (non-sysops) have se it though. But people who never did use BBSs probably aren't searching for information these days..
I've had several people call my system, never having called a BBS before, who cite that documentary (or perhaps some articles they've read) as the reason for their call. Typically these are younger people with some interest in computer history, who ran into some reference to BBSs while reading stuff online and then followed up on it.
A Progidy CD that I have has a Windows 3.x program called C-- on it.
Have you heard of that one?
I have always been interested in the inner workings of programs so I
tried out C-- to see if it would help me learn C. It didn't.
I tried looking at a Disassembly of several C=64 games to try to see
what made them work but got in over my head. <GRIN>
I haven't written a Q-Basic program in a long time.
I just lurk in here to learn what the folks who know this stuff KNOW.
if your going to learn C, then .... "Learn C", rather than playing around with a C derrivitive. In this age when you can obtain free C compilers
and C++ compilers, there is no reason not to learn C or C++. Now I know
Re: Anyone With A Tandy 1000h
By: Ed Vance to NIGHTFOX on Mon Aug 06 2012 08:19:00
A Progidy CD that I have has a Windows 3.x program called C-- on it.
Have you heard of that one?
I have always been interested in the inner workings of programs so I tried out C-- to see if it would help me learn C. It didn't.
I haven't heard of C--. But from the name, it doesn't sound like it would b good learning tool.. But I'm probably wrong. :)
I tried looking at a Disassembly of several C=64 games to try to see
what made them work but got in over my head. <GRIN>
It is difficult to get the idea of a program from reading assembly code. In most cases, looking at the disassembly is not something that should be required, as higher-level languages are designed to express a program in mor understandable terms. It's especially true these days, since compilers have become smarter and often implement optimizations, such that the disassembly might not represent everything written in the higher-level language, even though it will accomplish the goal.
I haven't written a Q-Basic program in a long time.
I just lurk in here to learn what the folks who know this stuff KNOW.
:) I haven't used a form of Basic in a long time either.. Many progrmaming tasks are probably a little too complicated for Basic.
Nightfox
paradigm used in software development these days, and the functional style of C (and in many examples of C code) seems to teach bad habits when moving to an object-oriented codebase or when object-orientation is desired on a project. Signs of this include many global variables, functions with many parameters, many structs that don't contain functions, variables scattered all over the place, etc..
Re: Anyone With A Tandy 1000h
By: John Guillory to Ed Vance on Wed Aug 08 2012 07:37:14
if your going to learn C, then .... "Learn C", rather than playing
around with a C derrivitive. In this age when you can obtain free C compilers and C++ compilers, there is no reason not to learn C or C++. Now I know
I'm somewhat of the mind that it's better to start out learning C++ rather than C. Object-oriented programming has become pretty much the standard paradigm used in software development these days, and the functional style of C (and in many examples of C code) seems to teach bad habits when moving to an object-oriented codebase or when object-orientation is desired on a project. Signs of this include many global variables, functions with many parameters, many structs that don't contain functions, variables scattered all over the place, etc..
I do think it's useful to learn the C standard library functions, since it contains many useful functions, but I think the object-oriented learning style gained from learning C++ is perhaps more important.
I'm somewhat of the mind that it's better to start out learning C++ rather than C. Object-oriented programming has become pretty much the standardThis state of mind is typical of a lot of people who never learned to
It really depends on what type of programming one is interested in. As a foundation, I think learning procedural (rather than object oriented) programming first is preferrable. In systems and embedded programming, objec
you have to learn a nd b before you get to c.
paradigm used in software development these days, and the functional style of C (and in many examples of C code) seems to teach bad habits when moving to an object-oriented codebase or when object-orientation is desired on a project. Signs of this include many global variables, functions with many parameters, many structs that don't contain functions, variables scattered all over the place, etc..
These are not good C programming practices either. Those are signs of a
bad programmer, not signs of a procedural style (functional style is something different again).
It really depends on what type of programming one is interested in. As a foundation, I think learning procedural (rather than object oriented) programming first is preferrable. In systems and embedded programming, object oriented methodologies are often (dare I say, usually?) not
preferred to procedural (e.g. plain ole C). The vast majority of the programming projects I've been involved with professionally over the past
20 years have been primarily C (with a sprinkling of C++ or assembler).
Most of the object-oriented (e.g. C++) projects I have been involved with were GUI applications programming (e.g. MFC and VCL). I'm not saying one is better than the other in a general sense, but for systems programming (e.g kernel and driver development), C is usually preferred over C++.
I'm somewhat of the mind that it's better to start out learning C++ rather than C. Object-oriented programming has become pretty much the standard
This state of mind is typical of a lot of people who never learned to
program in non object oriented programming. Most people with this mind
set can not program in a non-object oriented language.
Object Oriented
languages tend to be bloated with a lot of overhead that is not
necessary
for the actual program because of the objects. Not every situation
lends
its self to Object Oriented Programming, and not every situation is
recommended to be programmed in Object Oriented Programming. I've yet
to
see a microprocessor with 8k or so of RAM and 8k of EEPROM actually use
object oriented programming to develop programs for the processor. If
someone wants to program in C, and you try to force them to use C++ because
you prefer object oriented programming, that's not much different than
Michelle Obama forcing restauraunts to not sell french frys to children
because she'd rather eat fruit.
paradigm used in software development these days, and the functional style of C (and in many examples of C code) seems to teach bad habits when moving to an object-oriented codebase or when object-orientation desired on a project. Signs of this include many global variables, functions with many parameters, many structs that don't contain functions, variables scattered all over the place, etc..
These are not good C programming practices either. Those are signs of a bad programmer, not signs of a procedural style (functional style is something different again).
True. However, I tend to see those things more often in C code examples tha in examples of object-oriented code.
Nightfox
if you try go join a project where most of the developers are using object-oriented code and you try programming in a non-object-oriented
style, your code additions likely won't fit in as easily as the others, and the other developers will probably be very annoyed at you. :)
object-oriented code and you try programming in a non-object-oriented style, your code additions likely won't fit in as easily as the others, and the other developers will probably be very annoyed at you. :)
Of course the opposite is true too.
I can't imagine someone *only* understanding or mastering object-oriented methodologies being very successful in any programming project/team. But that's just my experienced opinion.
Jose! can you C?Not if you throw bleach in his eyes!
Re: Anyone With A Tandy 1000h
By: Ed Vance to NIGHTFOX on Mon Aug 06 2012 08:19:00
A Progidy CD that I have has a Windows 3.x program called C-- on it.
Have you heard of that one?
I have always been interested in the inner workings of programs so I tried out C-- to see if it would help me learn C. It didn't.
I haven't heard of C--. But from the name, it doesn't sound like it would be
good learning tool.. But I'm probably wrong. :)
I tried looking at a Disassembly of several C=64 games to try to see
what made them work but got in over my head. <GRIN>
It is difficult to get the idea of a program from reading assembly code. In NI>most cases, looking at the disassembly is not something that should be NI>required, as higher-level languages are designed to express a program in more
understandable terms. It's especially true these days, since compilers have NI>become smarter and often implement optimizations, such that the disassembly NI>might not represent everything written in the higher-level language, even NI>though it will accomplish the goal.
I haven't written a Q-Basic program in a long time.
I just lurk in here to learn what the folks who know this stuff KNOW.
:) I haven't used a form of Basic in a long time either.. Many progrmaming NI>tasks are probably a little too complicated for Basic.
Re: Programming
By: Nightfox to Ed Vance on Wed Aug 08 2012 07:19 pm
Re: Anyone With A Tandy 1000h
By: Ed Vance to NIGHTFOX on Mon Aug 06 2012 08:19:00
I tried looking at a Disassembly of several C=64 games to try to see what made them work but got in over my head. <GRIN>
It is difficult to get the idea of a program from reading assembly code. most cases, looking at the disassembly is not something that should be required, as higher-level languages are designed to express a program in m
understandable terms. It's especially true these days, since compilers ha
become smarter and often implement optimizations, such that the disassembl
might not represent everything written in the higher-level language, even though it will accomplish the goal.
I haven't written a Q-Basic program in a long time.
I just lurk in here to learn what the folks who know this stuff KNOW.
:) I haven't used a form of Basic in a long time either.. Many progrmami
tasks are probably a little too complicated for Basic.
Nightfox
you have to learn a nd b before you get to c.
you have to learn a nd b before you get to c.
And then there's D:
http://dlang.org/
Nightfox wrote to Mro <=-
Re: BBS Doc
By: Mro to Nightfox on Thu Aug 02 2012 17:53:35
remember the documentary saying something about telnet BBSs though.
he said nothing about telnet bbses.
I guess I'll have to watch it again.. I thought I remembered a little blurb (as text on the screen), on one of the last episodes, about how there are still some BBSs running on the internet as telnet BBSs. I
guess I could be remembering it wrong though.
i think it's got old sysops to call bbses. i dont think users even know about it.
That could be true. I wonder how many former BBS users (non-sysops)
have seen it though. But people who never did use BBSs probably aren't searching for BBS information these days..
Nightfox wrote to Mro <=-
Re: BBS Doc
By: Mro to Nightfox on Thu Aug 02 2012 17:53:35
remember the documentary saying something about telnet BBSs though.
he said nothing about telnet bbses.
I guess I'll have to watch it again.. I thought I remembered a little blurb (as text on the screen), on one of the last episodes, about how there are still some BBSs running on the internet as telnet BBSs. I guess I could be remembering it wrong though.
He's got a section in the "No Carrier" episode about BBSes on the
Internet. His interviews include the Citadel guys, the telnet-able Commodore 64 BBS, and reference to a couple hundred active systems.
He also mentions the boom in the Russian Fidonet, but that might be in
the "Fidonet" episode.
i think it's got old sysops to call bbses. i dont think users even know about it.
That could be true. I wonder how many former BBS users (non-sysops) have seen it though. But people who never did use BBSs probably aren't searching for BBS information these days..
I was never a sysop, just a user circa 1992-1996. The documentary was pretty inspiring for me to keep chugging away on qodem. The years
from 2004-2007 I got a lot more into BBSes, particularly while playing
a few rounds of TradeWars. After 2008 I've been very much off-and-on
due to my job eating so much of my available time.
... MultiMail, the new multi-platform, multi-format offline reader!
He's got a section in the "No Carrier" episode about BBSes on the
Internet. His interviews include the Citadel guys, the telnet-able Commodore 64 BBS, and reference to a couple hundred active systems.
He also mentions the boom in the Russian Fidonet, but that might be in
the "Fidonet" episode.
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 128:29:02 |
Calls: | 506 |
Messages: | 219668 |