| ▲ | bottlepalm 3 hours ago |
| You know what, that is some pretty readable code.. COBOL might have been on to something there. I've gotten so used to syntax soup this is refreshing. https://github.com/icitry/FPS.cob/blob/main/fps.cob |
|
| ▲ | ternaryoperator 30 minutes ago | parent | next [-] |
| That readability is the upside of COBOL’s oft-assailed verbosity. |
|
| ▲ | giraffe_lady 3 hours ago | parent | prev [-] |
| I had to get into an old tcl program for work recently and had the same thought. I wouldn't necessarily pick it today but it was kind of nice in a way that's unfamiliar to me from modern development. |
| |
| ▲ | moregrist 2 hours ago | parent [-] | | The tcl syntax is fine. And modern tcl is fine. But tcl 7.x and before was a pure string-based language. Everything was essentially a eval(). People would hit syntax errors on production code. Fun, painful times. The flip side: the interpreter is super simple and fun to write. | | |
| ▲ | IshKebab 2 hours ago | parent [-] | | Tcl is still entirely stringly typed. That's never changed. There are under-the-hood optimisations to make it less insanely slow but that only affects performance. Tcl is a cool hack (the interpret is simple to write) but it's insane to actually use it. I wish the EDA industry would realise that. |
|
|