Blue White wrote to Arelor <=-
That business model is at least part of what lead to the dot.com crash
in the late 1990s.
Blue White wrote to Arelor <=-
That business model is at least part of what lead to the dot.com cras in the late 1990s.
Those were heady times. I loved reading fuckedcompany.com and seeing
companies with horrendously non-viable business ideas, like flake.com,
a social network for people who like breakfast cereal.
A company had their comeout party in San Francisco and closed
operations the next day.
That makes sense, the PASCAL class was used mostly to teach data structures and algorithms, then everything else was in C, assembler or LISP. In retrospect I'd rather just jump into C or C++ instead of spending time learning another language.
Honestly, at this point, I can't think of a good reason
to teach C at the collegiate level.
tenser wrote to Dr. What <=-
I used to read "Programming Pearls" in the back issues of the Journal of the ACM back in college and had picked up the book. Sadly, I let it go
a long time ago.
I think you meant Communications of the ACM; JACM is mostly
theory. :-)
Bwk, but yeah. One of the problems was that they were
working in the context of standard Pascal, so they didn't
have some of the nice-ities that say Turbo Pascal brought
to the language (like a string type). It would have been
interesting to see a version of Software Tools in e.g.
Oberon.
Re: Re: RIP Niklaus Wirth
By: tenser to poindexter FORTRAN on Mon Jan 08 2024 03:51 am
That makes sense, the PASCAL class was used mostly to teach data structures and algorithms, then everything else was in C, assemble LISP. In retrospect I'd rather just jump into C or C++ instead of spending time learning another language.
Honestly, at this point, I can't think of a good reason
to teach C at the collegiate level.
C++ (not C) appears to be the collegiate programming language of choice these days.
It was Java for a while, C before that, Pascal before that,
and FORTRAN before that.
tenser wrote to Dr. What <=-
I used to read "Programming Pearls" in the back issues of the Journal the ACM back in college and had picked up the book. Sadly, I let it a long time ago.
I think you meant Communications of the ACM; JACM is mostly
theory. :-)
I'm not sure. By the time I actually joined the ACM, I got Communications. But I'm pretty sure that the back issues I read were called "Journals of the ACM". But I'm uncertain which had "Programming Pearls", but I think it was Communications.
One of the things that surprises me as I get into vintage computers is
how much I mis-remember.
Bwk, but yeah. One of the problems was that they were
working in the context of standard Pascal, so they didn't
have some of the nice-ities that say Turbo Pascal brought
to the language (like a string type). It would have been
interesting to see a version of Software Tools in e.g.
Oberon.
Ya, the Software Tools was mainly about writing unix-c-like stuff in various languages. But C was becoming the dominate tool by then and Software Tools in OtherLanguage wasn't that much in demand.
C++ (not C) appears to be the collegiate programming language of
C++ (not C) appears to be the collegiate programming language of choice these days. It was Java for a while, C before that, Pascal before that, and FORTRAN before that.
boggles the mind. Hoping people move to Rust. C++ is a disaster, and I
can safely say that as someone extremely proficient in the language (up
to C++20)
C++ (not C) appears to be the collegiate programming language of
Every time I see students come out of these courses, or the courses themselves, it's really "C with a C++ compiler and we used a stream".
boggles the mind. Hoping people move to Rust. C++ is a disaster, and I can safely say that as someone extremely proficient in the language (up to C++20)
rust isn't the answer. it just allows you to write crap code that doesn't crash. some might think that's a good thing, but it's just another in a long line of bloated junk.
I live near Santa Cruz, and drive by the old Borland building
occasionally, Seagate's old office (the address was 1 disk drive...) and where I took a UNIX training class at SCO.
tenser wrote to Dr. What <=-
the rest of the research community). So Communications
used to have a lot of papers that were kind of systems-y,
but much less these days. Communications nowadays is
more like a magazine.
Software tools took on a life of its own outside of the
books, and was a thriving project for quite a while,
particularly in the minicomputer era. E.g., it was quite
popular on Pr1me computers.
These days, of course, there's a C compiler for everything;
back then there was a Fortran compiler for everything, and
then a Pascal compiler for everything since that was the
language of teaching for so long.
Oberon was the last of
Wirth's languages, and in many respects, it was closer to
C than to Pascal; as such, it remedied many of the short
comings that Kernighan noted in his polemic about Pascal
(for example, in Oberon, the size of an array is not part
of its type, like in C). Had there been an Oberon version
of the book, it may have been a more natural presentation,
like a C version, for many of the utilities. Of course,
Oberon didn't exist at th time.
tenser wrote to Digital Man <=-
Yeah. My sense observing those classes was that
Pascal was used in the lower year classes, then C
for things like compilers, OS, etc. At one point
I saw a COBOL class offered. *shudder*
rust isn't the answer. it just allows you to write crap code that doesn't crash. some might think that's a good thing, but it's just another in a long line of bloated junk.
I've heard claims like this before, but I haven't experienced it myself.
I came to Rust very skeptical, but figured if it could deliver on even a quarter of its claims I'd be way ahead of C; it's pleasantly surprised me, and I've been using it professionally for about 5 years now. One _can_
I've heard claims like this before, but I haven't experienced it myse I came to Rust very skeptical, but figured if it could deliver on eve quarter of its claims I'd be way ahead of C; it's pleasantly surprise and I've been using it professionally for about 5 years now. One _ca
What are you using it for? I've heard people like Rust, but none of the companies I've worked at have used Rust at all.
Yes. A lot of programmers seem to _really_ love complexity,
and some I'm sad to say view their ability to handle complexity
as a sign of superiority over those around them who, perhaps,
can't keep quite as much in their heads at one time. It's not
great.
I remember when they "Numerical Recipes in FORTRAN" book became
"Numerical Recipes in C". C seemed like the wrong language for the
higher-level stuff that FORTRAN did well.
Office Politics 101. Now, that would be a valuable class!
As vaulable as Data Structures, FORTRAN and C, that's for sure.
Adept wrote to Dr. What <=-
Teaching social skills to a nerdy crowd is probably hard work, too, so good teachers there would be _invaluable_.
But the second time through? It was fun! Just kinda neat to see how the various things fit together.
Yup. Plus having teachers who have spent some time in the corporate
world would have been very helpful. I don't think I've ever had a
teacher that hadn't spent his whole career in academia.
My dad taught 8th grade science, so I was exposed to that at a very
early age. That laid the base for me when he bought home a TRS-80 Model
I for the summer.
Adept wrote to Dr. What <=-
That _does_ make sense, though that sort of thing is so hard --
teaching _is_ a skill, so it kind of becomes like training an astronaut
to drill, or teaching drillers to be an astronaut.
repair logic skills. And with those skills I started doing tech support
at least by 5th grade when I got called out of a class to fix a
computer.
And, while I pride myself in being able to explain technical things to less-technically-inclined people, I've never had the slightest clue on
how to get people to _think_ in that sort of fashion, even for people
who do well with logic outside of the computer realm.
They may not be the best teachers, but they do have more knowledge than
a teacher who has never had a "real job".
don't prepare you for that. And for geeky people, that prepartion would have been very useful.
They were bored until I told them that they could program the computer
to do their math homework. They had so much fun that they didn't
realize that they worked harder to write that program than the would
have done just doing the homework.
And I found that you can't get people to think in certain ways. The
best you can do is explain things in many different ways, hoping that
one will stick.
Adept wrote to Dr. What <=-
It does seem like something that might be ideal as guest lecturers of
some sort.
But always kind of hard to say what would be best, at least without
lots of well-designed studies.
And who knows how one _tests_ for such things.
Neat! I do remember, in my Physics class, where we could put stuff onto the calculator as notes for whatever we were doing.
So I wrote a program for a particular set of problems, which, of
course, meant that I knew the formula _really_ well, rather than it
being remotely useful as a cheat sheet.
They may not be the best teachers, but they do have more knowledge th a teacher who has never had a "real job".
It does seem like something that might be ideal as guest lecturers of
some sort.
the prof gave us the specs. Every other class or so, he would change
the specs - just a bit - or add another small requirement (scope creep). At the end, he told us why he did it that way - to simulate what you
will have to deal with on the job.
I did the same thing for Chemistry class in high school. My classmates said "The teacher won't accept the printout". But he did - along with
the source code for the BASIC program I wrote. He then said I didn't
have to do the homework for this anymore because if I could teach a computer how to do it, I must have mastered the concept.
Adept wrote to Dr. What <=-
Though, in school, I remember switching IDE, language, code repository, and probably lots of other things with each different set of classes,
so by the time things became requirement creep it just seemed like,
"okay, someone else has another set of requirements for us to deal
with".
But, yeah, not _quite_ the same, since theoretically the professor gave enough information at the beginning to know the final outcome.
We handed in the printout along with the logic, but it just got a
question mark or something on it, so I think we just confused the professor. But someone used to humans doing logic things is going to
have a different idea of what's possible to brute force than someone
who thinks it through with a computer.
Closer to the real world than you might think. Especially if the tech lead of the project suffers from neophilia.
It's no wonder why their IT dept stayed in the 70's so long.
Kinda make me think that that college needed to take a page from
Dartmouth and their BASIC program. It got a very high percentage of people involved in computers - and not just the one going into computers.
Adept wrote to Dr. What <=-
Obviously, with K-Mart, it wasn't blockchain or AI that would've been
the issue. And we're mostly talking about business people. For tech people, honestly, while it's exhausting to be changing things all the time, it's also pretty exciting to be trying new things all the time.
The other problem is that something that already works is generally
going to outperform something that might be better, but will have
teething problems. Sticking in the 70s is fine for a lot of things.
I've experienced too much pain where we had a developer who decided New Tech X was cool and then built a critical production process around it. Never mind that no one else on the team was interested in New Tech X, didn't know New Tech X and New Tech X didn't do a much better job than the current tech.
Bob Worm wrote to Dr. What <=-
Oh, yes. A hundred times... and usually said dev then leaves the
company and nobody can maintain this completely bespoke thing they left behind with no documentation!
As one of my university lecturers used to say - there's a difference between being clever and being smart...
I've experienced too much pain where we had a developer who decided New Tech X was cool and then built a critical production process around it. Never mind that no one else on the team was interested in New Tech X, didn't know New Tech X and New Tech X didn't do a much better job than
the current tech.
problem. Many companies out there will support you - for an arm, a leg and your first born. But that's usually a good indication that you
should be moving on. And they were trying to do that, they just kept derailing themselves.
I used to read "Programming Pearls" in the back issues of the Journal the ACM back in college and had picked up the book. Sadly, I let it a long time ago.
I think you meant Communications of the ACM; JACM is mostly
theory. :-)
C++ (not C) appears to be the collegiate programming language of choice these days. It was Java for a while, C before that, Pascal before that, and FORTRAN before that.
the rest of the research community). So Communications
used to have a lot of papers that were kind of systems-y,
but much less these days. Communications nowadays is
more like a magazine.
Ya, I let my membership lapse because they were moving away from computer technology and getting into more social-issues-and-stuff.
Adept wrote to Dr. What <=-
Yeah, shiny new things. Though, also, it's generally more fun building something up yourself than figuring out what the heck the last twenty people were doing with this code that's supposedly self-commenting.
Adept wrote to tenser <=-
I get Communications of the ACM, and it doesn't seem to have
Programming Pearls, at this point in time.
Which means _nothing_ for this discussion, but it sounds like an interesting column.
Though Communications of the ACM is still interesting, though I'm not
sure I've found any of it to be useful, practically, at this point.
Or, heck, not sure how useful my ACM membership has been, but I like
being a part of it, regardless.
I've dealt with (and still deal with) some developers who have an
attitude of "I don't need to document it. It's self-evident." Ya, to you, who did the research and wrote it. But it's greek to someone else who didn't.
For my magazines, I use a 3 issue test: When the renewal comes up, I look through the last 3 issues. If I can easily find at least 1 article that
I want to keep for a long time, I renew. If not, it's not worth my
money.
I used to think the same way. Even ignoring my 3 month test. But it reached a point that, for me, I really didn't want to be associated with it anymore.
it anymore. And I had to give up my acm.org email address that I had
for ages.
Adept wrote to Dr. What <=-
it anymore. And I had to give up my acm.org email address that I had
for ages.
And you actually _used_ it?
Or I'm worried that my personal domain is getting e-mails sent to spam folders. But I long ago went away from having e-mail connected to
things that other people control, because they tend not to have my interests at the front of their mind.
That's why I don't use my gmail account anymore. But setting up my own domain, email server, etc. was just too much work to be of value to me.
I did locate a service that I seems to be trustworthy (so far). It's
pay, of course, which helps to push it to the more trustworthy category.
I used to read "Programming Pearls" in the back issues of the Jo the ACM back in college and had picked up the book. Sadly, I le a long time ago.
I think you meant Communications of the ACM; JACM is mostly
theory. :-)
I get Communications of the ACM, and it doesn't seem to have Programming Pearls, at this point in time.
Which means _nothing_ for this discussion, but it sounds like an interesting column.
That's why I don't use my gmail account anymore. But setting up my own doma email server, etc. was just too much work to be of value to me. I did locat service that I seems to be trustworthy (so far). It's pay, of course, which helps to push it to the more trustworthy category.
I liked the Tagline about XEROX Alto You used.
Why isn't Multimail available in the APP Files on this thing.
Sometimes I have to "Praise The Lord ANYHOW".
Ed Vance wrote to poindexter FORTRAN <=-
The Tagline "Albatetize the Alphabet" brought to mind this:
ZYXW VUTS RQ PONML KJIH GFED CBA
Those spaces between the backward Alphabet mean pause(s).
On a good day I can say the above in 3 point 5 seconds.
On a Prodigy(sp?) CD years ago was a C- - Program and I
think some instructions for C - - too.
NOW C=64 BASIC and IBM DOS 2.11 BASIC I DUG.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 124 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 11:11:30 |
| Calls: | 7,808 |
| Calls today: | 12 |
| Files: | 9,388 |
| U/L today: |
1 files (340K bytes) |
| D/L today: |
2,573 files (1,309M bytes) |
| Messages: | 398,579 |
| Posted today: | 5 |