I do not know the rules. But if anyone would like to write it in Nim I would be
happy to join. Recently I was working on something that resemble Roguelike:
[Not Roguelike!](https://dl.dropboxusercontent.com/u/21455945/NotRoguelike.GIF)
Sublime works decent with nimlime. However it was recently abandoned so I am a
bit worried.
> Skins were part of my original Nim "vision".
Nobody's perfect
That vision is consistent with the style insensitive naming, which I'm also not
crazy about.
> There is a big difference between features that cost us manpower (cough
> concepts) and > features that are mostly free of maintenance
> I hope this is not stuff the core team spends any time on.
Don't worry. New release is coming, nimsuggest is improving, bugs get fixed,
nobody works on "Nim syntax skins".
That said:
* Skins were part of my original Nim "vision".
* There is a big difference between features that cost us
Just to chime in on this: I see nothing wrong per se with TMTOWTDI
(theres-more-than-one-way-to-do-it) but a syntax skin is a hard sell
considering the main priority should be getting that v1.0 release out now. I'm
a fan of the principle of least surprise - programming is hard enough to get
rig
> Multi-syntax is harmful for such small amount of developers.
I think this is an important point. At the current community size, an
alternative syntax is a bad idea. That might change if Nim were to 'take off'.
For example, in the nascent D community, Tango/Phobos split may have been a
fatal b
Well just that you know, autocompletion in emacs works, that's why I
recommended it.
RedFred is right, Nim core developers have to focus on important things, like
stability, documentation, and making the language complete (Nim is not a
complete language, yet).
Nim's Python-like syntax is nice and there is no way to change it, because Nim
in Action is finished. If you want to ha
@lltp says:
> > Imagine yourself in 2 years, Nim is flourishing, a community starts to
> > build, the standard lib improved by a lot... However you uncovered a bug in
> > it. You have a look at it and you see a perl-ish "Nim" that you spend weeks
> > to learn (since the guy who made it didn't c
@lltp
> You have a look at it and you see a perl-ish "Nim" that you spend weeks to
> learn
No, with skins done right, you wouldn't: the Perl afficionado would have used
an editor which supports a perlish skin for AST display, but saves the source
code as Nim proper (the default skin). You coul
I agree with @scriptkiddy.
I think syntax skins are a complete waste of time and resources when stable
language v1.1 and better documentation will do far more for adoption.
I have nothing to add to the arguments I've made for why I think turning Nim
into a platform that's not monogamously married for life to a single language
frontend would broaden Nim's appeal.
I would just like to express my utmost respect for all people who've weighed in
on this discussion, eve
Bindings are ready now -
[https://github.com/zacharycarter/blt-nim](https://github.com/zacharycarter/blt-nim)
Hi all,
7drl - [http://7drl.org](http://7drl.org)/ \- starts this weekend. I figured
I'd mention it here, as there are some bindings available to some roguelike
development themed libraries in the Nim community floating around.
I personally just finished bindings to -
[http://foo.wyrd.name/en:
14 matches
Mail list logo
