You had me there for a few minutes @Araq, fair play :)
today I don't eat fish (lol) on April 1st
rewrite all that in Python ... and why not in gwbasic with the one
opening on the assembler
I'm strongly opposed to that plan! While I fully agree that Nim (currently)
does a lot of uncool stuff (e.g. static typing) I do not consider Python and C
good choices. Instead of Python we should be bold and directly walk into where
the future is: AI based image interpretation instead of Python
"I think we can get away with modelling the Nim AST in C via a single void*
type"
This one line killed me haha
Best 1 April ever XD
Read that post, peek at the calendar and have a laugh ;-)
what does this mean for us, humble mortals?
Writing performant code in C these days? How absolutely immoral! Have you
considered our lord and saviour Rust? /s
Also, I love this part: "The perfomance critical parts inside the Nim compiler
are probably: The lexer, the parser, the semantic checker, the overloading
resolution mechanism, the
great ! I can't wait !
😈 🤦♂️ Nice one.
Hey jjude - Check your calendar.
All of NIM will be rewritten in Python or only machine learning part? Isn't
rewriting all of the language into another language waste of time rather than
spending it on improving either the language or the ecosystem?
Took to long for me to realize XD
So, this is something that we've considered for a while now, after all these
years writing production code in Nim, we long for Python's lack of static
checking; in the end there is always a Nim code snippet that tests the part of
the Nim compiler we touched anyway, the static type system doesn't
14 matches
Mail list logo
