TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

BYTE Magazine: The C Language (1983)

141 pointsby bleakgadflyabout 10 years ago

14 comments

kasajianabout 10 years ago
The thing to keep in mind with regard to the significance of the C language and this particular time-frame is that personal computers were becoming capable of hosting a C compiler. Today, we don&#x27;t think about the ability to host a C compiler to be a constraint, but with early micro-computers it was. For instance, the Atari-era of computers, could not easily host a C-compiler. There was a version called &quot;Deep-Blue-C&quot; which is a subset. In fact, &quot;compilers&quot; were rare. More common were interpreters because they required less resources.<p>Running alternative operating systems on early micro-computers, such as CP&#x2F;M on an Apple-II, provided more capabilities, and ability run slightly more powerful software<p>The IBM PCs and clones around that time-frame certainly had the power to host compilers, Turbo-Pascal was one early example.<p>Also, back then, with some exceptions, most commercial products on micro-computers were written in Assembly language, not a high-level language. This was done for performance. This was common.<p>However, C was generally regarded as producing code that&#x27;s fast enough that enabled programmers to use it instead or coding directly in Assembly. Certainly, with the new crop of computers, the faster IBM PCs (ATs), Macintosh, Atari ST, Amiga, all had sufficiently sophisticated compilers where that became standard issue. Pascal and then C.<p>So around 1983, C was become something that people were starting to take a much closer look at because of the availability of hardware and operating systems that allowed them to use C. It is not that C was not available previously, but it was used by a different class of developers, the ones with S-100 Bus machines running CP&#x2F;M of some form.. these are machines that often required you to re-target the BIOS from source when you add more RAM.<p>C also became the default language for Windows. For the Mac, it was a form of object Pascal at first, and then moved to C++ with MacApp.<p>This is an example of C being powerful enough, being at the right place and at the right time to where now it&#x27;s the lingua-franca of system software.
评论 #9253611 未加载
niraiabout 10 years ago
the magazine is from 1983, so the C language was not news by then.<p>Flipping the pages of the magazine is awesome - the ads on every other page are just like time travel.<p>It has been so long since I have last seen the Charlie Chaplin ad for IBM: <a href="https://archive.org/stream/byte-magazine-1983-08/1983_08_BYTE_08-08_The_C_Language#page/n81/mode/2up" rel="nofollow">https:&#x2F;&#x2F;archive.org&#x2F;stream&#x2F;byte-magazine-1983-08&#x2F;1983_08_BYT...</a><p>I was a kid back then with a Commodore 64
评论 #9253383 未加载
评论 #9253969 未加载
评论 #9253251 未加载
评论 #9253550 未加载
评论 #9254000 未加载
评论 #9254951 未加载
评论 #9253544 未加载
评论 #9254118 未加载
评论 #9253879 未加载
watmoughabout 10 years ago
Interesting how times change.<p>I remember as a child, being bitterly disappointed with how bad Ferrari Formula 1 was on the Amiga, and I ended up blaming the slow speed on C. That colored my attitude toward the language for years, though once I started working, I ended up writing C++ mainly.<p>Nowadays, I&#x27;ve reverted to coding in C99, simply because I can easily find libraries for &#x27;hard things&#x27; like generating jpeg files, and because cleanly written C performs like almost nothing else, and because console programs have a refreshing simplicity about them, especially if you put all the cool stuff in a library, then just hash up a text-based front-end.<p>There&#x27;s a <i>heck</i> of a lot you can do in 1000 lines of C, and it&#x27;s fun to write too, without the hassle and slow performance of an IDE like VS or XCode.
t1mabout 10 years ago
Byte Magazine had a history of forward-looking articles for microprocessor and software technology. There were entire issues devoted to LISP in (1979), Smalltalk (1981), and the 68000 (1986). It wasn&#x27;t that C was new, it wasn&#x27;t, but in 1984 it was certainly new to their target audience, which was the micro-computer industry.<p>While it&#x27;s true that C compilers were available for MS-DOS and CP&#x2F;M in &#x27;84, these were by no means mainstream, and were prohibitively expensive. Turbo Pascal was still taking the world by storm, and it would be another three years before Borland would introduce an &#x27;ANSI Compatible&#x27; C compiler and IDE - the much anticipated (by me anyway) Turbo C in 1987.
5555624about 10 years ago
It&#x27;s not too clear, but if you click on the link in the upper left corner, Byte Magazine Volume 08 Number 08 - The C Language (<a href="https://archive.org/details/byte-magazine-1983-08" rel="nofollow">https:&#x2F;&#x2F;archive.org&#x2F;details&#x2F;byte-magazine-1983-08</a>), there are a number of different options for downloading the entire issue.
hvsabout 10 years ago
OT, but on page 70 there&#x27;s an ad for the Franklin Ace 1000, which was ultimately found to be infringing on Apple&#x27;s copyrights (they directly copied portions of the ROM from the Apple II). It was a landmark case for computers:<p><a href="http://en.wikipedia.org/wiki/Apple_Computer,_Inc._v._Franklin_Computer_Corp" rel="nofollow">http:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Apple_Computer,_Inc._v._Frankli...</a>.
mutagenabout 10 years ago
p 52: &quot;With the freedom implicit in C&#x27;s use of pointers come certain risks. Much of C&#x27;s growth over the last decade has been in ways of detecting erroneous uses of pointers without restricting the ability to write efficient code when necessary.
评论 #9254859 未加载
munificentabout 10 years ago
Obvious in retrospect, but I never realized that ++ and -- were created specifically to map to native instructions and not just as a convenience for &quot;_ = _ + 1&quot;.
评论 #9254884 未加载
kzhahouabout 10 years ago
There&#x27;s an interesting article by William Gates in that issue:<p><a href="https://archive.org/stream/byte-magazine-1983-08/1983_08_BYTE_08-08_The_C_Language#page/n400/mode/1up" rel="nofollow">https:&#x2F;&#x2F;archive.org&#x2F;stream&#x2F;byte-magazine-1983-08&#x2F;1983_08_BYT...</a>
评论 #9255726 未加载
stoxabout 10 years ago
This was not the first mention of C in Byte. That happened in 1977, if memory serves correct.
评论 #9253530 未加载
alayneabout 10 years ago
I worked with a lot of K&amp;R C in the early 1990s, getting software to run on newer compilers and Solaris. I actually learned C++ before I learned C. It still looks strange to me. I believe the parameter declaration style comes from ALGOL (please correct me).
评论 #9253731 未加载
devsd0about 10 years ago
c is just a flash in the pan. I will stick with Cobol thanks.
评论 #9253368 未加载
talleyrandabout 10 years ago
The articles about C programming and UNIX basics are models of clear, crisp, and concise writing. Really nice.
brlewisabout 10 years ago
(1983)