3 ms·

Sounds like your use case is perfectly tailored for Tcl. Runs everywhere, simple for the simple stuff, scales well to moderately complex tasks, integrates well

Sounds like your use case is perfectly tailored for Tcl. Runs everywhere, simple for the simple stuff, scales well to moderately complex tasks, integrates well with C, can write a web server in a dozen lines, made for embedding.

bigiain 8y ago
The only thing I'd suggest missing out for TCL is the implied requirements in the "work" and "masters degree" comments - that at least some of this code is probably going to need to be shared and used/understood with others. For that reason alone I'd say Python is likely to be a significantly better choice. (If I'm interpreting the implications correctly) I've got experience with trying to find people who can work in Groovy on Grails projects - it's not easy. That's not a great reason to stick to "mainstream languages", but I won't be making the Groovy mistake again any time soon... And while TCL is definitely _capable_ of replacing Groovy, it is the wrong choice for me that same way that Groovy was...
- auto 8y ago
  I definitely see how that could be inferred, but here it actually isn't the case. I need something that works just for me, so the ease of use from anyone else isn't really a concern.
  - bigiain 8y ago
    In that case, if it were me - I suspect I'd be jumping into Swift. It _feels_ nice to play with (but playing with it is all I've _really_ done, so take that into consideration when evaluating this advice...)
- vorg 8y ago
  > trying to find people who can work in Groovy on Grails projects - it's not easy. That's because many of the people who used Grails to build a website didn't intend sticking around to fix the bugs or maintain it -- they just wanted to get paid and move on to hawking themselves as experts in the next fashionable technology. Others chose Grails because they saw they could introduce loads of technical debt thus giving themselves an opportunity to charge a high hourly rate later on. > I won't be making the Groovy mistake again any time soon Oh, so you didn't choose Grails so you could skim an agent's fee from sourcing these people? Many did.
  - bigiain 8y ago
    Nope. I inherited this Grails codebase. The people and reasoning behind the decision were long gone before I started here. There's a lot I actually (now) like about Grails. Hiring talent is definitely not part of that.

bigiain 8y ago

The only thing I'd suggest missing out for TCL is the implied requirements in the "work" and "masters degree" comments - that at least some of this code is probably going to need to be shared and used/understood with others. For that reason alone I'd say Python is likely to be a significantly better choice. (If I'm interpreting the implications correctly) I've got experience with trying to find people who can work in Groovy on Grails projects - it's not easy. That's not a great reason to stick to "mainstream languages", but I won't be making the Groovy mistake again any time soon... And while TCL is definitely _capable_ of replacing Groovy, it is the wrong choice for me that same way that Groovy was...

auto 8y ago
I definitely see how that could be inferred, but here it actually isn't the case. I need something that works just for me, so the ease of use from anyone else isn't really a concern.
- bigiain 8y ago
  In that case, if it were me - I suspect I'd be jumping into Swift. It _feels_ nice to play with (but playing with it is all I've _really_ done, so take that into consideration when evaluating this advice...)
vorg 8y ago
> trying to find people who can work in Groovy on Grails projects - it's not easy. That's because many of the people who used Grails to build a website didn't intend sticking around to fix the bugs or maintain it -- they just wanted to get paid and move on to hawking themselves as experts in the next fashionable technology. Others chose Grails because they saw they could introduce loads of technical debt thus giving themselves an opportunity to charge a high hourly rate later on. > I won't be making the Groovy mistake again any time soon Oh, so you didn't choose Grails so you could skim an agent's fee from sourcing these people? Many did.
- bigiain 8y ago
  Nope. I inherited this Grails codebase. The people and reasoning behind the decision were long gone before I started here. There's a lot I actually (now) like about Grails. Hiring talent is definitely not part of that.