Earlier quoted context omitted.
>it started to require me to work for Google for free How did that work?
Recaptcha and tracking.
Nim 1.2
61–70 of 130 posts
Re: Nim 1.2
#62Earlier quoted context omitted.
Can't find anything dark mode related on that page
There's a large button. It loads before the text does. When the text loads, you'll see in big letters, right next to the button, Dark Mode , italicization and all. If you click on the button, suddenly you get a very blue-purple dark mode experience.
Re: Nim 1.2
#63Earlier quoted context omitted.
Do you think the gcc -std flag would exist if every distribution of gcc included a command to easily download alternate versions and swap them out depending on project configuration? -std seems more like a bandaid around a difficult install/config than a feature, in my opinion. Obviously nim is free to make implement whatever options they want, but it seems to me like every second spent triaging/fixing/etc bugs about…
Yes, the -std flag would definitely still exist: the thing being changed by that flag is a lot of stuff in the parser, some stuff in the standard library, and some semantics bits further towards the backend, but at some point the versions converge and go through the same optimisation pipeline. A pipeline that definitely has seen improvements in more recent versions, so it's totally worth it to use a new compiler with…
Re: Nim 1.2
#64Dup is very interesting to me. Does that mean that in Nim all functions will be impure by default, and that it's considered idiomatic to modify the input? I guess it's nice that they're trying to make behavior consistent. It just seems like the opposite of the recent directions I've seen other languages take.
Mutating in place is often times faster and is more straightforward. I do feel Nim embraces mutation more than other recent languages.
Re: Nim 1.2
#65Earlier quoted context omitted.
What advantage does it bring that Kotlin hasn't?
No JVM.
There's also Kotlin JS, which targets the JS ecosystem, and comes with tools that let you import TypeScript type definitions into Kotlin, so you can easily interact with third-party JS modules.
A pure Kotlin library could easily be used on JS, JVM, and native/LLVM seamlessly. Which is pretty impressive. All your non-platform-dependent logic could be placed in a decoupled shared pure Kotlin library. Which avoid code duplication that is so common when you need web + iOS + Android client apps. (And the Intel Multi-OS Engine could be used to write your iOS app in Kotlin.)
Re: Nim 1.2
#66I really with more people used NIM for web development. It really seems like the best of all worlds (e.g. perf, developer ergonomics, productivity, etc).
How would the dynamism and expressivity of something like Django port to Nim? I love the whole declarative paradigm of the Django forms and models API. Is Nim good at this kind of DSL-ish plasticity?
You could certainly write an expressive web framework in nim, but a django/rails sort of paradigm is not the way.
Re: Nim 1.2
#67Earlier quoted context omitted.
Kotlin support AOT so moot point
Not really. Kotlin/native is still super experimental and graal isn't exactly that easy either.
Re: Nim 1.2
#68Earlier quoted context omitted.
Having only played a little with both (Kotlin and Nim), I enjoy Kotlin syntax but overall it feels as heavy as Java (need to setup an IDE for even getting started, choose and understand some package manager, slow compile times, etc.) Nim feels as lightweight as Go, but with great syntax. The main thing holding me back now is the lack of libraries, but it's definitely on my radar.
Isn't an ide just a choice? You don't have to use intellij. There are vscode plugins. Don't you also need to understand the go package manager or Nim's? I don't see how this is different than learning Gradle.
It’s pretty liberating to put some text in a single file, pass that file to a compiler, and have a single executable binary.
A devolved workflow I know.
Re: Nim 1.2
#69Dup is very interesting to me. Does that mean that in Nim all functions will be impure by default, and that it's considered idiomatic to modify the input? I guess it's nice that they're trying to make behavior consistent. It just seems like the opposite of the recent directions I've seen other languages take.
I haven't played with nim for a few months, but only parameters with var will get mutated. I suspect you want to use someone else's cursed function and don't want to poison your blessed code
Re: Nim 1.2
#70Dup is very interesting to me. Does that mean that in Nim all functions will be impure by default, and that it's considered idiomatic to modify the input? I guess it's nice that they're trying to make behavior consistent. It just seems like the opposite of the recent directions I've seen other languages take.
Mutating in place is often times faster and is more straightforward. I do feel Nim embraces mutation more than other recent languages.