Views : 457,793
Genre: Education
Date of upload: Jan 1, 2024 ^^
Rating : 4.966 (126/14,741 LTDR)
RYD date created : 2024-05-16T13:04:24.28592Z
See in json
Top Comments of this video!! :3
When I worked at AT&T in the 80's, I went to the Murray Hill Bell Labs facility for a day-long conference. At lunch, my wife (who was also an employee), one of my co-workers, Martin, and I decided to wander around looking for "famous people". We wandered into the lab in area 11 where Unix was born, and Dennis Ritchie was sitting at terminal typing. We told him we were there to see "famous people". He laughed and asked if we wanted to see the first Unix bug. When we said yes, he held up a glass jar containing a dead cockroach.
218 |
Correction: 'ex' was not WYSIWYG, but a line editor always displaying only the line currently edited in a file, just like 'ed' on which it was based.
Billy Joy then used 'ex' as a base for his first 'vi' editor with 'vi' derived from 'visual' standing for the at that time pretty revolutionary new 'visual' mode that by using terminal commands let the user navigate through a text file on screen as we know it today.
'vim' came much later and isn't even based on the original 'vi' source code (according to Wikipedia its forefather was a vi clone called 'stevie').
94 |
As a fledging EE in 1974, I was fortunate to join Digital in Maynard where I worked with the PDP-11 team. I enjoyed the vintage photos of the hardware and of some of my colleagues that I enjoyed working with. I left Digital to become a software engineer in 1982, joining a Pittsburgh startup called "3 Rivers Computer Corporation". Our hardware was an innovative workstation called the PeRQ. Gordon Bell joined us briefly after leaving Digital.
One of our major projects at 3RCC, done under contract in Edinburgh for ICL (a major UK supplier at the time), was a port of Unix using "C-Codes". Our hardware was a bytecode machine (very fast for its day) and we developed a bytecode interpreter for C. We used a portable assembler to generate C-Codes from standard C. That let us run Unix on our hardware.
This piece reminded me how much fun we had in the early years of the workstation world.
7 |
Good work so far. I have one disagreement. Take macOS, still a Unix (and OpenSource since its beginning) certified system, being the successor to NextStep. And all other Apple OSes (iOS; iPad, WatchOS, tvOS and soon VisionOS) also share the same fundamentals, kernel and framework. Also, though seen as different, Linux is, on purpose, a close open source variant. Let's not argue about the variation of kernels... What I'm saying is that all the concepts of Unix are still widely present in all those Operating Systems. Unix has not fallen at all, it is the dominating philosophy of all modern operating systems. Windows is extremely marginal in fact, as all the operating systems I mentioned are present in many more devices than PCs. Think mobiles phones, access points, switches, routers, IoT, cars, etc.... Unix variants are really dominating.
105 |
When I was in the navy all of the weapons and sonar systems ran on some flavor of Unix or Linux. Windows was just for email. This is still true today because of the flexibility it offers. In fact I'd say that the US military is probably the largest user of unix/Linux. It's not going away any time soon
98 |
This video helps me understand some things that happened in the software world while I was otherwise occupied working in OS/360, VMS, MS-DOS, Windows 95, and Windows NT environments. I hope there will be a next video, or maybe it's two videos, about the proprietary Unix wars and the subsequent rise of open source and Linux. One of the most fascinating things to hear in this video was that the Bell Labs inclination toward open source was the result of an antitrust action taken by government.
71 |
@Arivia1
4 months ago
"Vim, a text editor, that some people like" this is the kind of diplomatic phrase that starts world wars. Wonderfully stated.
1.8K |