refaqtor

13 ms·

1. 1.▲
   by refaqtor 7y ago

   Well, if you're talking GUI stuff, nothing in Nim compares to Qt. But, I did routinely use Qt for console, server, and headless embedded stuff. The Qt environment compensated for lots of C++ shortcomings up to recently. I think I&#x
2. 2.▲
   by refaqtor 7y ago

   I've quit using Python, unless forced, because I've gotten too many folders of files that "work on my(the original developer's) machine," but fail on mine because I didn't find or follow a README that said &quo
3. 3.▲
   by refaqtor 7y ago

   Nim is great for knocking out commandline apps, I recommend "cligen" for quick and clean options, or "docopt" for friendlier cli options. They feel "scripty" when you can begin with a couple lines and grow it
4. 4.▲
   by refaqtor 7y ago

   I don't have vague memories. I use it everyday on production code on server and embedded. I find it stable, solid, dependable.
5. 5.▲
   by refaqtor 7y ago

   "Nimrod" experience is quite outdated. There have been great improvements in documentation in the last year.
6. 6.▲
   by refaqtor 7y ago

   cross-compiling to ARM embedded was surprisingly simple
7. 7.▲
   by refaqtor 7y ago

   ditto! docker and kubernetes are solutions to problems that shouldn't be there in the first place!
8. 8.▲
   by refaqtor 7y ago

   I'm using Nim in production since .18 with zero issues. I spent many years in Qt/C++ and was reasonably quick, but not as quick as I was with D. But then, in an evening, from a cold start, using nothing more than the two Nim Tut