You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
4You nailed it. Having a multi-line screen rather than just a printing tty or single line makes it easier, but without a source file concept it's still line oriented.JDługosz– JDługosz2016-02-11 07:16:35 +00:00Commented Feb 11, 2016 at 7:16
-
The fact that the system is an 8-bit architecture isn't really the limiting factor, though. Now, the fact that said system might have only a few kilobytes of RAM and a handful of kilobytes of ROM, and possibly even no permanent storage (if your casette tape recorder broke)...user– user2016-02-11 20:37:13 +00:00Commented Feb 11, 2016 at 20:37
-
it's still hard to imagine coding without a text editorphuclv– phuclv2016-02-12 14:12:33 +00:00Commented Feb 12, 2016 at 14:12
-
@LưuVĩnhPhúc Well, there are plenty of emulators for running "the real thing", such as almost any 8-bit home computer, or MSDOS and its GWBASIC with dosbox. Just as an example, you could get one of the many C64 emulators, and then Google to find its User's Guide as PDF :-)hyde– hyde2016-02-12 15:31:35 +00:00Commented Feb 12, 2016 at 15:31
-
3@phuclv - Hard to imagine coding without a text editor now. At the time, hard to imagine the inconvenience of having to use a text editor, save it, and compile it before it could be run ... and that's really what came next to the PC world; Pascal and C. Both compiled languages, both freely editable with a text editor, both definitely not a programming environment in and of themselves (BASIC was both programming environment and runtime environment). Pascal was my next language, and in many ways quite liberating. Definitely more powerful. But in other ways, a little less thrilling.DavidO– DavidO2019-09-03 02:55:51 +00:00Commented Sep 3, 2019 at 2:55
|
Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you