Slashdot Mirror


Obsolete Technical Skills

Ponca City, We Love You writes "Robert Scoble had an interesting post on his blog a few days ago on obsolete technical skills — 'things we used to know that no longer are very useful to us.' Scoble's initial list included dialing a rotary phone, using carbon paper to make copies, and changing the gas mixture on your car's carburetor. The list has now been expanded into a wiki with a much larger list of these obsolete skills that includes resolving IRQ conflicts on a mother board, assembly language programming, and stacking a quarter on an arcade game to indicate you have next. We're invited to contribute more."

603 comments

  1. Assembly isn't obsolete! by nurhussein · · Score: 5, Insightful

    Systems programmers worth their salt can at least read assembler output. It's a valuable skill when debugging kernel errors.

    1. Re:Assembly isn't obsolete! by Zondar · · Score: 5, Informative

      I guess they're forgetting about things like optimized device drivers, true performance-oriented embedded systems architectures, microcode segments, and anything to do with hardware development.

    2. Re:Assembly isn't obsolete! by Oscaro · · Score: 5, Insightful

      Every programmer should know something about assembly. It gives you a better insight on what the compiler does for you, on how a function is invoked, on how an array is accessed, and so on.

    3. Re:Assembly isn't obsolete! by DMUTPeregrine · · Score: 3, Insightful
      From TFA:

      Still used when the utmost performance or very low-level control (e.g. in bootloaders) is desired. Still may be used particularly for small, frequently used sub-routines. On simple processors (not Intel/AMD), it is still viable.
      They didn't forget, it's just a niche skill. Assembly is obsolete for most purposes. You don't see it in application programming. You rarely see it in systems programming. You never see it in web programming. Even games don't use it anymore.
      --
      Not a sentence!
    4. Re:Assembly isn't obsolete! by SharpFang · · Score: 4, Insightful

      Actually, assembly is very relevant for embedded devices - except i386 assembly that is :)

      Sure 'smartphones' etc start getting programmable in high-level languages but OTOH simple microcontrollers enter more and more of daily appliances. You don't write firmware in assembly for a DVD player anymore, but you write it for a toaster or a bicycle lamp, devices that 5 years ago didn't have any firmware or programming capability. The frontier is and likely always will be assembly, and even though the frontier keeps moving and likely in 5 years the bicycle lamps will be programmable in Java, maybe ballpens will be programmable in assembly.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    5. Re:Assembly isn't obsolete! by MichaelSmith · · Score: 3, Interesting

      Every programmer should know something about assembly.

      Two hundred million VB, PHP and Ruby programmers want to disagree with you. But you are right. Assembly is as much a part of the system as transistors and stack pointers. My first system had a 6502 with a BASIC interpreter in ROM. The back page of the instruction book had the 6502 instruction set printed on it (lucky it wasn't a Z80). That was much more interesting for a 13 year old than basic.

    6. Re:Assembly isn't obsolete! by Oscaro · · Score: 3, Insightful

      Also, compilers are written by people, and compilers' output is assembly code.

    7. Re:Assembly isn't obsolete! by Zondar · · Score: 3, Insightful

      When you can write a bootloader that fits in the unused sectors on a floppy disc using Java or C++, come talk to me and I'll be impressed. Until then...

    8. Re:Assembly isn't obsolete! by MichaelSmith · · Score: 1

      compilers' output is assembly code

      I had a compiler on CP/M which generated assembly and sent the output to an assembler. I don't think GCC works that way. It probably generates machine code directly. Maybe it has a symbolic "assembly" layer inside.

      DEC C on alpha/OpenVMS had an option to output assembly. I don't think it generated it otherwise.

    9. Re:Assembly isn't obsolete! by smittyoneeach · · Score: 1

      The development environment is a form government.
      Just offload all of that heavy "thinking" stuff onto the development environment.
      You'll be much happier for it; really, you will.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    10. Re:Assembly isn't obsolete! by MichaelSmith · · Score: 4, Funny

      You never see it in web programming.

      Well not reputable web programming anyway.

    11. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Assembly language is more or less human-readable machine code (depending on how clever your assembler is). If a compiler generates machine code (i.e. it's not interpreted, but a real compiler), it's effectively generating assembly language.

    12. Re:Assembly isn't obsolete! by Oscaro · · Score: 5, Informative

      I don't think GCC works that way. Actually, it does. You can use "gcc -S" to write the assembly output on a file. I find it very instructive, and you can see the effects of the various optimization options...
    13. Re:Assembly isn't obsolete! by Technician · · Score: 3, Informative

      I would say understanding and using the manual octal grouped switches on the front of a PDP11/35 is high on the list. Using the halt/run switch is a lost art.
      http://en.wikipedia.org/wiki/Image:Pdp-11-40.jpg
      Running a shmoo curve on magnetic core memory is an obsolete skill.
      http://ieeexplore.ieee.org/iel5/20/22897/01066073.pdf?arnumber=1066073

      --
      The truth shall set you free!
    14. Re:Assembly isn't obsolete! by nogginthenog · · Score: 2, Informative

      I had a compiler on CP/M which generated assembly and sent the output to an assembler. I don't think GCC works that way. It probably generates machine code directly. Maybe it has a symbolic "assembly" layer inside.

      Actually most compilers work this way.
    15. Re:Assembly isn't obsolete! by deathy_epl+ccs · · Score: 1

      compilers' output is assembly code

      I had a compiler on CP/M which generated assembly and sent the output to an assembler. I don't think GCC works that way. It probably generates machine code directly. Maybe it has a symbolic "assembly" layer inside.

      To be fair, you're picking nits... most folks mean both assembly and machine code when they say either. Yes, there is a difference... us old school demo coders used to write our code in a monitor, and I'm sure we weren't the only masochist coders around. However, it's a pretty fine point and one that's probably not worth being terribly picky about these days.

    16. Re:Assembly isn't obsolete! by stretch0611 · · Score: 1

      I do not think it will ever go truly obsolete. I have learned assembly programming on three different Microprocessor architectures and I do not think it will ever be truly obsolete.

      I admit I never write assembly code anymore and I only did write it in a classroom. However, learning assembly taught me a lot about a computer's architecture that I probably would not have learned otherwise.

      When you know how a computer works on a basic level, you better understand what goes wrong when you are debugging problems. A very simple example of this is if you add two positive integers together and wind up with a negative result, you understand that you are overflowing the result. I may not directly use my assembler skills, but knowing them helps me indirectly and makes me a more efficient developer than someone that does not understand the computer like I do.

      --
      Looking for a job?
      Want your resume written professionally?
      DON'T USE TUNAREZ!!!
    17. Re:Assembly isn't obsolete! by PhilHibbs · · Score: 2, Informative

      I had a compiler on CP/M which generated assembly and sent the output to an assembler. I don't think GCC works that way. It probably generates machine code directly.
      There is a very close to 1:1 mapping between assembly language and machine code. The only thing assembly gives you that machine code doesn't is readability and labels.
    18. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 2, Informative

      The machines I use every day don't even have floppy drives. The article points out that this is a niche skill, not one that's widely useful. For what it's worth, I write a lot of assembly language code but it's all for Atmel AVRs.

    19. Re:Assembly isn't obsolete! by bentcd · · Score: 5, Funny

      Well not reputable web programming anyway. "Reputable Web Programming and One Hundred Other Mythical Beasts": a fantastic compendium of modern urban legends :-)
      --
      sigs are hazardous to your health
    20. Re:Assembly isn't obsolete! by Opportunist · · Score: 2, Interesting

      I'm glad to see that the first post already challenged the uselessness of asm.

      But it goes beyond kernel debugging. Any Antivirus researcher worth his weight (or at least a fraction thereof) knows x86 assembler to the core. When the automatic analysis fails, you still toss the malware into a disassembler and you have to find out why the analyser failed. What system did they use this time to foil your analysis attempts?

      Although you do notice that also on the "other side" (i.e. at the people writing those critters), asm progging becomes a dying art, you still have encryptors and manipulation schemes that try to obfuscate malware so you can't just simply 'read' them. For obvious reasons, you only get the executable into your hands, but rarely if ever the source.

      So yes, asm knowledge is still very valuable. asm programming might be a 'dying skill', since it is rarely necessary (except in very specialized areas) to be able to write asm code, but knowing how to read it will be very useful and necessary for years to come.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    21. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 1, Interesting

      How about an entire desktop operating system written in asm that fits in a 1.44 floppy and runs incredibly fast even under a slow machine emulator like Qemu?
      Not that I'm pushing the use of assembly when writing applications, but this example should teach something to those people who ignore the art of optimizing things, then just tell you to buy a faster machine.

    22. Re:Assembly isn't obsolete! by Aladrin · · Score: 1

      You may be happier, but you may not be a better programmer for it.

      Yes, I let the IDE do the heavy 'thinking' most times, but I also find it helpful to have an understand of what's going on. I have never actually programmed anything in assembly, but just learning how things worked definitely made me sharper when it came to the logic necessary to make things happen.

      In fact, I've never found a language yet that made me say 'Wow, I'm dumber for having learned that.'

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    23. Re:Assembly isn't obsolete! by pgillan · · Score: 2, Informative

      At several points I've taken assembly classes, and I've come away from them feeling like I learned some incredibly valuable information about how computers "actually" work, at their most fundamental level. The odd thing is, though, that I can't remember anything specific about assembly. Nothing. I know it informed some of my thinking about other things, and I probably have answers to questions I wouldn't otherwise have known, but I couldn't tell you what or why. That being said, I also recommend it for anyone who works with computers, for some reason.

    24. Re:Assembly isn't obsolete! by Zondar · · Score: 2, Interesting

      It also fits in the unused boot sectors of a hard drive, but the point was that there are fewer sectors and less space to play with on a floppy... so maybe I should have worded it that it *even* fits in the unused boot sectors of a floppy or hard drive.

      Last I checked, his bootloader could load nearly any OS for x86. Doing all of that in a few KILOBYTES of otherwise unused space would be just about impossible with anything other that assembly.

    25. Re:Assembly isn't obsolete! by kvezach · · Score: 2, Funny

      Not to mention black-box reverse engineering, be it for purposes reputable (figuring out what malware does and how to clear the infection from the entire bot network by saying the right thing on the right IRC channel, or getting the program to stop nagging you for the CD you own), to less so (getting the program to stop nagging you for the CD you don't own).

    26. Re:Assembly isn't obsolete! by Basehart · · Score: 0, Redundant

      You were lucky.

      When I were a lad we'd have to pile huge rocks on top of each other until we got ten of them stacked up, then double that until we got to twenty, and all the way up to a thousand.

      Then we'd have to climb to the top, all seventy of us in our classroom, and sing the lords prayer a million times.

      After that we'd stand on each others shoulders until the top one was all the way up into the clouds, and then we'd do a controlled fall.

      The last one down had to pack all the rocks away until lunchtime when we'd do it all over again.

      We had to do that until the age of twenty one months old.

    27. Re:Assembly isn't obsolete! by cpt+kangarooski · · Score: 1

      Try learning the following: INTERCAL, Malbolge, Befunge, brainfuck.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    28. Re:Assembly isn't obsolete! by Aehgts · · Score: 3, Informative
      I completely agree with the sentiment, but the examples are a little behind...
      Here's a programmable pen, couldn't find a bicycle lamp, so here's a NetBSD Toaster instead, for 4096 levels of burned bread and a web server.

      aahh, so you're a waffle man...
      --
      "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein
    29. Re:Assembly isn't obsolete! by danwesnor · · Score: 1

      And how to write code that isn't vulnerable to buffer-on-the-stack overflow exploits.

    30. Re:Assembly isn't obsolete! by doti · · Score: 2, Informative

      Or figuring out what the C++ (or any other) compiler does. When you're concerned about performance, you may need to be sure that your template/virtual function/whatever is properly optimized. Use the gcc option to output assembly code, and study it.

      --
      factor 966971: 966971
    31. Re:Assembly isn't obsolete! by PinkyDead · · Score: 3, Insightful

      I think you could go further and say that the reason so much bloated garbage is produced is because developers have such a thin understanding of the techniques they are using and have no idea of the consequences of their actions.

      For example, data structures such as lists and arrays are used interchangeably without any idea of the pros and cons of each, and the right place to use them. There are plenty more examples of this.

      At the very least, the abstract notion that we should aspire to understand what lies beneath our current level of knowledge and how it affects the quality of code is fundamental to good practice.

      --
      Genesis 1:32 And God typed :wq!
    32. Re:Assembly isn't obsolete! by DrLang21 · · Score: 1

      Apparently the article forgot that assembly is still widely used in embedded software for controlling microcontrollers. C might be starting to take hold, but many systems still use assembly, especially when the microcontroller isn't very sophisticated.

      --
      I see the glass as full with a FoS of 2.
    33. Re:Assembly isn't obsolete! by jellomizer · · Score: 3, Interesting

      Perhaps it is why it is a required course for a Computer Science Degree. I know threw out my work I never do anything close to assembly level coding. But when I see odd behavior I often have a better idea on why it does so.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    34. Re:Assembly isn't obsolete! by Anonymuous+Coward · · Score: 4, Informative

      I don't think GCC works that way. It probably generates machine code directly.
      No, GCC generates plain old text assembly, then calls the assembler (as) on that.

      In fact, the gcc or g++ commands are 'drivers' that first call a preprocessor, then a compiler, then an assembler and finally a linker (all of them separate executables).

    35. Re:Assembly isn't obsolete! by Lussarn · · Score: 4, Funny

      then just tell you to buy a faster machine.

      Well, you just told me to get a floppy drive.

    36. Re:Assembly isn't obsolete! by Octorian · · Score: 1

      And if you're using C, its at a level that you can directly see the translation to assembly code. C just makes it a lot easier to have human-readable structure to the program. Of course even then, you need to break into in-line asm every time you need to access a specific feature of the hardware. (which are quite common on microcontrollers, or anything where you are programming without an operating system, for that matter)

    37. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      "You rarely see it in systems programming." I work with mainframes, and you have me laughing so hard right now... Systems programming on mainframes still involves alot of S/360-derivative assembler code. The kernels of those old OSses (at least the ones I've worked with) are still programmed almost entirely in assembler. There are too many years worth of work invested into those kernels, making it unfeasible on many levels (and quite undesirable) to translate them into something more "modern" (like C).

    38. Re:Assembly isn't obsolete! by ultranova · · Score: 3, Insightful

      They didn't forget, it's just a niche skill. Assembly is obsolete for most purposes. You don't see it in application programming. You rarely see it in systems programming. You never see it in web programming. Even games don't use it anymore.

      Niche ? JIT compilers depend on it - to nitpick, they propably product opcodes, but it's not like there's much difference. In fact all compilers which produce machine code depend on it. All systems programming depend on someone writing the assembler routines to actually manipulate the hardware.

      Assembler is a niche skill to a programmer in the same way that knowing how to build foundations is a niche skill to a house builder: you can make do without, but only as long as you get someone else to do the groundwork for you.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    39. Re:Assembly isn't obsolete! by nkh · · Score: 1

      And don't forget the assembly window of the debugger when your program crashes. I use it all the time and it gives way more information about how the crash happened. I know that debuggers give the value of all the variables in real-time but the assembly output is the only way to understand what the operating system was executing during the crash.

    40. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      I write boot monitors for new CPUs when they are released. In the near recent past I wrote metal layer ROM code for an ARM core in an SOC. I also develop small control devices in Atmel AVR. All these require the ability to craft sensible assembly code.

      There are many many things (I sense it is humor) on that list that are still useful skills to many people. I am not going to enumerate the many I found browsing through the list.

      I think it is easy for people to dismiss things that you they do not understand as being obsolete. If the list is intended to be humorous and to raise discussion, it is interesting, if it is intended to be definitive, it displays ignorance and hubris.

    41. Re:Assembly isn't obsolete! by Elgon · · Score: 1

      This is exactly how I learned assembly language back in the dim and distant days of the mid-eighties. My ZX Spectrum manual has the Z80 opcode to hex listing in the back, and I went from there. A wave of nostaligia overcame me when I read your post.

      Ah, salad days.

      Elgon

    42. Re:Assembly isn't obsolete! by bob.appleyard · · Score: 1

      aahh, so you're a waffle man...

      One of the more plausible elements in that show. I can imagine being able to buy a toaster that will annoy me as much as Toastie in my lifetime.

      --
      How dare you be so modest!! You conceited bastard!!
    43. Re:Assembly isn't obsolete! by jcnnghm · · Score: 5, Insightful

      And this is exactly the problem with computer science education today. I don't think I had a well rounded understanding of computer science until after I learned assembly and implemented my own instruction set on an FPGA. Doing that was kind of like hearing the music when the apes touch the obelisk in 2001. When all you know is Java, it's kind of hard for the computer to be anything more than a magical box that run Java. As soon as you implement jump instructions, everything else seems to fall into place.

      --
      You don't make the poor richer by making the rich poorer. - Winston Churchill
    44. Re:Assembly isn't obsolete! by hey! · · Score: 1

      I don't know if every programmer has to know how to use assembler, but I can't imagine a good programmer who wouldn't find interesting, or who wouldn't find a way to benefit from knowing it.

      Programming is about transforming abstract and fuzzy problem domains into specific and concrete procedures. Assembly, then, is the ultimate challenge. An assembly program, no less than any other program, should be readable. The fact that assembler doesn't give you any abstractions that aren't there in the hardware means you've got to be that much more disciplined. You can't let code accrete; everything has to be purposeful and well organized. You need to adopt conventions and stick to them; the fact that each line of code does less means you refactor more. The lower level the language, the higher the barrier to entry and the slower the start to getting the problem solved. But, over time, a better programmer in a low level language eventually will overtake a lesser programmer in a higher level language, even if the lower language is assembler. That's why C will never go away as a systems programming language; it straddles the line between a low and high level language in an unique way.

      This gets back to the article a few months ago about Java being harmful to CS programs. I don't think it is harmful, but I think students should work in both featureful systems like Java and low level languages like C and assembler. Each has its own lessons to teach.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    45. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      VB, PHP and Ruby are scripting. C++, Cobol, fortran and to a lesser degree Pascal are real programming languages.

    46. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Systems programmers worth their salt can at least read assembler output. It's a valuable skill when debugging kernel errors.

      Ha ha! im n ur l4\/\/n!
    47. Re:Assembly isn't obsolete! by TheThiefMaster · · Score: 2, Informative

      Games almost always use assembler for vector and matrix math functions, because speed is critical and explicitly using SSE is more reliable than hoping that your compiler can figure out how to turn a long list of multiplies and adds into the appropriate SSE instructions.

      However the most common use of lots of assembler is compilers. Not just traditional source->executable compilers, but JIT recompilers are in every emulator that wants a sensible amount of speed.

    48. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 1, Informative

      Nope, you can put it in a 1.44 disk but you're not forced to.

      Small and fast OSes aren't exactly a niche for floppy-obsessed old timers. Think about handhelds, cellphones etc.
      Current cellphones OSes for example are way slower than those produced 7-8 years ago because they're putting in tons of features, but you can't have both a fast processor and a decent battery charge duration because battery technology doesn't progress comparably fast, so even the portables market would benefit from using a bit more asm or C and less Java and similar obscenities.

    49. Re:Assembly isn't obsolete! by h4rm0ny · · Score: 4, Insightful

      The article points out that this is a niche skill, not one that's widely useful.

      It was always a niche skill, possessed by only a tiny fraction of the population. There are probably more assembly language programmers today than there were forty years ago. And assembly language is used for the same things today as it was back then. If people want to say that today, programmers use languages like PHP and Java for creating web-applications not Assembly, then that is fine. Assembly never was used for creating web-applications because they didn't exist back then. Assembly has neither diminished in popularity nor entirely been superceded in its area. Shouldn't be on that list.
      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    50. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      "Reputable Web Programming and One Hundred Other Mythical Beasts": a fantastic compendium of modern urban legends. Did you see the Deluxe version? It came boxed with "OT-III your way to Happiness", a Guy Fawkes mask, and a card reading "All your tin hats are belong to us!"
    51. Re:Assembly isn't obsolete! by mehdi · · Score: 1

      ..about the subject....
      I dont know?, I guess it all depends...I am afraid for instance , that the new generation of kids using only digital clocks and watches slowly will not know the meaning of such words as "couter-clockwise" in few years! in essense we are not doing ourselves any favors by making certain (old) things become Obsolete!

      I learn computers when/if you had an i386 SX at 16 MHz and DOS 3 , you were the king lol,(I still like my command line screen a lot better than the one with a pointer...) and it is funny NASA at one time started to buy the old computer parts and memory (off ebay, remember?) bcs they are tough and rugged and dont break so easily when sent up into space. so there are still good things about the old and the obsolete!
      I know it was meant to be a fun thread but it can certainly wake us up as well!

      regards;

      --
      ..And Everyone Is Entitled To My Opinion! but hey, I am old enough not to care too much, about what you think of me!
    52. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      I am a VB programmer, and I sometimes have to use assembly for things that wouldn't be possible otherwise. I usually prefer AsmPatcher, although CallWindowProc can be useful as well.

    53. Re:Assembly isn't obsolete! by neumayr · · Score: 1

      While that feat is impressive and all, it does not repute the GP's point in any way.
      Or are you seriously arguing that coming up with a tricky way to store a bootloader is a techskill nobody, at least no Java/C++ coder, can do without?

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    54. Re:Assembly isn't obsolete! by neumayr · · Score: 1

      Oops, s/repute/refute/;

      --
      Truth arises more readily from error than from confusion. -Francis Bacon
    55. Re:Assembly isn't obsolete! by mdmkolbe · · Score: 1

      This just in: Arithmetic is now an obsolete skill. Now days people just use calculators.[/sarcasm off]

      Just as arithmetic is rarely(*) used in every day life, the same could be said for assembler. But also just like arithmetic, to use the tools well (calculator/compiler), you have to understand what happens under the covers (arithmetic/assembler). In that sense assembler is far from obsolete.

      (*) Well maybe not as rarely as assembler.

    56. Re:Assembly isn't obsolete! by claytonjr · · Score: 1

      I had a compiler on CP/M which generated assembly and sent the output to an assembler. I don't think GCC works that way. It probably generates machine code directly. Maybe it has a symbolic "assembly" layer inside. DEC C on alpha/OpenVMS had an option to output assembly. I don't think it generated it otherwise. Yes, it does. EVERY compiler does it that way.
    57. Re:Assembly isn't obsolete! by Lumpy · · Score: 1

      It goes farther than that, the guy is a complete moron for saying that assembler is a worthless skill. the strongest and fastest growing IT field is embedded systems. All those embedded 8 bit processors with 4K of storage for the program are not going to be programmed in C#, C++, Java or some other bloated language. It's going to be programmed in assembly language. and tight code at that.

      There are so many "gizmos" coming out that rage from the inane like alarm clocks and consumer junk to the intense like medical, aeronautics, military, automotive, and communications that someone with skills to work on those small embedded systems are far more employable and valuable to a company than a guy who wrote an entire operating system for a PC. embedded systems is where it's at, and it's mostly assembler for the guys that are good at what they do. Yes you can over specify the processor and get a crap load more speed and space in it so you can program it in C but when you scale up to 10,000 units, the extra costs more than pays for a competent Assembler programmer.

      I think the Article's thinking is from someone why barely understand computers and has great amounts disdain for those that do.

      --
      Do not look at laser with remaining good eye.
    58. Re:Assembly isn't obsolete! by Jarik_Tentsu · · Score: 1

      Oh really?

      Damnit! I was wondering why that high-school dropout was making utility applications faster than me...

    59. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      I know threw out my work I never do anything close to assembly level coding.

      You should never throw out your work. You might need it in the future.

      Or did you mean "throughout"?

    60. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      They didn't forget, it's just a niche skill.

      Nice and obsolete are not even close to the same. Assembly was always a niche skill. Sure it's a smaller part of programming, but there's far far more programmers now. This it's not like the rotary phone or carbon paper.

    61. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Asm is also used to validate the compiler is actually generating the right code. Without knowing it, how would you know? If you want to write a compiler, you need to know it - or worse, machine language. It is often used when the compiler generates the right code but in a non-optimal way. Lastly, asm is often used to run instructions which compilers simply don't generate.

      Granted, the number of people that need to know asm is much reduced from even twenty years ago, but it is still far, far, far from being obsolete. Nor do I see a near future where asm will be made obsolete.

    62. Re:Assembly isn't obsolete! by Kadin2048 · · Score: 4, Insightful

      The article points out that this is a niche skill, not one that's widely useful.

      It was always a niche skill, possessed by only a tiny fraction of the population. There are probably more assembly language programmers today than there were forty years ago. And assembly language is used for the same things today as it was back then. If people want to say that today, programmers use languages like PHP and Java for creating web-applications not Assembly, then that is fine. Assembly never was used for creating web-applications because they didn't exist back then. Assembly has neither diminished in popularity nor entirely been superceded in its area. Shouldn't be on that list. I think this is an excellent point and one that really doesn't get mentioned enough whenever the topic of "dying" technical skills comes up.

      Some skills just seem like they're obsolete or dying because the proportion of people within a field that have them is getting smaller -- but they're really stronger than ever when you look at the raw numbers.

      I agree with the parent and fully suspect that there are more people who understand x86 assembler today than there were at the perceived 'height' of assembler, back in the early 90s. There are just that many more people in the IT field. Learning assembler, if you happen to be interested, is also a lot easier now than it was then. Today, computers are basically a mainstream subject, plus you have all the information available on the Internet. In 1990, finding a good book on assembler programming would probably have required a trip to a large university's library.

      Obviously there are some skills that really are on their way out, or will be when the current crop of people who truly understand them either retire or die. But in many cases I think it's easy to confuse the S/N ratio in a particular sphere with the number of people who actually are familiar with a topic.
      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    63. Re:Assembly isn't obsolete! by dwye · · Score: 1

      > You'll be much happier for it; really, you will.

      Just like Joey Pants' character, in the Matrix.

      Oh, God, I just wrote approvingly of something from the Matrix Trilogy! Early Onset Alzheimer's, for certain.

    64. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      When you can write a bootloader that fits in the unused sectors on a floppy disc What's a floppy disc?
    65. Re:Assembly isn't obsolete! by heelrod · · Score: 1

      What about how to pick up chics?

      these guys still need that skil

    66. Re:Assembly isn't obsolete! by dwye · · Score: 1

      All those embedded 8 bit processors with 4K of storage for the program are not going to be programmed in C#, C++, Java or some other bloated language. It's going to be programmed in assembly language. and tight code at that.

      Even if you only program them in C (guilty, on 80552 microprocessors) or C++, you will still want to read the emitted assembly code to make sure that you wrote something that the compiler doesn't generalize to the point that it takes forever to process the inner loops or interrupt service routines.

    67. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      You don't see it in application programming. You do in speed critical items. This is why it is sometimes used in cryptography applications because it can often be more efficient then higher-level languages.

      You rarely see it in systems programming. Are we talking about device drivers and kernel level development? If so, while it might not be as prevalent as in years past, I would still challenge you that it is often used for the same optimization as anything else.

      You never see it in web programming. The web is not programmed. It is scripted. Get over yourself if you think you are "programming" anything when you write a "web application". It would be worthless without some language interpreter on one end or the other of the transaction.

      Even games don't use it anymore. I cannot speak directly to this. But some of the other replies seem to disagree.

      BTW, for all of your babbling, how much dev time have you spent on any of the categories you mentioned? I somehow think you are re-hashing words from other know-nothings that hang out around here waiting for some assembly flame war.
    68. Re:Assembly isn't obsolete! by poot_rootbeer · · Score: 1

      For example, data structures such as lists and arrays are used interchangeably without any idea of the pros and cons of each, and the right place to use them.

      When the consequences of using a sub-optimal data structure are barely perceptible, what driving force is there to compel a developer to give data structures more careful consideration?

    69. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Yes, just like operating an industrial refinery is a niche skill. The modern economy would grind to a creaking halt if we didn't have people making gasoline, but you don't see people arguing that the practice of fractional distillation and crude oil cracking is a necessary skill for anyone who drives a car - even those who drive professionally.

      Just because it's important, doesn't mean it isn't "niche".

    70. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Shut the fuck up. Scripting is a type of programming and you know it. Those "icky scripters" are already at "our" table, and no amount of passive-aggressive whining on your part will or should make them leave.

    71. Re:Assembly isn't obsolete! by Richard+Steiner · · Score: 1

      Stop calling scripting programming. You web guys are desperate to join the software programmers lunch table and it is not gonna happen guys, so stop calling yourself programmers.

      What would you consider a Java programmer? Jave is essentially a scripting language which compiles to bytecode, after all.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    72. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Well... besides that, someone has to actually write the fucking code generation phase of a fucking compiler.

    73. Re:Assembly isn't obsolete! by petermgreen · · Score: 2, Informative

      the trouble is while one bad descision is barely perceptable a load of bad descisions stacked together make the difference between an app that is fast and responsive even on old hardware and a peice of horrible bloatware.

      and sometimes programmers make really horrible descisions like trying to delete elements from the middle of an array and move up everything after it. Sometimes programmers read large blocks of data into strings and try to use string manipulation on them etc. Theese bad descisions are imperceptible on the small datasets the dev typcially tests with but far more substatial when the data in question grows to hundreds of megabytes.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    74. Re:Assembly isn't obsolete! by vidarh · · Score: 2, Insightful
      One of those things from my childhood that's now deeply embarrassing: I started programming very young, but only in basic at first. Around 10-11 I realized that to do any "cool stuff" I needed to know about assembler. But the sources I had didn't even really explain WHAT assembler was, and together with a couple of friends I tried figuring out how to do it, with rather poor results.

      At first we tried poking in the textual strings of BASIC programs into memory, not realizing that even BASIC programs were stored in a more advanced way (on the C64 they were tokenized and keywords were stored as mnemonics to save space and speed up the interpreter). When we found out about the mnemonics bit we tried poking them in, which might've would've worked if we'd put them in the right locations and run them as basic programs instead of trying to use "sys" to call it. Finally one of us got hold of an assembler, and eventually a book on assembler programming.

      I think it took a year or so from we started exploring it until we actually were writing simple assembler programs.

      While an adult would've had an easier job finding and obtaining books about it instead of fumbling around the way we did, it does illustrate how much harder obtaining technical knowledge was.

      Already when I got an Amiga it was far easier - there was a number of technical books (my first one for the Amiga was probably the Advanced System Programmers Guide), and mainstream computer magazines were running articles on assembler programming and other languages.

      When I got a modem it got almost trivial.

      If I'd started fresh again today, I'd probably just gone to wikipedia, followed by going to a search engine and searching for "assembler tutorial"

      x86 assembler put me off, though. I haven't done any serious assembler programming since my Amiga days largely for that reason - when you've done M68k assembler, x86 assembler looks about as fun as poking your eyes out with a fork.

    75. Re:Assembly isn't obsolete! by TheLink · · Score: 1

      You know why ASM is still important for viruses/malware?

      Because Windows doesn't bundle a decent interpreter and java isn't very fun for doing naughty stuff.

      Now if OSX or Linux really gets popular on the desktop, perhaps you'll see more malware written in scripting languages.

      --
    76. Re:Assembly isn't obsolete! by Monsuco · · Score: 4, Funny

      When you can write a bootloader that fits in the unused sectors on a floppy disc
      If you can find a modern computer that still comes with a floppy drive I will be impressed.
    77. Re:Assembly isn't obsolete! by das_schmitt · · Score: 0
      Two hundred million VB, PHP and Ruby scripters want to disagree with you.

      Fixed that for you.

    78. Re:Assembly isn't obsolete! by Sperbels · · Score: 1

      I disagree. There's so much bloated garbage code out there because the people in charge always desire quantity over quality. Sure there are plenty of bad coders out there, but even they could do a great deal to clean up their code if they were only given the time to do it.

    79. Re:Assembly isn't obsolete! by AdamThor · · Score: 1

      At the very least, the abstract notion that we should aspire to understand what lies beneath our current level of knowledge and how it affects the quality of [work output] is fundamental to good practice.

      I become amused, thinking of how executives and administrators would react to this concept.

      --
      -- "Oh. This guy again."
    80. Re:Assembly isn't obsolete! by sootman · · Score: 1

      But how much is enough to be useful, versus "just enough to be dangerous"? I can imagine a programmer knowing a bit of assembly and therefore spending too much time trying to (over-)optimize some particular thing, when a) it's already optimized as much as it can be, or b) putting effort into another part would yield much greater returns. You need look no further than the daily wtf for proof.

      As for the article itself, I think the main point is correct--not that no one anywhere needs to know these things, but that fewer and fewer people need to know them, and that lots of us who've been around a while know lots of stuff that will never again be useful. I'm a huge believer that knowing history is a good thing and it gives you useful perspective and good general knowledge but these things just won't be day-to-day useful the way they once were. I am by no means the oldest guy in the room but I was working with computers in the mid-90s and I do remember fiddling with the dipswitches on the back of a 14.4 modem, then working out the proper AT commands, and moving IRQ jumpers on an ISA sound card, futzing with SCSI IDs and terminators on Mac equipment, etc etc etc. Many, many things that I'll never, ever, ever have to do again.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    81. Re:Assembly isn't obsolete! by EgoWumpus · · Score: 1

      "The web is not programmed. It is scripted. Get over yourself if you think you are "programming" anything when you write a "web application". It would be worthless without some language interpreter on one end or the other of the transaction."

      *sigh* Do you really think this? I mean, come on. The web does not exist as some magical land of script-only madness that somehow works. It *is* programmed, even if there is a much higher percentage of scripts running out there than honest-to-goodness applications. But note that the real applications are the ones that are doing well.

      But that aside, there is a good reason scripts exist; and they exist everywhere. A real programmer would be foolish to decide that they are somehow meaningless child's play alone.

      --

      [Ego]out

    82. Re:Assembly isn't obsolete! by Opportunist · · Score: 1

      True, to some degree. Some of the popularity with asm for malware is due to its ability to "toy" with the processor in a way you simply cannot with high level languages. It's actually more complicated to impossible to write a self recrypting program in any high level language.

      What makes asm so powerful for malware is simply that there is only one processor type in existance today that runs Windows. If there was some diversity in the processor market, you won't see much malware relying on the quirks (and often even undocumented side effects) of the intel x86 processor family.

      Now, whether that would change with people switching over to linux is debatable. Sure, you will see a lot of script malware (you already do to some extent, especially with malware that tries to sneak past some quirks and bugs in browsers), but unless you see a diversity in the CPU market, you won't see asm becoming obsolete in malware anytime soon.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    83. Re:Assembly isn't obsolete! by ma_spacechip · · Score: 1

      More specifically, knowledge of assembly is crucial for virus/malware research + understanding common program vulnerabilities like buffer overflow. In general, it's just better to have more knowledge regarding every level of abstraction in computer programming, rather than coding in HLL's blindly.

    84. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Not true, not true! I work on console game engines and let me tell you:

      (1) you have to be able to read assembly code in order to debug code compiled with any sort of optimization (e.g. when the engine crashes, how are you going to find the pointers to the data structures it was manipulating when it crashed? You're going to scan through the disassembly and figure out which register has your pointer in it by matching the generated code up to the source, that's how).

      (2) we definitely do use assembly for certain performance-critical things or things where we need to get really close to the bare metal in order to implement them properly. We try and do it using the compiler intrinsics (not separate .asm files) but its still assembly programming, in some weird fashion.

    85. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      > You never see it in web programming.

      Sure you do. It goes right after the NOOP sled.

    86. Re:Assembly isn't obsolete! by PinkyDead · · Score: 1

      Generally the good coders will use their brains where as the bad coder will copy and paste without any appreciation for what they are doing.

      You are right that the bloat comes from quantity over quality - but that is achieved by packing projects with anyone who can use Edit/Copy, Edit/Paste (even Ctrl-C, Ctrl-V would be beyond them). Re-use means copying some crap from one place to another (with a whole new set of bugs). And testing is a waste of time.

      --
      Genesis 1:32 And God typed :wq!
    87. Re:Assembly isn't obsolete! by reub2000 · · Score: 1

      Loose sheets of carbon paper may be obsolete, but many forms still have carbon paper built into them.

    88. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Based on many posts, spelling and grammar (or using a spell checker or grammar checker) are obsolete.

    89. Re:Assembly isn't obsolete! by slapout · · Score: 2, Interesting

      You never see it in web programming.

      Steve Gibson does it:

      http://kleinmatic.typepad.com/kirkunit/2007/03/steve_gibsons_a.html

      --
      Coder's Stone: The programming language quick ref for iPad
    90. Re:Assembly isn't obsolete! by JasterBobaMereel · · Score: 1

      If you program in Java then you know assembly language - Java *is* the assembly language of a java machine (the Bytecode is the machine code)

      This means you are no longer talking to your machine, you are talking to the JVM ....

      C# does much the same thing with CLR (I believe it gives some access to low level .NET and Windows services etc...)

      Unfortunately this means you lose control over the real hardware and a lot of low level optimisation techniques, which is why people still program in C/C++ (with an optimising compiler), and occasionally in assembler where the optimising compiler cannot cope and cannot be coerced by a good low level programmer to optimise enough.

      --
      Puteulanus fenestra mortis
    91. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Real programmers can code assembly in any language

    92. Re:Assembly isn't obsolete! by notdarkyet · · Score: 1

      Sadly, this couldn't be more true. At my university we glossed over assembly and I it would seem as though they have distanced themselves from lower-level programming. I am not sure whether this is out of practicality or to make the curriculum easier and have more students join the program. It is interesting how many students lack skills outside of the point-and-click gui's when it comes to computing. Gasps can be heard around the room at the mention of a command line. To me the most important part of learning programming was not the syntax, but what is actually happening behind the scenes. The focus seems to have drifted away from those areas and is a little disconcerting, I would directly that to the shift in what people believe is the importance of college. Rather than giving individuals knowledge and insight so they can easily adapt to many skills, they tend to focus on just jumping straight to the skills and produce great worker bees. What I am attempting to explain is that rather than have a few courses on theoretical concepts and how various languages are used and interrelate, they just teach you a few of the common languages and ship you off (ie. java). What this is going to produce is a large group of young workers who will easily integrate into the current workforce right now, but once technologies change, those same individuals are going to have a hard time adapting and understanding the new concepts (well, they also might be producing bloated code not knowing what is truly going within the hardware). So the growing concern is not technology becoming obsolete, but the young workforce.

    93. Re:Assembly isn't obsolete! by jcnnghm · · Score: 1

      Case in point. You seem to lack a fundamental understanding of a basic concept. Java is definitely not assembly language. Java code doesn't even translate one-to-one to bytecode, let alone machine code. GCJ can compile java to machine code, or byte code to machine code. In addition, quite a few JVM's and the CLR make use of JIT compilation. If java is an assembly language, then so are ruby and python.

      --
      You don't make the poor richer by making the rich poorer. - Winston Churchill
    94. Re:Assembly isn't obsolete! by certsoft · · Score: 1

      The summary is incorrect. TFA was actually referring to converting assembly language to binary opcodes by hand, not assembly language programming itself.

    95. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      They are also forgetting microcontroller programmers, or anyone who developes for higher level languages. asm is alive and stronger, sorry noobs, its not obsolete like your java skills will be in afew years.

    96. Re:Assembly isn't obsolete! by vivin · · Score: 1

      "x86 assembler put me off, though. I haven't done any serious assembler programming since my Amiga days largely for that reason - when you've done M68k assembler, x86 assembler looks about as fun as poking your eyes out with a fork."

      I couldn't agree more. I started off with the 6811 in college, followed by the 6800. Then my professor invited me to take his graduate class where we used the M68k. I was blown away by the beauty of the thing. It was almost completely orthogonal. We wrote a simple pre-emptive multi-tasking OS for the final project. I tried to do x86 assembly, but the whole thing looked like such an ugly hack that I could never get into it.

      --
      Vivin Suresh Paliath
      http://vivin.net

      I like
    97. Re:Assembly isn't obsolete! by Lazerf4rt · · Score: 1

      How interesting to hear this news that game developers don't use assembly language. Just what the hell was I doing last week?

    98. Re:Assembly isn't obsolete! by Kaz+Kylheku · · Score: 1

      Uh, it was always a niche skill. When assembly language programming was a more common way to write large programs, computer programming was a niche skill.

      It's not comparable to the obsolete skill of tuning a carburetor. That's obsolete because, like, your car doesn't have one. Fuel injection doesn't work by controlling a carburetor.

      Your computer is based on machine language, and it's pretty safe to say that your next one will also, and so will the one after that.

      Due to the growth in computing, there are probably more people working with assembly language today, in terms of absolute numbers, than in 1968.

    99. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Does anyone here actually program assembly on the dual data path TI DSPs? Cause if so, wow. It seems like that type of design is what will help push the *writing* of assembly code off the map.

    100. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      There's almost always some assembley to be written usually hidden from peoples prying eyes, but good examples are early boot code, and processor functions: eg turning off interrupts, flushing the cache etc.

      That and people who work on compilers to save the rest of us from the pain :)

    101. Re:Assembly isn't obsolete! by gnupun · · Score: 1

      How much do you want to bet Google doesn't use assembly? I read some of their whitepapers years ago stating something about increasing max efficiency of cpu resources like cache.

    102. Re:Assembly isn't obsolete! by pw1972 · · Score: 1

      I work for a fortune 500 bank. We have a gaggle of mainframe assembly programmers still. A couple of them are well into their 70's in age and we are having a nightmarish time trying to replace them. These guys were pretty smart though, the software they wrote some 30 years ago, they sold to the bank, and support as contractors. I wouldn't say that assembly programmers are thriving, but I definitely don't think they are dead.

    103. Re:Assembly isn't obsolete! by Beardo+the+Bearded · · Score: 1

      OR:

      Debugging.

      The truth is that we all programming in machine code. The abstractions that we use to understand the machine's language (or to make it understand ours) have to be fully understood to prevent serious errors. Even people programming in a high-level language that will run on an abstraction layer (i.e. JRE, .NET) should be aware of what your target audience is. That audience is the machines that will eventually run your code.

      What you write as one line could, in fact, be interrupted in the middle of execution. Assembly is as close to machine code as you can get.

      Take the easiest example:

      i++;

      You can't get much easier than that in C. Now let's look at it in pseudo-assembly:

      LOAD i
      ADD 1
      OUT i

      What's the difference here? One appears to be an impenetrable one-line function, but it is in fact about three lines. The difference can be significant:

      LOAD i
      INTERRUPT HEY WHAT HAPPENED TO THE ACCUMULATOR VALUES
      ADD 1
      OUT i

      Usually, the stack will take care of keeping track of what happened in the accumulator during the interrupt. That's what everyone will tell you. This is not true in real life, at least not always.

      And yes, I speak from personal experience.

      Feel free to list "Assembly" as an obsolete language. I can understand it and use it. I've paid bills with it as recently as 10 months ago. The fewer there are that can use it, the more I can charge.

      --

      ---
      ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    104. Re:Assembly isn't obsolete! by Guy+Harris · · Score: 1

      EVERY compiler does it that way.

      No, not every compiler does. Most if not all UN*X compilers do ("generate assembly and let the assembler handle generating an object code file" is a long-standing UN*X tradition, antedating GCC), but at least some compilers on non-UN*X OSes generate object code directly.

    105. Re:Assembly isn't obsolete! by Guy+Harris · · Score: 1

      In fact, the gcc or g++ commands are 'drivers' that first call a preprocessor, then a compiler, then an assembler and finally a linker (all of them separate executables).

      ...following in a UN*X tradition that dates back long before GCC (at least back to Dennis Ritchie's C compiler for PDP-11 UNIX).

    106. Re:Assembly isn't obsolete! by Beardo+the+Bearded · · Score: 1

      I can't tell you how many times looking at the ASM output (on CCS-C) has saved my butt. Not as many times as a good diff program, but close.

      You know you're getting close when you replace some ASM code with your own because the compiler didn't do a tight enough job. It's even better when you get a 6% reduction in code footprint. You know you're crazy when you're doing the same thing on the compiled HEX output.

      I remember once when my boss came in and said, "Wow, now THAT'S programming - just... a page of HEX."

      I've done a fair bit of Embedded C. One chip I used had 512 bytes of Flash and 24 bytes of RAM.

      --

      ---
      ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    107. Re:Assembly isn't obsolete! by T-Ranger · · Score: 1

      I could not disagree more so.

      An application/web/game/blah programmers job is to write programs to do that. A compiler programmers job is to right good compilers. They are separate and distinct tasks... And really are distinct jobs/trades.

      If an application programmer needs top think about what the compiler is doing, then the compiler isn't doing its job well.

      In any case, with processors (and good compilers) from the last decade, trying to second guess what the hardware will do and how the compiler will try and optimize things.. Its just as likely you will make things worse then better. With SMP machines seeming to be the default moving forward, it is even more critical that compilers are less shitty. Writing cross platform apps? Different OSs, compilers, hardware? You should be able to ignore this, iff the low level tools/os/lib developers did their job well.

      In short: If "every" programmer needs to know about assembler, then some programmers are not doing their jobs.

    108. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      The only thing assembly gives you that machine code doesn't is readability and labels.

      Sure, if by "readability" you mean comments, namespaces, macros, pseudoinstructions, constants, structures (with automatic padding and offset calculation), and so on.

      These aren't new innovations; we had sophisticated macro assemblers in the 1970's. The toy assembler you typed in for your C=64 was not representative of the state of assemblers. Remember that (pre-ANSI) C compilers were once a hard sell, and look at how little they provide. Assemblers were just shy of that mark.
    109. Re:Assembly isn't obsolete! by TheLink · · Score: 1

      "It's actually more complicated to impossible to write a self recrypting program in any high level language."

      I think in theory that should be easier to do in Lisp than ASM/machine code ;). Plus you wouldn't trigger the Data Execution Prevention/NX thingy if you use a Lisp interpreter.

      There's also a lot you can do with a few lines of perl, given the very powerful built-in libraries on most platforms that bundle it.

      I think you could say similar things about python.

      --
    110. Re:Assembly isn't obsolete! by drozofil · · Score: 1

      I worked as an intern in a video game development studio, and they definitely used assembly, especially for those nice SSE2 tricks that MSVC++ doesn't really grasp.

    111. Re:Assembly isn't obsolete! by Zondar · · Score: 1

      "When you can write a bootloader that fits in the unused sectors on a floppy disc" ... or hard disc. Geez, +1 for not even visiting TFsite.

    112. Re:Assembly isn't obsolete! by Sperbels · · Score: 1

      No sir. I can write totally original crappy code. :)

    113. Re:Assembly isn't obsolete! by sean.peters · · Score: 1

      You may not be able to put a bootloader written in Java on the unused sectors of a floppy, but that says nothing about whether assembly is obsolete. In fact, it weakens your point, since floppies themselves are obsolete.

    114. Re:Assembly isn't obsolete! by letxa2000 · · Score: 1

      Indeed assembly language is only "obsolete" in certain circles. It might be obsolete to some random VB programmer but it's definitely not obsolete to a host of other industries, including true embedded programming. There are still applications that need to be written to fit in 2k of ROM. Those programs might not be common on end-user PCs any more, but that doesn't mean they don't exist. I believe it's fair to say that most programs that are running at any given time in the world are not running on PCs or Macs. And those that aren't are usually still subject to efficiency and optimization requirements that many PC-world programmers have long since forgotten.

      Assembly language (and related experience) can be the difference between an "embedded programmer" grunt that makes $50/hour and a senior embedded programmer that makes $125+/hr.

    115. Re:Assembly isn't obsolete! by Belial6 · · Score: 1

      You are correct that the poster above you is lacking a fundamental understanding of a basic concept, but he is close. Java byte code IS machine code. It is the machine code for the Java emulator. Sun was pretty clear on what their original plan for Java was. They were going to make Java emulators for every popular platform so that people would write code for their new processor. Then when there was enough code to generate demand, they would release the actual Java processor which they called the 'JavaOne'. The plan for the actual hardware was abandoned when they found that they could not make the JavaOne run as fast as an x86 could emulate it. The JavaOne processor was also not helped by the fact that the Java Emulator was a piece of crap. It was buggy and inconsistent. This meant that code written to run on the emulator would not always run unaltered on the actual hardware.

      JIT is not an indication that code compiled to the JVM is not machine code, as JIT for Java came after JIT was proven to work in many game console emulators. Java was kind of a Johnny come lately to the JIT emulation scene.

      To simplify it:

      Java Virtual Machine = Java Emulator Byte Code = Machine Code

      I still think that Java would not have taken so long to be usable, and that it would have had a wider range of relevance if Sun had actually built Java hardware before releasing the emulator, and had actually tested the JVM against real live reference hardware.

      I always liken Java to the x86 platform. It was a poorly designed system that had a big name trusted by business behind it. Eventually after enough companies dumped enough money into trying to fix it, we finally ended up with something that works pretty good. A lot of time has been wasted, but that is in the past, and we now have a usable system to move forward from.

    116. Re:Assembly isn't obsolete! by jellomizer · · Score: 1

      Yea Like I am going to open up word write out my comment. Copy and Paist my comment back to slashdot. IE 6 doesn't have spell checking built in. Some people are at locations where they are not allowed to install their own apps or plugins for the apps... So Deal with it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    117. Re:Assembly isn't obsolete! by Darinbob · · Score: 1

      I use assembler on the job. It is not obsolete. Sure, maybe a lot of people don't use it, but someone does. You might as well say that programming is an obsolete skill, since most people just use computers and browsers without worrying about that sort of icky behind-the-scenes stuff. In the grand scheme of all jobs on earth, programming in any language at all is a niche job. Niche is not obsolete.

    118. Re:Assembly isn't obsolete! by Darinbob · · Score: 1

      If you can find a modern computer that still comes with a floppy drive I will be impressed.
      Really? It was on option I could have gotten on my Dell I purchased in December. I didn't get it since I can recycle the drive on my old computer. Or maybe get a USB floppy drive. I still have floppies I would like to use again someday (old computer games).
    119. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Thats pretty cool! I'll have to play around with that.

      Assembly and basic architecture are still taught to the computer science and software engineering students. Even though I doubt I will ever use it directly, the basic understanding definitely will help with writing efficient code. Its just plain better to not assume its a magic box that uses blue smoke to interpret random code.

    120. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      200 million VB programmers, maybe.

      The programmers at my company all use Ruby, and I won't say never, but I highly doubt we'd ever hire a Ruby programmer who doesn't know assembly (and data structures, and big-O notation, and database theory, and ...). I know, because we've passed on people for exactly this reason.

      It may sound convenient to lump VB, PHP, and Ruby together because they're all languages that let you write "hello, world" without a lot of obscure geekery (like, say, C or Fortran), but that doesn't mean it's not a real programming language. I think the difference between "average" and "great" is much larger for Ruby than for C, simply because it gives you a longer lever. I would say that every Ruby programmer worth hiring knows assembly.

    121. Re:Assembly isn't obsolete! by Pseudonym · · Score: 1

      Add compiler development to that list.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    122. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      Wow you guys have NO sense of humor. It's obvious he was joking.

      I guess it's true what they say about you guys. you dont belong at the big guys lunch table

    123. Re:Assembly isn't obsolete! by LoztInSpace · · Score: 1

      Well apparently riding a bicycle is also obsolete so there is no need for your lamp anyway. I didn't realise the way I have been getting to work for the last 8 years was obsolete!
      WFT?

    124. Re:Assembly isn't obsolete! by CaptainCarrot · · Score: 1

      What the hell's embarrassing about that? Most kids are nowhere near curious enough about anything to bother either experimenting with it or learning about it. You were 12 years old and writing in assembly. That's reason to be proud, not embarrassed.

      One of my own complaints about modern home PCs and how programming is taught is that kids never get a chance to work so close to the machine anymore. A Java programmer can consider himself fully educated and never have the faintest clue about what the underlying hardware is doing. I suppose for web applications it doesn't matter so much, but I reflexively cringe when I see wasted resources.

      I didn't learn assembly programming until I worked on the DEC-10 in college. It had a number of unique features, not least of which was a 36-bit word and 6-bit character set, which meant you naturally worked in octal instead of hex. Never had the opportunity to work on an M68k family processor, unfortunately.

      --
      And the brethren went away edified.
    125. Re:Assembly isn't obsolete! by david_thornley · · Score: 1

      It may take five times as long to write in assembly, but if you're shipping ten million widgets, and you can knock a dollar off the production cost if your engineers can squeeze things into a smaller format, it's worth it to pay for the extra development time.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    126. Re:Assembly isn't obsolete! by mojogrande · · Score: 1

      An article by Gustavo Duarte referencing Richard Fenyman on the Challenger disaster and found here: http://duartes.org/gustavo/blog/post/2008/02/20/Richard-Feynman-Challenger-Disaster-Software-Engineering.aspx provides Olympian support for bottom up software design, of which assembly language is a part.

    127. Re:Assembly isn't obsolete! by wkitchen · · Score: 1

      The frontier is and likely always will be assembly, and even though the frontier keeps moving and likely in 5 years the bicycle lamps will be programmable in Java, maybe ballpens will be programmable in assembly.
      I don't disagree with your point. There remain many good uses for simple processors and assembly programming. But I think you may have underestimated the technology that can already be had in a ballpen.
    128. Re:Assembly isn't obsolete! by Anonymous Coward · · Score: 0

      ... I know threw out my work I never do anything close to assembly level coding.

      Did you ever take any English courses?

      *ducks*

    129. Re:Assembly isn't obsolete! by dave87656 · · Score: 1

      I guess they're forgetting about things like optimized device drivers, true performance-oriented embedded systems architectures, microcode segments, and anything to do with hardware development. What also seems to get ignored by the point-and-click programming crowd is the inevitable problem that happens when your system starts getting heavy use. Some of these systems just all apart because many young programmers and system designers just don't understand what's happening at a lower level.
    130. Re:Assembly isn't obsolete! by jacquesm · · Score: 0, Flamebait

      thank you AC, that's a really nice project there! Good to see such skillful work produced today.

    131. Re:Assembly isn't obsolete! by SharpFang · · Score: 1

      Sure you can squeeze lots into a very expensive ballpen.

      My point is a commodity, not a gadget though. It's very hard to find a bicycle lamp without a CPU nowadays - the off/blink/permanent light cycle is handled by one, and that's the standard in the industry. Toasters are some way behind, but microwave ovens - I hate the ones with buttons and LED display, give me rotary dial any day - but these are increasingly harder to come by. CPU inside, and the rotary dial is often just an interface to optical encoder. Or what about multimeters? I still have some old-fashioned ones with a needle and multiple scales, but nowadays you'll find only digital ones.

      All these devices are programmed in assembler and all of them dominated the market to the point of pushing non-digital counterparts off the market entirely.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    132. Re:Assembly isn't obsolete! by ohmpossum · · Score: 1

      Taught myself assembler around 1982-3 using the book "Apple Machine Language" published in 1981 which I used to make a dumb terminal that let me talk to my 300 baud modem. Then in 1986 I went to college and took a VAX assembly class. Did more on a 68000 eval board for a lab class. I was also in the last class they required to take the then obsolete language FORTRAN! Years later (1994) I was an graduate summer intern at Bell Labs (now lucent) where they told me "yeah, the guys who wrote the C programming language are down that hall." but the funny part was watching some other interns I shared a room with struggle to make mathlab work on a high end Mac (with the new PowerPC uP) only to have their advisor run off in frustration and solve the problem by writing a FORTRAN program in under 30 minutes. The reason I know the assembly book I learned on is I have it here now. I mostly write VHDL/Verilog nowadays but am now working on an ASIC where I need to use some assembly too...in 2008! +++ ATH

      --
      Just set me up a basic sig... 10 PRINT "Gordon Aplin" : GOTO 10
    133. Re:Assembly isn't obsolete! by JasterBobaMereel · · Score: 1

      Sorry my analogy was one step away ....

          Java Byte Code = Machine code
          ? = Assembly language
          Java = System programming language (as low level as C (or maybe even lower) but a more advanced language)

        The problem was that there is no assembly language for the Java machine, the only people who deal with the machine itself are the people who write the VM's and those who write bytecode compilers

      If there was a real java machine then an assembly language probably would get written so that people could program the machine directly and to make writing the bytecode simpler ...

      Since the optimisation of code to the VM may not work if you are using a different VM (e.g. using MS JVM, IcedTea etc ..)
      the only thing worth optimising is the Java bytecode compiler (not assembler level...), and the compiler (a task beyond most people)

      --
      Puteulanus fenestra mortis
    134. Re:Assembly isn't obsolete! by Killjoy_NL · · Score: 1

      I got a quite modern comp and still have a floppy drive :P
      I was even thinking about plugging in an old 5 1/4" drive, just for fun :D

      --
      This is the sig that says NI (again)
    135. Re:Assembly isn't obsolete! by David+Parker · · Score: 1

      Flaming Thunder, a new programming language for everyone from elementary
      school students to scientists, mathematicians and engineers, is
      programmed entirely in 32/64-bit assembly language.

      Flaming Thunder supports interval arithmetic, supports number theoretic
      transforms for O(N log(N)) multiplication of high precision numbers,
      supports 64-bit platforms, and supports FreeBSD, Linux, Mac OS X and
      Windows. It can cross-compile from/to any of those platforms.

      It takes less than 120K of disk space. For more info:

      http://www.flamingthunder.com/index.html

    136. Re:Assembly isn't obsolete! by necro2607 · · Score: 1

      Also consider that some of the latest machines don't even come with a CD/DVD drive. MacBook Air anyone? Speaking of which, it's very very rare for me to have to use a CD or DVD these days. All my music is in mp3 format already, and I transfer most data over the network or using a 2 gigabyte USB memory stick.

  2. Shorthand is not redundant yet by chriseyre2000 · · Score: 1

    My other half still uses shorthand at work.

    1. Re:Shorthand is not redundant yet by Zugok · · Score: 4, Funny

      I actually WANT to learn short hand. Then people don't bother asking me for lecture notes.

      --
      "I just can't sit while people are saying nonsense in a meeting without saying it's nonsense" J Watson, Sci Am 288:(4)51
    2. Re:Shorthand is not redundant yet by Wowsers · · Score: 4, Funny

      [quote]My other half still uses shorthand at work.[/quote]

      Kinky!

      --
      Take Nobody's Word For It.
    3. Re:Shorthand is not redundant yet by koinu · · Score: 2, Interesting
      I like shorthand, too.
      • I can leave my notes on my desk. Nobody can read it.
      • It actually is useful (can write faster).
      • Shorthand looks very nice. Your handwriting style gets better.
      What is the alternative? Learn Klingon? Yeah, go on, waste your time.
    4. Re:Shorthand is not redundant yet by Anonymous Coward · · Score: 0

      You can get the same result by having a really crappy handwriting.

    5. Re:Shorthand is not redundant yet by Mr.+Underbridge · · Score: 1

      You can get an even better effect by not going to class.

    6. Re:Shorthand is not redundant yet by steveo777 · · Score: 1

      Or very tiny handwriting. Back in my college days my classmates would prefer my roommate's messy scrawling to having to get a magnifying glass to read mine. Mine was very neat, but I'd fit 3-4 lines or numbers into a single cell of 5x5 per inch graph paper. What fun.

      --
      This sig isn't original enough, it's time to come up with something witty...
    7. Re:Shorthand is not redundant yet by smellsofbikes · · Score: 1

      When I was in school, there was this incredibly annoying guy who sat right beside me and just wrote down whatever I wrote. I've since realized he probably just had really bad glasses and couldn't *see* what the teacher was writing, but it was very irritating because he was a pushy, socially inept jerk.
      Soooo I learned Anglo-Saxon runes.
      I can write as quickly in a runic transliteration as I can in English block letters, and it made my notebooks look *beautiful*. I have three years' physics, biochemistry, and organic chemistry notebooks in solid runes, interspersed with drawings of chemical structures and the like.

      The only drag was when a cute girl would ask if she could have a xerox copy of my notes...

      --
      Nostalgia's not what it used to be.
    8. Re:Shorthand is not redundant yet by mrv20 · · Score: 1

      Part of me fervently hopes that your notebooks survive to be discovered by archaeologists centuries from now. That'll really confuse their theories about the 21st century...

      --
      "Algebraical symbols are used when you don't know what you are talking about" - BCS
    9. Re:Shorthand is not redundant yet by smellsofbikes · · Score: 1

      Alas, they're merely English written with different letters. Now if archaeologists found people actually using Old Norse or Anglo-Saxon on a day-to-day basis in the modern US, that'd shake things up.

      We can go further: I got so inspired by my little hobby that I changed the default font on my computer -- an Amiga, because you could DO that on them -- so it booted up in runic. That's a whole different type of archaeology, looking at what sort of software and data people were working with at different times.

      --
      Nostalgia's not what it used to be.
  3. All skills are of value by MichaelSmith · · Score: 5, Interesting

    My Dad started out working on valve amplifiers in the 1950's. Now that he has retired I want to start a business with him fixing valve amplifiers.

    1. Re:All skills are of value by MikeUW · · Score: 1

      Maybe I've misinterpreted, but that sounds a little backwards - isn't your dad supposed to retire based on you applying some skills of your own?

    2. Re:All skills are of value by MichaelSmith · · Score: 1

      His job was pretty crappy by the time he retired. But he is always looking for things to tinker with. I am mainly thinking of it as a way for him to stay mentally active. I would hate to see him gardening all day or something.

    3. Re:All skills are of value by maestroX · · Score: 1

      All experience is valuable, skills are for your resume.

    4. Re:All skills are of value by skarekrough43 · · Score: 2, Informative

      As long as there are guitar players in the world you'll have work.

    5. Re:All skills are of value by msormune · · Score: 1

      Good for you. I think valve amplifiers are far from obsolete, I have built two myself last year. Saying tubes are obsolete is like saying oil painting is obsolete, because you can use "better" materials for painting.

    6. Re:All skills are of value by blackest_k · · Score: 1

      He might find this quite inspirational

      http://blog.makezine.com/archive/2008/01/make_your_own_vaccum_tube.html

      He might not want to go this far, but skills like this are rare.

    7. Re:All skills are of value by Pope · · Score: 2, Interesting

      What's wrong with gardening? Maintaining a varied garden with multiple bloom times is a tough thing to learn and takes quite a lot of skill and effort.

      --
      It doesn't mean much now, it's built for the future.
    8. Re:All skills are of value by Anonymous Coward · · Score: 0

      "I want to start a business with him fixing valve amplifiers."

      Fixing? No, building new. They now are worth
      their weight in gold to those who appreciate
      such things.

    9. Re:All skills are of value by petermgreen · · Score: 1

      I would say it is more like saying horse/cart combinations are obsolete. Sure a few people hang on to them either for nostalgic reasons or because they have convinced themselves they are better but IMO that doesn't stop them being obsolete.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    10. Re:All skills are of value by Fallingcow · · Score: 2, Funny

      What's wrong with gardening? Maintaining a varied garden with multiple bloom times is a tough thing to learn and takes quite a lot of skill and effort.

      Yes... the skill and effort to find a compilation of garden plant data and feed it into a MySQL database, then create a website that generates a list of appropriate plants for a given span of bloom-time, with automatic adjustments for latitude and user-selected variance allowance, and then to build a wiki-ish element where users can submit layouts for whole gardens and for individual beds with their dimensions, so you can just find the ones with the highest user ratings, arrange them in your yard, print the website-generated list of required materials/plants, and plant a garden that has been democratically-selected as the optimal arrangement in whichever style you've chosen.

      You are correct. Truly, gardening is a geek's art.

      What? Why are you looking at me like that?
    11. Re:All skills are of value by Fallingcow · · Score: 1

      OMG my BLOCKQUOTE has gotten out of its cage!

    12. Re:All skills are of value by Anonymous Coward · · Score: 0

      In related news, referring to vacuum tube amplifiers as "valve amplifiers" became obsolete once we passed 30 degrees west...

    13. Re:All skills are of value by msormune · · Score: 1

      Tube amps are not used for nostalgic reasons. They DO sound better as guitar amplifiers, than solid state ones, for example. No, it's not just my opinion :) Most players and just about every major guitar amplifier maker thinks the same way.
      Yes, tube technology is mostly obsolete, in radio transmission for example. But it really excels still in some applications...

  4. Assembly coding isn't obsolete... by HappyOscar · · Score: 2, Informative

    If you have to write bootloaders and a very small number of other programs or routines. For most purposes, yes, it's rather counterproductive.

    --
    "Your mouse has been moved. Windows 95 must be restarted for the change to take effect."
    1. Re:Assembly coding isn't obsolete... by drinkypoo · · Score: 1

      It depends on what you're writing. Almost no one needs assembler until the optimization stage and even then only computationally intense tasks are likely to need it. The only other reason you need it is for bootstrapping (when instructions must be executed in a very specific order.) But there's a lot of optimization to be done. On the other hand, most people don't need to do much optimization, if they just use library functions.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Too many jokes and false entries by philbert2.71828 · · Score: 4, Insightful

    Fortran isn't obsolete. It's still popular in particle physics. Also, "buying an HD-DVD" is on the list. Not that that was ever a "skill." This list is just begging to be filled with joke entries like that.

    1. Re:Too many jokes and false entries by Anonymous Coward · · Score: 0

      Yah, I also noticed that.. for every joke entry you find just append (in Space)...

    2. Re:Too many jokes and false entries by Anonymous Coward · · Score: 2, Interesting

      Fortran is definitely not obsolete. In another life I worked for Bloomberg - the foundation of the whole Bloomberg system is written in fortran - contrary to what they'de like new hires to believe. Yeah, use C++ but we'll prevent you from using the majority of its most useful features. Weird development shop.

      -- Moomin Troll

    3. Re:Too many jokes and false entries by Anonymous Coward · · Score: 0

      FORTRAN is also still "popular" in a certain large company's turbine engine group. It's used to develop engines for aircraft that you would recognize. I put popular in quotes because almost no one actually likes it, but its still used regularly.

    4. Re:Too many jokes and false entries by Anonymous Coward · · Score: 0

      Fortran's been obsolete since 1978, it's just that
      particle physicists have no need for complex data
      structures like "trees". Recursion? for the birds!

    5. Re:Too many jokes and false entries by pimpimpim · · Score: 1

      This is good news for a whole lot of theoretical physicists/chemists who could finally put some good income to the many painful years trying to work with fortran :) Maybe I'm just not enough of a Fortran wizard but I get gray hairs just thinking about the idea of writing more than a 100 output files in fortran. At least I think that was the limit of fort.xx files you could have, I did my very best to forget all about it.

      --
      molmod.com - computing tips from a molecular modeling
    6. Re:Too many jokes and false entries by sm62704 · · Score: 2, Interesting
      The other side of the coin is a couple of articles I wrote a couple of years ago, Useful Dead Technologies and Good Riddance to Bad Tech. Both were written in a humorous vein, but I tried to be interesting and informative as well. It can be done, but I don't think Obsolete Technical Skills suceeds. Here are excerpts from my old obsolete articles mentioned above, starting with Useful Dead Technologies:

      Volume control knobs
      You're driving down the road and that song comes on. You know the one, it really rocks and you must crank that sucker up.

      But there's no crank any more. You have to take your eyes off of the road to find the one button on the fifty buttons to turn the damned thing up or down. Thank God they invented cell phones so you can call an ambulance after you wreck your car trying to turn the volume down to answer your cell phone!

      And if you want to adjust the tone, balance, or rear fade, forget it. You're either going to have to stop the car, or get a passenger to do it for you. If, that is, he or she can find the owner's manual to figure out how to.

      The automobile distributor and points
      Unless you are a classic car collector, or a geezer, you have no idea how much of a pain in the butt these things were. About every oil change or two, your car's performance and gas mileage would go down, and you would need a tuneup.

      To tune your car, you could simply hire someone. That is, if you were a sissy.

      A real man changed his own oil and tuned his own car up. You could tell a real man by the scars and scabs on his knuckles from working on his car.

      First you had to change all eight of your spark plugs. What? You only have six? Pussy! Make sure you don't get the wires on wrong, or if your car will start at all, it will lurch and backfire and run like crap.

      Then you had to take off the distributor cap, usually held on by two clips that would cut your fingers and were harder than a rubic cube solution to get clipped back on.

      Under the distributor cap was the contact points. These had to be replaced. Then you had to adjust the gap on the points. Oh shit, I forgot to adjust the gaps on the spark plugs... do that all over again...

      Now that the plugs are gapped and the points are replaced and gapped, you put the new distributor cap on... Come on... SHIT... GOD DAMNED PIECE OF SHI... ok, there it goes. Good. Gimme a bandaid, would ya?

      Now you have to set the points' dwell. What's "dwell?" Beats the hell out of me, maybe it's the amount of time the points are closed. But you have to set it with a dwell meter or your car will run like it's powered by gerbils and will suck gas like Bush sucks at being President.

      Then you have to get out your strobe and set the timing. You loosen the distributor, point your strobe at the mark on the... wait a minute... I can't see the damned mark. Stop the engine, would you?

      Damn, it's all rusty and... to hell with it, start it back up and I'll time the God damned thing by ear, piece of shit...

      Thank God and modern electronics for electronic ignition!


      --
      mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
  6. Stretching a bit to make the list by sakdoctor · · Score: 1

    I suppose it depends on your definition of skill, but I think only 4 of the 11 qualify, since although the technology might be obsolete, the "skill" would still be intuitively obvious.

  7. It's a crap list. by d3m0nCr4t · · Score: 2, Informative

    This is a list that states what the author doesn't do any more, but it's quite arrogant to assume he speaks for everyone.

  8. Great! by K.+S.+Kyosuke · · Score: 2, Insightful

    I've been waiting for this all the time... The knowledge of assembly language should have been obsoleted a long time ago, since, naturally, all the compiler programmers today just...wait...there's something fishy here...

    --
    Ezekiel 23:20
  9. Navigating by compass is obsolete? by dave1791 · · Score: 5, Insightful

    Navigating by compass is obsolete? That's like saying that keeping candles in your house in case of extended blackouts is obsolete.

    Some things on that list are either silly or shortsighted.

    1. Re:Navigating by compass is obsolete? by jez9999 · · Score: 5, Funny

      Of course it's obsolete.

      Another thing that's obsolete is like maths, because we always have calculators now.

    2. Re:Navigating by compass is obsolete? by WilliamSChips · · Score: 1

      Tell me, have you used a log table in the past ten years?

      --
      Please, for the good of Humanity, vote Obama.
    3. Re:Navigating by compass is obsolete? by Calinous · · Score: 1

      Even in this age, ships navigate using the girocompass (not a magnetic compass, but still). Yes, navigational satellites are used for pinpointing the position, but the actual helm navigation follows the indications of the girocompass.

    4. Re:Navigating by compass is obsolete? by Opportunist · · Score: 4, Funny

      Yes. Every day.

      You know, there is this one leg of my table that's a little short, so the log table comes in handy.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    5. Re:Navigating by compass is obsolete? by icebrain · · Score: 1

      Pretty much every airplane is required to have a magnetic compass of sorts. It still gets used quite a bit on small airplanes; larger ones like airliners and business jets only use it as a backup.

      --
      The meek may inherit the earth, but the strong shall take the stars.
    6. Re:Navigating by compass is obsolete? by Anonymous Coward · · Score: 1, Funny

      My solar-powered calculator doesn't work by candle-light, you insensitive clod!

    7. Re:Navigating by compass is obsolete? by ForestGrump · · Score: 1

      Why use your brain when you got buttons?
      -My 11th grade math teacher

      --
      Is it true that more people vote for the winner of American Idol, than vote for the president? -Ali G.
    8. Re:Navigating by compass is obsolete? by Chrisq · · Score: 1

      navigating by starlight is very useful in emergencies. When a hike went wrong (lost a trail) I had to use the stars to head for a road

    9. Re:Navigating by compass is obsolete? by groovelator · · Score: 5, Funny

      You ever tried to write 5318008 or 71077345 on a computer and then turn the monitor upside-down? Calculators are not - and will never be - obsolete and there, gentlemen, I rest my case.

    10. Re:Navigating by compass is obsolete? by ZeroExistenZ · · Score: 1

      I regurlary see an ad in the papers for a "Skilled calculator", always from the same firm. It seems to me, they were too progressive and now realized their mistake.

      --
      I think we can keep recursing like this until someone returns 1
    11. Re:Navigating by compass is obsolete? by Anonymous Coward · · Score: 0

      Wi got teh spel cheka no to!

    12. Re:Navigating by compass is obsolete? by Karl0Erik · · Score: 0

      gramer n speellin also obslet cuz we hv speel checker lol

    13. Re:Navigating by compass is obsolete? by gravesb · · Score: 1

      Even in the Army, with full access to GPS satellites, the compass is essential.

      --
      http://bgcommonsense.blogspot.com
    14. Re:Navigating by compass is obsolete? by Anonymous Coward · · Score: 0

      A compass is really only useful when doing search and rescue operations. However, you still have and use the GPS.

    15. Re:Navigating by compass is obsolete? by mdmkolbe · · Score: 1

      Tell me, have you used a log table in the past ten years?

      Actually, yes I have. It comes very much in handy when multiplying powers of 2. Example from my work yesterday: How may bytes does this 16x256 array of double (8 byte each) take. 16->4, 256->8, 8->3 so the total is 15 which is 32k. I'm only 25 years old and I find it useful day to day work.

    16. Re:Navigating by compass is obsolete? by Anonymous Coward · · Score: 0

      The magnetic is also used to set and adjust the gyrocompass. Gyros precess faster than the magnetic pole drifts.

    17. Re:Navigating by compass is obsolete? by Don853 · · Score: 1

      That's got nothing to do with log tables. It requires understanding of logarithms, but that's not the same thing.

      This is a log table. It's the equivalent of a sine or cosine or tangent table - it's almost totally useless if you have a working calculator.

    18. Re:Navigating by compass is obsolete? by Thumper_SVX · · Score: 1

      Navigating by compass is certainly NOT obsolete. I'm a private pilot as a hobby, and in my flight bag I have a few items I might need in the event I end up on the ground somewhere I don't know. Things like maps, a small first aid kit and a COMPASS. Sure, in most of the midwest if I set down I'm usually not too far from a road... but having had one forced landing in my life I can tell you that it's easy to get disoriented when you're on unfamiliar ground. Where I set down, there was a main road just a couple of miles to the Northwest (I could see it as I descended and made a note of it). After the plane landed and flipped, I got out and had no idea which way was Northwest... until I whipped out my compass and then took a sort of limping hike.

      Hell, I've even used my compass in-flight in a plane that had no compass on the dash (unusual) and the gyro decided it was going to spin incessantly when I tried to cage it and pointed in the right direction for maybe two seconds every minute.

      I disagree with just about everything on this list. The skills may be unpopular... but most of them aren't obsolete. Not yet... and some never will be.

    19. Re:Navigating by compass is obsolete? by Tracy+Reed · · Score: 1

      As a pilot I can tell you that navigating by compass remains a critical skill used by anyone who flies an airplane. I often have other instruments to help me along as well but a compass is a critical no-go if not working instrument by my own rules and by the FAA regulations.

    20. Re:Navigating by compass is obsolete? by zippthorne · · Score: 1

      ahem: Gyrocompass, as in gyroscope, which is all it is. And you still need a magnetic compass to set it, because it will drift, nutate, and precess. And, in an airplane, you can get gimbal-lock, too. (well, a ship that crosses the globe could have gimbal lock, as well, but they'd probably travel through a number of ports so they'd have ample opportunity to keep the gyros updated)

      --
      Can you be Even More Awesome?!
    21. Re:Navigating by compass is obsolete? by martinQblank · · Score: 1

      Alright - who turned their laptop upside down after they read that? Or, should I say, who ELSE...

    22. Re:Navigating by compass is obsolete? by maxume · · Score: 2, Informative

      I used print screen and an image editor...

      --
      Nerd rage is the funniest rage.
    23. Re:Navigating by compass is obsolete? by dido · · Score: 1

      The US Navy still teaches its people how to navigate using chronometers, almanacs, sextants, and compasses, just in case the GPS system falls out for any number of plausible reasons.

      I bought an abacus on my last trip to Japan. Will be buying a slide rule when I can find one. All of these on the same principle...

      --
      Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
  10. Assembly language is obsolete? by Malevolent+Tester · · Score: 3, Informative

    I'm neither a console programmer nor a demoscener, but isn't assembly very much alive and kicking in these two fields?

    --
    If you haven't made a developer cry, you've wasted a day.
    1. Re:Assembly language is obsolete? by sqldr · · Score: 3, Insightful

      Correct. They also missed out one of the main reasons for the demise of assembler though - the rise and rise of x86 compatible CPUs with their shit-awful instruction set and 4 registers. Assembler on 68k, powerpc, risc, cell, hell, anything but intel is still very doable.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    2. Re:Assembly language is obsolete? by MichaelSmith · · Score: 1

      Assembler on 68k, powerpc, risc, cell, hell, anything but intel is still very doable.

      I taught myself 6502 when I was a teenager. It had a nice, logical instruction set. Much later I had a look at the alpha assembly output from a DEC C compiler. Very nice code. Easy to relate to C source.

    3. Re:Assembly language is obsolete? by nagora · · Score: 1
      They also missed out one of the main reasons for the demise of assembler though - the rise and rise of x86 compatible CPUs with their shit-awful instruction set and 4 registers.

      Oh, yes; so true. Actually, until AMD came along the x86 set only had 1 general purpose register where you could put data and know that it wouldn't be smashed as a side-effect of some instruction. Utter garbage of a processor family. Still is, really, if you're one of those nut-cases that think they might want TWO stacks on the go at the same time! Crazy, I know.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    4. Re:Assembly language is obsolete? by Wingsy · · Score: 1

      I agree with ya, mostly, but having 2 stacks is perfect if you're writing a Forth compiler. I went through a period in the early 80's where just about everything I did (embedded systems) was in Forth using compilers I wrote. Loved that 6809 chip, and the 68000 family made writing software just plain ole fun. In assembly & Forth of course.

      --
      If I didn't have absolutely NOTHING to do, I wouldn't be here.
    5. Re:Assembly language is obsolete? by kestasjk · · Score: 1

      Assembler on "risc"? One of the reasons for not using risc is to make assembly programming easier, because you don't have to do every little thing yourself.

      The meme is: x86 is slow because the instruction set is old and caters to the needs of assembly programmers.

      --
      // MD_Update(&m,buf,j);
    6. Re:Assembly language is obsolete? by Calinous · · Score: 1

      You haven't seen the Obfuscated C Contest source code. I don't think you can relate that to any kind of assembler

    7. Re:Assembly language is obsolete? by learningtree · · Score: 1

      Absolutely correct.. In fact, I work for a company where I have to analyze the architecture of DSP processors and optimize the assembly code to achieve the best performance for applications. I wonder if there is any other way to do it other than assembly code.

    8. Re:Assembly language is obsolete? by nagora · · Score: 1
      I agree with ya, mostly, but having 2 stacks is perfect if you're writing a Forth compiler.

      I was being sarcastic about the lack of a need for 2 stacks, specifically because I have written Forth compilers myself. There are many other uses for multiple stacks, of course. 68K was a great programming model.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    9. Re:Assembly language is obsolete? by sqldr · · Score: 2, Informative

      Assembler on "risc"? One of the reasons for not using risc is to make assembly programming easier, because you don't have to do every little thing yourself.

      The ARM Risc is a joy to program. 15 general purpose registers that could be used with any instruction, conditional instructions, I could go on all night. This caters perfectly to the needs of assembly. The only thing that x86 caters for is the need for compatibility with the 8086.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    10. Re:Assembly language is obsolete? by iainl · · Score: 1

      That's hardly fair though; I struggle to relate it to the sensible way of writing the same C, half the time.

      --
      "I Know You Are But What Am I?"
    11. Re:Assembly language is obsolete? by Anonymous Coward · · Score: 0

      Get your facts straight please. Yes, there are a few instructions with dedicated registers, but nowadays you can use most instructions with most registers (of the appropriate type), and there are quite definitely more than four of them. Of course you can't touch eip directly and messing with esp is kind of a no-no too, but other than that, you're usually free to do whatever strikes your fancy.

    12. Re:Assembly language is obsolete? by Anonymous Coward · · Score: 0

      They are. If you take a look at Pouet you can find many demo engines that would put any commerical game engine to shame in a fraction of the space.

    13. Re:Assembly language is obsolete? by EnglishTim · · Score: 1

      For current-gen consoles, there's not a great need to write very much assembler (even SPU code on the PS3 is commonly done in C or C++), but being able to read and understand assembler is still a very useful skill.

    14. Re:Assembly language is obsolete? by Malevolent+Tester · · Score: 1

      I was thinking in terms of handhelds rather than 360s and PS3s. I've only done a tiny bit of x86 ASM, but I can imagine how coding in ASM for the Cell processor could turn you into a gibbering, drooling wreck.

      --
      If you haven't made a developer cry, you've wasted a day.
    15. Re:Assembly language is obsolete? by EnglishTim · · Score: 1

      Even on something like a PSP, most of the code will be in C++ or C. A few odd bits might be optimised in assembler, but the majority of the game team will not write any assembler. It's still useful to be able to read assembler, though.

      I don't think the ASM for the Cell is that tricky - but most of the time you'd still use C or C++ - just so much more maintainable and straightforward to write.

  11. I have some news for this douchebag by Anonymous Coward · · Score: 1, Insightful

    Assembly programming is still a very much needed skill for embedded systems developers that need to run highly-optimized code with very limited memory and processor resources. Your cellphone doesn't have a Core 2 Duo in it, retard.

    1. Re:I have some news for this douchebag by demallien2 · · Score: 1

      To expand on this, I write code for set top boxes. I recently saw some code written by someone evidently completely untrained in assembly programming. It looked like this:

      for (i = 0; i field0 = blah_0; ...
              pStruct->.fieldn = blah_n;
      }

      which in turn gives:

              mv r1, i
              mv r2, sizeof(struct)
              mult r1, r2 ;result now in r1
              mv r2, addr(struct_array)
              add r1, r2 ; result now in r1 is the pointer to struct_array[i]
              mv r3, r1 ; copy stored in r3

              mv r1, r3
              add r1, field0_offset ; r1 now contains a pointer to field0 of the first struct
              mv addr(r1), blah_0 ....
              mv r1, r3
              add r1, fieldn_offset ; r1 now contains a pointer to fieldn of the first struct
              mv addr(r1), blah_n

      The programmer has probably just saved a few hundred bytes of code, and lots of processor cycles each time the routine is run.

      As it so happens, I discovered this little effort when I was reverse engineering some code. Later, when I was given access to the actual source, it amused me greatly to see it all written out in C :-)

  12. I'll add one by edittard · · Score: 5, Funny

    Here's mine: writing decent stories for slashdot.

    --
    At the bottom of the /. main page it says 'Yesterday's News'. Well they got that right.
    1. Re:I'll add one by edwardpickman · · Score: 4, Funny

      Decent stories are more like Bigfoot. Lots of people claim to have seen them but there's no physical evidence.

    2. Re:I'll add one by eclectro · · Score: 1

      I think that getting "first post" on slashdot is an obsolete skill. I mean, we've all done it already, right?

      --
      Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
    3. Re:I'll add one by Anonymous Coward · · Score: 0

      I saw a decent story on Slashdot just the other day!

    4. Re:I'll add one by Not_Wiggins · · Score: 1

      Here's mine: writing decent stories for slashdot.

      Ha! That's not valid because it presupposes that the skill ever existed!

      Might as well include "hunting unicorns" or "RTFA." 8D

      --
      Diplomacy is the art of saying, "Nice doggie!" until you can find a rock.
  13. Using a rotary phone is a "technical skill"?? by Viol8 · · Score: 4, Interesting

    Next he'll be saying we've lost the technical skill of picking up the phone handset because of speaker phones and mobile phones.

    Anyway , here in the UK new and refurbished rotary phones are a niche fashion item. You can pick them up in a number of places for a reasonable amount.

    1. Re:Using a rotary phone is a "technical skill"?? by MichaelSmith · · Score: 1

      Anyway , here in the UK new and refurbished rotary phones are a niche fashion item.

      I am sure my six year old son would find it hilarious, and need help using one for the first time.

    2. Re:Using a rotary phone is a "technical skill"?? by stiggle · · Score: 1

      New and refurbished?
      What about those of us who still have an original (admittedly with a modular plug on the end) but it thankfully still works, although I tend to only use it for incoming calls and don't dial out on it much.

    3. Re:Using a rotary phone is a "technical skill"?? by PinkyDead · · Score: 1

      You are remiss in your child's education: Phone

      --
      Genesis 1:32 And God typed :wq!
    4. Re:Using a rotary phone is a "technical skill"?? by archen · · Score: 1

      If you've ever seen a kid approach a rotary without having ever seen one, you'd be surprised at how they are not accustomed to such a device having grown up in a world where everything has a button. Think about it. What other device aside from a rotary would you use in that way now days? Aside from that taking your finger out of the dial and placing it over the next digit before the dial returns to speed things up is sort of a skill (not much of one and not technical) that has to be learned.

      I still have a rotary phone because I for some reason like them, however the real pain of rotary is only realized by the extremely long phone cord you need in order to move the phone anywhere.

    5. Re:Using a rotary phone is a "technical skill"?? by Lawrence_Bird · · Score: 1

      Mine is right next to the TV chair..it will not get lost as it weighs in at a good 3 lbs if not 5. Its far easier to cradle a handset then the crappy wireless (which are for all intents cell phone clones) ones. And it can be used as a weapon in a pinch!

      As to kids seeing one.. hide the TV remote and see if your kid can figure out how to change the station. 'Daddy don't lie! Nobody ever had to get up and touch the TV to change the channel!'

    6. Re:Using a rotary phone is a "technical skill"?? by Viol8 · · Score: 1

      "that has to be learned."

      Sure it has to be learned , in the same way as how to open a coke can has to be learnt. But you can hardly call something that takes 5 seconds to master a skill.

    7. Re:Using a rotary phone is a "technical skill"?? by ZERO1ZERO · · Score: 1
      No, this is where the rotary phone is at: http://www.redferret.net/?p=7335

      Imagine in the bar, phone goes, and you whip that bad boy out on the bar and answer it - how cool you would be!

    8. Re:Using a rotary phone is a "technical skill"?? by ZERO1ZERO · · Score: 1

      That toy has been around for decades... I remeber playing with one 25 years ago. Now my kids have one. And I'm sure their kids will have one as well.

    9. Re:Using a rotary phone is a "technical skill"?? by Blkdeath · · Score: 1

      As to kids seeing one.. hide the TV remote and see if your kid can figure out how to change the station. 'Daddy don't lie! Nobody ever had to get up and touch the TV to change the channel!'

      Heh, remotes are so ubiquitous it's actually getting harder. It was only by accident that I found the panel that changes channels on my set. It's on the right side near the top behind the front panel behind a door ...

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

  14. Cracking protected information. by Thanshin · · Score: 5, Insightful

    Without assembly knowledge we'd have uncrackable IP "protection" schemes.

    1. Re:Cracking protected information. by smittyoneeach · · Score: 1

      Oh, so when there is a major format change in a piece of hardware, like DVD players, I won't be left out in the cold if I can find a way to make other equipment work?
      This kind of thing hardly sounds good for the economy.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    2. Re:Cracking protected information. by Opportunist · · Score: 4, Insightful

      The problem goes way beyond IP protection. Do you think that pseudo "AES encryption" device we heard of yesterday that only used some XORing for "protection" would have been debunked if there wasn't people who still know their assembler?

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    3. Re:Cracking protected information. by somersault · · Score: 1

      Why would you need an assembler to examine the differences between an input and an output? There are more ways to decipher encryption than by reverse engineering the machine that did the encrypting. I doubt the hard drive even used any actual code to do the encryption, and even if it was proper AES encryption it would probably still have been done in hardware rather than software?

      --
      which is totally what she said
  15. Churn butter? by WK2 · · Score: 5, Insightful

    Churn butter is on the list. I guess it just comes that way out of the cow now. Science is amazing.

    --
    Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
    1. Re:Churn butter? by Farmer+Tim · · Score: 5, Funny

      I guess it just comes that way out of the cow now.

      The surprising part is how butter comes out in those brick shapes. Surprising for the cow, that is...

      --
      Blank until /. makes another boneheaded UI decision.
    2. Re:Churn butter? by Anonymous Coward · · Score: 0

      And frozen, too! Man, that has to hurt. Sure glad that I don't have udders. (for more reasons than just that...)

    3. Re:Churn butter? by kryliss · · Score: 1

      Gives a new meaning to shitting a brick.

      --
      --- If the bible proves the existence of God, then Superman comics prove the existence of Superman.
    4. Re:Churn butter? by JabberWokky · · Score: 1

      I believe they mean Churn Butter by hand, which is what it is listed as on the original wiki that this one was lifted from.

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    5. Re:Churn butter? by BForrester · · Score: 1

      I feel sorry for the "cheese cows."

    6. Re:Churn butter? by acciaccatura · · Score: 0

      Like separating out the cream. Now the cows just lie on their backs and the cream rises to the top.

  16. But what is going to be obsolete ? by CreatorOfSmallTruths · · Score: 1

    As a middle manager with programming and design experience and CS degree in my 30s I'd much rather know what *is going to become obsolete* in the next 10 years, and have that list updated each .. say.. month.

    Why? because then I'll be able to make educated guesses about where I'm going next. Hell, for a western culture manager the answer may be "you are going to be out of work next" because managerial skills are going to be very inexpensive (I don't know , but that may be the case).

    So - predicting the future is not that hard for the most part - for example, C - will it survive or not? I'd say that seeing linux popularity and the things people do with C today its going to stick around for at least the time it takes to build a new open source OS - something like 4 years at least. C++ - some people like it, others hate it, if Java will continue getting better, who knows?. PCs - will probably get easier to use, less technical to operate and more friendly. Managers - who needs them anyway :-) ?

    1. Re:But what is going to be obsolete ? by MichaelSmith · · Score: 3, Informative

      So - predicting the future is not that hard for the most part - for example, C - will it survive or not? I'd say that seeing linux popularity and the things people do with C today its going to stick around for at least the time it takes to build a new open source OS - something like 4 years at least. C++ - some people like it, others hate it, if Java will continue getting better, who knows?

      Everything which is written in Java uses C.

      Everything which is written in C uses Assembler.

      Everything which is written in Assembler uses machine code.

      And so on.

    2. Re:But what is going to be obsolete ? by tyresyas · · Score: 1

      So - predicting the future is not that hard for the most part - for example, C - will it survive or not? I'd say that seeing linux popularity and the things people do with C today its going to stick around for at least the time it takes to build a new open source OS - something like 4 years at least.

      Seriously? You think C is going disappear? You can talk about all the other programming languages you like, but what do you think most interpreters/compilers are written in? And I'm dying to know what this new open source OS will be written in if not C.

    3. Re:But what is going to be obsolete ? by CreatorOfSmallTruths · · Score: 1

      So you actually say that assembler is needed and not obsolete like tfsdp says ? If you do - that's a valid opinion as well, if you think the list is correct - why not add C in the mix (and I'm not saying it should, just raising the question)

    4. Re:But what is going to be obsolete ? by MichaelSmith · · Score: 1

      I think I am saying that the whole stack is still there, like the genes we share with crocodiles.

    5. Re:But what is going to be obsolete ? by CreatorOfSmallTruths · · Score: 1

      .. I didn't say anyone is going to do it, I didn't even say it's going to be done by a language other than C if it's done. What I said was that *if* anyone will choose to create an open source OS *without using C* and it will be as successful as linux *then* we need to think about C.

      As for interpreters and compilers are concerned , lots of them are not using C per say, they bootstrap from their own language, so find another strawman to hang your claims on.

      p.s. I really like C and wouldn't like to see it vanish.

    6. Re:But what is going to be obsolete ? by Opportunist · · Score: 4, Insightful

      As someone who uses many languages I can tell you this: All imperative languages can be learned in very reasonable time if you know your C. Everything is derived from C today, from PHP to Perl to Java. Why? Well, maybe because the guys who wrote those languages come from C.

      In a nutshell, it doesn't matter what language you use, which language is the next big thing, or what language becomes obsolete tomorrow. You will probably not know all those fancy functions that do what you used to do by hand, but what matters is whether you know the math behind the code. I've seen so many people claiming to know Java, C# and whatnot, just to give me that incredibly blank stare when I ask them for hash tables. Yes, they know every function, every class in Java by heart, but they have no knowledge of what they should actually DO with it.

      Now, it might not be a "necessity" tomorrow when there is a function that does it for you. But it is VERY easy to learn about a function (hell, look it up, it ain't like there's no online help file for it) while it is not so trivial to understand what it actually DOES.

      So it does not matter what language will arise or what language becomes obsolete. What matters is that you know the theory behind the structures you're supposed to use. When you know that, you can understand what the functions and classes do. When you understand that, you can more efficiently and sensibly fill them. When you do that, your program will work with fewer bugs and fewer "why the fu.. doesn't that work now, it did last time" moments.

      Don't learn languages. Learn theory!

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    7. Re:But what is going to be obsolete ? by Calinous · · Score: 1

      So, in the end, everything which is written in Java uses machine code. Yet, I haven't seen any job openings for people writing programs in machine code, while the Java market is rich.
            Writing programs in machine code (or repairing programs by modifying their executable image, modifying the machine code) was a real skill back then - see the story of Mel (and Real Programmers).

            A skill that is certainly obsolete is programming a computer using switches (or introducing the boot loader from a panel with switches)

    8. Re:But what is going to be obsolete ? by CreatorOfSmallTruths · · Score: 1

      In that case, I agree - this whole post is stupid - never laugh on someone competencies!

      Anyway, the number of people who are knowledgeable in assembler, for example, these days is very small; that probably mean that if you think its not a lost art and it will live on you should find a job at it :) because it's going to worth a lot in the next couple of decades.

    9. Re:But what is going to be obsolete ? by Fnord666 · · Score: 1

      I'd much rather know what *is going to become obsolete* in the next 10 years, and have that list updated each .. say.. month
      Each month just scan the trade rags for the hot new whatever technology that they say is going to revolutionize the industry. There's your list.
      --
      'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
    10. Re:But what is going to be obsolete ? by Saint+Stephen · · Score: 1

      Who writes Java Virtual Machines?

    11. Re:But what is going to be obsolete ? by ultranova · · Score: 1

      Yet, I haven't seen any job openings for people writing programs in machine code, while the Java market is rich.

      Assembly guys don't search for job openings. Assembly guys have teams of agents managing their job offers.

      Seriously speaking, if you need assembly coders, it is likely that you have an embedded device, a runtime, low-level kernel issue, or some other kind of problem where whatever is written must work and work well from the beginning, since failure to do so would take the whole system down - and in the case of embedded devices, updating might be impossible, so the only way to fix bugs is to exchange the faulty devices to new ones.

      Would you hire Joe Random who happened to answer a newspaper add for such a job ? Of course not, you want someone who you have some reason to think actually knows his stuff. So you hire a headhunter to find someone for the job. So assembly guys don't look for jobs, assembly guys have jobs looking for them.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    12. Re:But what is going to be obsolete ? by Anne+Thwacks · · Score: 1
      it doesn't matter what language you use so long as its c.

      Of course, people fail to notice that c is, of course, just the assembler for the PDP11 in a handy, pocket size, format, and the PDP11 was designed as a hardware Fortran machine!

      Life would be funny if it was not so confusing. If you dont believe me, try debugging CDC7600 assembler.

      --
      Sent from my ASR33 using ASCII
    13. Re:But what is going to be obsolete ? by quizzicus · · Score: 1

      Don't learn languages. Learn theory! Most of the people who've interviewed me for jobs would disagree with you there, but I find it holds true when you actually want to accomplish something.
    14. Re:But what is going to be obsolete ? by Opportunist · · Score: 1

      The point is that C has become the "basic" language of imperative programming. Yes, it was designed as a tool so you don't have to dive into the pits and arrows of hardware, so you can program more sensibly, but it has grown beyond that point. Every programmer who ever touched something resembling "system programming" has come into contact with C, whether he wants or not, because C has become the language to program close to hardware while still maintaining at least some degree of hardware independence.

      So every "good" programmer, at some point in his career, learned C, and usually learned it pretty well. Since new languages are usually made by good programmers (at least good new languages, which become popular), most of them somehow lean towards C in their syntax. Of course it has its shortcomings in different areas, that's why new languages arose. If C was the pinnacle of languages, no new languages would ever come into existance because, well, why reinvent the wheel when you have one that does everything you want to do?

      But those languages are made by people who know C. Many of those languages are even written in C or one of its direct descendents, like C++. So it is logic that the syntax used will be similar to C. Why should someone who knows his C in and out invent a completely different syntax? Just to confuse the presumably "new" coder who needs a language that's easier to learn than C? He won't ever be able to move to C without problems.

      So knowing C usually means that you have a rather smooth transition towards other imperative languages which are used today. Yes, some have slightly different functions, some use a slightly different syntax, but when you look at it closely, you will notice that the basic makeup is still the same. Whether the start of a function is indicated by brackets or some keyword does not matter, what matters is that there are functions and those functions work in exactly the same way.

      I don't question that C was originally meant to be just a tool. Many great things came from small inventions that their developer didn't dream of when they created them. I doubt Linus thought that Linux could become such a huge hit when he wrote his first kernel.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    15. Re:But what is going to be obsolete ? by Opportunist · · Score: 2, Insightful

      That's because HR people interview for jobs. This is changing, at least here, where the recruitment of key personnel is being outsourced to recruiting companies who DO know what to look for in a good applicant. Mostly because they usually have terms like "applicant must stay 6 months before we see any money" in their contracts.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    16. Re:But what is going to be obsolete ? by Arapahoe+Moe · · Score: 1

      Theory and syntax are serious boring horseshite. Combine the two and I can see why most people can't manage to learn more than 1 or the other. There's only so much novocaine that the skull can take and all. Maybe if one of the high paid professors or authors of successful language books took the time to design a system/class/whatever that allows you to learn a programming language such that you understand the theory and syntax while doing something interesting! It would be like having a Hooked on Phonics for programming.

      You think people learn how to build houses best by learning about the theory of building houses? Or do they learn best by helping to build some houses while learning pratical implementation details as well as the theory behind said implementation? Seriously man, when you tell people to just "learn theory!", you really just sound like a fucken princess who doesn't have a clue how much money her shoe habit is costing her father/husband. Do you really want to act like a princess, mang?

    17. Re:But what is going to be obsolete ? by Anonymous Coward · · Score: 0

      I've seen so many people claiming to know Java, C# and whatnot, just to give me that incredibly blank stare when I ask them for hash tables. Yes, they know every function, every class in Java by heart, but they have no knowledge of what they should actually DO with it.

      Now, it might not be a "necessity" tomorrow when there is a function that does it for you. But it is VERY easy to learn about a function (hell, look it up, it ain't like there's no online help file for it) while it is not so trivial to understand what it actually DOES. You mean like a dict? Yeah, I really don't care that it is a hash table. I just care about its properties: unique keys that must be immutable. Values that can be mutable. Methods for testing membership are "d.has_key(x)" or "if x in d" and so on... And I care that it's fast already, so I don't have to reinvent the wheel (hash table), which would almost certainly be slower than the C-coded, optimized built-in.

      Why should I care again? It's not going to break on me. It's going to have the same exact properties I already mentioned every time I use it. I guess I could subclass the dict type and write my own (slower) sorting and membership testing functions if I felt like being a masochist one day, but why?
    18. Re:But what is going to be obsolete ? by Anonymous Coward · · Score: 0

      Our story opens with a view of a gentle lake. We see a white eighteen foot sailboat quietly making its way along pushed by a light breeze. Two old men are lounging in the back taking in the sun and sipping from ice filled glasses.

      The peace is suddenly broken by the appearance of a sleek low speedboat screaming across the lake. Inside are two young surfer types with dark tans, rippling muscles, and huge smiles of excitement on their faces as they fly along at heart stopping speed.

      The speedboat rips past the sailboat like a bat out of hell and the two old men grin knowingly at the beautiful coloring and pin stripes that adorn the arrow-like hull. The wake from the speedboat bounces the sailboat and causes one old man's fishing hat to fall off into the water. The old man hands his drink to his buddy, reaches into the water and retrieves the soggy hat. He twists the hat to squeeze out the water and places it on the railing to dry in the sun.

      Suddenly, the scene is shattered by an explosive bang and the speedboat is engulfed in a cloud of inky black smoke. When the smoke clears, the speedboat is sitting lifeless in the water and the two surfer dudes are standing at the open engine compartment cursing and arguing.

      "Ahoy! Can we help?" calls one of the old men.

      "Have you guys ever seen one of these Flash 300V racing engines before?" yells back one of the kids with a clear look of doubt on his face.

      "Can't say that I have," answers the old guy. "But I'll be happy to see what I can do."

      "Forget it old man!" yells the kid. "You'll just get in our way. Stick to your row boat and we'll take care of it ourselves."

      The old man grins acceptance and waves goodbye to the kids as they grab tools from a box and start turning screws and pulling cables on the engine hoping to figure out what happened and how to fix it.

      As the sailboat bobs away pushed by the breeze, the old men sit back down and relax taking in the warmth of the sun. The old man that talked with the boys turns to his buddy and asks, "Do you suppose that I should have told him that they probably just needed to lessen the voltage being fed to the fuel flow control module in the intake subsystem?"

      "Not really," answers his buddy. "They wouldn't be interested. They'll just turn adjustment screws and tinker with module inputs and outputs until they finally stumble upon a combination that works."

      "I suppose that you're right," replies the first. "After all, that's pretty much how we figured things would go back when we were first designing the damn things. Can I get you a fresh drink?"

    19. Re:But what is going to be obsolete ? by Opportunist · · Score: 1

      You think people learn how to build houses best by learning about the theory of building houses?

      Most definitly, it was way more action building those cathedrals in medieval times with try and error, with people dying in the collapse than today, with people computing statics before trying to build something.

      But then again, do you think you could get that past building codes of today? Damn bureaucrats, I tell you.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    20. Re:But what is going to be obsolete ? by Arapahoe+Moe · · Score: 1

      Well you twisted my argument around but whatever, go ahead and can claim that theory in the ivory tower is the best way to go, all you want. You'd be incorrect but I'm pretty sure that doesn't matter to the kind of people who would argue something like that.

    21. Re:But what is going to be obsolete ? by demallien2 · · Score: 1

      Do a search for "embedded" instead of "assembly language" on any job site...

    22. Re:But what is going to be obsolete ? by Anonymous Coward · · Score: 0

      Which is why I'll stick with an HLL implemented in itself, like Lisp, or Factor, or Forth. No C required.

      Doesn't it seem kind of damning that the Java guys couldn't even write Java in itself? Java is such a good language that ... even C is better than it at the one program we're writing.

      Metacircularity isn't exactly a new concept, and it brings a ton of other benefits.

  17. Carb settings? by aproposofwhat · · Score: 1
    My 1993 VW Vento still has a carb - I never have to tweak it though, because it's a VW ;o)

    Now if it was a Dagenham dustbin...

    --
    One swallow does not a fellatrix make
    1. Re:Carb settings? by linzeal · · Score: 1

      You don't drive very often from sea level to 8000 feet like we do here in Oregon and Washington or you would be used to it. Last one I changed was on a 68 VW bus though.

    2. Re:Carb settings? by jd678 · · Score: 3, Informative
      No, it isn't a carb. It's single point injection, aka throttle body injection.

      Have a good look around the car and you might notice the mono-motronic ecu, the catalytic converter, the fuel pump for the injection system. Take the air filter housing off and you'll spot the injector aswell...

    3. Re:Carb settings? by Gordonjcp · · Score: 1

      My 1991 Citroën AX GT has a carb, my 1988 Citroën CX 22TRS has a carb and my 1981 Citroën CX 2400 Break has a carb. They all produce slightly cleaner emissions than the limit for modern, fuel-injected, catastrophic converter-equipped cars.

    4. Re:Carb settings? by hal2814 · · Score: 1

      At least you could argue new automobiles are exclusively fuel injected now and have been for at least a decade. Most new boats sold today are still carbeurated. I'm pretty sure that's also the case with motorcycles and ATVs.

  18. Obsolete skills by ta+bu+shi+da+yu · · Score: 5, Insightful

    I'm looking forward to the day when blogging becomes obsolete.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Obsolete skills by Anonymous Coward · · Score: 0

      I'm looking forward to the day when blogging becomes obsolete.
      It already is. Anything a blogger has to say has been said before on another blog that nobody cares to read.
    2. Re:Obsolete skills by Mythrix · · Score: 1

      I'm looking forward to the day when blogging becomes obsolete.

      That will be when these lasers are finished.
    3. Re:Obsolete skills by ta+bu+shi+da+yu · · Score: 1

      I guess. But if one blogger writes in a forest, will anyone bother to make a comment?

      --
      XML is like violence. If it doesn't solve the problem, use more.
    4. Re:Obsolete skills by Anonymous Coward · · Score: 0

      I too would like a time machine

    5. Re:Obsolete skills by Anonymous Coward · · Score: 0

      I think your definition of the word "skill" might be a tad inclusive...

  19. Another one by L4t3r4lu5 · · Score: 5, Funny

    Voting for a democratically elected official?

    Yeah yeah, Troll.

    --
    Finally had enough. Come see us over at https://soylentnews.org/
    1. Re:Another one by Anonymous Coward · · Score: 0

      You still vote, and the officials are still elected democratically; however, the "Voice of the People" is distorted, remixed, and only then declared. It's merely a question of the voice of which people?

  20. So, I'm obsolete, huh? by Wingsy · · Score: 5, Insightful

    I design embedded systems for a living, and this obsolete assembly language skill is what distinguishes my designs from those other companies. True, it takes me a little longer to get the code done, but it runs faster, has more features, and fits into a much smaller memory space than what I could do with C, or anything else. (Not to mention the fact that all the bugs in my code are all mine and none were introduced by a compiler.) I feel like it's to my advantage that assembly has faded from most designer's skill set. I won't deny that this skill is on the endangered species list, but to group it with the skill needed to dial a rotary phone made me speak up. It may be rare but it certainly isn't useless.

    --
    If I didn't have absolutely NOTHING to do, I wouldn't be here.
    1. Re:So, I'm obsolete, huh? by imsabbel · · Score: 1

      My grandfather also still makes basket from willow wickers.
      They are more durable than plastic ones, repairable, and look nices.

      He is still obsolete in doing so.

      (and i dont get those "more features" part. Are you talking about your bugs?)

      --
      HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
    2. Re:So, I'm obsolete, huh? by Wingsy · · Score: 1

      No, I'm not talking about my bugs. I'm saying (as if you really didn't know) that I can pack more stuff into a smaller chip with assembly than with any higher level language. The end result is I can use a cheaper chip to do the same thing, or more things with an equivalent sized chip. So making something that's $12 rather than $14 means my wicker basket is not only more durable but costs less. When that becomes obsolete let me know.

      --
      If I didn't have absolutely NOTHING to do, I wouldn't be here.
  21. Creative Destruction at Work by OakLEE · · Score: 4, Interesting

    I have been reading Alan Greenspan's autobiography and he consistently mentions the concept of "creative destruction," which perfectly describes the duality of the capitalist society we live in (even all of you supposed socialists in Europe). It describes both the benefit and burden of the market economy. The benefit of having (generally) free markets allocate resources in society is the innovation they brings (i.e., progress), but a cost of that progress is the obsolescence of things which are now, for lack of a better phrase, useless because of it.

    I've noticed that we on Slashdot seem to struggle with this concept daily, be it the loss of jobs to outsourcing, development and adoption of new technology, reform of IP laws, the slow death of the MPAA/RIAA, and even the subject of this article (which is the perfect example). It is probably a little off-topic, but I think this common thread should in these subjects should be pointed out, because all of our discussions seem to hinge on this critical question: Is the creation worth the destruction?

    --
    The sun beams down on a brand new day, No more welfare tax to pay, Unsightly slums gone up in flashing light...
    1. Re:Creative Destruction at Work by c6gunner · · Score: 1

      Creation and destruction? Nonsense. Using that mindset, every time you get a job in a new field, you're destroying your previous career. If you get married, you're destroying your bachelorhood. And if you have kids, you're destroying your life.

      Well, ok, maybe that last one is true.

      Anyway, what you call "the duality of capitalism / creation and destruction" I call life .

    2. Re:Creative Destruction at Work by top_down · · Score: 1

      Apparently Alan Likes Schumpeter. Creative destruction is central to his work.

      --
      Anyone who generalizes about slashdotters is a typical slashdotter.
    3. Re:Creative Destruction at Work by belg4mit · · Score: 1

      http://en.wikipedia.org/wiki/Creative_destruction

      a) Greenspan is just parroting prior thinkers
      b) it's not really about capitali$m

      --
      Were that I say, pancakes?
  22. The only thing redudant is this list by timmarhy · · Score: 0, Redundant
    assembly language, IRQ conflicts? fuck all these things are VERY important and used by people everyday.

    they still teach asm at uni.

    --
    If you mod me down, I will become more powerful than you can imagine....
  23. Funny, I wrote in assembly language only last year by slashbart · · Score: 2, Informative

    Writing a interrupt driving task switcher for uCos-II, completely impossible in even C.

    Bart.

    P.S. developing on Rabbit microcontrollers sucks for large applications. Dynamic-C is a toy, and the Softools compiler is buggy as hell.

  24. carbon paper by rpillala · · Score: 1

    Sometimes when my students suffer an arm/wrist injury and can't write, I give carbon paper to someone else in the class with good handwriting to make an instant copy of the notes. This also works well for students with visual impairments (it's not the only thing I do in those cases) or absentees when I know someone is going to be absent for an extended period.

    I wouldn't call writing on carbons a technical skill. Not to mention that we use NCR paper, not actual carbons.

    --
    When the axe came to the forest, the trees said, "Look out - the handle was once one of us."
    1. Re:carbon paper by 4181 · · Score: 1

      I wouldn't call writing on carbons a technical skill.
      The technical skill required is inserting the carbon paper facing the right direction.


      I recently saw carbon paper in action at a customs and immigration office in Thailand (when posting a bond to change my visa status as captain of a boat -- in effect promising that I'd come back to sail the boat out of country). When the officer finished typing the form, she was amused to discover that the copy had been made in reverse on the back of the original.

    2. Re:carbon paper by Anonymous Coward · · Score: 0

      Well, since it is something you have to learn, and it requires following a simple procedure correctly, I guess it technically is a skill.

      OTOH, it's about as complex a 'skill' as knowing which side of a hammer to use when striking a nail. :-/

    3. Re:carbon paper by Zerbey · · Score: 1

      It's still used in some legal firms even today. Sometimes those tricky forms are just easier with a manual typewriter. And, of course, we have to make copies of everything!

  25. the interent by theheadlessrabbit · · Score: 1

    the internet has made direct human interaction obsolete.

    why would i want to waste a whole day hanging out with anyone, when I can just wait for you to add the highlights to facebook, where i can skim over your day in 30 seconds or less.

    Unlike relationships, internet porn does not come with a mother-in-law.

    And in the real world, no one comes by to mod up every every insightful comment you might come across, the internet does this! So critical thinking is another skill to add to that list.

    --
    -I only code in BASIC.-
  26. Edlin by 00_NOP · · Score: 1

    Just added this to the wiki. Has anybody used it recently? I was very surprised to find that it is still there, in fact.

    1. Re:Edlin by Anonymous Coward · · Score: 0

      Good one. When I saw Edlin I was thinking "that sounds familiar" where have I seen it?

  27. Catch-all by Baldrson · · Score: 1

    Any skill that an engineer who can't pay the mortgage has is obviously an obsolete technical skill. It couldn't be that the economy is run by a bunch of imbeciles.

    1. Re:Catch-all by MichaelSmith · · Score: 1

      Any skill that an engineer who can't pay the mortgage has is obviously an obsolete technical skill. It couldn't be that the economy is run by a bunch of imbeciles.

      Actually I think less common skills are better at paying the mortgage than common skills. I would hate to be a generic java or VB programmer. Too easy to ship offshore.

  28. I can think of a few by ThreeGigs · · Score: 5, Insightful

    Using PEEK and POKE to 'unerase' that Apple II basic program someone erased when they accidentally typed 'NEW'.
    The skill to determine a modem's connect speed from hearing the negotiation sounds.
    'Notching' an old single-sided floppy to be able to make it a double-sided disc.
    Cleaning and/or aligning the heads on your cassette player.
    Terminating or crimping coax.
    Knowing you need to type "DIR /S /AH /ON" without having to DIR /? first.
    Was 'winding your watch' in the list?

    I'd love to see some speculation on what skills you'd expect to be obsoleted by 2029.

    1. Re:I can think of a few by MichaelSmith · · Score: 1

      Was 'winding your watch' in the list?

      It is, but it is the kind of thing which will persist for a long time. Why aren't mechanical watches obsolete? My wife has a wind up watch. It is a beautifully made antique boys watch.

      I'd love to see some speculation on what skills you'd expect to be obsoleted by 2029.

      I can't honestly think of anything. Most old skills are still used in the third world. Most modern skills will still be used in 20 years time.

    2. Re:I can think of a few by SirSmiley · · Score: 2, Insightful

      Crimping Coax? Im guessing you've never dealt with security cameras (bnc connectors) or satellite or cable or any residential video systems (coax is a type of cable and not a connector)

    3. Re:I can think of a few by Anonymous Coward · · Score: 0

      Using PEEK and POKE to 'unerase' that Apple II basic program someone erased when they accidentally typed 'NEW'.

      BBC Micro users just typed old. Another thing BBC BASIC got right!

    4. Re:I can think of a few by kghougaard · · Score: 1

      It is sad how - almost lifesaving - skills become obsolete...

      I miss all the great fun with config.sys and autoexec.bat.

      Making the CD ROM drive work after booting into DOS from a floppy. Or the art of memory optimization. Fiddling with programs and upper, extended, and expanded memory, so you could free 620kB out of 640kB conventional memory to run your new game. Games which by the way had a completely superior gameplay, compared to the games of today :-)

      --
      He, who dies with the most toys, wins
    5. Re:I can think of a few by mdmkolbe · · Score: 1

      Terminating or crimping coax

      Yeah, no one ever uses coax anymore not even the cable company ... oh.

    6. Re:I can think of a few by jhjessup · · Score: 1
      WooHoo!

      Knowing you need to type "DIR /S /AH /ON" without having to DIR /? first. Get directory listing, include sub-directories, show hidden files, sort output by filename

      Do I get a cookie?
    7. Re:I can think of a few by Anonymous Coward · · Score: 0

      No one needs to terminate/crimp coax anymore. Those cable modems just sprout out of the wall, connected to the internets and everything! And television is totally wireless, straight from the camera to your livingroom.

    8. Re:I can think of a few by Anonymous Coward · · Score: 0

      X11 configuration? (Getting close...)

    9. Re:I can think of a few by Anonymous Coward · · Score: 0

      Actually terminating and crimping coax is still used all the time in the broadcast and pro AV industry, where we can't use DVI to run HD long distances, and HDMI (well, HDCP, rather) is a four-letter word.

      HD-SDI, 'nuff said.

      It used to be even more widespread when RGBHV was transmitted over 5-wire snakes, but its all moving towards CAT5 mux/demux nowadays.

  29. Back in the day... by smittyoneeach · · Score: 1

    I could boot an AN/UYK-7 without using a reference.
    These days, I just play highland bagpipe.

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  30. It's not obsolete, here's why: by Nicolas+MONNET · · Score: 4, Insightful

    There are probably many times more people capable of programming in assembly language today than in the 70s. Kernel developpers, compiler developers (obviously!), CPU designers, embedded systems developpers and so on.
    On the other hand, there are many times less people capable of making horse buggies than in the XIXth century; that's obsolete.

    1. Re:It's not obsolete, here's why: by drinkypoo · · Score: 1

      Actually, a more useful measure is whether a larger percentage of programmers can write assembler code. I suspect the opposite is actually true. Besides, you can write device drivers in C just fine, as well as most parts of the kernel and all of the compiler.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:It's not obsolete, here's why: by Nicolas+MONNET · · Score: 1

      Why percentage of programmers? Why not percentage of the population as a whole? I bet the number has grown.

    3. Re:It's not obsolete, here's why: by Jason1729 · · Score: 2, Insightful

      I write my compilers in Bison

      Seriously though, I do a lot of PIC assembly programming. Something like Arduino is fun to play with, but for anything non-trivial in an embedded system, it has to be assembly.

    4. Re:It's not obsolete, here's why: by drinkypoo · · Score: 3, Insightful

      Why percentage of programmers? Why not percentage of the population as a whole? I bet the number has grown.

      Because non-programmers don't program in ANYTHING? Duh?

      I bet the number has fallen sharply. It used to be impossible to do many things without ASM. Now you can just throw processing power at problems and hope they go away. Ever notice how much less responsive your computer is when you're not even USING all the amazing new functionality, compared to say PC-GEOS? A lot of that is due to lazy programming. And part of that is not optimizing much, if at all; and part of that is not doing any assembler.

      Most programs are never optimized (or at least never heavily optimized) because they can run on our computers of today. Think about it: right now I have barely more actual functionality than I did on my Sun 4/260, but in the name of eye candy and tooltips and shit I run Ubuntu and it's about as responsive on this Core Duo T2600/2GB DDR/80GB 7200rpm SATA as Solaris 1.x was on a SPARC at 16 MHz, with 24MB of FPM DRAM, and a 500MB 5400 RPM SCSI-II fast/narrow disk.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:It's not obsolete, here's why: by English+French+Man · · Score: 1

      Writing compilers in C is indeed possible, but you still need to know assembly, just to compile the code.

      --
      If I'm wrong, please correct me ; learning is better than being right.
    6. Re:It's not obsolete, here's why: by Talchas · · Score: 1

      You can write a compiler without writing assembly for the compiler, yes. But you must know assembly (or the bytecode/IL/whatever you are targeting) in order to write a compiler, otherwise it isn't a compiler. Whether or not you call this writing assembly code is pretty arbitrary, as you'll still have to know it and use it.

      --
      As the Americans learned so painfully in Earth's final century,free flow of information is the only safeguard against...
    7. Re:It's not obsolete, here's why: by John_Booty · · Score: 5, Insightful

      How much of the cool stuff you enjoy using today would even exist if it had to be coded in assembly? You think you'd be using a nice, modern web browser or game if they had to code the whole thing in assembly?

      Coding in higher-level languages frees programmers up to create actual cool stuff. It's great that some ur-geek wrote a bitchin' disk driver in ASM that fits in 7KB of code during one Jolt-and-meth-fueled month back in 1991 but jesus, who cares. Given the chance, I bet that engineer would have done it in 1/4 of the time in C and actually done something useful with the rest of his month. Or at least stayed away from the meth and Jolt.

      It's the technological equivalent of carrying buckets of water three miles from the stream to your prarie frontier home every single morning. Like, it's cool and admirable that people once did that, but thank goodness we generally don't have to do that these days. Even if my tap water really doesn't have any new functionality compared to that stream water.

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    8. Re:It's not obsolete, here's why: by Ihlosi · · Score: 2, Interesting
      How much of the cool stuff you enjoy using today would even exist if it had to be coded in assembly?

      Maybe less in terms of quantity, but more in terms of quality.



      You think you'd be using a nice, modern web browser or game if they had to code the whole thing in assembly?

      Quite possibly, yes. The assembly requirement would present quite a barrier of entry, but at least it would raise the overall quality of the software. People who manage to write bug-ridden crapfests in high level languages would have a hard time getting their program to start in assembly.


      Afaik the last "big" game written entirely in assembly was Elite 2:Frontier. And while the game suffered from its own set of problems (namely: it was kinda boring), it was technically extremely impressive (not to mention that it fit on a single freakin' floppy disk).

    9. Re:It's not obsolete, here's why: by drinkypoo · · Score: 1

      How much of the cool stuff you enjoy using today would even exist if it had to be coded in assembly? You think you'd be using a nice, modern web browser or game if they had to code the whole thing in assembly?

      It's too bad you got modded up. Guess the moderator can't read English either. I never said all the optimization or all the code had to be done in assembler. Only that more optimization SHOULD be done (whatever form it takes) and is NOT done because it doesn't HAVE to be done. The code works, it just works slower than it should.

      Assembler is just one optimization technique; it may not even be the most important one. However, it clearly is important.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:It's not obsolete, here's why: by Kamineko · · Score: 1

      With mature software engineering principles and rigorous unit testing, there's absolutely no excuse for horse buggies at all.

    11. Re:It's not obsolete, here's why: by John_Booty · · Score: 3, Insightful

      >>How much of the cool stuff you enjoy using today would even exist if it had to be coded in assembly?

      >Maybe less in terms of quantity, but more in terms of quality.


      I disagree. The complexity of a software module does not grow linearly with size. It grows much faster than that. Something like Firefox (a piece of software most of us enjoy, though most of us agree it could be much more svelte) just couldn't be accomplished in any reasonable time frame in assembly because of the sheer complexity involved.

      Assembly has its place (and always will) and I'll ALWAYS look to assembly programmers as the true heroes of the programming world. I just like to take issue (or rather, poke fun) at these people that pine for an imaginary world where everything is written in assembly.

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    12. Re:It's not obsolete, here's why: by jedidiah · · Score: 1

      The mathematical constructs that "allow you to create spiffy complex programs"
      are still available to you even as an assembler programmer. If you understood
      this "obsolete skill" you would realize that.

      It's not the language. Ultimately all of the popular ones are glorified assembler
      anyways. It's the programming practices.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    13. Re:It's not obsolete, here's why: by mindstrm · · Score: 1

      It's absolutely true... as the field of programming itself is vastly larger now.

      As the grandparent said - nobody was doing web programming in 70s.

    14. Re:It's not obsolete, here's why: by drinkypoo · · Score: 1

      Assembly has its place (and always will) and I'll ALWAYS look to assembly programmers as the true heroes of the programming world. I just like to take issue (or rather, poke fun) at these people that pine for an imaginary world where everything is written in assembly.

      I object to your characterization of (presumably) my as pining for this imaginary world.

      As opposed to poking fun, I prefer to correct people whose grasp on English is inadequate to comprehend my comments, but who respond anyway.

      I never said everything should be written in assembler, only that optimization is not just a lost art, but a forgotten one. It was deliberately forgotten by legions of programmers drunk on too much computing power.

      I believe that all introductory programming classes should be taught on equipment as primitive as possible, to try to teach the value of efficiency. The simple truth is that Mozilla (your prime example) had to start with a lot of cruft, and no one has really tried to write a full-assembler OS (at least, in the modern age of computing) as a commercial product - and Mozilla didn't just spring up out of the soup of Free Software.

      I more or less agree with your basic premise; we have a lot of convenient shortcuts in higher-level languages that make programming much more practical. But then, I never actually said everything should be written in assembler. I only said that it is an indispensable tool when it comes to optimization, and that we need more optimization. You leapt to your own conclusion.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    15. Re:It's not obsolete, here's why: by Cairnarvon · · Score: 1

      High-level languages make it much easier to write bug-free programs. While knowledge of assembly is always necessary to produce beautiful code, actually writing said code in assembly is a horrible idea for nearly every decent-sized project.
      Maybe the quality of the applications as designed would be higher, but I'd be willing to bet they'd have considerably more bugs than the same applications written in a high-level language, even if the programmers of the latter are less skilled.

    16. Re:It's not obsolete, here's why: by daniel422 · · Score: 1

      My reasons exactly. The fact is, when you get down to the hardware level (like in microcontrollers and embedded systems) assembly is often the best and easiest way to get your system running and optimized. It's the closest thing we've got to direct machine code (and that's hard to read!).
      I'd also say it's more prevelent now - despite the fact that there are many high level languages out there (and you don't really have to understand anymore EXACTLY what they are doing on a low level) - because of the increase in engineers in general and the increase in embedded systems in general. And hey - you propbably have a lot of cool things that were programmed in assembly at the embedded system level. I personally programmed a surround sound decoder for a consumer product once (not the actual DSP, but the micro) not that long ago.
      HARDLY obsolete.

    17. Re:It's not obsolete, here's why: by demallien2 · · Score: 5, Insightful

      Actually, percentages are quite simply a sucky way of judging whether something is obsolete.

      In the context of this discussion, a skill is obsolete when it is no longer needed to do something that is still being done today - For example, nobody needs to know how to load a program off tape on a C64 these days, because we don't have C64s anymore.

      By this definition, assembly programming is obviously NOT obsolete. We still need assembly programmers: for device drivers, for kernel programming, for writing compilers, for reverse engineering old code that is no longer supported, for cracking dumb DRM schemes that take away our fair-use rights, etc etc etc. The fact that not many people know how to write assembly is irrelevant: does the fact that few people know how to build a human-rated space launch vehicule mean that it is obsolete?

    18. Re:It's not obsolete, here's why: by Mongoose+Disciple · · Score: 1

      I never said everything should be written in assembler, only that optimization is not just a lost art, but a forgotten one. It was deliberately forgotten by legions of programmers drunk on too much computing power.

      Well, yes. And to be fair, it was deliberately forgotten for good reasons.

      Optimization in a development project isn't just about optimizing memory usage or CPU cycles -- it's also about optimizing developer time, and often money. For the overwhelming majority (not all) of development projects, it is more important to have a product that works correctly within its constraints built quickly/cheaply than to have one that runs faster or uses less memory (within reason) but costs more or takes longer. If having a service run concurrently on five machines instead of three is dramatically cheaper (that is, the cost of buying/operating the two additional servers is much cheaper than the developer salaries) than paying developers to get it optimized enough to run on the three, what's wrong with that choice?

      The modern paradigm, in most cases, is to "just make it work" first and then to use that as a starting point to perform optimizations if necessary. I think it's hard to seriously argue that that's not as it should be.

    19. Re:It's not obsolete, here's why: by Anonymous Coward · · Score: 0

      Quite possibly, yes. The assembly requirement would present quite a barrier of entry, but at least it would raise the overall quality of the software. People who manage to write bug-ridden crapfests in high level languages would have a hard time getting their program to start in assembly.

      Hate to tell you...people who write crappy C++/Java/C#/pick your poison, would also write crappy Assembly given the chance.
      Just because a programmer knows assembly does not make him a good programmer.

    20. Re:It's not obsolete, here's why: by drinkypoo · · Score: 1

      The modern paradigm, in most cases, is to "just make it work" first and then to use that as a starting point to perform optimizations if necessary. I think it's hard to seriously argue that that's not as it should be.

      Of course, that is as it should be. The problem is who is deciding what is necessary.

      Lots of companies ship things when they compile and run, or at least, so it seems. And I'm tired of people telling me it's a nonstandard configuration; Microsoft software will crap itself when running on a machine with nothing that doesn't come from Microsoft, for example; they're hardly the only ones but they come immediately to mind since they offer a "complete" software package of OS and apps.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    21. Re:It's not obsolete, here's why: by sausageonastick · · Score: 1

      Apps written in assembly will be slower and possibly take up more memory in the long term. A compiler can use processor profiles to generate much more efficient code for the latest chips than someone hacking around in assembly 3 years prior.

    22. Re:It's not obsolete, here's why: by celle · · Score: 1

      What a shame. Since with gas prices going into orbit we may be forced back to horses and buggies eventually. Maybe that wouldn't be such a bad thing. Slower life with a little more direct responsibility, might be a good thing.

    23. Re:It's not obsolete, here's why: by Fjandr · · Score: 1

      This entire argument completely misses the point. For what assembly language is used for, it is critical. Look at it this way: without assembler you would not be capable of running all that cool stuff.

      Not everything needs assembly integrated into it. Almost everything depends on assembly at some level to run.

    24. Re:It's not obsolete, here's why: by Lazerf4rt · · Score: 2, Interesting

      Dude, nobody's threatening to write an entire application in assembly. The debate is about whether assembly language programming is an obsolete skill.

      You're also overlooking something called "debugging". You think you'd be using a nice, modern web browser or game if nobody involved had any understanding of assembly language? When testers send crash dumps back to the developers of IE & Firefox, what do you think those developers are looking at? Same thing for games. The latest few months of any project are dedicated to stability. A game written by a team with no assembly knowledge is a game that doesn't ship. Nothing more to it. I don't know if you consider shipping a product to be something practical, but in my mind that makes ASM programming count as pretty practical.

    25. Re:It's not obsolete, here's why: by Anonymous Coward · · Score: 0

      Ha ha fucking ha. Did they teach you that in school sonny boy? I've been hearing this shit about "optimizing" compilers for at least 20 god damn years now, and they still produce shit code in terms of performance. I look at "auto" vectorizing output of icc and gcc and just laugh at the morons like you that buy into this lie. It isn't true kid. Note that much of the time shit code from a compiler is good enough, but they aren't magical mystical creatures that are going to give you optimal code at the flick of a command line switch.

    26. Re:It's not obsolete, here's why: by John_Booty · · Score: 1

      You're talking about something completely different now. We were talking about writing and/or optimizing things in assembler versus high-level languages. You're talking about insufficient QA. Totally independent issue.

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    27. Re:It's not obsolete, here's why: by John_Booty · · Score: 1

      You said that we'd have a lesser quantity of software were things written in assembler, but a higher quality of software. I took issue with your assertion that software would be higher-quality if written in assembler, because because I think the level of complexity would just be too high for software projects of any significant size.

      You simply said that software would be of higher quality if written in assembler. Since you didn't specify any exceptions, it's only reasonable to assume that you were talking about all software.

      If you weren't, fine. You corrected and clarified yourself, and I don't disagree with anything you just posted.

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    28. Re:It's not obsolete, here's why: by letxa2000 · · Score: 1

      How much of the cool stuff you enjoy using today would even exist if it had to be coded in assembly?

      And how much of the cool stuff you enjoy wouldn't exist if it had to be coded in anything other than assembly language? A lot of the processors that run the motor of your car, probably most fixed phones, garage door openers, your sprinkler system, very possibly your refrigerator, washing machine, dryer, networked smoke detectors, voltmeters, traditional non-geek calculators, a lot of electronic musical instruments, your heater/air conditioner thermostat, networked smoke detectors in your home, the little speed/odometer on your bicycle, the same type of controls on home/gym exercise equipment, the code that's inside your external mouse or keyboard...

      You think all that stuff is written in 'C' or Java? Maybe a few... but as I said elsewhere: At any given time on earth, I can almost guarantee that there are more programs running end-user applications that were written in assembly language than there are programs written in other languages.

      So many people forget that the "programming universe" is far, far larger than just Windows and Linux.

    29. Re:It's not obsolete, here's why: by jacquesm · · Score: 1

      I think if assembly would be the barrier to entry for a programming job, there would be less software of much higher quality, but also at a *much* steeper price.

    30. Re:It's not obsolete, here's why: by Anonymous Coward · · Score: 0

      Yet my computer today *STILL* takes just as long to start (if not longer) to start up. Software is not getting faster. It is getting slower. Just due to the fact all those awsome tricks we used to make the thing SMOKE are not being used anymore. There is a huge difference between a n squared operation and a n log n operation. But WHO CARES you say the hardware is faster. What if I want to use that code a billion times? Where you intended it to be used once.

      I heard a story once of steve jobs forcing a programmer to make the bootup process of the mac faster. Why? Thousands of people every day were going to be using it. If it saved 1 second per persons day it was a huge aggregate effect.

      With all the extra power and space we have... We are wasting it. That dude who wrote that bitchen code took the time to make sure it ran in a reasonable time. Not just slop something together that 'worked'. He used the thing holding his ears appart out of neccessity. These days we slop it together and hope its good.

      You should crack open some of the code you write and take a look at the ASM produced. You would be shocked at what the compiler does to it. It is not pretty. People seem to think -O2 produces awsome code. In some cases it does. Others well its lets just say ... bad.

      for example

      if (x && y)
      { dosomething(); }

      if (x & y)
      { dosomething(); }

      Which one is faster? For integers the second one as there is one branch instead of 2 'branch' as branches kill cpu performance. For function calls the first one on average is probably faster. Yet EVERYONE I know writes the first one for everything as 'thats the way they were taught, so it is more clear'. Dont think so? Test it. Maybe it doesnt make much of a difference most of the time. But small tricks like that are BUILT on the knowledge of the processor, and assembly language, AND what the compiler does to your code.

    31. Re:It's not obsolete, here's why: by thogard · · Score: 1

      So why is visicalc so fast on modern computers?

    32. Re:It's not obsolete, here's why: by ignavus · · Score: 1

      Besides the ease of programming in higher level languages, there is also the matter of portability.

      Imagine if all the programs running on Linux for x86 had to be rewritten (in assembly) to run on Linux for PowerPC? That would be prohibitive. OpenOffice? Firefox? Gnome or KDE? Totally rewritten for each new family of chips? That would multiply the work of a software platform like Linux beyond all practicality. Compilers take (a lot of) the pain out of portability.

      Of course, on this argument, we should all be writing in something like Java, where the OS and GUI toolkit is abstracted as well as the hardware. "Write once, run everywhere" is a desirable goal.

      But even C gives a lot of "Write once, run everywhere".

      --
      I am anarch of all I survey.
    33. Re:It's not obsolete, here's why: by Anonymous Coward · · Score: 0

      And to counter your hypothesis, Frontier failed (amongst other reasons) because it had lots of bugs!

    34. Re:It's not obsolete, here's why: by sjames · · Score: 1

      Interestingly, compilers have gotten so much better in the last decade that in most cases they do a BETTER job at generating assembly than a human would. It's been a good while since i++, i+=1 and i=i+1 would compile to different opcodes. Asm these days is mostly useful for very low level things such as atomic ops, context switches and early system boot before you have a working stack.

      The real bloat problem is the big blobs of one size fits all everything but the kitchen sink libraries, poor data structures so that the code has to do contortions to get at what it needs (while it can easily access things it never needs), inappropriate object models and such as that.

    35. Re:It's not obsolete, here's why: by drinkypoo · · Score: 1

      You're talking about something completely different now. We were talking about writing and/or optimizing things in assembler versus high-level languages. You're talking about insufficient QA. Totally independent issue.

      Sorry, again, too many liberties with the language there. What I meant was, it runs unacceptably slow.

      Luckily Microsoft doesn't do too much heavy-lifting kind of software, which makes the poor performance less apparent.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  31. - Putting a needle on a vinyl record? by davepermen · · Score: 1, Informative

    Hm.. I'm a DJ. This is sort of daily business for me. Granted, nowadays we have a lot of other options, but its still alive and kicking. Vinyl just feels great, as you have the music sort of "in your hands". (and yes, I'm using Vinyl Tracks, CD Tracks over CD Players, Mp3 over Vinyl with Traktor Scratch, Mp3 over CD with Traktor Scratch, Traktor over Midi using a Faderfox DJ2, etc.. and all combinations of it...). Actually, I'd love to have vinyl control for much more work than just for DJ'ing. Imagine a Turntable between the video editing PC. Using the turntable, you could very rapid move trough the whole video, search a certain place, scratch trough to watch animations, find specific frames, etc. Would be quite usable (and sort of gets used in VJing.. but I'd love to use it for generic video cutting).

    1. Re:- Putting a needle on a vinyl record? by brainwash · · Score: 1

      Actually the 'turntable' you speak of is being used in video editing. It's a rotary [wheel] which advances or recedes frame by frame and another joystick-like wheel which controls the speed of forwarding/rewinding, in the same physical ensemble.

    2. Re:- Putting a needle on a vinyl record? by brainwash · · Score: 1
    3. Re:- Putting a needle on a vinyl record? by davepermen · · Score: 1

      It's not the same. A Jogweel can not be used to directly position on a Track/Video. This is the same with CD Players in DJing, where you have to "scroll", or "joggle" to your prefered position. Using a turntable, you could simply "drop the needle" at the specific place. in case of mp3's over traktor with the control vinyl of traktor scratch, this means you see actual 1minute rings on the vinyl, and if you want to go to minute 5, you can directly take the needle, put it to the fifth line, and you're there. this fast direct movement to a specific position is what lacks with jogweels. you get that with mice, pens, and turntables. but sure, a jogweel is quite nice and helps quite much.

  32. Thank your local deity for Plug-n-Pray by kitgerrits · · Score: 1


    I, for one, welkcome automatic resource allocation.
    No longer disabling your printer port in order to get that second soundcard working.

    --
    "I was in love with a beautiful blonde once, dear. She drove me to drink. It's the one thing I am indebted to her for."
  33. asm is NOT obsolete! by Alioth · · Score: 5, Interesting

    Assembly language is FAR from obsolete. Embedded hardware outships PCs by probably 100 to 1, and much of that is programmed using assembly language (especially if you want to get the most out of the tiny hardware). I have modern microcontrollers in my parts box with 64 *bytes* of RAM and 1kbyte of flash (Atmel ATtiny13) - while you can write a C program for this device, you can get much more out of it with asm, and it doesn't really take any longer to write (AVR asm is one of the nicer 8 bit ISAs). Portability is rarely an issue for devices like this, since even the C code won't be portable to other microcontroller architectures.

    Every serious programmer should have some experience of assembly language so they can grok what's really going on. Nothing tells you why buffer overruns are so bad than watching a program written in asm run over its own stack obliterating the return address. It doesn't need to be a fancy 32 bit or 64 bit desktop chip, an 8 bit ISA or one of the classics such as the Motorola 68K is enough to understand the principles of what happens at the chip level. If you want to see what happens when programmers simply don't grok the hardware, just check out The Daily WTF. ...oh, and I have a rotary phone, too. It was first installed in my grandparents home in 1969 when the house was built. It's just the plain GPO phone of the time, but it's a little reminder of them each time I phone someone.

    By the way, get off my lawn!

    1. Re:asm is NOT obsolete! by ghyd · · Score: 1

      "Embedded hardware outships PCs by probably 100 to 1"

      I'm not in the field, but I can imagine that a single person can program a whole lot of different washing machines, but a single person won't provide me with office softwares, a MMORPG, professional musical applications, to name a few that I know of.

    2. Re:asm is NOT obsolete! by Anonymous Coward · · Score: 0

      > Portability is rarely an issue for devices like this, since even the C code won't be portable to other
      > microcontroller architectures.

      Well, that depends on what your code does, but I have some Atmega32 code that can run on linux as well. Sure all that code to render a character on a graphical display becomes a simple printf with some VT100 commands but there is still loads of non-hardware-specific code, and most assembly code has an alternative C version to help with debugging anyway (debugging a purely asm AES code would be no fun, really, especially if you do not have a good simulation or JTAG-debugging environment).
      Admittedly things are likely a bit different when targeting an Attiny13...

    3. Re:asm is NOT obsolete! by Ihlosi · · Score: 1

      I'm not in the field, but I can imagine that a single person can program a whole lot of different washing machines,

      No. Because for the programmer of the washing machine, it isn't acceptable to soak your silk shirts in near-boiling water and then flood your basement with hot, soapy water. That's what most "accepted" bugs in PC apps would result in if they were applied to embedded software. You also probably don't want your car to think that it's a good idea to turn off the engine when you're going 75 mph on the highway, or your pacemaker to have the equivalent of a BSOD.

    4. Re:asm is NOT obsolete! by east+coast · · Score: 1

      While your point is kind of well made the fact is that most of these systems they're talking about having embedded have a much simpler time than any PC does regardless of OS...

      For example, you mention a BSOD. I can not recall the last time I've seen a PC get a BSOD aside from hardware failure and I have over 1000 of them in my workplace. The reason for this isn't that W2K and XP are so solid (and not that they aren't. let's try to avoid the MS bashfest here please) but rather because I work in a controlled environment where we don't let any user put any software they want on a machine. So with a mixture of Microsoft software, some third party apps and even some inhouse applications we have managed to build a fairly smooth machine with the majority of users having nothing better than a high school graduates education.

      So the same is true for the guy programming the washer's code. He has a very specific system that he's probably fairly knowledgeable about. And like with us he doesn't have to concern himself with a user trying to install WeatherBug on his Maytag. It's not that the PC is so bad but Bill, Linux and Steve should not be looked down on when a third party application or some random hardware gives the machine fits. In most embedded systems you simply do not have those concerns. Controlled environments are a Godsend to most coders.

      --
      Dedicated Cthulhu Cultist since 4523 BC.
    5. Re:asm is NOT obsolete! by zopf · · Score: 1

      "I have modern microcontrollers in my parts box with 64 *bytes* of RAM and 1kbyte of flash (Atmel ATtiny13)"

      Indeed. I am a senior in Biomedical Engineering (Electronic Instrumentation focus) at a major US university, and assembly language was a required component of my curriculum. It turns out to have come very much in handy: I am currently working on a project using a TI MSP430 with 128B RAM and 2kB flash in conjunction with a sensor to detect apnea in premature infants. Because the processor specs are so miniscule, not only does the processor cost less than $1, but it also runs at only 220 microamps. This can give us a battery life of roughly 3 months on a watch battery. The entire application logic and signal processing algorithm will be coded in assembly.

      There's a significant difference between obsolete and esoteric.

      --
      Did you see the pool? They flipped the bitch!
    6. Re:asm is NOT obsolete! by Anonymous Coward · · Score: 0

      can not recall the last time I've seen a PC get a BSOD aside from hardware failure and I have over 1000 of them in my workplace. The reason for this isn't that W2K

      Oooh! Oooh! Want to see one? W2K with Word XP: insert floppy in A drive, load foo.doc from A drive. Now, because everyone tells you to make backups in case you lose a floppy, remove floppy from A drive, then insert a new floppy and save your document.

      I ran a student lab full of this setup in college and BSODs due to this was a daily event leading to the wailing and gnashing of teeth by students who lost their thesis due to MS thinking it would be Teh Awesomez to use a removable disk as a temp directory instead of the temp directory that they themselves put on the harddrive. 95% of the time the original document is unopenable thanks to word's inability to reassemble its own temporary file, and once (that I witnessed) W2K actually wrote the first floppy's FAT to the second floppy before crashing.

      Newer versions manage to avoid the complete and utter crash, but the underlying problem still hasn't been fixed, leading to corruption of files edited over the network in vista, or temporary network glitches causing newer versions of word to helpfully tell you "data has been lost" (before replacing the entire text with gibberish) in XP.

  34. Transferable skills..? by teh+kurisu · · Score: 1, Interesting

    If you're using any device that communicates over a serial port (Telit GT864-PY for example), you're going to use parts of the Hayes Command Set. Not necessarily all of it, but it's certainly not obsolete.

    And as for 'Changing the battery of a Sega Dreamcast VMU'... isn't that just a case of unscrewing the cover, removing the battery, and popping in a replacement? The Dreamcast VMU might itself be obsolete, but I just went through that exact procedure yesterday while changing the battery in my car's central locking remote.

    I'm not taking the list too seriously though, seeing as 'sex' is on it...

  35. Turbo Button by Mishra100 · · Score: 1

    The almost ubiquitous turbo button on your computer is completely obsolete. I can't remember the last time I had to worry about the yellow light because my computer was slow.

    1. Re:Turbo Button by Tim+Browse · · Score: 1

      Ubiquitous? I haven't seen a turbo button in years. I used to use them though - to turn off the turbo speed to debug redraw bugs under Windows 3.1 in an illustration package I was working on. It slowed down things enough so you could often see where it went wrong. And when I say it, I mean my code, of course.

      It reminds me of when a fellow developer was trying to debug stuff, and couldn't see what was going wrong. Another developer said, "Ah, but what happens when you do this?", and pressed the turbo button. Or so he thought. The first developer, somewhat bemused to see the screen go blank and the BIOS screen appear, said slowly, "Well, it resets my PC. Duh."

      Still makes me laugh :-)

    2. Re:Turbo Button by Mishra100 · · Score: 1

      Ubiquitous in its day is what I was referring to. :) Nice story.

  36. Tag by Sobieski · · Score: 1

    It is my opinion that this article may now be tagged "troll", or "flamebait". I can't keep up with the intertwining meanings of these words.

    --
    Particles, stuff that matters.
  37. Punch Cards by tekrat · · Score: 0, Troll

    Now that's an obsolete skill!
    I'll bet half the readers of Slashdot have never even seen a punch card in real life.

    Now get off my lawn!

    --
    If telephones are outlawed, then only outlaws will have telephones.
    1. Re:Punch Cards by Anonymous Coward · · Score: 0

      started on punch cards in uni, mainframe had haseltine terminals connected through some sort of front end that kept crashing. easier to just punch the cards.

      graduated to paper tape on a wang console, then to the ibm pc with dual floppy drives to run a spectrometer.

      nowadays you'll have to pry my mac from my cold dead hands

    2. Re:Punch Cards by Lawrence_Bird · · Score: 2, Funny

      And many of them deserve to get an EOF card right up the ....

    3. Re:Punch Cards by reub2000 · · Score: 1

      I once used one as a bookmark.

  38. assembly language programming by phrostie · · Score: 1

    it was because assembly language programming was considered obsolete that my dad could make a living at it.
    there was still lots of code out there and someone had to maintain it.

  39. BASIC indeed by Danzigism · · Score: 1
    I beg to differ on the rabbit ears thing. Well, maybe and maybe not. I still use rabbit ears to receive the new DTV signal and at first I did have to do some minor adjusting ;-) but you've never seen a grown man more excited to get about 4 new channels that he's never had before, and for free.

    but I wanted to add BASIC programming to the list of obsolete tech skills. for a long time it was the only way to even operate your computer. If I could only get $100,000 for being a BASIC programmer nowadays, that'd be freakin awesome. screw these object oriented languages! just kidding, they're just too hard for me..

    --
    *plays the Apogee theme song music*
    1. Re:BASIC indeed by FuzzyDaddy · · Score: 1

      I still have rabbit ears to pick up my analog TV signals. I'm too cheap for cable, and I'm using a nice, 15 year old television.

      --
      It's not wasting time, I'm educating myself.
  40. MFC by kahei · · Score: 1


    I spent years on MFC. I was really good at MFC. I even *liked* MFC, not because it's elegant or effective, which it isn't, but because it has many clever solutions to the *particular* problems that the designers originally faced when building a library for creating GUI apps on puny machines without even knowing whether the OS would support true multitasking or not. Custom message maps, dynamic resource handles, ATL integration, I did it all. I knew which specific message ID is handled differently in a Windows message queue than any other. I knew how to have a form containing windows with their message pumps in different threads. This was back before we had that fancy 'Java' and 'Flash' and 'C#', you know -- back when writing really powerful GUI apps involved a bit more than dragging your chart control onto your docking window control. And we lived in a cardboard box in the middle of a motorway.

    Now all my MFC skillz are obsolete. Years of study and experience that I wouldn't even dare mention on my resume. Deader than cursive handwriting. Half my working life down the drain.

    Good. That's progress.

    The practise of stacking coins on an arcade machine to indicate that you are next, on the other hand, is much missed. Man, those were the days. When you went *out* to play instead of cowering in your house... what the hell happened?

    --
    Whence? Hence. Whither? Thither.
    1. Re:MFC by david_thornley · · Score: 1

      I still work on a big MFC application. I don't think we'd keep it in MFC if we had to do it all over again, but it sure isn't worth doing it all over again in order to get rid of MFC. (Okay, so I have to pick up some of my technical books used. So what?)

      In my experience, any time you find a large established application, there's going to be a lot of stuff you'd think obsolete in there. The people working on it are going to need "obsolete" skills to keep the app going and continually improve it.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  41. Stacking quarters is still valid by NoPantsJim · · Score: 1

    Come to the bars at Purdue, stacking quarters on a machine is still the preferred method to indicate you've got the next round on a pool table or dart board. If my friends and I feel like playing pool for awhile, usually we just keep our own stack on the table and dump quarters directly into the machine while rotating players every game. Usually people are too drunk to notice.

    1. Re:Stacking quarters is still valid by Pumpkin+Tuna · · Score: 1

      Works in a bar, but I always hated it in the arcade. I don't remember how many times I was standing in a line waiting on a game and some punk walks past the three people waiting to put his quarter on the game like none of us existed. I hated that.

  42. IRQ conflicts? by Rhapsody+Scarlet · · Score: 1

    resolving IRQ conflicts on a mother board

    I once saw a topic on Gaia Online where a suggestion on the cause of BSODs while playing some PC games was an IRQ conflict between the video card and something else. What... the... fuck? On a modern PC? Using an AGP video card? With Windows XP? I suddenly felt like I'd stumbled into some technological version of House where the likelihood of a given problem being true is based on how astronomically unlikely it is to actually happen.

    I haven't had to even think about IRQs for the last decade or so, and I can't really say I miss the days when they were still a problem.

  43. Dos... by denalione · · Score: 2, Interesting

    ...memory management.

  44. So, I'm obsolete, huh?-carrousel by Anonymous Coward · · Score: 0

    True, and as we get away from von neumann architectures assembly will certainly change. Remember the SUN Java chip, and the Harris Forth chip?

  45. Just change the name by Anonymous Coward · · Score: 0

    In the 1970s I worked with a programmer (I was a hardware tech). We were working on desktop computers the best known of which would have been the PDP-8. I met him a couple of years ago. He had become a college teacher. He complained that his students called him things like fossil. The solution was easy. All he had to do was preface everything he said with the word 'embedded'. A couple of the boxes we used to work had instruction sets that exactly match those of modern chips.

    A lot of skills aren't as dead as we think they are, we just call them different things.

  46. Assembly in VM by bhaak1 · · Score: 1

    Assembly skills aren't as obsolete as one might think.

    The same skills one needs to programm Assembler are needed if one programms virtual machines directly.

    Especially Java Bytecode is a good example of this. The Java VM runs Bytecode that is extremely similar to SPARK assembly.

    And what about Parrot? It is also programmed with an assembly language.

    1. Re:Assembly in VM by Laughing+Pigeon · · Score: 2, Funny

      And what about Parrot? It is also programmed with an assembly language.

      I'll tell you what's wrong with it, my lad. 'E's dead, that's what's wrong with it!

  47. Nonsense. by jotaeleemeese · · Score: 1

    The level of abstraction of many programming languages is now so far detached from the hardware that this ascertion is pure nonsense.

    Some programmers may benefit from it, but for many others it would be an unnecessary hindrance.

    --
    IANAL but write like a drunk one.
  48. Mish mash proves you're clever? by Anonymous Coward · · Score: 0

    Why did you use XIXth for 19th and 70s for LXXs?

    1. Re:Mish mash proves you're clever? by Anonymous Coward · · Score: 1, Insightful

      Romans are still widely used for numbering front matter. Niche - somewhat, obsolete nope.

  49. Slashdot agrees by Daimanta · · Score: 1

    Humor is an obsolete skill :-|

    --
    Knowledge is power. Knowledge shared is power lost.
    1. Re:Slashdot agrees by gzerphey · · Score: 1

      and netcraft confirms it.

      --
      I don't have a microwave. I do, however, have a clock that occasionally cooks shit.
  50. That's just great by rbarreira · · Score: 4, Funny

    I'm glad some people think that Assembly programming is obsolete. That way, it's much easier for me to get one of the many jobs which requires assembly programming.

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  51. How come this is marked "It's funny. Laugh."? by Flambergius · · Score: 1

    Ok, so I appreciate schadenfreude as much as the next guy (and he's an asshole), but I still fail to see how this is funny. In fact, this is a big part of the reason why most people are so bad at technical things, which is an increasingly difficult problem in Western societies. Most people have learned the hard way that technical skills are a bad investment just because they become obsolete or commoditized so quickly. We (and I speak both as a techie and an educator) need to better guiding people to durable skill paths.

    --
    Computers are useless. They can only give you answers - Pablo Picasso
  52. It's not obsolete,here's why:Revolution's not here by Anonymous Coward · · Score: 0

    "On the other hand, there are many times less people capable of making horse buggies than in the XIXth century; that's obsolete."

    The only thing is when the revolution comes that slashdot's always going on about. Those who know assembly will be less in demand than those with obsolete skills like churning butter and building buggies.

  53. Whoo, trollbait! by Anonymous Coward · · Score: 2, Funny

    Emacs! No, wait, VI! Functional programming! Python! Java! Perl! Ruby! Oh man, I'm like a troll kid in a candy store!

  54. One more for the list: by megaditto · · Score: 0, Troll

    Putting on a condom.

    Face it, it's true. Either you are a geek not likely to get laid, or you are a hot trash stud that could use the kids to get a bigger welfare check. In neither of these cases you actually need to know how to operate a condom.

    --
    Obama likes poor people so much, he wants to make more of them.
    1. Re:One more for the list: by blindd0t · · Score: 5, Funny

      I was gonna simply say sex, which became an obsolete skill once I got married.

    2. Re:One more for the list: by Anonymous Coward · · Score: 0

      I was gonna simply say sex, which became an obsolete skill once I got married.


      Not from my own experience, but this will land you into world of hurt.
    3. Re:One more for the list: by Machtyn · · Score: 3, Funny

      Very interesting. For me, sex was a non-skill until I got married.

    4. Re:One more for the list: by Anonymous Coward · · Score: 2, Funny

      Bad career move, huh?

    5. Re:One more for the list: by genican1 · · Score: 0

      you had SEX? You must be new here.

  55. remember by Anonymous Coward · · Score: 0

    it is important to remember how far we have come.

  56. a photocopier beats carbon paper any day by petes_PoV · · Score: 1
    doesn't your place have a photocopier?

    It strikes me that this would be far simpler, more reliable and maybe even cheaper than this method. Carbon paper might just have a marginal use when you have a multi-copy document and you need to get a "true" signature on each layer. Other than that I can't think of a single modern use for it.

    Photocopying also gets round the obvious problem of unfamiliar students having it the "wrong way up" and copying their notes onto the backside of the same sheet of paper.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
    1. Re:a photocopier beats carbon paper any day by teamhasnoi · · Score: 2, Informative

      Carbon paper is still used to transfer designs to objects other than paper, or oversize paper that wouldn't fit in a copier/printer. Admittedly, it's use is nowhere near its once ubiquitous amount, but crafters, luthiers, carpenters and other tradespeople still use it.

  57. websites in assembly ... by YeeHaW_Jelte · · Score: 2, Interesting

    Programming in VB, PHP or Ruby does not make you stupid per se. Capable programmers that understand what goes on under the hood actually use these languages.

    Programming a website in assembly, on the other hand, would be pretty thickheaded.

    My point is that a knowledge of assembly is indeed very usefull for any programmer. I only disagree with your gratitious bashing of script languages and their users.

    --

    ---
    "The chances of a demonic possession spreading are remote -- relax."
    1. Re:websites in assembly ... by jellomizer · · Score: 1

      If you were doing all your coding in assembly, I would say that they were stupid. They would be wasting the companies money for code that will not have a major benefit. If it takes them twice as long to write code that is 25% faster. The cost could have better gone to getting a computer that is 100% faster to run the slower code. As well the cost of changing platoforms... OS and Hardware, means you will need to redo the program all over again. Even with languages such as C for the most part you need to do a recompile and only change any particular OS/Hardware paricular code but if you do it all in assembly every time you get a new OS or hardware you need to rewrite the entire code. 10 out of 10 points for geekyness -1,000,000 points on being a professional.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  58. Hmm? by untouchable · · Score: 1

    I still go to the arcade and we still stack quarters/change to indicate who is next on DDR and Tekken. Whatever is he talking about?

    --
    As Seen On TV's? Come back!!!
  59. Wrong way 'round by Anonymous Coward · · Score: 0

    If a compiler generates machine code (i.e. it's not interpreted, but a real compiler), it's effectively generating assembly language.

    Close, but not quite. If it generates machine code then it generates machine code, the end product, and to say that it does so is to specifically state that it delivers the binary form directly. If it generates assembly code then it's not generating the end product, but an intermediate product with a (more or less) 1:1 mapping with the end product. Just because there is a 1:1 mapping doesn't make them the same.

    There is a significant semantic and practical difference between saying "generates machine code" and "generates assembly", stemming from the higher level of abstraction of the assembly code. The code generator doesn't need to know anything about instruction opcode assignments when spitting out assembly language, and such output may be assembled to suit a range of related CPUs when a specific machine code might work on only one. Assembly code is substantially more portable than machine code, and very commonly you name the target CPU when you run an assembler.

    While the two things are very close, they're not the same, and using them interchangeably loses information.

  60. Re: Obsolete Trolls by TaoPhoenix · · Score: 1

    Yes it has.

    It has been superseded by this "SFW" historical article.

    http://www.goatse.cz/goatse.htm

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  61. Umm, yes. by Nursie · · Score: 1

    As I cracked something very similar recently, using known input and output and two devices called eyes.

    I then wrote a decoder in C.

    That's not to say knowledge of assembly isn't useful. It is, it gives you a much better insight into what's going on on the hardware level than any other language (though C isn't too bad either). This is essential to take into consideration when doing anything that is performance critical, be it a large server app or a small embedded system.

    There are too many people these days that just think "The compiler/web platform/vm does that all for me, besides which, processor power and memory are cheap these days".

    That's fine for consumer grade desktop apps and web "apps". It's not so good for all the stuff going on underneath that it seems most coders these days have no idea about.

    1. Re:Umm, yes. by Opportunist · · Score: 1

      From experience I can tell you, when you have the decyphering algorithm in front of you, it's heaps easier to follow the trail from encrypted to plain text than just trying to decode it with those two visual devices you used.

      At least when it gets a wee bit more complicated than static XOR.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    2. Re:Umm, yes. by Nursie · · Score: 1

      Oh sure, when it's a touch more complex than "XOR with predictable data", I'm sure it's far better to be able to use a low-level dump of the instructions used to create the ciphertext.

      But for the example given, well, it was trivial.

  62. Everything I learned as a kid is obselete now... by spywhere · · Score: 4, Interesting

    My father and I worked on old Saabs, way back when they were cool. He was a self-taught engineer: he had a Civil Service equivalency, no college degree, and worked as an engineer for the FAA.
    He was the master at converting 3-cylinder Saab 96 (and 95) models to the newer V4 engine. He had it down to a science, and cars we converted ran all over the country.

    A few of the more mundane skills I learned back then:
    --Setting the dwell angle by adjusting the ignition points, then rotating the distributor to set the ignition timing.
    --Disconnecting the ringer on Western Electric rotary-dial phones, so Ma Bell couldn't detect how many extentions you had (illegally) connected to your line.
    --Dialing only the last 5 digits of a 7-digit phone number: within the same exchange, the mechanical switches at the local Bell office would make the connection.
    --Scraping conducting material off the rotary dial in the cable box to enable HBO and Showtime.

  63. Jumping off the bandwagon? by TheRealChuckNorris · · Score: 5, Insightful

    I've been thinking about retiring - I'm 34 years old. I think I'd be happier if I'd jump off the bandwagon and started doing something totally different. Something that would not require me to study all the time and be stressed all the time.

    I grew up with home computers. I learned BASIC when I was 11. That is obsolete skill now. Then I got my first PC in 1988 and learned DOS. That's obsolete. Then I learned Borland's Turbo Pascal. That's obsolete. Then I learned Microsoft C programming and started programming Windows 3.1 applications that used Windows menus etc. That's obsolete. I learned Gopher and Telnet in the 80s. That's obsolete. I learned Pine. That's obsolete. I learned to tweak Windows 95 registry. That's obsolete. I learned BEA Tuxedo at work. That's obsolete. Looking at it now - I've wasted countless of hours to something that is totally obsolete now! Had I invested that time into improving myself - learning who I am, how I behave, how to enjoy this life - I would be much happier now I guess.

    --
    Don't F**K with Chuck!
    1. Re:Jumping off the bandwagon? by mrxak · · Score: 3, Insightful

      Did you not enjoy learning all those things? There's plenty of stuff I know that's obsolete now, but I enjoyed learning it all. I guess if you haven't enjoyed it, or feel it was a waste of time, you should definitely quit and do something else.

    2. Re:Jumping off the bandwagon? by jjackalb · · Score: 1

      I can't imagine the day where I don't learn anything new.

      Learning is the spice of life.

    3. Re:Jumping off the bandwagon? by Guerilla*+Napalm · · Score: 2, Funny

      Are you learning any specific skills at the moment, so that we can avoid it?

    4. Re:Jumping off the bandwagon? by Amigori · · Score: 1

      I agree. With a similar skill set, I came to a similar decision about 4 years ago. Did I enjoy learning all those now obsolete things? Definitely, but eventually I realized that other careers didn't require a skillset overhaul every 3-5y. I also realize the older I get, the less time I have to invest in eventual obsolecence because my priorities have changed.

      What did I change to, you may ask? Sales. Yes, I have to learn about new products when they come out, but the underlying selling skills are the same. Its certainly a people-oriented position that isn't for everyone here on /., but I enjoy it. Plus, you get in the right field, say chemicals, logistics, or manufacturing, and there's still lots of technology to learn about to keep the geek in you happy.

      I still like keeping up with Tech News, but I'm glad I'm not in the trenches anymore.

      --
      "The quality of life is determined by its activites."--Aristotle
    5. Re:Jumping off the bandwagon? by sharp-bang · · Score: 1

      IT is no place for someone with learning fatigue.

      One of our local universities routinely surveys its students upon completion of corporate summer internships and gives the area companies the results. We like their interns, so we read the report very closely. A couple of years ago they released results that contained a significant trend- the vast majority were happy with their internships and enthusiastic about pursuing a career in the field in which they interned, with one exception, you guessed it, IT. The number one reason given was the learning fatigue- they didn't want to keep up with the pace of technological change. (As I recall, being treated like dirt, the usual reason for intern dissatisfaction, was a distant second.)

      So if you think you would be happier in another field, you're not alone and you're probably right. My advice to you is to start planning that career change now, because I am older than you and let me tell ya, sonny, it doesn't get easier, it gets harder, to keep up.

      Good luck.

      --
      #!
    6. Re:Jumping off the bandwagon? by Kevin+Stevens · · Score: 4, Informative

      Are you sure its all obsolete?

      Basic:
      Basic programming building blocks- variables, statements, control of execution flow with if/then/else and goto

      DOS:
      directory structures, command line navigation, computer architecture (and how bad design time decisions can lead to decades worth of headaches)

      Turbo Pascal:
      Not too familiar w/ Pascal anymore, but if IIRC, you should have learned how to use functions, namespaces, and the modular programming model.

      Microsoft C Programming:
      Event driven programming models, resource handles, GUI development issues- how to expose just enough complexity to make things useful without cluttering the screen, and the C aspect... you learned the syntax underpinning just about every other major language since and the basics of using structures, pointers, handling memory, the list could go on for pages.

      Gopher/Telnet:
      How plain text internet protocols generally work- and if anything you learned some cool tricks to do a raw telnet session on port 25 and spoof email from the boss.

      Pine:
      Email concepts/netiquette. Was Pine really so hard to learn anyway?

      Windows 95 registry:
      Eh probably the least portable skill here- you at least learned to be comfortable with digging into a blackbox OS and looking under its skirt. The registry is still in use in XP, not so sure about vista, so this is a skill you will get at least 15 years of use out of.

      Bea Tuxedo:
      not too familiar w/ this product, but if I remember correctly, its all about virtualization, which is now one of the hottest new technologies in the sysadmin/IT world.

      Sounds like you learned a hell of a lot. Sure none of these are all that employable *today* but couple that background with a weekend spent with a Java book and I would employ you with a 6 figure salary in a second over some newly minted sun certified ITT Tech grad.

    7. Re:Jumping off the bandwagon? by thechao · · Score: 1

      In the 90s I learned C and C++. They're still relevant and I use them all the time; I know many programmers who learned those two languages even earlier, i.e., in the 70s and 80s. About 5 years ago I picked up Python, which has been around (in one form or another) for a couple of decades. I learned SPAD (a computer algebra language) a couple of years ago, and there's SPAD code from the 60s.

      I still do all of my Windows coding in a C++ (in-house, open-sourced) wrapper around C; I also use wxWidgets in any of several languages, because the API is the same across a number of different languages---and wxWidgets is what? 15 years old?

      Sounds like you made poor choices. Also, if you have a problem with "learning all the time," why the hell are you reading Slashdot?

    8. Re:Jumping off the bandwagon? by Animats · · Score: 1

      It gets frustrating. Especially when something good is replaced by something worse. Misery is going back from Plan 9 to Unix/Linux, or from Modula 3 to C++, or from Ada to C, or QNX to real-time Linux, or LISP to XML, or BeOS to Windows.

      Learning yet another API, with a thousand API calls and a few hundred undocumented bugs, is rarely fun. Especially with the trend to "ritual-taboo programming", where each new thing has a huge manual full of examples, rather than a small manual which accurately describes what each component does.

      (A "ritual-taboo culture" in anthropology which refers to a culture where things are done or not done in certain ways, but the people doing them don't know why. Programming has moved in that direction.)

    9. Re:Jumping off the bandwagon? by Hack'n'Slash · · Score: 1

      I know what you mean! I've seriously considered becoming a diesel mechanic, machinist, cabinet maker, mechanical or chemical engineer, etc., but the family needs food and shelter so I'm stuck working with these silly computers until my wife can go back to work. If you don't have family responsibilities, don't hesitate - GO FOR IT!!

    10. Re:Jumping off the bandwagon? by Grishnakh · · Score: 2, Insightful

      Get off the Microsoft bandwagon, and you'll find your skills don't become obsolete as fast.

      C programming (not MS-specific) has been a useful skill for decades now, with no end in sight. I program in C every day.

      telnet: it's been replaced by ssh, which basically works the same. Command-line UNIX doesn't seem to be going anywhere.

      Pine: who cares? Email programs aren't hard to learn.

    11. Re:Jumping off the bandwagon? by Thumper_SVX · · Score: 1

      I'm the same age... and I love learning new stuff all the time. It keeps me active.

      Plus, by doing "obsolete" things I learned the basics early on... I learned the principles on which IT works. As a result, the only thing new I learn are semantics, and I can keep ahead of that easily. New concepts are rare in IT. For example, I learned 68K assembly language in my teens (I was a demo coder) and though I haven't seen 68K code in years (except on Wikipedia) I still use the principles and concepts behind that assembly language to understand better the flow of applications and how a stack overflow actually occurs... not to mention speak intelligently with coders where I work and surprise them with the fact that an infrastructure guy can talk "code"

      Really, I mean what do I deal with on a daily basis? Windows servers, ethernet, routers, TCP/IP... all stuff that's relatively unchanged in decades (in the latter) or just a few years (Windows servers). Even then, concepts remain the same and I apply my knowledge of Windows servers to Novell, UNIX, Linux, BSD, MacOS etc... because they all do the same thing. Only the specifics vary and they're easy to learn.

      But if you're suffering real learning fatigue... go for it. If you're not happy learning new stuff, then you will never be happy in this field. I question whether you've done it all right given what you said, but only you know what's right for you.

    12. Re:Jumping off the bandwagon? by jim3e8 · · Score: 1

      Maybe you should take up martial arts?

    13. Re:Jumping off the bandwagon? by jafac · · Score: 1

      I dunno; Java was in pretty high demand about 5 years ago, and guess what? It's still pretty much in demand now.

      Windows Registry Swashbuckling will also, probably, never go out of style, until Microsoft delivers an OS that no longer uses a registry. (Windows 2009, right?).

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  64. Floppy disks by bandersnatch · · Score: 2, Insightful

    Turning a single-sided floppy into a double-sided floppy with a hole punch.

  65. Decoding an MVS JCL SysAbend dump by ed · · Score: 2, Informative

    Back in my young day the dread OC7 Abnormal ending of a cobol PROGRAM MEANT A LOT OF FERRETING AROUND hEXADECIMAL CODE

    Days thankfully gone

    But boy, I miss COBOL

  66. Skills? by LatencyKills · · Score: 1

    I notice that they list "slaughtering small mammals and birds" on the list. What the hell kind of skill is that? Did such a "skill" ever have value? Are computers now slaughtering all our small mammals and birds for us? Oh, and one skill that I used to be quite good at that is now clearly obsolete: operating a mimeograph machine.

    --
    Jealously hoarding mod points since 2007.
    1. Re:Skills? by YrWrstNtmr · · Score: 1

      I notice that they list "slaughtering small mammals and birds" on the list. What the hell kind of skill is that? Did such a "skill" ever have value?

      It had great value if you wanted to eat.

  67. Not So Obsolete by marzipanic · · Score: 1

    I still do 99 percent of them listed on Scobleizer's blog. We still have a rotary phone and some of those methods are more reliable, in my humble opinion, maybe I am just old and need to reboot my humour..

    "Can I borrow your Dictaphone?"
    "No use your finger like everyone else!


    In the wiki: Governmental Data Protection, LOL, being British knowing my data is all over the place thanks to governmental (or just mental) protection or lack of. If they had done it the old fashioned way (by hand) none of it would have gone AWOL...

    I fondly remember the days of cleaning the betamax by taking a huge breath and giving it a good blow. Those cleaning tapes that used to jam up instead of cleaning it.

    Hours of trying to load Jet Set Willy to my ZX Spectrum, making sure it had the right tone, the joys. I miss it actually!

    I am trying two cups joined with a piece of string for my cable connection now, I just have to see if Mr Branson will let me stick one up his end

    That wiki is like the Blue Peter for nerds, I like it

    --
    In the name of sticking up for someone with autism, f**k you! Prejudiced bastard.... that is unlawful and linuc for dumm
  68. Quarters on Arcade Machines by Anonymous Coward · · Score: 0

    Last time I checked, people still stack quarters on arcade machines to get in line. Arcades are hardly common any more, but that's not really an obsolete skill. Look at any queue for a DDR machine and you'll see a line of quarters along the edge of the cabinet.

  69. Sorry /. no mention of the lost skill of by zappepcs · · Score: 1

    undoing a bra with one hand...

    Changing tracks on an 8-tack tape is a skill?

    Adjusting rabbit ears? Isn't that still used? Then why the subsidies for over broadcast digital converters?

    Technically, isn't stenography a type of shorthand?

    At the rate they are naming things, fsck, changing a tape in a Walkman counts.

    I bet drinking a a 12 oz beer in three swallows is actually a skill? hmmm

    Did they miss loading Windows from 21 floppy disks?

    1. Re:Sorry /. no mention of the lost skill of by jeremyp · · Score: 1

      undoing a bra with one hand...
      Seeing as this is Slashdot, for most people here that's more of a never acquired skill than a lost one.
      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
  70. A couple more by pen · · Score: 1

    Rolling down a car window manually. Matching up IRQ settings for hardware devices. That's all I can think of for now.

  71. Vacuum tubes? by tech10171968 · · Score: 1

    You say changing vacuum tubes is an obsolete skill? I guess someone forgot to tell most of your favorite musicians; their thousand-dollar guitar amplifiers are built with the darned things, even in this day and age (yes, I know about solid-state amplifiers but a lot of guitarists seem to prefer the warmness of the older-style technology, and the manufacturers are doing a booming business still building them).

    --
    This space for rent!
  72. Population: Growing! by tepples · · Score: 3, Funny

    On the other hand, there are many times less people capable of making horse buggies than in the XIXth century Citation needed that the population has not grown since then, even among the plain people.
  73. Context is key to his list by Shivetya · · Score: 1

    Especially in this case. Assembly programming is still used on different systems. Sure on some it is not needed because of the tools provided but in every platform I have found there is always something that can be done better in assembly rather than a high level language. The key is to know when it not only is better to do so. That determination is usually based on performance versus time to develope versus ease of maintenance.

    --
    * Winners compare their achievements to their goals, losers compare theirs to that of others.
  74. The whole list is crap by Nursie · · Score: 2, Interesting

    Threading a Needle
    Using a Fountain Pen
    Coins on the machine to reserve next go
    Memory Management ...

    There are many many useful and relevant skills on there.

    1. Re:The whole list is crap by autophile · · Score: 1

      I think the point of the list was to point out skills that everyone in that field knew, but is not broadly necessary anymore. In the 1800s, everyone who wrote had to know how to use a fountain pen. Today, it's limited to a few (proportionally speaking) FP enthusiasts.

      Although I have to agree -- for people who sew, how do you get by without knowing how to thread a needle?

      --Rob

      --
      Towards the Singularity.
    2. Re:The whole list is crap by Anonymous Coward · · Score: 0

      Although I have to agree -- for people who sew, how do you get by without knowing how to thread a needle?

      That's easy, you just buy prethreaded or self-threading needles, not.

  75. Using a Fountain Pen?!?! by idiotnot · · Score: 1

    Using A Fountain Pen. At least someone had the good sense to edit that one. I will admit that finding a fountain pen has become difficult. Other than specialty stores, the only major retailer I've found lately that routinely has them is Staples (and the nearest one of those is around an hour drive away). I use one of these (the charcoal model) pretty much exclusively at work. And I do get quite a few positive comments about it from people who try it.

    1. Re:Using a Fountain Pen?!?! by Anne+Thwacks · · Score: 1
      Fountain pen? Some of us were taught to make our own quill pens (first catch a large swan or goose:-)

      My father was even taught to make his own ink! Hell, I bet you youngsters would not even know how to fetch ink from an ink well. As for Clerkenwell..

      --
      Sent from my ASR33 using ASCII
    2. Re:Using a Fountain Pen?!?! by _Shad0w_ · · Score: 1

      I use a fountain pen all the time, a Sheaffer Prelude one in matt black with gold plate trim. I use ink from bottles too, not cartridges. But then I also use a turquoise ink, just to be different.

      I'm tempted to get the pencil and the rollerball to go with it at some point.

      --

      Yeah, I had a sig once; I got bored of it.

  76. Skills I'd expect to be obsoleted by 2029. by Anonymous Coward · · Score: 0

    The 3-finger salute, Regedit, non-standard HTML to work around IE bugs, associating filesystems with letters of the alphabet.

  77. LIST of obsolete things by electrictroy · · Score: 5, Interesting

    Oh this is cool! I could go on and on and on. While it's true some of these skills are still necessary for a few "elite" programmers or engineers, most of these skills are no longer used by the average user. To wit:

    - what to do with a Commodore 64 when its cursor is blinking at you
    -----(everyone I know in my circle of friends would go "duh")
    -----(they have no clue how to navigate without icons or explorer)
    - how to write a simple basic program for your C=64:
    ----- 10 print "hello"
    ----- 20 goto 10
    ----- RUN
    - LOAD "$" to get directory off my cassette drive (yes we used cassettes)
    - LOAD "*",8,1 to autoload & start most floppy disks
    - how to crate 16-color pictures that look good
    - how to program the SID to make music

    - dir df0: to get a directory on a Commodore Amiga 500/2000
    - the difference between Chip and Fast RAM
    - why it's a bad idea to multitask 2 programs off the same floppy
    -----(because the floppy will knock itself silly trying to read two tracks at the same time)

    - ATDP 5601750 to dial on a rotary/pulse phone (ATDT for touchtone)
    - +++ to get your modem's attention so you can issue commands like:
    - ATH to hang up
    - how to create pretty pictures using ANSI
    - what is Zmodem, and why it's better to download files with Z rather than Xmodem
    - how long will it take to download a 3.5 inch floppy over 2.4k modem
    -----(long enough to eat supper and take a shower)
    -----(or watch the latest episode of Star Trek The Next Generation)

    - how many hours you can squeeze on a T-180 VHS tape (9)
    - how many episodes of Quantum Leap if you remove the commercials (12)
    - how to repair your copy of Star Wars after the tape tears in half (scotchtape)

    Most of the things I just listed were items known by "everyone" back in the 1980s. If you wanted to use a computer, you had to know the various commands and understand how/why things work.

    Today people don't need to know command-line text.
    They can just point-and-click; it's become easy.
    And a lot of the things we used to need to know?
    It's essentially automatic now.

    --
    The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    1. Re:LIST of obsolete things by mapsjanhere · · Score: 4, Interesting

      where's the set of boot floppies with different emm.386 configurations to get all those early PC games going? I remember Ultima Underworld being my favorite game but also the one that taught me most about dos memory allocations. Not to mention cutting notches in the C64 5.25" floppies to make them work dual sided (saved 50 cents a floppy).

      --
      I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
    2. Re:LIST of obsolete things by Ihlosi · · Score: 4, Informative
      where's the set of boot floppies with different emm.386 configurations to get all those early PC games going?



      Sorry, those became way obsolete with Dos 6.22s ability (iirc) to have multiple configurations to chose from. :P


      Anyone remember countless runs of memmaker to squeeze the last byte of RAM out of a config ?

    3. Re:LIST of obsolete things by Saffaya · · Score: 1

      >

      I can't understand what were thinking the Commodore engineers, really.

      By comparison :

      How to start floppy on an ATARI 800 XL ?

      -Just hold the start function key at Power On.

      No instruction to type
      No funky parameter "*" to remember
      No obscure sequence of number 8,1 to remember

      Not to mention the god-awful speed (lack of) of the commodore disk drives

    4. Re:LIST of obsolete things by IorDMUX · · Score: 1

      - why it's a bad idea to multitask 2 programs off the same floppy *shudder*

      I literally cannot picture anyone in their right mind trying to do this. Maybe it just shows my computer-age, but that sounds to me about as good an idea as drunken NASCAR.
      --
      >> Standing on head makes smile of frown, but rest of face also upside down.
    5. Re:LIST of obsolete things by electrictroy · · Score: 1

      A couple thought:

      (1) The start key on the 800XL probably issued the same command (LOAD "*") but it was automatic, rather than typed. The Commodore 64, being developed earlier, also included an autoload function, but it autoloaded off the cassette drive (the most common device in 1982).

      (2)(a) LOAD "*" is nothing exotic. * is just a wildcard that says load the first program. I'm sure you're familiar with wildcards. Right? (Maybe this is another thing that today's users have forgotten.)

      (2)(b) ,8 == use drive 8 (disk drive). 9 == use drive 9. And so on.

      (2)(c) ,1 is optional. Without it, the program loads directly to BASIC, and many programs will work just fine with LOAD "*",8

      With the 1, it tells the C64 to dump the operating system and allows the program to fill-up as much space as possible (thus enabling the C64 to use all 64 kilobytes of space for the user application) (Atari800 programs were limited to only 48(?)k of RAM). The first byte in the C64 file usually specified where in memory it should reside.

      (3) The drives were not slow once you loaded them with fast-loading software. After that was done, the C64 drives ran faster than did the Atari drives. As example, Microprose's Red Storm Rising loads in just 20 seconds time, thanks to its fast loader.

      (4) Commodore 64 also had better sound with triangle and sawtooth generators (atari had none), thus enabling the C64 to sound like various instruments rather than like a touchtone phone. The C64's SID chip still remains popular today, used by artists like Timbaland in their latest over-the-radio creations.

      --
      The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    6. Re:LIST of obsolete things by ncc74656 · · Score: 1

      I can't understand what were thinking the Commodore engineers, really.

      By comparison :

      How to start floppy on an ATARI 800 XL ?

      -Just hold the start function key at Power On.

      No instruction to type
      No funky parameter "*" to remember
      No obscure sequence of number 8,1 to remember

      ...and on the Apple II, you don't even need to do that. It'll automatically boot (or try to boot) from the storage device (could be a floppy drive, hard drive, CD-ROM, or even a LocalTalk network) in the highest-numbered slot as soon as you flip the switch.

      Apple II FTMFW! :-)

      --
      20 January 2017: the End of an Error.
    7. Re:LIST of obsolete things by mapsjanhere · · Score: 1

      Dos 6.22 was released 1994, while ultima underworld came out in 1992. Just in time to acquire another obsolete skill.

      --
      I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
    8. Re:LIST of obsolete things by Mister+Whirly · · Score: 1

      Ah yes, the glory days of loading as much into HIMEM as possible so your games could use all of the "conventional" memory. You would feel like a wizard after struggling for hours, and then suddenly IT WORKS! And boy, look at those stunning EGA graphics!! Now that it is working you just need to spend another half hour configuring your soundcard to work.
      And the old paper hole punch trick to make double sided floppies out of single sided ones. If I remember correctly, I think I saved more than 50 cents a floppy this way. I think it was more like a buck. Which at the time was worth a lot of money. (Just kidding.) But seriously, get off my lawn you kids!

      --
      "But this one goes to 11!"
    9. Re:LIST of obsolete things by Torontoman · · Score: 1

      I used to recall even shortening LOAD to "L O"

    10. Re:LIST of obsolete things by electrictroy · · Score: 1

      I did it.

      Once.

      It sounded like my Commodore Amiga's floppy was trying to pound its head to pieces, and of course it took three times as long to load two programs. After that I learned to run my programs out of the RAM: disk. In defense of myself, the whole multitasking thing was new back then. We users had to learn as we went.

      Of course, isn't that how Windows operates today? Multiple programs often try to access the hard drive at the same time, causing the head to make lots of noise. As example, try running Vista on a 256 megabyte machine (and just listen to the hard drive grind). Ugh.

      --
      The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    11. Re:LIST of obsolete things by louisadkins · · Score: 1

      MemMaker... The trauma, it makes my brain bleed..

    12. Re:LIST of obsolete things by electrictroy · · Score: 1

      Yeah.
      Well.
      My Commodore 64 only cost $300! ($100 for the computer and $200 for the drive). Bet you couldn't buy an Atari or Apple equivalent for the same price. So there! ;-)

      Actually the low price was the reason Commodore 64 became the best-selling computer 1984, 85, and 86. But anyway.... This conversation reminds me of the old flame wars on 1980s-era BBSes. "68020 is better. No 80286! You're wrong! No you are." Heh. Seems kinda pointless now.

      I now have my C64 hooked to a 27 inch television.
      It is slightly blurry (S-video), but fun to play the old games.

      --
      The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    13. Re:LIST of obsolete things by Pathwalker · · Score: 1

      I don't remember ever needing to hold down START to boot from a disk.

      Disks would boot by themselves, but usually you had to turn off BASIC to make more memory by holding down OPTION.

      SELECT I think was to boot from a tape.

    14. Re:LIST of obsolete things by mvdwege · · Score: 1

      Your explanation is subtly wrong.

      The final parameter of the LOAD statement has nothing to do with switching off the ROMs. The final parameter is 'absolute address loading'. The first two bytes of a program file hold the starting address, and setting the final parameter to 1 makes the KERNAl load the program file at its indicated address. Most autostarting programs used this by setting the starting address to a system vector (like the BASIC interpreters main input loop), starting the program automatically after the LOAD terminated. BASIC programs carried $0801 (or $0800, that I keep forgetting) as starting address, as this was the start of user RAM ($0000-03FF was system pages, $0400-07FF was screen RAM.)[1].

      Neither the KERNAL nor the BASIC ROMs carry any function to switch off the ROMs. That is purely done by manipulating bits in the processor I/O registers at $0000 and $0001.

      Mart

      [1] To complete my C64 geekery: user RAM ran from $0800 to $9FFF. The BASIC ROM ran from $A000 to $BFFF, $C000-CFFF was 4K of free RAM usable as scratchpad, often used for machine language routines that would not interfere with user RAM, $D000-DFFF was I/O space, where the video, sound and general I/O chip registers lived, overlayed with the character ROM, and $E000-FFFF was the KERNAL.

      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    15. Re:LIST of obsolete things by Sigma+7 · · Score: 1

      And the old paper hole punch trick to make double sided floppies out of single sided ones. If I remember correctly, I think I saved more than 50 cents a floppy this way. I think it was more like a buck. That's a neat trick. It's also a great way to make the disks more unreliable than they are - those floppies would only properly work at 360K/720K and would collect bad sectors much more rapidly when formatted to 1.2M/1.44M.
    16. Re:LIST of obsolete things by cayenne8 · · Score: 1
      "Maybe it just shows my computer-age, but that sounds to me about as good an idea as drunken NASCAR."

      You just confused me...I thought drunken was a necessary part of NASCAR enjoyment!!!

      :-)

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    17. Re:LIST of obsolete things by mikael · · Score: 1


      - ATDP 5601750 to dial on a rotary/pulse phone (ATDT for touchtone)
      - +++ to get your modem's attention so you can issue commands like:
      - ATH to hang up


      Those skills are still in use if you want to use a wireless or satellite modem using PPP and Linux - but not many people need to if they have a landline broadband connection.

      I still use rabbit ears antennae for my PC - it has a TV card inside, but since the room it is in, doesn't have an external antennae socket, rabbit ears antennae are necessary. Not that the reception is improved that much.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    18. Re:LIST of obsolete things by Dun+Malg · · Score: 1

      And the old paper hole punch trick to make double sided floppies out of single sided ones. If I remember correctly, I think I saved more than 50 cents a floppy this way. I think it was more like a buck. That's a neat trick. It's also a great way to make the disks more unreliable than they are - those floppies would only properly work at 360K/720K and would collect bad sectors much more rapidly when formatted to 1.2M/1.44M. You're talking about the HD vs DD/QD IBM disks. That's not what we're talking about. As the GP poster SAID, the hole punch trick with was to make double sided floppies out of single sided ones. The only difference between a single sided and double sided disk WAS the second hole. Disk manufacturers made both sides of equal quality because some single-sided drives had the head on top, some had it on the bottom, and they had no way of knowing how the disks were going to be used.
      --
      If a job's not worth doing, it's not worth doing right.
    19. Re:LIST of obsolete things by Anonymous Coward · · Score: 0

      Someday, when I'm old and senile, I might not remember the names of my grandkids, but I *will* remember that JSR'ing to $ffd2 prints the PETSCII value in the accumulator...

    20. Re:LIST of obsolete things by Eivind · · Score: 1

      Quiz do-you-remember: POKE 53280, 7 does -what- precisely ? (for non-nerds: what happens if you store "7" in memory-address 53280 on a C64 ?

      Bonus: What -other- "magical" memory-adresses do you still remember ?

    21. Re:LIST of obsolete things by electrictroy · · Score: 1

      Thanks.

      I was mainly trying to refute the statement that Commodore 64 made its users "remember funky parameters and obscure sequences".

      LOAD "*"

      should be blatantly obvious to anyone who knows wildcards or uses search engines. It simply loads the first program it sees. Nothing complicated about that. And the appended ,8 is simply the drive (like a: b: c: d: on Windows).

      The command is not "obscure" is you use your brain.
      I guess that's something else that's become obsolete
      (casual users don't need to use their brains on modern winDoze).

      --
      The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    22. Re:LIST of obsolete things by Mister+Whirly · · Score: 1

      B.S. - it didn't make them any more "unreliable". How would punching a small hole in the outer plastic sleeve of a diskette have any sort of effect on reliability? And if that were true there would have been millions of "unreliable" disks out there as everyone I knew would also use the same trick. Why pay more for exactly the same thing when you can do it yourself? The purchased "double-sided" disks had no more of a guarantee than the single-sided ones.

      --
      "But this one goes to 11!"
    23. Re:LIST of obsolete things by blincoln · · Score: 1

      How would punching a small hole in the outer plastic sleeve of a diskette have any sort of effect on reliability?

      Using a DD disk as an HD disk by punching the extra hole did in fact lower the reliability considerably - not because punching the hole did anything to the media, but because the media was not designed for that density of data. I ran into this myself years ago when I discovered that all of the disks I'd done this to were no longer readable, whereas the actual HD floppies still were.

      As others have said, this does not apply to the single-to-double-sided thing, only to DD-to-HD.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    24. Re:LIST of obsolete things by Mister+Whirly · · Score: 1

      We were never discussing punching a hole in double/high density disks, only single/double sided disks. Putting more on a disk than it is rated for capacity is NEVER a good idea, although was possible through any number of hacks.

      --
      "But this one goes to 11!"
    25. Re:LIST of obsolete things by ncc74656 · · Score: 1

      This conversation reminds me of the old flame wars on 1980s-era BBSes. "68020 is better. No 80286! You're wrong! No you are." Heh. Seems kinda pointless now.

      True, but what's wrong with a little mindless diversion for old times' sake? :-)

      (FWIW, I have a VIC-20 and some of those Commodore 64-in-a-joystick thingys to go along with my Apple IIs. Still don't have anything from Atari (other than a 2600), but that's mostly because I haven't gone looking for one yet. I wouldn't mind having one, though. While most school districts stuck with Apple IIs, DoDDS put Atari 800s in its schools, so that's what I ended up playing with in 8th and 9th grade.)

      --
      20 January 2017: the End of an Error.
  78. Degaussing a CRT monitor? by Anonymous Coward · · Score: 0

    CRT's are still in high demand. Some of us prefer good image quality, thank you very much.

  79. LILO?!!! by Eudial · · Score: 2, Funny

    LILO is not obsolete! They'll have to pry it out of my cold, dead hands. GRUB is the work of Satan!

    --
    GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
  80. Starting a fire with sticks by gelfling · · Score: 4, Funny

    Skinning a hide
    Crushing a Mastadon with a bolder
    Killing your enemies & impregnating their women
    Being a Sun God

    1. Re:Starting a fire with sticks by danilo.moret · · Score: 2, Informative

      Being a Sun God I am not obsolete, mortal. And to show my powers, I will run an eclipse today. Not the IDE.
      --
      ^[:wq!
    2. Re:Starting a fire with sticks by shiftless · · Score: 1

      Crushing a Mastadon with a bolder

      spelling

  81. using Microsoft Vista! by Anonymous Coward · · Score: 0

    Oh wait, that has to be a skill that was once used. never mind then

  82. it exists by Anonymous Coward · · Score: 0

    Using the turntable, you could very rapid move trough the whole video, search a certain place, scratch trough to watch animations, find specific frames, etc. Would be quite usable (and sort of gets used in VJing.. but I'd love to use it for generic video cutting).

    Yeah I have seen edit machines with that type of interface. They do exist

  83. Real Carriage Returns by BoRegardless · · Score: 1

    Still have my Hermes portable from the 60s that I went through school with. That was an easy carriage return to make.

    But if you like excersize. The old 50 lb cast iron Royal I learned to type on had a literal carriage whose weight exceeded the weght of my Hermes.

  84. rotary phones are not obselete by Anonymous Coward · · Score: 0

    I use a 40-year-old pinkish rotary phone all the time. The sound quality on those things is way better than on most modern phones, and the handset has a nice hefty feeling.

  85. IRQ Settings by Anonymous Coward · · Score: 0

    I'll have to say I wish I didn't have to deal with IRQ settings anymore, but it comes up everyday using embedded motherboards since we end up using all 4 serial ports for communications.

  86. Who says assembler is not used for applications? by Panaqqa · · Score: 1

    I disagree, and I know of someone else much more prominent than me who would disagree also: Steve Gibson of Gibson Research Corporation. Steve has written some amazing little applications in assembler, and "little" is a good adjective for them. Try using Visual C++ to write a comprehensive disk recovery application that fits in 170K. And within that 170K is the capability to work under any operating system (Windoze, Linux, ...) using any file format (FAT, NTFS, ...) on any type of drive (SATA, SCSI, ...) connected to the PC in any way (USB, 1394/Firewire, ...)

    Writing application software in assembler is not easy, therefore very few people undertake to do it, but the results can be well worth the effort. Tiny executables that run with blinding speed are the most obvious advantage.

  87. I'm gonna go out on a limb here... by Jedimstr397 · · Score: 2, Insightful

    HD-DVD is obsolete. I feel sorry for those poor bastards that bought the new Beta. I never had a Beta Player myself, my mom opted for the VHS based on my uncles' advice. Any comments from anyone with prior experience in owning and operating an obsolete device that feels as though it just wont let go? In this day and age with HD-DVD I wonder how long it will take to completely disappear? We're either going to have bargain basement prices on HD hard and soft ware or they'll skyrocket in hopes of being a collectors item.

    --
    This signature has The Force
  88. ASSEMBLY LANGUAGE IS OBSOLETE?! by PaulG.1 · · Score: 0, Redundant

    So all future operating systems will work worse than Vista. We are DOOMED.

  89. By 2029 by Reader+X · · Score: 1

    Storage management, i.e. any skill specific to disk array management/maintenance.
    Cabling, period.
    Typing, for most users.
    Reading, for a significant fraction of users.

  90. PostScript Errors? 'member them? by Ralph+Spoilsport · · Score: 1
    Remember them? Remember having to untangle some document because some incompetent fucking boob loaded a FreeHand or Illustrator file with 20 megs of crap on 40 different layers, only to make all but 3 invisible, and then the film printer would shit itself and dump mega$ worth of blank film on the floor, with some obscure error "sorry, could not complete operation, postscript error 23726" or some shit like that?

    God - I hated those days. And then the asshole would show up for his separations and be slapped with some huge ass bill and whine and whine and whine. "buh buh buh if it didn't print why did it finally print?" and we had to tell the stupid little fuck that he should have copied out the three layers he wanted into a single document, and saved it to a damn floppy instead of hauling in a Syquest drive full of bullshit.

    Grrr. I still get steamed thinking about all those two bit losers calling themselves "Designers".

    RS

    --
    Shoes for Industry. Shoes for the Dead.
  91. Syquest drives. by Ralph+Spoilsport · · Score: 2, Funny
    remember those pieces of shite? Remember when you put one in and it would go tickety tickety tickety and freeze up and you couldn't eject it? fuck I hated those things. The technique I found was to unplug it, eject it, then start it up, put in a black drive to see if it's the disk (which it usually was) or the drive that had died.

    RS

    --
    Shoes for Industry. Shoes for the Dead.
  92. I miss carbon paper by hansamurai · · Score: 1

    I used to buy carbon paper when I was younger and copy art from magazines and video game strategy guides. That was so much fun. My Chrono Trigger strategy guide is basically destroyed because of that.

    Then I moved up to *ahem* copying "other" magazines.

  93. Oh - and bad fonts - remember those? by Ralph+Spoilsport · · Score: 1
    Because some stupid shithead thought that buying Fontographer turned him into the second coming of Fred Goudy himself, but the fonts said idiot made were for shit, because points were on top of points, or the paths weren't closed or there were paths on top of paths in opposite directions making the raster engine explode. FUCK I hated crapola fonts - they'd blow up the postscript printer, or they'd print with nasty spikes coming out of them. damn.

    RS

    --
    Shoes for Industry. Shoes for the Dead.
  94. Troubleshooting/repairing hardware... by TFGeditor · · Score: 3, Interesting

    ...to component level with an oscilloscope and DVM. ...calibrating instruments using a precision voltage source, resistance decade box, or signal generator. ...using a frequency counter. ...hand winding precision wire resistors. ...reading resistor color codes. ...writing test algorithms in machine code (usually hex or octal, the language level between binary and assembly) ...making your own application-specific test instruments.

    --
    Ignorance is curable, stupid is forever.
    1. Re:Troubleshooting/repairing hardware... by rampant+poodle · · Score: 1

      I'll second that. Cut my electronic teeth in my grandfather's radio/TV shop. Tube testers, Signal Generators and tracers, and ocilliscopes. No DVMs 'tho - just a Simpson 260 VOM and a Heath VTVM. I'm dating myself but we also used soldering irons that looked like pistols, weighed a couple of pounds, and drew 100W. Anyone remember when a vibrator was part of a power supply, (rather than a sexual gratification device)?

    2. Re:Troubleshooting/repairing hardware... by TFGeditor · · Score: 1

      "Anyone remember when a vibrator was part of a power supply, (rather than a sexual gratification device)?"

      Is that anything like a chopper stabilized amplifier?

      --
      Ignorance is curable, stupid is forever.
    3. Re:Troubleshooting/repairing hardware... by Ellis+D.+Tripp · · Score: 1

      Similar piece of hardware, but larger/higher powered.

      Vibrators were used in vacuum tube car radios and other applications where high voltages were needed and only low voltage DC power was available. The vibrator was essentially a buzzer that was used to rapidly switch DC power on and off in the primary of a transformer, creating a pulsating DC which could be stepped up by the transformer and then rectified/filtered and used as the plate voltage for the vacuum tubes. They were constant trouble sources, with contacts that would stick (and blow the radio fuse), and they emitted large amounts of RF noise which had to be filtered out for the rest of the radio to work. Sometimes they wouldn't want to start without pounding the dashboard to get the weighted reed inside moving.

      They were rendered obsolete once crude power transistors came along, allowing the audio power output stage of a car radio to be transistorized. The other stages of the radio could then use specially designed tubes that would operate at low voltages, or, in a few short years, they became fully solid state.

      The electromechanical choppers that were used to stabilize op-amps in precision instrumentation were somewhat similar devices, but they tended to be more reliable because they only switched tiny signal levels, as opposed to the 15-20A typical of a car radio operated from the then standard 6 volt battery.

      --
      Remember "News for Nerds, Stuff that Matters"? Help make it a reality again! http://soylentnews.org
    4. Re:Troubleshooting/repairing hardware... by TFGeditor · · Score: 1

      Ah, okay. Essentially a mechanical DC to DC converter.

      Thank Bob for 1947 (or was it 48?) and Bell Labs.

      --
      Ignorance is curable, stupid is forever.
  95. I stack quarters, I'm 19 by Anonymous Coward · · Score: 0

    >>and stacking a quarter on an arcade game to indicate you have next

    I've often seen people of my age range (18-25) stack a coin on the side of a pool table to indicate they have next play.

  96. I do some of these things every day by John+Hasler · · Score: 1

    Others make no sense. A 2" floppy disk? There never was such a thing. Adjusting the gas mixture on a carburator? I adjust the carburator jets on my gasoline tractors from time to time, but they have nothing I would call a gas mixture adjustment.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  97. motorcycles are getting fuel injection by georgeha · · Score: 1

    FI is even trickling down into motocross. If you ride an older one though, get used to carbs and jets, my 75 Kawi still uses carbs, with three jets per carb.

    1. Re:motorcycles are getting fuel injection by pintpusher · · Score: 1

      My 93 Bandit 400 is a finicky little bitch. With high compression, small displacement, insane redline (13.5k) for the date, and 4 carbs in need of sync, tuning is a trick. It has to be done at least seasonally and with an eye to what altitude you'll be riding at.

      I probably spend about 20 hours a year tweaking the carbs to get it perfect for the next little piece of riding. But the carbs are such dead simple technology (if a little mysterious) that it's a skill you can pick up through trial and error and a little common sense.

      The results you get from a good tuning session are incredible though. I don't care how incredible FI gets, nothing beats an hour of tuning followed by hours of riding a barking howling piece of barely restrained chaos. There's something about the performance characteristics of carburetion that I don't think could be matched with FI.

      But I'm kinda spoiled by this bike... she's so sweet ;)

      --
      man, I feel like mold.
  98. Carbon paper still has many uses. by Anonymous Coward · · Score: 0

    It makes for an awesome way to transfer a printed document or photo on to a canvas for an artist to paint on. You don't even need to buy the carbon paper... just some notebook paper and a good ol number 2 pencil can be used. Scribble all over the back of the paper til it's coated with the lead, then you have instant carbon paper. A similar method of transfer involves poking holes in the source paper and pouncing that with some chalk dust, pastel dust, or charcoal dust in a little cloth bag. That pounce method has been used since the renaissance era.

  99. There are hundreds of obsolete skills. by ledow · · Score: 4, Interesting

    There are hundreds of obsolete skills. But there is one that NEVER goes out of fashion, never gets obsoleted, never stops coming in handy... the ability to learn quickly, and to remember what you learn. Seriously. I make a point of putting it on my CV (resume for you Americans). Learning quickly means you can adapt to ANY environment quickly. Remembering what you've learned means you can draw parallels and keep "generic" knowledge going. Bung me in front of a particular UNIX server and I might not have any idea how to do much but login. Give me ten minutes to acclimatise and I can be doing ANYTHING on it. TCP/IP is TCP/IP... the places where you change the settings may differ but knowledge of protocols, routing, etc. is the same whether it's a Commodore 64 on the web or a network of virtualised Vista PC's.

    I don't have MCSE, CCNA or anything else because the sheer fact is that by the time you've passed the course and been using it for a year, its content is out of date. Not all of it, but quite a bit of it. Especially on those courses designed for particular bits of software. And they are nothing but memory tests. That's not learning.

    I've done assembly, I've done BASIC and everything in between. My University tried to teach me Java until I stopped attending the lectures for that part and was instead "hired out" to other students as the person to ask about the Java coursework. I'd only ever dabbled in it but having programmed in a lot of other languages it was no more than a curiousity to flick through a Java book and pick up the syntax. I did the coursework myself at home, taught many others to pass the course, and passed myself (good grades for that course) with barely a sweat. I'd dabbled in Java before but it was merely a matter of flicking through a half-decent book on the subject, applying everything else you already know and making sure you have a list of function-method-procedure (call them whatever you like, OO is just a shortcut that saves you typing so much functional-programming code) name changes handy. KMP search algorithms are the same in any language, it's just a matter of learning or merely memorising (which is NOT learning) the differences between languages.

    Similarly, my primary job is being hired by schools to manage their networks. First one was 98-standalones with Ethernet cables basically used for display. :-) The next was a full Windows 98 network with custom management software and an NT server. The next was a 2000 Server and XP network with custom management software. The next was plain 2000 + XP with Active Directory. The next was similar but with some other custom management software bodged to perform some of the more tedious tasks. The next was Server 2003 + XP + Vista. And so on. The last one I had was another "design me a network from scratch" for a school, and so they got Server 2003, XP and Linux for some tasks (it was just easier, made more sense and cheaper).

    Formal training in any of the above OS, network management, network management software or application software? Zilch. Number of networks exploded? Zilch. Number of networks more productive once I had finished with them? 100%. Number of schools chasing me for further employment to work on their next big network, next OS, next suite of applications? I lose count. And these are critical networks - they run everything from the canteen to the staff wages to the legally required paperwork to the student desktops to the fire and security systems. You have no idea how crippled a school is nowadays if its servers go down... lessons stop, systems go haywire and the students get sent home. And they literally fight over getting an imbecile like me in to manage their systems, or even just clean them up so that they can employ a "normal" technician next year.

    If you can learn, you can run any OS, of any age, at any time, in any combination without a problem. If you can't then you're stuck memorising "Windows Vista for Dummies" until the next OS comes out a

    1. Re:There are hundreds of obsolete skills. by Anonymous Coward · · Score: 0

      Could you, please, name the software you use as remote desktop analogue? VNC is bandwidth-hungry (at least instances I have ran) so that is not an option for my class :(

    2. Re:There are hundreds of obsolete skills. by instarx · · Score: 1

      I make a point of putting it on my CV (resume for you Americans) Pardon me, but a curriculum vitae and a resume are different things. CVs are a history of academic/research experience (life's study) while resumes are a history of, well, work experience. Labeling one's work history (as a self-described hot-shot programmer, for example) as a CV is considered more than a bit pretentious - at least on this side of the Atlantic.
    3. Re:There are hundreds of obsolete skills. by ledow · · Score: 2, Informative

      Speaking for the UK:

      Erm... You might have been technically correct fifty years ago when everybody still did Latin but not any longer. It's standard practice in every company I've ever worked, for the last 20-odd years and probably a lot longer than that. CV = personal details + list of qualifications + (summarised) work history + references + (possibly) brief statements about important project you've done in the past (unless you're under 18 when it seems you're taught to list "interests" like "watching TV"... I've actually seen it on a CV). You usually cram it all onto 1 or maybe 2 A4 pages. Possibly a personal statement (1 page of A4) if requested stating briefly why you'd be good at the job, clarify anything listed on the CV. Cover letter to wrap it all up (two lines and some decent letter-writing layout).

      In the UK, no job agency would distinguish between CV and resume, unless they only deal with very pretentious clients, but I've never heard of anyone distinguishing over such a minor detail even in the City. Job adverts include the line "Send CV to:". Never any mention of anything else, except possibly "CV and Personal Statement". We don't even CALL it, or any part of it, a resume. We might have done once (I don't know the etymology, but it sounds French) but we haven't for years.

      And, working in schools, I can tell you that this is EXACTLY how children are taught to apply for jobs and have been for about the last two decades (I was, when I was at school/university). And it's exactly how every adult job application I've ever seen has arrived. You send a CV which incorporates all your qualifications and work experience, wrapped in a two-line cover letter (Dear Sir/Madam, My CV, Thanks). If asked, you provide a "personal statement" which is an A4 diatribe about your work life and what you can bring to a company.

      Maybe you're just nit-picking on the origins of the word but in the UK, you have a CV that tells you EVERYTHING you need on one page. You normally head it "Curriculum Vitae" (which lets you instantly discard those who can't be bothered to look up "Vitae").

    4. Re:There are hundreds of obsolete skills. by instarx · · Score: 1

      Having read your orignal post and now this reply, I find it hard to believe you could fit anything on one page! Just kidding - don't take offense.

      But back to the topic - this is similar to the "begs the question" merry-go-round on slashdot. Just because many people incorrectly use a term doesn't mean the incorrect usage magically becomes correct. You think chronic misuse of "CV" makes it correct to substitute for "resume", I don't. Cheers.

    5. Re:There are hundreds of obsolete skills. by oldbamboo · · Score: 1

      Mate, You have just gone so far off topic, you've done a slingshot around the sun, and have returned in a parallel discussion about wanking for coins. I'll applaud you for one thing, passion counts. And on the topic of redundant skills: There are no redundant skills, not really, what is really redundant and dead scary, is any computer book over five years old that doesn't deal in pure theory.

      --
      You may not agree with what I say, but you should fight to the death to allow me to say it, by modding me up.
    6. Re:There are hundreds of obsolete skills. by Anonymous Coward · · Score: 0

      "CV (resume for you Americans)..."

      In the US (and several other countries as well), both terms used, NOT interchangably.

      Headline in a mgazine once described how your resumes should not be overly long: "Windy Resumes Blow Jobs".

      Not very funny if you substitute "CV", now is it?

  100. Blowing dust from a Nintendo cartridge? by xgr3gx · · Score: 1

    I remember that! Hahah, that's a valuable skill...I can be used on all those NES emulators out there.
    My technique ... a hard blow from left to right, then blowing air from your nose going right to left, then a final soft blow from your mouth (like saying "ha") from left to right again. --It was 100% effective, 60% of the time.
    Any other children of the 80's have a whacky way to get their Nintendo to start working?

    --
    Shameless plug alert: Game server control panel
    1. Re:Blowing dust from a Nintendo cartridge? by Nerftoe · · Score: 1

      Any other children of the 80's have a whacky way to get their Nintendo to start working?

      This worked for me quite often:
      A swift, deliberate blow with two fingers (middle and ring) in the direct center of the top of the NES console. I would say it was 95% effective 70% of the time.

  101. Hardly obsolete by Tydelhof · · Score: 1

    Our NES and SEGA still work so blowing out cartridges is still useful occasionally. We just played Mortal Combat and Sonic the Hedgehog a couple nights ago.

  102. Getting off the couch to change channels on your T by nickname29 · · Score: 1

    Getting off the couch to change channels on your TV set Yeah, we had a manual TV. I think that is why parents got children - to get some little bugger to change the channels for them.

  103. Re:Syquest drives. And SCSI by Ralph+Spoilsport · · Score: 1
    I forgot: another useless skill: making sense out of multiple devices in a SCSI chain. Argh. Fucking PAIN IN THE ASS. USB and Firewire are SO much nicer...

    RS

    --
    Shoes for Industry. Shoes for the Dead.
  104. There really is a world outside Slashdot... by Anonymous Coward · · Score: 0

    Let's see - not long ago I had to deal with IRQ sharing issues in hardware and had to know how to resolve IRQ conflicts.

    Then there's the fact that I program in assembly language on a daily basis for my job - many low-end micro's still don't have C compilers and the scripting languages they do have are abysmal, buggy and bloated.

  105. We're talkin about "obsoleteness" by Nicolas+MONNET · · Score: 1

    Because non-programmers don't program in ANYTHING? Duh?
    Horse buggy makers are obsolete, their number has dwindled, both in percentage of anything and in percentage of vehicle makers.
    ASM programmers are not obsolete, their number is probably higher today than it was in the 70s.
    That's my point.

    1. Re:We're talkin about "obsoleteness" by drinkypoo · · Score: 1

      That's my point.

      and my point is that programmers who are actually functional with assembler are probably a smaller percentage of programmers today, because you don't HAVE to in order to perform most tasks.

      But since neither of us knows which is true, I guess it's a moot point.

      Anyway it's not obsolete until you don't need to do it, regardless. If I USE something which was optimized (or developed!) in assembly, then I am proving the point that it is not obsolete.

      And of course, anyone who drives a fuel-injected (or even O2-sensored) car is using assembler code EVERY DAY. Although, that is changing too; ECUs are getting more complicated and these days may actually be quite powerful, so I expect the amount of ASM in the PCM to decrease as well. But I will bet you money that the ~3MHz microcontroller-based PCM in my '89 Nissan was running code that was mostly or entirely written in assembler. And there's still plenty of that going on.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  106. Not obsolete (yet) by greysky · · Score: 1

    changing the gas mixture on your car's carburetor

    I'd hardly consider it an "obsolete" skill, as probably every mechanic school still teaches carburation to its students simply due to the fact that so many carburated motors are still out there in common use. I do this on a regular basis for my motorcycles, both of which are 2006 models. Nearly all off-road motorcycles today still use carbs.
    1. Re:Not obsolete (yet) by rampant+poodle · · Score: 1

      I wonder how many people still have the skills to set mixture and balance on SU carburetors? Then again - how many actually have a "Color Tune" to help them do it.)

  107. Pregnancy Test by Anonymous Coward · · Score: 0
  108. Appearently the poor are obsolete. by Steauengeglase · · Score: 1

    Building a computer from individual components: Only the mentally deranged don't go out and buy a Mac.
    Also if you purchase a Dell for less than $2,000 it is proof that you are a sub inbred hillbilly.

    Car repair: The dealership, please.

    Hayes Commands: Those who use dialup must DIE!

  109. RS232 isn't Obsolete!!! by cuby · · Score: 1

    In practice, only because it's hard to find a computer with a RS232 COM port, or because it's old, doesn't mean it is obsolete...
    My last two jobs, at some point, I used this port.
    If you work with "data terminals/pic programing/automotive industry/uncommon devices" it is certain you will work with one of these.

    --
    Math is beautiful... e^(pi*i)+1=0
  110. This is the list for morons. by kabocox · · Score: 4, Funny

    Guys print this out and hand it to your HR person. Here are things every new hire should know.

    Balancing a checkbook
    Clicking on the up and down arrows of a vertical scrollbar
    Commuting
    Extracting square roots

    Handwriting (How to fill out forms and sign stuff and write notes.)
    Having Cash (and how to properly make change)

    Long division?
    Look for a job in the classifieds?
    Looking up a business on the yellow pages
    Local Grocery Store?

    Paying for something with a check
    Playing solitaire with playing cards
    Reading a paper map

    Searching a card catalog

    Using a cell phone to make a call
    Untangling the cord of a telephone
    Using a card catalog
    Using a fax machine

    Using the Dewey Decimal System

    Zipping your pants

    If your new hire can't do any of those, you do you really want them?

    1. Re:This is the list for morons. by drew · · Score: 1

      Having cash?

      The only time I ever have cash on me is when I've just gone to happy hour at the Mountain Sun. It's the only place I can think of that doesn't take credit/debit cards (friggin' hippies) and they have an ATM right in the back. Why else would I ever have cash with me?

      --
      If I don't put anything here, will anyone recognize me anymore?
    2. Re:This is the list for morons. by kabocox · · Score: 1

      Having cash?

      The only time I ever have cash on me is when I've just gone to happy hour at the Mountain Sun. It's the only place I can think of that doesn't take credit/debit cards (friggin' hippies) and they have an ATM right in the back. Why else would I ever have cash with me?


      I'm not that paranoid, but I only use my debit card at places that I trust like walmart. Any mom & pop gas station could be over charging/double charging me. I'd much rather pay cash there. What's this aversion some people have with physical money? If you are concerned at all about your privacy, you'd pay cash every where except large purchases that you want registered.

      I shop at 3 types of places: gas stations, fast food, and Walmart. I only use debit card at Walmart.

  111. 8bit IRQs by ElephanTS · · Score: 1

    I used to program IRQ interrupts in 8 bit assembler. When I was 13 I thought those skills would take me round the world! 40 next week, bah!

    --
    spoonerize "magic trackpad"
  112. Author obviously doesn't work in government.. by Nukenbar · · Score: 1

    I have to use carbon paper forms every day.

    They may be obsolete, but they are still very much in use..

    1. Re:Author obviously doesn't work in government.. by HikingStick · · Score: 1

      They may be very much in use, but it just means the government work processes are also obsolete.

      --
      I use irony whenever I can, but my shirts are still wrinkled...
  113. You have a point - by Nursie · · Score: 1

    And I admit that I am the only person I know that writes with a fountain pen.

    Things that are not broadly necessary are not the same as obsolete though. Intimate knowledge of kernel programming is quite esoteric, but one could hardly call it obsolete.

    1. Re:You have a point - by JabberWokky · · Score: 1

      Same here. In fact, that's one of the next skills I'm planning on writing up for the original wiki the content of this one was lifted from. Somehow it seems slightly perverse to think about posting photos of my nibs online.

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
  114. Old-fashioned skills by JRHodel · · Score: 1

    My first computer justified text into full-width columns using 6-level paper punch tape for input and output - it had a plexiglass front and blinking neon lamps on the cards for problem diagnosis. It was the size of a home refrigerator! The generated tapes were used to control Mergenthaler Linotypes casting type using molten lead.

    I was able to operate all the machinery used in hot-type newspaper publishing by the end of that job, as well as most used in offset printing. This was true industrial-revolution age machinery, lots of cast iron and steel, vats of molten lead, huge presses spinning cylindrical lead plates with paper running by so fast the words and pictures were a gray blur.

    I also learned most of how to operate a photo-engraving shop using line screened negatives to etch photos into zinc plates using nitric acid baths for printing photos in hot-type publishing. How to spool film onto reels for processing in the dark! By feel!

    Later on I learned to milk cows, producing milk with nothing but my hands and a bucket! I still have a strong grip, 25 years later, and forearms like Popeye! Not quite, but sill...

    I know how to butcher meats in the back yard, and how to can food in the harvest season so as to be able to eat in the winter.

    I also know how to debug a hex dump, the worst bug I ever found was an unprintable character that occurred right where a decimal point belonged....whooo!

    I know Calculus, is that obsolete now?

    I have several slide-rules, but haven't used them in a long time, so I would have to review that technology to be proficient.

    There are others...using non-synchronized transmissions, some skills I won't fess up to...

    --
    Think of the Irony!
  115. Carbon paper isn't obsolete by pbhj · · Score: 1

    I've used carbon paper several times today ... for simple receipt counterfoils. We're too small a business to afford the cost / time-cost of implementing a fully computerised system - also the method we use the counterfoils for (tracking with pottery items) would need large hardware expenditure. I can currently just put the counterfoil in a mug ... how do I replicate that with computers, perhaps an item recognition system create closest matches based on colours, or an RFID system. I could just print lots of receipts ... but the benefit isn't great enough to implement.

    Like I said not obsolete. The right tools for the job.

    Also, we use carbon paper for transferring images onto once-fired pottery (bisque) to aid painting.

    We're a pottery painting studio - Barefoot Ceramics pottery painting studio, Newport, UK.

  116. Blowing Nintendo Cartridges by Supergibbs · · Score: 1

    Unless you still have one that (sorta) works like me. Plus you are all welcome to blow my Wii :-)

    --
    First post! (just in case I am...)
  117. 68k 3 site? by Anonymous Coward · · Score: 0

    So many people love 68k that there really ought to be a love site for the architecture.

    With the demise of the Amiga, the processor family got "demoted" to the esoteric haunts of embedded systems programmers, which is a great pity. I bet that a 68k fansite would draw a lot of support. That architecture was so beautiful, a joy to use.

  118. Many entries are not correct by Anonymous Coward · · Score: 0

    Looks like about 10% are valid. Many of these skills are absolute baseline requirements when working with high reliability legacy interfaces. You have to know how assembly code works, or the "older" character codes. Even the ones like BW darkroom photography are still coveted skills. Try again an about 10 years.

  119. Faxing a Document? by fuzznutz · · Score: 1


    The real estate industry lives by the fax machine. You gotta have the client's signature on the document before presenting it to the other party. You can't do that with an email fax.

    Negotiation counter offers are all done by fax.

  120. Changing tracks on a 8 track player isn't a skill by trailerparkcassanova · · Score: 1

    Positioning the folded matchbook cover between the cartridge and the player to optimize the tracking is a skill. And disassembling the deck to remove an accumulation of roaches is a skill with a reward.

  121. darkroom skills by swschrad · · Score: 1

    no, you cad, I mean working with film, not the opposite half. spooling development tanks, or pushing a tape measure through the tanks of a continuous processor to rethread it when a stapled splice breaks. dodging an image to lighten an area when making prints. it's all going fast... totally gone in production, going fast in art photography.

    --
    if this is supposed to be a new economy, how come they still want my old fashioned money?
  122. Not only particule physic by aepervius · · Score: 1

    A lot of mathematical application in research are in Fortran. They use known library, debugged for the last 40 years, giving known results, with a known precision. Most people which I know do some research using a lot of math (physic, etc...) don#t use c or java or whatever on their irix-origin, they use Fortran, most probably HPF. Heck i know of some airline IT provider using fortran...

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
  123. Obsolescent but not obsolete by grandpa-geek · · Score: 1

    In our house, we still have a black, rotary-dial phone that we continue to use. Obviously we have to use one of our (many) "touch tone" phones for things like working through telephone menu systems.

    We also have two VCR's and sometimes have to adjust tracking.

    Many of the skills listed are obsolete only for people who don't keep older products around or who are too young to ever have used them.

  124. Troubleshooting IRQ conflicts still neccesary by BcNexus · · Score: 1

    Don't believe me? IRQ conflicts make Ghost run slow on computers (2004), and believe you me that this is still a problem on Dell Optiplex 745s in 2007 and 2008!

  125. emacs not obsolete by Anonymous Coward · · Score: 0

    Emacs is not obsolete. It's widely used. The author obviously is showing bias, which brings into question other items the author has claimed obsolete. The author has lost credibility with such derogatory flames.

  126. Phone Books by Schnapple · · Score: 4, Interesting

    I haven't read the article or the Wiki (I'm not new to Slashdot, after all) but I figured this is as good a place as any to post this insane dribbel from my head.

    Back when I was a kid, I grew up in a modest town of about 50,000 people. Too big to be a small town, not big enough to get on most maps. Our phone book was about one inch thick. Small towns had phone books that were essentially glorified pamphlets, about 1/4" thick, and even then they shared it with all the neighboring towns. I knew people from small towns who thought phone numbers were four digits long, since the first three digits were always the same (and the then-optional area code was the same for probably a hundred miles).

    When my family would go on trips we would visit "big cities" like Dallas, Houston, Orlando, Memphis, etc. (yes, I'm from the South) and in the hotel rooms I would notice that the phone books were always really thick. Like 4-5" thick. And sometimes, that was just the yellow pages, the white pages were an entirely different book, itself 3" at least. And they always had these awesome pictures on the front of the local skyline instead of the giant public domain "fingers do the walking" logo that would grace the phone book back home.

    So consequently I made the connection early on in my mind that living in a huge city meant you were a success. And living in a huge city meant a huge phone book. Therefore, having a huge phone book in your home meant you were a success. A tenuous connection, but even then I had big dreams of moving to a "big city" later in life and one of these days I would have a big phone book in my house because hey, that's what big successful people living in big successful cities do.

    Years and years pass. I grow up, go through High School, go to College, graduate, get married, and eventually my Wife and I move to the Dallas/Fort Worth Metroplex. We get good paying jobs and rent then eventually buy a house. Initially the phone books that would appear on our porch would be the same standard one-inch affairs I grew up with because we live in the suburbs and they only cover the suburbs, but then one day a bag with two phone books, a 3-inch white pages and a 5-inch yellow pages, shows up on our front porch. These phone books cover the entire Metroplex. They have amazing photos of the Dallas skyline, with Reunion Tower (the one with the ball on the end) on them (under a stuck-on ad for some ambulance chaser, but that peels off easily enough).

    I'm elated. After all these years, I've finally made it! I'm finally in a good job making good money and living in a big city and hey, like all big successful people living in big cities, I have a pair of bigass phone books. I've arrived! Every time I look at these phone books I'll remember how I'm in a big city.

    So I put these phone books next to the phone and the first thing my Wife says was "Just throw those things away. We have the Internet now."

    I ignore the order and I keep the phone books under the phone cradle for a few years, exchanging them out when a new one comes in. I never tell my Wife the insanely silly "but I've always wanted a big phone book" fantasy because I'm not in the mood to get laughed at (though, apparently, I don't mind that people on Slashdot will laugh at me). I get to keep them in place with the razor thin "well what if we want to look up a phone number when the power's off or our Internet is down?" excuse.

    But then one day I'm cleaning the house and I'm trying to reduce some clutter and it occurs to me that in two years I've never opened these things, ever, and they're just collecting dust and the odds of the power going out or the Internet going down at the same time as my cell phone battery dying and me having to have some obscure phone number are vanishingly small. Oh, and in the years since we moved out here we've switched to Vonage so we couldn't even use the phone in a power outage anyway. And I now have Internet access on my phone (hell my wife has a Treo) so if we needed to

    1. Re:Phone Books by anthonys_junk · · Score: 1

      Nice story. Thanks.

      --
      Barbara Felden claims prior art on the flip phone, sues Motorola, Nokia.
    2. Re:Phone Books by Anonymous Coward · · Score: 0

      Not to sound like a commercial here, but I've thrown out my phone books since I discovered 800-GOOG-411. Toll-free yellow pages that will connect you to the businesses it finds. Between that and the POIs that come on my GPS, I haven't looked at a yellow pages in a couple of years.

    3. Re:Phone Books by Anonymous Coward · · Score: 0

      Thanks for the story ...

      The only problem - I couldn't get Steve Martin out of head: "The new phone books are here! The new phone books are here!"

  127. Loss of technical skills by swb · · Score: 1

    I worry that we (collective we) are losing touch with the "entry level" technology which got us to the 20th century and that if we faced a significant enough "situation" we would have to go through a very long time re-learning how to do things that were considered basic mass production skills in the 1800s or basic farmstead skills.

    Hell, it may actually be worse -- we may not know how to do things in ways that were considered technologically trivial in the 1930s -- the example that comes to mind is making metal parts without a 6-axis CNC machine fed with a design from a 3D CAD program.

    If we get too "advanced" and lose touch with more simple technologies, we may find our society struggling through a long dark ages simply because nobody knows how to do anything anymore.

    1. Re:Loss of technical skills by Miamicanes · · Score: 1

      That brings up an interesting point.

      Allegedly, a large-scale EMP blast could destroy just about every semiconductor on earth. If Intel or AMD were instantly reduced to making PNP and NPN transistors and trying to rebuild their entire chip portfolios from scratch -- with notes (hopefully in hardcopy and not only in now-unreadable digital form), how many years would it take just to regain the technology we had in 1970? Would we go through a decade of reinventing and using the 74xxx discrete logic chips (but maybe this time going straight to surface mounted chips?), or would we mostly skip over that era and go straight for CPLDs and FPGAs? Or TRY to skip over them and go straight to CPLDs & FPGAs, fail miserably (or price them out of the market), and end up wasting 5 years on a temporary technological/economic dead end?

      Ditto, for CPUs. Would we even screw around with reinventing the Z80 & 6502? Try building a 680x0 with twenty thousand discrete chips? Go straight for ARM? Would the race be on to regain 2 gigahertz, or would multicore chips hit post-apocalypse computers before speeds even made it back up to 100MHz again?

  128. Getting an NES cartridge to work by asiansteev · · Score: 1

    Blow in it. Push it as far back as you can or let it teeter where the connectors are barely touching. Shift it from side to side when it's pushed in and down before turning the system on. Stick another cartridge in the space once the cartridge is pushed down to keep it a little further down than it sits naturally. Swab the connectors with a q-tip. Swab the connectors with an alcohol soaked q-tip. Last resort: buff the connectors with your mom's fingernail file (not because you'll damage the cartridge, but because you'll have to explain to your mom why her file has green dust on it). HTH.

  129. Some weird choices there by smellsofbikes · · Score: 2, Informative

    Very computer-centric, and more particularly, very 1970-1985-computer-centric.
    How about: making wooden wheels, for cars or carts?
    Drilling holes in stone with a hammer and a stardrill?
    Repacking plumbing/steam gasket seals?
    Installing/maintaining lead/oakum plumbing?
    Relashing valve pushrods or regrinding valve seats with a file?
    Filing threads?
    Making nails with a hammer and a header?
    Making wrought iron?
    Making aluminum without electricity?
    Forming lumber with a froe, an adze, and a two-man saw?
    Tanning leather?

    And some of the items, I just flat-out disagree with: making a fire by striking two pieces of flint together? That *doesn't work*. You strike a piece of steel against flint, which throws sparks because the steel is cut by the flint and showers off bits of hot steel. Flint doesn't burn.

    --
    Nostalgia's not what it used to be.
  130. I feel old by ceeam · · Score: 1

    As for the first link, I can do - and did - all 11 bullet points.

    And I'm only 33.

  131. old skills by nozzo · · Score: 1

    It brings a tear to my eye thinking about all those old skills I've got but are useless. Here's a few: Knowing the pinouts of a 25D to 9D sub serial connector Been able to solder the above from a bag of connecters and a spool of cable. HP3000 system admin commands Been able to use Highmem and devicehigh etc to optimise MS-DOS workstations Knowing your ISA from your PCI from EISA from MCA Knowing how to configure BIOS on an IBM PS/2 using a floppy Building a TCP/IP stack in MSDOS using NDIS drivers How to apply a bee-sting to the RG coax etc etc It's all too easy now-a-days which is why I'm now into Linux. At least I can retain _some_ mystique on how to get hardware working and pretend it's all black magic.

  132. Ah, the obsolete disk drive interfaces... by Rey+Willie · · Score: 1

    Properly configuring SMD interface disk drives. First, properly configure your SMD A-cables (daisly chain) and B-cables (radial). Don't forget to ground properly, or you'll never reliably support the blistering 3Mbit/sec. transfer rates. Then set the DIP switches for the proper sector size, and insert (or remove) a jumper shunt to supress the "runt" sector. Ahhh, glory days.

    For those a little bit younger, configuring and terminating parallel SCSI interfaces is also a lost art, or at least on the way out.

    Then you've got your ESDI and IPI stuff. All gone.

  133. More complete wiki (and source for content) by JabberWokky · · Score: 1

    As the linked to wiki indicates on the home page, they took a chunk of content from the more complete Wiki Spot Wiki of the same title. In fact, the owner of this wiki wanted to take the Wiki Spot Wiki's logo and everything. It would be nice if the Slashdot editors could give obsoleteskills.wikispot.org a little linkage love too, since I and several other wiki editors spent time writing the entries there, setting up photo shoots (note my 8 track of Monty Python) and basically creating content which was basically lifted for this wiki. Ah, well.

    --
    "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
  134. Calibrate an R390A by alfredo · · Score: 1

    churn butter, rebuild a Bendix kickback hub.

    --
    photosMy Photostream
    1. Re:Calibrate an R390A by nsaspook · · Score: 1

      I could rebuild a R390A in my sleep. (1970s) ex-old-school RADIOMAN http://www.rotten.com/library/history/espionage/uss-pueblo/

      --
      In GOD we trust, all others we monitor.
    2. Re:Calibrate an R390A by alfredo · · Score: 1

      05H20 Asmara Eritrea 66 - 69 "Body of Secrets" James Bamford and "I Didn't Do it For You" Michela Wrong (Chapter 10)

      Demand Justice for the USS Liberty sailors.

      --
      photosMy Photostream
  135. Simpson 260 and Triplett 630 by the_rajah · · Score: 1

    I've still got one of those on my bench along with a Triplett 630, that was similar and, IMO, a little better meter. Of course, too, I'm a ham and still home-brew some tube type rigs and maintain some older radios like my Hammarlund HQ-129X and Collins 75A-2 receivers from the late 40's and early 50's.
    I've still got and use two rotary dial phones, a 500 series 2 line and a 302 from 1947 with the two line feature, too. One thing about the rotary dial phones is that they work during the occasional power outages when the powered cordless phones don't.
    In my day job, I still write and maintain a lot of assembly code that runs dedicated industrial controllers.
    I've given up on my buggy whip making, though.

    --


    "Do the Right Thing. It will gratify some people and astound the rest." - Mark Twain
    1. Re:Simpson 260 and Triplett 630 by TFGeditor · · Score: 1

      The only "period" equipment I still have is a 1950s-era capacitance decade box in a phenolic cabinet.

      And I troubleshot/fixed many a gadget and widget with a Simpson 260.

      Them was the days.

      --
      Ignorance is curable, stupid is forever.
  136. only CS courses at MIT were obsolete by peter303 · · Score: 1

    When I was a MIT student I took courses in LISP, Pl/I, using APL, OS-360. All these are obsolete. The mainstays like calculas, physics, analog and digital circuits, are still relevant.

  137. Really by Anonymous Coward · · Score: 0

    Not to quibble about semantics but most of the skills listed are obsolescent not obsolete.

  138. Java is NOT a scripting language by EgoWumpus · · Score: 1

    I realize a lot of people look down their nose at Java, but give it up! It's not a scripting language - it's a full fledged computer language and most people recognize that. The differences from C are minimal in terms of structure of the language - and if you're calling C a scripting language, well, then, there is nothing that can be done for you.

    Javascript is a scripting language, but it's relation to Java is superficial. JSP, ASP, CSS; all of these are scripting languages - but they are actually quite distinct from compiled programmed languages.

    --

    [Ego]out

    1. Re:Java is NOT a scripting language by Anonymous Coward · · Score: 0

      CSS is a scripting language now?

    2. Re:Java is NOT a scripting language by EgoWumpus · · Score: 1

      It's not too hard to call CSS a scripting language to control browsers. It's rather limited as far as scripting languages are concerned, but powerful within it's context.

      --

      [Ego]out

    3. Re:Java is NOT a scripting language by Richard+Steiner · · Score: 1

      I like Java, and I code in Java for a living (along wthi other languages), so slow down with the attack dogs! :-(

      It was a question intended to illustrate that "scripting" isn't enough of a boundary -- it's the nature of the projects themselves which determine the nature of the software developer, IMO, not the toolset being used.

      I've written some fairly complex stuff in Telemate's scripting language, for example. Once you get up to a few thousand lines, it ceases to be a trivial undertaking. Again IMO...

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
  139. note really skills by j_166 · · Score: 1

    "Scoble's initial list included dialing a rotary phone, using carbon paper to make copies, and changing the gas mixture on your car's carburetor"

    Those aren't really 'skills' though. Well, maybe changing the gas mixture on your car's carburetor is.

  140. here's mine... by CrazyTalk · · Score: 1

    Memory location for setting screen color for commodore 64: 53280. For changing the border, 53281. For some reason those numbers are burned in my brain from 25 years ago.

  141. Simplistic thinking in this list by amper · · Score: 4, Insightful

    What strikes me as astonishing about this topic, other than the fact that the majority of the discussion seems to revolve around the utility of assembly programming, is that the list itself displays a marked lack of understanding of the ongoing utility of low technology devices. For instance, one of the items listed is "Buttoning one's trouser fly". Perhaps the author of that idea has never heard of Levi's 501 Jeans? I submit that the 501's are some of the most popular trousers in the world, and the skill of buttoning them could hardly be considered obsolete. The rest of the list is rife with items that only the most technologically-blinded among us could possibly think of as obsolete.

    Even the summary contains a dubious suggestion, "Changing the gas mixture on your car's carburetor". Perhaps the author is unaware of the vast numbers of motorcycles and small engines sold each year that incorporate carburetors?

    "Cast lead bullets"? Thousands, if not millions, of ammunition reloaders would disagree.
    "Changing vacuum tubes"? Millions of musicians would disagree.
    "Darkroom photography skills"? "Developing photographic film"? Obviously, this person is not a photographer!

    That's as far as I can get without becoming even more disgusted with the state of humanity, or at least the supposedly tech-savvy people who probably are contributing to this list.

    1. Re:Simplistic thinking in this list by Skynyrd · · Score: 1

      I agree with much of what the parent is saying. I'd like to add "changing the gas mixture on your car's carburetor" to the list.

      Although cars have now switched to fuel injection, there are millions of people in this country who still drive older, carburated cars. There are still motorcycles, chain saws, lawn mowers, generators, and many, many other engine powered tools what have carburetors.

      Sure, the average guy won't be able to make changes to the air/fuel mix in his injected car, but the average guy didn't have the skills to adjust the carb anyway. It's always been a job for competent mechanics (whether they were professional, or just a guy in his driveway).

    2. Re:Simplistic thinking in this list by shiftless · · Score: 1

      Even the summary contains a dubious suggestion, "Changing the gas mixture on your car's carburetor". Perhaps the author is unaware of the vast numbers of motorcycles and small engines sold each year that incorporate carburetors?

      Not to mention the vast number of people in the first world building, working on, and driving old cars, drag racing (where carburetors are used almost exclusively), etc?

      What about other countries like China where automobiles with carburetors are abundant?

      There are arguably more carburetors in service today than there ever has been at any time in the past. Just because the author and all his friends drive late model fuel injected vehicles does not mean that tuning a carburetor is an obsolete skill.

    3. Re:Simplistic thinking in this list by instarx · · Score: 1

      What strikes me as astonishing about this topic, other than the fact that the majority of the discussion seems to revolve around the utility of assembly programming, is that the list itself displays a marked lack of understanding of the ongoing utility of low technology devices


      I have to agree with you. Many of the tasks listed as "obsolete" are incorrectly included simply because few people have to do them for themselves anymore. It is interesting to look at the list with an eye toward which of these "obsolete" skills would become critical knowledge once again with a simple lack of batteries.
  142. Testing Tubes by DynaSoar · · Score: 1

    My first job, 42 years ago, was testing vacuum tubes scavenged from TV's. We sold the new ones and hauled away the old as a favor. Any good tubes got saved and used in other sets that needed them (with a discount for being used). Now days you can hardly find a tube tester, though they used to be in drug stores, supermarkets, etc.

    Do I win the "old fart" award for this thread?

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B
  143. robots by enjahova · · Score: 1

    give me a break.

    Think of the quality of programs written in ONLY 1s and 0s. Every single bit would have to be accounted for!

    I mean, the barrier of entry would make it so that practically only ROBOTS could would be able to write code.

    Oh wait, thats right, we have compilers for higher level languages.

    --
    "how can they call it a MINE if everything here is THEIRS?!?!" -Straight Jacket
  144. the list has skills not technologies you nitwits! by DragonTHC · · Score: 1

    here's my top 5 obsolete skills.

    All taken from my father's job at Data General, which he retired from around 10 years ago.(Just after EMC raped DG)

    5. setting the Host ID on a SCSI controller.
    4. making custom serial terminal cables.
    3. aligning a r/w head on a magnetic tape drive with an oscilloscope.
    2. running hardware diagnostics.
    1. troublshooting a tokenring network.

    The only skill he now uses at his retirement job (walmart, which is required by law) is customer service.

    Granted, things were easier then when you had a terminal which just couldn't catch a virus.

    --
    They're using their grammar skills there.
  145. Building your own PC? by smchris · · Score: 1

    CPU magazine will be surprised.

    Knowing that a Radio Shack nibbling tool is perfect for cutting another slot in your 5-1/4" DS disks so you can use both sides in your Commodore. _That's_ obsolete.

  146. Five Whys by epine · · Score: 1
    Another slashdot story this morning has Joel commenting about binary Office formats. I read a little more while I was there, and came across this excellent post:

    http://www.joelonsoftware.com/items/2008/01/22.html

    Our link to Peer1 NY went down

    * Why? - Our switch appears to have put the port in a failed state

    * Why? - After some discussion with the Peer1 NOC, we speculate that it was quite possibly caused by an Ethernet speed / duplex mismatch

    * Why? - The switch interface was set to auto-negotiate instead of being manually configured

    * Why? - We were fully aware of problems like this, and have been for many years. But - we do not have a written standard and verification process for production switch configurations.

    * Why? - Documentation is often thought of as an aid for when the sysadmin isn't around or for other members of the operations team, whereas, it should really be thought of as a checklist. Apparently, *manually overriding* all this automatic shit (that makes our manual skills obsolete) hasn't died yet.

    Skill not destined to die any time soon: credit repair.

    Useful when: your crap-ass Wifi is breached

    Reason: the skill of hardening wireless consumer convenience-toys is receiving a long course of immunotherapy at a clinic in Cuba, after years of dissolute, party-hard lifestyle
  147. One man's obsolete... by FeebleOldMan · · Score: 1

    "Cast lead bullets"? Thousands, if not millions, of ammunition reloaders would disagree. "Changing vacuum tubes"? Millions of musicians would disagree. "Darkroom photography skills"? "Developing photographic film"? Obviously, this person is not a photographer! ...is another man's absolut.
  148. So Predictable by ponraul · · Score: 1

    I looked at the fine list before I read the comments. As soon I saw assembly programming, I knew there were going to be a GigaSlashbots opining indignantly and at length and with links and citations that the list is clearly wrong---my god. The question remains: how does such an awful cross-section of humanity come to congregate together? The only comparable scenario that comes to mind is the brotherhood of Islamic suicide bombers. Slashboters hate anything that calls into question their technical machismo; suicide bombers, the Jews.

  149. I'm so totally obsolete... by Fuzzzy · · Score: 1

    A. I'm still using rotary phone.
    B. In my previous job, I wrote in assembly.
    C. I'm still missing the BASIC of my good old BBC...
    Ok, I'll crawl back into my cave.

  150. Double de-clutching is alive and well by lisnter · · Score: 1

    Double de-clutching, or just double-clutching or rev-matching, is no longer necessary but is still a useful skill when driving at a track or autocross. The point of double-clutching is to make the transition from gear-to-gear smooth so as not to upset the suspension during a downshift. If the suspension is fully loaded then the abrupt weight transfer forward if double-clutching is not used can cause the car to slide or otherwise take a corner incorrectly. This is not something most people worry about, granted, but it is by no means obsolete. Some automated manual gearboxes (Ferrari, Mitsubishi Evo X, etc.) do this rev-matching so well and so quickly the driver almost doesn't notice.

    1. Re:Double de-clutching is alive and well by kc2keo · · Score: 1

      I agree with you... When I drive my 5-speed manual car I always double de-clutch the car mainly to not put lots of stress on the gear box and to get a smoother gear change. It also saves the syncro mesh. Not only that I enjoy double de-clutching. Some people worry that the clutch will wear out more if you do that but I understand that it does not. Sure, your cars take off can be slower when you do this but I think the advantages outweigh your extra take off. I never really understood why everybody has to be in such a rush all the time. Why not leave early then you won't be in a rush. Sometimes thats how people are though. I live in New York so that could be another reason... always in a rush :-P

  151. Couldn't Disagree More by severoon · · Score: 1

    Assembly is what the computer runs. If you don't know the fundamentals of how a machine works, how can you claim to be a developer?

    I'm troubled by the tendency of most computer science programs in the US moving away from assembly as a requirement. I'm also troubled by the awful job most universities do teaching object-oriented programming and design, and the complete and total lack of architecture and tools skills required at the college level. When I graduated, it was a rude shock to discover on my first job as a software developer that very little of what we do is write code—it's nearly the shortest part of the development process. I was also not happy to find out that, at the higher levels, very little attention is paid to languages and most successful projects focus on good design that can be implemented in any language.

    --
    but have you considered the following argument: shut up.
    1. Re:Couldn't Disagree More by Lazerf4rt · · Score: 1

      I agree with you. Understanding assembler is the difference between shipping a stable product, and not shipping it. It takes an academic to call it an obsolete skill. Academics don't have to ship anything.

  152. Re:Who says assembler is not used for applications by Dwedit · · Score: 1
    I've actually found that C++ itself can be quite lean, as long as:
    • You never ever use iostreams, which includes a lot of "locale" baggage and other junk
    • You don't instantiate global or static instances of a class.
    • You use a leaner C or C++ library
    • Don't use exceptions or run-time type identification

    In a static linked program, I've seen the linker add as little as 8k of library code to a C++ program. So from there, it's up to the programmer to write efficient C++ code instead of watching the linker adding 500k of unused crap onto your program.
  153. Assembly language vs. Web 2.0 culture by heroine · · Score: 1

    Definitely 2 parallel universes here: the assembly language culture of making things talk to hardware & the Web 2.0 culture of slapping together Java.

    Have found assembly language more useful than it was 7 years ago because of the rising usefulness of robotics & the need to interface the physical world. Most of the jobs of course, don't deal with the physical world & aren't that useful either.

  154. Re:Who says assembler is not used for applications by Panaqqa · · Score: 1

    Very true, I'll concede that. One can always have gcc output the assembler code also (-S) and the assembler can then be played with and further shrunk. No matter the tool used, if someone is well aware of how their use of the development environment impacts the actual code produced, then huge bloated aplications can be avoided. I guess part of my comment stems from frustration with so-called "developers" who practically cannot write a single line of code. Without their IDE they are helpless. It is the ubiquity of this type of Microsoft certified bloat builder that might very well lead someone to conclude that assembler is dead or dying.

  155. Re:It's not obsolete,here's why:Revolution's not h by Fjandr · · Score: 1

    Not to mention knapping flint, building fires with friction or flint and steel, or casting lead bullets. :)

  156. and good riddance. by Mike+Buddha · · Score: 1

    Morse code

    --
    by Mike Buddha -- Someday the mountain might get him, but the law never will.
  157. Entire list is bunk by DigitalCrackPipe · · Score: 1

    This entire list is bunk. Look at some of the skills that are not obsolete (like the assembly discussion above, using a compass, map reading, writing a check, spelling, etc). The editorial action on that list is apparently MIA. They do list some of the skills as "not completely obsolete", but a huge number of skill don't belong on that list at all. Just because the authors don't possess that skill (or the basic ability to understand when it would be used) doesn't mean it's not very relevant to society today. The skills just may not be practiced as broadly as they once were.
    Perhaps the site author thinks the skill to look up the meaning of the word obsolete is obsolete?

  158. Using DEBUG to Start a Low-Level Format "g=c800:5" by Pinback · · Score: 2, Interesting

    Using a chip puller.
    Cutting write enable notches in 5.25" floppies.
    Drilling write enable holes in read only 3.5" floppies.
    Replacing worn out switches in Amiga mice.
    Building custom serial cables.
    Re-ordering items in config.sys to optimize the amount of RAM free.
    Monochrome VGA, with 704k free.
    Watching terminal output to figure out serial speed, bits, parity, and stop bits.
    Disabling screen I/O while using punter, to get that extra 5% of throughput.
    Avoiding the zero subnet.
    Working with non-CIDR subnet masks, or masks with zeros in them.
    PC-NFS.
    Deleting enough files on RSX, so that there was contiguous space to put system files on.
    PIP on CP/M. Hiding files using a programmer number.
    Generating Novell remote program loader files using diskettes.
    EMS vs XMS debates. The Intel Above Board.
    Locking up Hayes 1200B modems by hitting backspace.
    Ripterm. Ymodem-G. QWK mailers. Whistling the modem tone to see if a modem was calling you.
    Intentionally misspelling things on a BBS to avoid the profanity filter. (Warez, pron, fcuk, leet, a$$, sh1t, etc.)
    Using high speed cassette copiers. Using Chrome tape.
    Connecting daisychained peripherals. Connecting separate analog and control busses on hard drives.
    Figuring out which drives were RLL capable.
    GCM vs GCR.
    Backing up data to VHS. Cofiguring multiport serial boards.
    Fossil drivers.
    The 5.25" hard disk.

  159. I live in the land of the obsolete...happily! by MindPrison · · Score: 1

    This may seem strange to you...but... ...I live in the land of the obsolete. My entire personal workshop is filled with 80's electronics, heh..I didn't even "save" the stuff from wayback then...I just love it for the coolness factor it has to ME - not to others. It may be obsolete...heck ...I know that my commodore-64 Assembly programming skills (ha! Skills!) are obsolete by now...but I WAS the first to get rid of the Commodore-64 BORDER - entirely, so what? No one knows my name - nobody cares and nobody ever gives a sh*t about it, what they do care about though...is what they have experienced in their own life. Good times man, enjoy it if you can and want to!

    My lab? My heaps and boundless amount of 80's electronic components? It's my life man - calling that obsolete would be to dig me 10 feet under and say goodbye. To me these things still matter, I still play with my radio-amateur stuff, I still build radios from scratch in my spare time - and build COMPUTERS from scratch...nooooo I don't refer to putting a bunch of cards inside a cabinet with a motherboard..I am refering to actually CONSTRUCTING a computer FROM SCRATCH....yes...schematics ....to the actual finish PCB! There is NO fun like it in the entire world - it may not get me laid - but it sure as h... entertain my sorry 80's carcass throughout my life,

    Whats obsolete about knowledge? Did you catch my drift? A old Hippie, am I? Well... I can tell you that I work in one of this countrys most successful businesses, why? Because I survive on my basic understanding of how it all started - the now "perhaps to you" obsolete knowledge is what FOUNDS all BASICS of EVERYTHING that is CREATED TODAY.

    Did you catch that?

    Well...I did! And there's no regrets about it.

    --
    What this world is coming to - is for you and me to decide.
  160. Hey!!! by NUBlackshirts · · Score: 1

    I, for one, can still tune a carburetor. Working on cars keeps me sane and calms my desire to kill users.

  161. Keypunch machine. by BitterOak · · Score: 1

    It took me a while to find keypunch machines, as they were alphabetized under "Operating". When I was in high school, girls were strongly encouraged to take a course in operating keypunch machines. The idea was even if your academic gifts let you aspire to be more than a keypunch operator, you would never, ever, EVER have to worry about being unemployed if you could operate a keypunch machine.

    And speaking of obsolete skills, how many remember what POKE 59468,14 does? Hint, it's NOT for the Commodore 64.

    --
    If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
  162. long time to reply... by gearloos · · Score: 1

    Sorry it took so long to reply, I was coding my reply on punchcards... But when I went to back it up I had to change out the Winchester Drive.. At least the core memory is still ok.

    --
    "Computers are a lot like Air Conditioners" "They both work great until you start opening Windows"
  163. get that list a wiki by PMuse · · Score: 1
    Oh, come on! To butcher Robin Williams, "That list is in more dire need of a [moderator] than any white man in history." Not only is it full of dupes and near-dupes, but it's overwhelmed by niche skills that less than 1 person in 1000 ever knew (in the general population, that is, not /. population).

    What shows us how fast the world is changing are the skills that, within living memory, lots of people had (e.g., 1 person/ several households or so) but that will have disappeared within our lifetimes. Sorted by device (as much as possible) these include:
    • Abacus
    • Arithmetic, reckoning without aid
    • Camera, focusing/ setting exposure on a
    • Camera, loading/unloading film into a
    • Card catalog, searching
    • Check, writing a
    • Fax machine
    • Fire, starting without matches, etc. a
    • Handwriting
    • Horses/ oxen, harnessing and/or riding
    • Knitting/ darning
    • Letter, writing and sending a physical
    • Machines/ appliances, fixing household
    • Meat, salting to preserve
    • Navigating by the stars
    • Needle, threading a
    • Nib pens, filling/ using/
    • Refrigerator, defrosting a
    • Sewing
    • Shoes, resoling / reheeling
    • Shorthand
    • Slide rule
    • Spelling
    • Straight razor, shaving with a
    • Telephone, calling collect on
    • Telephone, remembering numbers for a
    • Vegetables/ fruits, canning
    • Yellow pages, looking up a business in

    --
    "We reject as false the choice between our safety and our ideals." --The American President (20.1.2009)
  164. Re:Tap water by Anonymous Coward · · Score: 0

    I guess you either don't count the absence of giardia cysts as a feature or I really don't want to drink the water at your house.

  165. Installing IRIX... by milatchi · · Score: 0

    Installing IRIX, that's my obsolete technical skill.

    --
    Slashdot = -1 Redundant, Asperger, kdawson FUD, Libertarian, and Linux
  166. Unlocking CPU by connecting traces with graphite by Anonymous Coward · · Score: 0

    Remember unlocking CPU multipliers by connecting the dots with graphite?

  167. I don't think some of them will be. by Neanderthal+Ninny · · Score: 1

    If your TV remote dies then you will need to get up off the couch to change channels or adjust the volume on the TV.
    I don't know about not booting to floppy to update some BIOS on some new systems.
    Using a rotary phone will stop any cracker/hacker from logging your keys.
    I think for most people Calligraphy is art rather than mean of communications.
    Well for Double De-clutching I still have to do that with my 1981 Honda Accord with an 5 speed manual but the syncro between the 1 & 2 gears are worn out so occasionally I have to double de-clutching to get into and out of 1 & 2 gear. I use this lovely car to commuting to the train station and leave there and no one touches it. Even they did (they should be in a insane asylum) they would discover the 1 & 2 gear problem. Eventually I'm going to get rid of this car soon and I'll forget this.

  168. Keying in the bootloader. by chris_sawtell · · Score: 1
    Keying in the papertape bootloader using the 16 switches.

    That must be an obsolete skill because the spellchecker doesn't even know about papertape or a bootloader.

  169. Trebuchet construction by KORfan · · Score: 1

    I can't believe this hasn't been mentioned yet.

  170. Last assembly game was RollerCoaster Tycoon by SageMadHatter · · Score: 1
  171. Wii have seen the revolution by tepples · · Score: 1

    The only thing is when the revolution comes that slashdot's always going on about. The revolution came in November 2006. Or are you talking about the r3VO_|ution?
  172. Using English correctly is important by rabiddeity · · Score: 1

    I don't know if English is your first language, but whether you like it or not people will judge your writing by its spelling and grammar. When you use them properly it shows that you've read your post before hitting submit and that you pay attention to details. One typo is generally excusable; everyone makes mistakes. On the other hand, multiple errors in capitalization, punctuation, and spelling make you look ignorant, regardless of the content of your post. Syntax mistakes also make your post confusing and difficult to read. At the worst it can change the meaning of your post. "Threw out" and "throughout" mean two completely different things.

    You might make good points, but if you don't show enough respect to proofread your own posts then many people will simply not take the time to decipher them. If you don't take your own writing seriously, why should I read what you wrote? This is the Internet, and the only thing we have to judge you by are your words. Make them good.

    1. Re:Using English correctly is important by jellomizer · · Score: 1

      Except for the fact that this is Slashdot. Most of the posts are done durring a few minute break I have to take my mind off what ever I am working on. On slow days I have time to come out with a more thoughful and organized thought and other times I just have less then a minute to get my point across. And due to the way slashdot is setup If you take 20 minutes to write a responce you will already be in the no-mans-land of comments where no one bothers reading them any more. The way the site is designed you need to write fast and it is more important then writting well. The difference between an insightful comment and a redundent comment is often in matter of minutes sometimes seconds. In real life for my work I put more time (But it usually takes me an hour to write a full page paper), I am diagnoes with writting disabilites. So writting is difficult for me.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  173. Beware of Flaming Ego by bill_mcgonigle · · Score: 1

    Even the summary contains a dubious suggestion, "Changing the gas mixture on your car's carburetor". Perhaps the author is unaware of the vast numbers of motorcycles and small engines sold each year that incorporate carburetors?

    My guess: he hires other people to do his real work for him, and dismisses the value of their labor to make himself feel superior.

    No joke - I spent over $300 at various small engine repair shops trying to get a lawn tractor working right, and finally gave up, went to Google, got out the toolset, and finessed the carb screws until the engine purred. Here's a skill that should be obsolete: hiring out jobs you should know how to do yourself in the first place!

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  174. Volume Control Knobs by jdschulteis · · Score: 1

    Here are excerpts from my old obsolete articles mentioned above, starting with Useful Dead Technologies:

    Volume control knobs
    You're driving down the road and that song comes on. You know the one, it really rocks and you must crank that sucker up.

    But there's no crank any more. You have to take your eyes off of the road to find the one button on the fifty buttons to turn the damned thing up or down. Thank God they invented cell phones so you can call an ambulance after you wreck your car trying to turn the volume down to answer your cell phone!
    It happened to me on the way home yesterday (Boston's "Smokin'"). Fortunately, my car ('07 Accord) has a big round knob smack in the middle of the dash--grab, twist, and there's no way I'll hear the cell phone. Someone at least is still paying attention to human interface design.
  175. I got one by vuffi_raa · · Score: 1

    running a mimeograph machine- when I was in elementary school in the pre-everyone has a copier days we had to run all of our school flyers and handouts on a giant mimeograph machine- I helped out because it was really fun to run the big noisy monster when you are a 7 year old kid- plus that is how I put out my 7 year old kid's 'zine when people weren't looking- mostly poorly written movie reviews and little comics I made of animals in tanks fighting robots all of the time.

  176. Re:Volume Control Knobs by sm62704 · · Score: 1

    Yes, my newer car not only has a big knob for volume too, and better yet it has controls on the steering wheel as well.

    Those new cars with the voice activated stuff wouldn't work for me, because unless I've got passengers I have the stereo turned up way to loud for voice activation to work. Plus, my last cell phone had voice dial, but in the car doing over 50 mph (when it would do the most good) it wouldn't work even with the stereo shut off. In fact any extraneous noise or sound got in its way.

    Also I can see driving along:
    Stereo: "But in the darkest depths of Mordor I met a girl so fair. But Gollum and the..."
    Me (almost getting run off the road by an idiot in a SUV): SHIT!!!!
    (Stereo switches to Britney Spears song)

    --
    mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
  177. Obsolete Skills by danielpauldavis · · Score: 1

    Balancing pennies on a phonograph needle so the vinyl record doesn't skip. Keeping track of the song list as the 8-track changes tracks. Getting to the unemployment office early enough to not be there all day. Navigating library cards to find the information one needs to write one's paper.

    --
    Cranky educator.
  178. So basically - by Geminii · · Score: 1

    Anything computer-related more than five years old, half the stuff your parents learned that your grandparents didn't, and anything they teach in the SCA.