Live data from Hacker News

Prologue: A web framework written in Nim

github.com

11–20 of 72 posts

Re: Prologue: A web framework written in Nim

#12
post #4
post #3

I guess all roads do lead to Prolog. Why risk the naming confusion? Doing a search for "prologue language" yields millions of Prolog results on both DDG and Google.

It's getting to be almost impossible not to have a similar name to something else.

NimPrologue, NWF (NimWebFramework) etc

I could probably come with dozen more names if I knew more about the project and after a bit of brainstorming.

Re: Prologue: A web framework written in Nim

#13
post #3

I guess all roads do lead to Prolog. Why risk the naming confusion? Doing a search for "prologue language" yields millions of Prolog results on both DDG and Google.

sincerely asking: are you worried that anyone will suffer from this decision? Personally I can't imagine a scenario where someone actually feels any pain from this naming decision. Adding "nim" to your prologue search is par for the course for many categories of search. I laugh about how often I get guitar string ads because I'm always looking up "elixir string" documentation xD but it's not a pain point. Who suffers here? It's FOSS so the "marketing" of the project has little to do with the name I'd suspect. I mean who is going to pick a technology based on the search-ability? We're talking about decisions being made by people who are highly skilled internet searchers.

Re: Prologue: A web framework written in Nim

#14
post #13
post #3

I guess all roads do lead to Prolog. Why risk the naming confusion? Doing a search for "prologue language" yields millions of Prolog results on both DDG and Google.

sincerely asking: are you worried that anyone will suffer from this decision? Personally I can't imagine a scenario where someone actually feels any pain from this naming decision. Adding "nim" to your prologue search is par for the course for many categories of search. I laugh about how often I get guitar string ads because I'm always looking up "elixir string" documentation xD but it's not a pain point. Who suffers…

It just seems like a minor annoying that could be trivially avoided

Re: Prologue: A web framework written in Nim

#15
It seems nothing groundbreaking. A router, some middleware and websockets.

Also, nim is a mess. Very poorly designed language. I tried it a couple of years ago and was repelled by its syntax and attempts to solve every single problem for you.

Re: Prologue: A web framework written in Nim

#16
post #4
post #3

I guess all roads do lead to Prolog. Why risk the naming confusion? Doing a search for "prologue language" yields millions of Prolog results on both DDG and Google.

It's getting to be almost impossible not to have a similar name to something else.

A lot of different words out there.

Re: Prologue: A web framework written in Nim

#17
post #4
post #3

I guess all roads do lead to Prolog. Why risk the naming confusion? Doing a search for "prologue language" yields millions of Prolog results on both DDG and Google.

It's getting to be almost impossible not to have a similar name to something else.

As a new user, I was able to get a pronounceable(ish) 4-letter username. It's not always hard. But Prologue is an English word and a lot of English words are taken. (and probably many words in other languages, too)

Re: Prologue: A web framework written in Nim

#18
post #15

It seems nothing groundbreaking. A router, some middleware and websockets. Also, nim is a mess. Very poorly designed language. I tried it a couple of years ago and was repelled by its syntax and attempts to solve every single problem for you.

Curious in what way you said it is very poorly designed other than syntax issue?

Re: Prologue: A web framework written in Nim

#19
NIM really is a full stack language and ecosystem. It has a first class compiler to JavaScript (though, I admit, I don't know how tuneable it is, so I think it just compiles down to ES5, it'd be nice to do a differential build where it would compile down to ES5 and/or ES2015/ES2016 at the users discretion)

Only thing it needs now is a compile to CSS solution and you would never have to leave the language. Its a very thurough language in that regard.

It also needs a strong GUI framework for desktop and mobile apps, as well, but still, its very fully featured! My hunch in this area is that you could just compile to Electron/NativeScript/React Native as a relatively 'quick' solution to these problems.

I'm excited to see where this language goes. I'm pretty tempted to use it in production to replace Python for some things and may find it more expansive due to its flexibility of compile targets.

My only gripe (and its relatively small) is I don't like its compiler directive syntax using the `{.directive.}` style, its a little ugly and noisy to me, I'd prefer something like rust's `#[]` (I think this is actually how you use a Rust macro, but its a nice syntax regardless)

Not enough to stop me from thinking the language has some real upside and potential, though.

Post reply on HN