3 ms·
I personally see nothing wrong with writing a prototype in a "slow" language, especially if speed ain't a priority (yet). Sometimes you just have to get an ini
by yellowapple 10y ago
I personally see nothing wrong with writing a prototype in a "slow" language, especially if speed ain't a priority (yet). Sometimes you just have to get an initial implementation written in some language, and if that language happens to be some interpreted language from the 80's, then so be it.
Now, sticking to that language for a final version would be more concerning, but even that ain't really a dealbreaker; lots of "slow" languages are perfectly capable of interfacing with "fast" languages through some kind of FFI (or, at the very least/worst, IPC over some kind of pipe or socket or what have you). Gradually writing faster implementations as you run into bottlenecks is a perfectly common and reasonable development approach.
- jerf 10y ago"I personally see nothing wrong with writing a prototype in a "slow" language, especially if speed ain't a priority (yet). " Neither do I. That's why I conditionalized that point on the intent of the poster, who as of this writing has not replied to any of these comments. I wish people would be more clear about their intentions. I have no problem with any of them, ranging from idly showing off something they did for discussion to "I intend professionals to drop everything and use this exclusively", but the feedback appropriate to the various cases along that range are very different. I don't want to blast a student for not creating something that Google can base their next 10 years on, but I don't want to provide someone trying to win over professionals with feedback about their capitalization of identifiers.