I love what you do, man! if it's not just the content itself, it's the topics. I always find myself looking up articles, cloning repos to learn more about things. thanks for everything!
For those that aren’t aware, before we had screens to look at, computers would output text by physically printing ink to paper. This is where “teletype” comes from. So, with this in mind, Ed makes a lot of sense for what it’s doing. And naturally, when we got our nice monitors Vi (what becomes vim/neovim) it becomes a natural progression.
7:45 can you imagine, i just today realized they did it like that, prompted by a long thinky about teletypes. i was thinking like "well, they at least wouldve had printed listings and such", but then it hit
Remember also that initial UNIX prototypes were written mainly in assembly, in which case programming assembly using ed is really easy to grok (or at least I do), whereas more structured languages are actually hard to be used in ed. Also a reason why they went to create more visual editors like ex or vi once C became the primary system interface to program UNIX in.
40:02 tsosing describing my mindset when quiting from AI for a bit to program a compiler with just the C standard lib. of course after I did that I did the 0 skill move of writing an extension in C++
Ed kind of reminds me of the C64 interface. It's so barebones and simple, yet does everything you need. The first interpreter I wrote was for BASIC and used a similar interface. Some parts of my high school experience didn't suck, I suppose. As for compile time versus runtime, I'd argue that compile time just means what gets done before your program enters runtime.
The minimal output makes so much more sense when you think about the computer doing all it's output through a printer.
Just uninstalled neovim. Let's go
I love what you do, man! if it's not just the content itself, it's the topics. I always find myself looking up articles, cloning repos to learn more about things. thanks for everything!
For those that aren’t aware, before we had screens to look at, computers would output text by physically printing ink to paper. This is where “teletype” comes from.
So, with this in mind, Ed makes a lot of sense for what it’s doing.
And naturally, when we got our nice monitors Vi (what becomes vim/neovim) it becomes a natural progression.
Ken Thompson developed both *Ed* and *Go*
And also UTF-8
So it was that man's fault all along...
And B
And the first regex processor
both poorly designed, but still a legend,
7:45 can you imagine, i just today realized they did it like that, prompted by a long thinky about teletypes. i was thinking like "well, they at least wouldve had printed listings and such", but then it hit
Remember also that initial UNIX prototypes were written mainly in assembly, in which case programming assembly using ed is really easy to grok (or at least I do), whereas more structured languages are actually hard to be used in ed. Also a reason why they went to create more visual editors like ex or vi once C became the primary system interface to program UNIX in.
You don't need DB. Just use Excel
You don't need Excel, just use text file.
We have that it's called csv@@Dr-Zed
Excel is a DB
@@Dr-Zed You don't need a text file, just use pen and paper.
@@spacey6960 You dont need pen and paper. Just memorise the data
Can your VIM do that!!!
Yes ackchualli
Yes, sure, just type asdfghjklqwertyuiopligmaballszxcvbnmqwertyuiopasdfghjklzxcvbnm!
I clicked on the video expecting ed. Was not disappointed.
1:17:41 can we all just appreciate how smooth that transition was🤯
Title should be 'Your own text editor, except everyone in the world can see it' 😂
This was such a fun stream!
we're gonna be running it in production
Super instructive thank you for sharing
Vim users wouldn't exist without ED.
40:02 tsosing describing my mindset when quiting from AI for a bit to program a compiler with just the C standard lib.
of course after I did that I did the 0 skill move of writing an extension in C++
Ed kind of reminds me of the C64 interface. It's so barebones and simple, yet does everything you need. The first interpreter I wrote was for BASIC and used a similar interface. Some parts of my high school experience didn't suck, I suppose. As for compile time versus runtime, I'd argue that compile time just means what gets done before your program enters runtime.
Great video. Keep up with the good work.
Would be cool if you did some assembly again like you did with raylib
Привет друг из Новосиба
1:13:00 1,2d would delete two lines
It would be fun if everybody had their own cursor but could work on a common file.
i want to know the story of creating 'ed' without something like 'ed'
wait
notepad of course
if you go all the way back, you will use punched cards
@@moussaadem7933 don't go that backward. Should be something in between))
great session
Explaining how a bot works to the bots.
ah phew a different kind of chatbot!
37:30 we know where
Ed, Edd, Eddy
Ed, man! !man ed
Hype-oriented programmers ;)
Great ❤❤❤
Only you can pull such a joke 27:25
we should have a nahui mode
Thank you....
Why does everyone have so much hatred towards Neovim?
Because we have better tools, like MrBotka Ed
@peterhebden1557 I don't argue that Ed is the best, but Vim and Neovim are also good
Try haxe
boss,. please more go
No chat bot mam
1:21:17 bro literally had strings in switch cases in the bot source code 🤦🏿
lol
!ed nahuy before anyone else gets to it 500 times
sam ed
9:55 too late
@@Kokurorokuko nope i posted this before the stream
My man why the hate on neovim?
The OP equally hates all the editors, don't take it too personally
He doesn’t unless you neovim users keep convincing him
Because Zozin is an Emacs user
Emacs better
hes GNU servant
hmmmm