Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:real cost benefit new language (Score 1) 520

The cost of a new language is that programmers have to take time to learn it and develop an infrastructure for it, things such as software libraries to do math, communications, user interfaces, etc. Not every programmer will learn every language, and, in particular, learn every language well, which may be a handicap for employers as they have a smaller pool to hire their programming teams from in their chosen language.

Companies have to spend time deciding which language to use, with a lot of people pitching this language over that one, and developing the languages will include a lot of duplication of effort.

The benefit is that new languages may improve productivity, with emphasis on 'may'. There's a lot of controversy about how good some languages are that have been widely deployed for a long time. Ideally, there will be a shakeout and the best languages will win, but I'm not convinced that's the way things happen. More likely it's whichever language gets the best salesmen out there selling it, and, to paraphrase Mae West, 'goodness has nothing (or little) to do with it.'

The earliest writing systems were complex and required years to learn. When easier to learn alphabets came along, the old scribal class would resist because it meant they couldn't command the high pay and respect they were used to. I suppose that might also exist to some extent with programmers and programming languages. It's hard to know who is being genuinely fair in judging languages.

The holy grail for employers and people who just want to use their computer to get work done, as opposed to people who make a living writing code (and I was one of those people who made a living writing code for over 20 years), is to have an artificial intelligence program where you can just explain what you want to it in human language and it will generate an optimal block of binary code to do it (after clearing up any ambiguities in your human language specification).

Comment Re:Peanuts (Score 1) 411

'having the code read like sentences' was one of the goals of COBOL wasn't it?

I studied COBOL in college, and the best Professor in the Department was a big fan, but I rememder it as being generally perceived as 'uncool'. (And I was the guy who, when given a choice of which language to write a project in, would write it in Univac 1100 assembler. This was before 'C' became widely known or implemented.)

Comment Re:The alternative (Score 1) 411

Actually, I think you can have 'fluff' in assembler, though when writing assembler you're usually very focussed on some very specific thing that needs to be done, and sometimes every CPU cycle counts, so in practice, yes, you'll see less fluff.

I have just enough experience with Perl that I think I know what you're talking about with 'too-clever Perl'. There must be some great examples of 'too-clever APL' out there unless the mag tapes and IBM 2311s they were saved on have all Gone South by now.

Comment Re:'Nothing' is an exaggeration (Score 2) 136

There are options to one's lifestyle that matter vis a vis cost of living. If you live frugally in a high cost of living area, you may still be spending more than if you live frugally in a low cost of living area, but you can probably save/invest more money from that high salary, so it may pay off as part of a long term plan to build up capital.

I also realize that inflation can wipe out savings. Any long term plan is something of a gamble. My point is, that one shouldn't be too simplistic about weighing the alternatives.

Comment Re:I thought the 'lazy evaluation' was clever (Score 1) 76

I see most replies are critical that you didn't read the original article. (Maybe they don't get the 'lazy evaluation' part if they've never dabbled in functional programming.) Maybe they don't know about the actually rather serious philosophical speculations that our universe may be a simulation. Anyway, I for one thought it was clever.

Comment What is the future supposed to be? (Score 1) 258

A thousand years from now is Homo Sap supposed to still be the pinnacle? A million years from now? Are we just supposed to evolve 'naturally' the way we did away from homo erectus? (And do you suppose that went easy on Homo E?)

I realize that since we H. Saps are still sort of in charge we may try for a gentler transition that has probably happened in the past, but we do want a transition don't we? I mean, we don't want everything to be just us with our limitations a zillion years from now do we?

Comment Re:The beaks won (Score 2) 138

I think it has more to do with being light weight since birds fly. After all, not all birds dig for grubs. Of course, not all birds fly anymore, but maybe the common ancestors did.

Another thing, birds evolved from reptiles. I watched the science documentary series 'Your Inner ...' (Inner Fish, Inner Reptile, etc). They mentioned that reptiles can replace their teeth but the teeth are undifferentiated, whereas mammals, who only get two sets, have them custom designed with a tight fit so some are good for tearing flesh, some for grinding, etc. Presumably the teeth the birds lost would have been less efficient reptile teeth.

Comment nobody knows the future but AI is gonna happen (Score 1) 417

Unless we wipe ourselves out or reduce ourselves to a stone age existence, AI will happen. Whether it will replace ordinary human beings in a gradual, gentle way (maybe preserving us awhile the way we preserve threatened species now) or whether it will be something more unpleasant, that's what is hard to predict. There's bound to be surprises however it goes.

But suppose somehow the folks opposed to AI could stop it. Then what? 1000 years from now, would ordinary human beings still be doing their thing? Would we have managed to create a utopia or would there still be human vs human strife? And a million years from now, would they still prevent anything 'superior' from replacing ordinary humanity? Is that a future to be yearned for?

Perhaps it will be a kind of middle way of transhumans with artificially enhanced intelligence, with the artificial part of the transhumans becoming a larger and larger part of the total being until the purely human part is just a tiny vestigial thing.

Comment The original 68000 interrupts were inadequate (Score 1) 147

The original 68000 was almost there for running a real multi-tasking OS. But, it didn't save enough state on the stack during an interrupt. You couldn't guarantee restoring a process's exact state when returning from an interrupt. I heard stories of designs that used two 68000s where one was running one step behind the other. I don't know how true they were. I see on the wikipedia that Motorola fixed that with the 68010 in 1982 and that's when the 68008 came out. So maybe the 68008 doesn't have that problem.

Comment Re:In theory (Score 1) 130

Hmmm, I really like that saying, but I learned it as
"In theory, theory and practice are the same; in practice, they're different." It might even be a Unix fortune. I've seen it attributed to Yogi Berra. (A lot of things are attributed to Yogi Berra by the way, "Deja Vu all over again" is another one.)

In my day (and I'm old enough to have actually seen Yogi Berra play, though he was in the outfield by then), computers were not that common, so going to school was a place to have access to a computer. I did notice that by the 1990s, employers would give you some kind of test to make sure you weren't a fraud during the job interview, no matter what your resume said.

Comment Re:Thinking back late 70's Algol, SNOBOL etc (Score 1) 547

I was a CS major in the late 70s too. We learned to program at least a smattering of Norwegian University Algol on our Univac 1106, as well as SNOBOL (StriNg Oriented and symBOlic Language), APL and something called XL6 (a 'list processing language' so obscure it's not even in the wikipedia, but I'm pretty sure I got the name right.) In other classes I learned some specialty languages, Dynamo (Dynamic Models) and GPSS (General Purpose Simulation System).

Whatever happened to Algol anyway?

As I recall, SNOBOL was actually pretty cool, sort of like Pearl in that you could learn to do some useful things very quickly in it. I don't know that the code was all that readable even to the coder after 3 weeks though, since I never had to look at my code 3 weeks later. And I think even the professor who taught it complained about some of the choices for characters to use as operators. Still, I have this lingering feeling that somehow SNOBOL was a language that was unfairly passed over, maybe because of the comical name.

Slashdot Top Deals

Kleeneness is next to Godelness.

Working...