grewsome

5 ms·

1.
by grewsome 1y ago
I've read previously that certain parts of the software industry at one point was all in on move fast and break things, but then after a while the quality of their code was so bad that they took a different course. Maybe some people di
2.
by grewsome 1y ago
Sometimes the last 10% takes 90% of the time. It'll be interesting to see how this pans out, and whether it will eventually get to something that could be considered a solved problem. I'm not so sure they'll get there. If the
3.
by grewsome 1y ago
Tcl doesn't have fewer features, it packs in a lot, probably because of its maturity, to a similar level as other mature scripting languages (OO, coroutines, event loop, slave interps, etc, etc). But it's poor when you want someth
4.
by grewsome 1y ago
Tcl is a real programming language, but it depends on what you are doing with it. There are a lot of people who have never come into contact with command languages, and so there are plenty that look at it and have a negative response. For a
5.
by grewsome 1y ago
Tcl does appear to be a command language done right, I don't think there is a better one. As it was designed after bash etc, I guess the Tcl developers could see the inconsistencies there, which helped them do Tcl right.
6.
by grewsome 1y ago
For incorporating into Tcl I'd prefer something simpler that would also work with existing procs. Building on {*}, maybe {@} could work (to skip over arguments to a specified argument}. e.g. when calling a function: someFunc someVal an