Sponsored Content
Full Discussion: A rant...
The Lounge What is on Your Mind? A rant... Post 303023570 by wisecracker on Wednesday 19th of September 2018 10:42:53 AM
Old 09-19-2018
A rant...

Hi guys...
(Apologies for any typos etc...)

This is basically a rant.

I have been doing kids level projects and writing code to suit since around 1982, for the uProfessor, for the Sinclair Spectrum and later for the QL, IBM-XT in MS-DOS and after that for a 386DX40 up to Windows 95, until I dedicated most my work for the AMIGA platform from 1996.
Since then I have built and coded for Linux and let us not forget AudioScope.sh for almost any *NIX style bash terminal.
It has been a hard slog to learn, even badly, 6502, Z80, 8088/8086/80186, x86, PIC and other assembler code as well as varying dialects of C, BASICs of many variants, ARexx, Python from version 1.4.0, Shell scripting, HTML 4+ and others I have since forgotten.

<rant>
Well I came upon an advert for Lego Boost, (a supposed programming app'), and in this advert it quotes:

"""
It's easy to keep things simple (...) but there is almost no limit to what you can program.
"""
WHAT??? Almost No limit?
Well maybe ALMOST NO LIMIT within the confines of these Lego kits. But believe me, doing my stuff has taught me a great deal about kids and their so-called abilities along with the programming languages I have used.

It also, in a promotion video, quotes - paraphrasing:
"""
Kids can learn how to code easily with this app'.
"""
SWEEPING STATEMENTS!

Well this app' is much like 'scratch':
Scratch - Imagine, Program, Share
Of which I tried for a nine year old to _learn_ how to code to create his own games. Not too successful I am afraid, the said nine year old boy's attention span was about 10 minutes at best and a book teaching scratch, (and python using pygame), that we bought him as a(n) XMAS present never ever got read.
He kept telling his parents he wanted to do programming.
After decades of doing projects mainly for kids from around eight years old I soon discovered that attention spans of even ten year olds was small and everything had to be designed to be built by a youngster, under supervision, within an hour at the absolute most.

Well there is programming and there is programming.
Learning a computer language is NOTHING like the same as drag and drop systems in a tight, closed, _eco_system_ where programming error reports don't exist.
Coding from the ground up may not be glamorous but you get to know how things work language wise and you soon find that the 'ALMOST NO LIMIT' sure has numerous limits.
Building hardware that has to be made from almost RAW materials is much more difficult than kits as those kids that have tried my stuff learn how to solder, mark out and drill boxes, how to lay out components, cut tracks etc on stripboard/Veroboard to get any home brew hardware to work.
</rant>

Questions to my friends on here:

What is/are your opinion(s) on my rant?
Do you think that apps' like 'scratch' and 'Lego Boost' actually teach kids programming?
How did you become the professional(s) that you are?
Other?
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Where can I rant?

First of all, apologies to the admins for not reading the rules totally and missing the bit about ranting off about other OSs. But that raises a question. Where do you go to have a good rant, to vent your disgust at various corporations and thier hideous behaviour? :confused: (2 Replies)
Discussion started by: u6ik
2 Replies

2. What is on Your Mind?

One liners, quick rant...

Hi fellas and fella-esses... There are numerous threads on here where people ask for, and often expect, solutions to difficult problems solved using _one_liners_. Why do they insist as such when it is virtually no different in execution time with well thought out indented code? Is it me... (12 Replies)
Discussion started by: wisecracker
12 Replies
C(7)						       BSD Miscellaneous Information Manual						      C(7)

NAME
c, c78, c89, c90, c99 -- The C programming language DESCRIPTION
C is a general purpose programming language, which has a strong connection with the UNIX operating system and its derivatives, since the vast majority of those systems were written in the C language. The C language contains some basic ideas from the BCPL language through the B lan- guage written by Ken Thompson in 1970 for the DEC PDP-7 machines. The development of the UNIX operating system was started on a PDP-7 machine in assembly language, but this choice made it very difficult to port the existing code to other systems. In 1972 Dennis M. Ritchie worked out the C programming language for further development of the UNIX operating system. The idea was to imple- ment only the C compiler for different platforms, and implement most parts of the operating system in the new programming language to sim- plify the portability between different architectures. It follows that C is very well adapted for (but not limited to) writing operating systems and low-level applications. The C language did not have a specification or standardized version for a long time. It went through a lot of changes and improvements for ages. In 1978, Brian W. Kernighan and Dennis M. Ritchie published the first book about C under the title ``The C Programming Language''. We can think of this book as the first specification of the language. This version is often referred to as ``K&R C'' after the names of the authors. Sometimes it is referred to as C78, as well, after the publishing year of the first edition of the book. It is important to notice that the instruction set of the language is limited to the most fundamental elements for simplicity. Handling of the standard I/O and similar common functions are implemented in the libraries shipped with the compiler. As these functions are also widely used, it was demanded to include into the description what requisites the library should conform to, not just strictly the language itself. Accordingly, the aforementioned standards cover the library elements, as well. The elements of this standard library are still not enough for more complicated tasks. In this case the provided system calls of the given operating system can be used. To not lose the portability by using these system calls, the POSIX (Portable Operating System Interface (for Unix)) standard evolved. It describes what functions should be available to keep portability. Note, that POSIX is not a C standard, but an operating system standard and thus is beyond the scope of this manual. The standards discussed below are all C standards and only cover the C programming language and the accompanying library. After the publication of the book mentioned before, the American National Standards Institute (ANSI) started to work on standardizing the language, and in 1989 they announced ANSI X3.159-1989. It is usually referred to as ANSI C or C89. The main difference in this standard were the function prototypes, which was a new way of declaring functions. With the old-style function declarations, the compiler was unable to check the sanity of the actual parameters of a function call. The old syntax was highly error-prone because incompatible parameters were hard to detect in the program code and the problem only showed up at run-time. In 1990, the International Organization for Standardization (ISO) adopted the ANSI standard as ISO/IEC 9899:1990. This is also referred to as ISO C or C90. It only contains negligible minor modifications against ANSI C, so the two standards are often considered to be fully equivalent. This was a very important milestone in the history of the C language, but the development of the language did not stop. The ISO C standard was later extended with an amendment as ISO/IEC 9899 AM1 in 1995. This contained, for example, the wide-character support in wchar.h and wctype.h. Two corrigenda were also published: Technical Corrigendum 1 as ISO/IEC 9899 TCOR1 in 1995 and Technical Corrigendum 2 as ISO/IEC 9899 TCOR2 in 1996. The continuous development and growth made it necessary to work out a new standard, which contains the new features and fixes the known defects and deficiencies of the language. As a result, ISO/IEC 9899:1999 was born in 1999. Similarly to the other standards, this is referred to after the publication year as C99. The improvements include the following: o Inline functions. o Support for variable length arrays. o New high-precision integer type named long long int, and other integer types described in stdint(3) and inttypes(3). o New boolean data type; see stdbool(3). o One line comments taken from the C++ language. o Some new preprocessor features. o A predefined identifier __func__ and a restrict type qualifier. o New variables can be declared anywhere, not just in the beginning of the program or program blocks. o No implicit int type. Since then no new standards have been published, but the C language is still evolving. New and useful features have been showing up in the most famous C compiler: GNU C (gcc(1)). Most of the UNIX-like operating systems use GNU C as a system compiler, but the various extensions of GNU C, such as attribute(3) or typeof(3), should not be considered standard features. SEE ALSO
c89(1), c99(1), cc(1), cdefs(3) Brian W. Kernighan and Dennis M. Ritchie, The C Programming Language, Prentice Hall, Second Edition, 40th printing, 1988. STANDARDS
ANSI, X3.159-1989. ISO/IEC, 9899:1990, Programming languages -- C. ISO/IEC, 9899 AM1. ISO/IEC, 9899 TCOR1, Programming languages -- C, Technical Corrigendum 1. ISO/IEC, 9899 TCOR2, Programming languages -- C, Technical Corrigendum 2. ISO/IEC, 9899:1999, Programming languages -- C. ISO/IEC, 9899:1999 TCOR1, Programming languages -- C, Technical Corrigendum 1. ISO/IEC, 9899:1999 TCOR2, Programming languages -- C, Technical Corrigendum 2. ISO/IEC, 9899:1999 TCOR3, Programming languages -- C, Technical Corrigendum 3. HISTORY
This manual page first appeared in FreeBSD 9.0 and NetBSD 6.0. AUTHORS
This manual page was written by Gabor Kovesdan <gabor@FreeBSD.org>. BSD
March 30, 2011 BSD
All times are GMT -4. The time now is 05:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy