You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Surely there are young programmers that still code using assembly? Or am I dreaming?
Hear, Hear! And don't forget Java. Auto heap management has a dark side; I tried to get a Java programmer to understand embedded development once. It was ugly.Yes, but it's a much higher tier than the rudimentary PHP/Python/Ruby crowd you find today. Smarter toolchains and lower marginal cost for performance and memory footprint have lent themselves to systems that don't need the hand-built optimization used in the past. Those skills are only learned when you have to deal with them.
(And then there's the matter of which processors your assembly is targeted at... can you do creative things with only 20 basic opcodes, 2 8-bit accumulators and 2 index registers, or do you need to have the whole orchestra that x86 provides today?)
Newer - especially self-taught - programmers who haven't gone through CS courses that teach the underlying details should all spend some time with assembly. They should also have to gain some programming experience in some type of real-mode code without interrupts running. My opinion, of course.
Surely there are young programmers that still code using assembly? Or am I dreaming?
Hear, Hear! And don't forget Java. Auto heap management has a dark side; I tried to get a Java programmer to understand embedded development once. It was ugly.
Surely there are young programmers that still code using assembly? Or am I dreaming?
Based on this article (from nasa.gov) and common sense (given when the probes were launched), these were purpose-built CPUs -- Z80 & M68000 experience might be helpful as far as getting started and oriented is concerned, but you'd probably have to unlearn some things as well...It depends on the processor, but anyone who knows assembly on one old processor can usually pick up another. Other than the FORTRAN, it sounds like they need an experienced embedded programmer. I've worked on a number of systems like that over the years.
Based on this article (from nasa.gov) and common sense (given when the probes were launched), these were purpose-built CPUs -- Z80 & M68000 experience might be helpful as far as getting started and oriented is concerned, but you'd probably have to unlearn some things as well...
http://history.nasa.gov/computers/Ch6-2.html
Sounds like fun!
You are all so young. I am 71 and started with computers in 68, as a student in engeneering physics. I touched a computer and I never stopped. I worked with mainframes then moved to micro computers. All of them, from Cromemco to IBM, CP/M to windows 10.
It depends on the processor, but anyone who knows assembly on one old processor can usually pick up another.
Hey, those weren't flaws, they were seams! I still have mine.Anyone own a Mac Cube G4 (circa 2000)?
I admit that I wanted one, despite the lack of expansion options and flaws in the clear plastic enclosure. The high price made it impossible for me to justify the purchase.
Reading an article in IEEE Spectrum about he intel 4004. Would love to get my hands on one of those.
I remember in high school we had a couple of Apple ][ or was it ][e computers with 5.25" floppy drives. Back then pirating was rampant with sneakernet. In order to copy your games faster, you would hook up both floppy drives to the same computer. Easy enough, right? Crack open the case by grabbing a hold of the rear and pull up, disconnect drive from the headers and repeat on other computer but put the header back in.
Come time to fire up the computer, smoke emits from the computer. Turns out it wasn't idiot proof with the surrounding guides on motherboards these days. I had inadvertently missed a row of pins. Let's just say the other computer didn't have a floppy drive for the remainder of the year and they never did catch the culprit!
Another time I went to the local computer store to upgrade my processor. Back then they didn't have ZIF sockets so you had to use some kind of chip extractor or something pry the processor out gently. As I was friendly with the owner of the store, he allowed me to do the work myself. Big mistake. I ended up snapping the processor and still had to pay out of pocket.