Live data from Hacker News

Show HN: Desed – Debugger for Sed

github.com

21–23 of 23 posts

Re: Show HN: Desed – Debugger for Sed

#21
post #8

Earlier quoted context omitted.

OK thanks, that's helpful! It looks like a lot of the newer terminal rendering library use "diff" style of rendering like web frameworks, rather than something more stateful like curses? Is that why you thought it would be easier? You just update the entire page on every action, and it takes care of the details of coming up with the minimal terminal codes? ---- This is only tangentially related, but for those interes…

Yes, my priority was making the UI done as fast as possible, as I wanted to focus on making the debugger and didn't want to think too much about UI. I looked at some examples of both of them and decided that tui-rs looks easier to use, it takes care of everything for me. Note that I might be wrong, I didn't spend even half an hour looking at the frameworks. Another reason, albeit really small, was that tui-rs was wri…

Yes that makes sense... I think I used curses once like 10+ years ago, and other than that haven't done any TUI programming.

So I'm interested in what people are using now, and it seems like there are some nice new libraries.

Re: Show HN: Desed – Debugger for Sed

#22
post #20
post #16

Earlier quoted context omitted.

COBOL was written in the 60s and has been in mission critical stuff for decades. Neither of those factors means it's the right tool for the job now . The things I'm recommending that are more mature are Go, Python, D, Rust, or any other language that is more verbose and maintainable than regular expressions. Anything with a full debugger, IDE support, and useful error messages is a better choice.

Except COBOL often is the right answer for text processing now , meets all your criteria (debugger, IDE, maintainable, etc) and far more mature than Go, Python, Rust or D (really...D?).

COBOL is the wrong tool for any new job now because hardly anyone knows it.

Re: Show HN: Desed – Debugger for Sed

#23
post #22
post #20

Earlier quoted context omitted.

Except COBOL often is the right answer for text processing now , meets all your criteria (debugger, IDE, maintainable, etc) and far more mature than Go, Python, Rust or D (really...D?).

COBOL is the wrong tool for any new job now because hardly anyone knows it.

Which could be said about any newly fashionable language. Or any niche language. And in the case of COBOL, it's not even true. Here's a little hint: just because you don't know any COBOL programmers, doesn't mean they don't exist. My own company has a couple of hundred, and we have an outsourcing partner that has a several thousand. We are not unique.
Post reply on HN