I used ed for the startup-sequence.
We've all done that at some point :lol: Ced is nice for stuff like that. Solid and fast (but a little on the basic side).
I don't even remember which editor I used in the old days when I did a lot of in assembly. Really a lot. I looked at seka, and had to p*ke about its user interface (or lack thereof) and decided against this primitive beast (a good decision), then used the Databecker "Profimat", which had a somewhat useful IDE, though a pretty limited assembler (not a good decision). Luckely, decided against the GFA assembler (I also used GFA Basic quite a bit, fast but buggy) and bought DevPac (2.0 back then), never regretted it, it was a decent choice. I believe I used the DevPac editor for quite a while, still a good thing. Then with Lattice C, I believe it was LSE, which had a couple of bugs, but still worked quite ok. Then came GoldEd, SAS/C and DevPac 3.0, again good investments. I guess I was never a particular fan of CED, but I already had good editors for what I needed. GED I used for almost everything, C, Assembler, PasTeX. Except for the Startup-Sequence. That was still in the hands of "Ed" because GED was a bit too bulky.
Back in the day I used to do everything in AsmOne. Now I do everything in FrexxEd, with Barfly for assembly language and SASC for C.
Sometimes you don't get to choose, and there are overriding constraints which spell out in so many words why we can't always have nice things.
Yes, but not when you're developing your own software from scratch.
Being a programmer can suck.
Yes, but not when you're doing it on a hobby basis. Then you get to do whatever you want in whatever way you want. You simply need the discipline to actually finish the project, or get it into a state where it can be released and used properly (after that you can keep working on it to make it better, but at least you already have something decent).
I think that Lua's a decent enough design, which is both powerful, well-documented and something newcomers can learn and apply. It's also embeddable with a small memory footprint. I once came close to using it in one of my applications, but then time constraints made me - wait for it - knock off one of those Lisp-like language interpreters instead (the fate of the world didn't exactly depend upon it, and if it did I didn't notice, but sometimes you just want to finish a project and not keep on tinkering).
What kind of time constraints cause you to have to make concessions like that?
As for using a 'C'-like language for the purpose of scripting, I can see the attraction for programmers who are already familiar with the language. For everybody else it's a long and ardous journey to even become competent in using the language, so I wouldn't want to force it upon anybody.
True, but it's still great for programmers editors because so many programmers know C. For something that's not related to programming I'd pick something else, too.