Anyone used this already ? I'm wondering now reliable this is.

 

1

 

1

 

1

 

1

 

1

 

1

 

1

 

Agree that Flask needs more community solutions sharing!

 

Thank you for your OP. This was the first time I decided to give Nim a serious look. I hope it succeeds to grow a sustainable community. I’ll be a part of that community for sure, but right now there is the OSS equivalent of market failure.

 

Interesting, thanks for your thoughts.

 

No sweat, take your time.

 

As a long-term python developer with basically no experience in compiled languages, I can tell you that Nim being a compiled language does not turn me off, and I really like the syntax. Being a compiled language would turn me off if it didn’t come with a lot of speed improvement, but the speed is drastically better than cPython. The reason why I will probably never give the language more than a moment of thought is because there is basically no ecosystem. The language has been around for longer than Rust and Go, yet it has basically 1 half-baked web framework. I didn’t see much in regards to any specific other niches either, besides meta-programming. I can tell you right now that if If I looked up “Nim web frameworks” or “Nim ORMs” and found a bunch of blog posts and libraries, I would be spending the next two months, solid, learning and using the language.

 

No, I hope to add some features in the next time, but I’m a bit underwater with client projects at the moment

 

You can! Just put “Ask PN:” in front of your submission and use the text field for whatever you like to ask!

 

Ok, so there's now way to make paragraphs here on PN?

 

Betteridge's law of headlines is an adage that states: “Any headline that ends in a question mark can be answered by the word no.” Speed or not, I believe that Python's interactive prompt + being able to run without compilation gives Python a head start. Nim looks interesting, though.

 

ok

 

In my experience, alpine's use of musl instead of glibc cost about a 30% performance hit on my csv processing workloads.

 

I would take this guy's take with a grain of salt. He's selling tools for creating Docker containers for Python. And some of the methods he uses aren't conducive to creating the best Docker images. See HN post for more discussion

 

Thanks for the heads up. I checked my work projects with -Werror and all I needed to do was update pytest.

 

You might be interested in adapting this template into a cookiecutter template[1]. That's my favorite way to start a new project, by far. This[2] is my current favorite one for new python projects. [1](https://cookiecutter.readthedocs.io/en/latest/) [2](https://github.com/wemake-services/wemake-python-package)

 

231

 

(It didn't, damn!)

 

In an article that talks about handling files, I feel that `pathlib` should have been mentioned: import pathlib path = pathlib.Path('/path/to/file') with path.open('w') as fptr: print('oh, hai!', file=fptr) (I wonder if identing the block above renders the block as a code block…)

 

Possible, yes. However you may decide that adding more technologies for specific parts of the application result in better usage of resources (time, money, etc). ex1: You could build your frontend using Django's rendering framework, but you may decide that it would be better to use a different rendering framework or even an api and separate frontend. ex2: You could store all your user-uploaded files on disk with Django, or you may opt to use an external service like AWS S3 or GCP GSB for those files.

 

I think there's a need for other technologies as well.

 

So what is the catch? Why is it free? How are they able to pay for all their developers? https://kite.com/careers/ It does say, "Kite runs locally. Your code is private." However, I'm still left wondering how they are paying for their developers. My guess is that they're selling analytics or they just have a bunch of investors and are trying to build a team to pivot eventually and do something else that makes money eventually.

 

Thanks! I didn't look in the source code, but I _did_ look in the documentation and I didn't find anything (I can't be absolutely sure I didn't overlook it, though). (Shift|Ctrl)-Esc is not exactly intuitive. Neither is my current editor's (jed) exit combo, ^X^C, but at least it's documented.

 

LOL. If you're still stuck inside your vy window, I found the key combo in the source code: Shift-Esc to quit or Ctrl-Esc to save and quit.