Live data from Hacker News

Felix - a fast scripting language

felix-lang.org

41–50 of 88 posts

Re: Felix - a fast scripting language

#41

I like the array type syntax: an array of five ints is int*int*int*int*int === int^5 instead of something like int[5]. Lots of interesting little ideas.

How is

    int*int*int*int*int
or even

    int^5
better than a plain int[5]? To me, the use of mathematical operators * and ^ causes dissonance.

Re: Felix - a fast scripting language

#42

The web page rubs me the wrong way. How can you claim to be the fastest anything without a single benchmark? How can you claim to be a "scripting language" when you're statically-typed and compile to C++? What does "scripting language" even mean then? How can you say things like "it will be a bit slow the first time but subsequent runs will load much faster than any VM." Any VM? Are you really "much faster" than: $ t…

are you referring to the "The fastest scripting language on Earth" tagline? i saw that as a way to say "look, this is a compiled language that you can use as a scripting language" with a touch of whimsical humour.

Re: Felix - a fast scripting language

#43

I've kept an eye on felix-lang the last several months, and the project seems to be progressing continuously. I'm curious though: has it been used in production? I'd be very interested in reading real use stories, with up and down sides! Also, how is the community doing, and what about contributors? Do both groups grow?

i've been keeping a vaguely interested eye on it for years, because it does look interesting. it has failed to make it to the front of my "learn this language next" priority queue due to the fact that i can't find anyone using it for anything, not even a hobby project on github. also, the documentation is a bit sparse.

one killer feature that would make me start learning it immediately is good, well-documented qt bindings (i'm sure it is possible, since felix compiles down to c++, but with the sparse documentation i have no idea how i would go about getting it up and running, and insufficient motivation to first learn the language and then figure out how to do it).

Re: Felix - a fast scripting language

#44

I like the array type syntax: an array of five ints is int*int*int*int*int === int^5 instead of something like int[5]. Lots of interesting little ideas.

How is int*int*int*int*int or even int^5 better than a plain int[5]? To me, the use of mathematical operators * and ^ causes dissonance.

If you're coming from a type theory background (which, granted, few are), this operator is actually perfectly natural.

http://en.wikipedia.org/wiki/Product_type

Re: Felix - a fast scripting language

#45

They are smoking crack if they think anyone will use a scripting language that doesn't have a functioning REPL. My goto-languages for quick development are Perl 5, Clojure and Javascript. All 3 are adequately fast for real tasks. All are cross-platform, and all 3 support a REPL that allows doing real work interactively. These conditions are the absolute minimum to be viable as a scripting or sketch/prototyping langua…

What REPL do you use for Perl?

As aflott does, I use the built-in debugger as REPL for most simple uses.

I also use re.pl from Devel::REPL (https://metacpan.org/module/Devel::REPL).

Re: Felix - a fast scripting language

#46

The web page rubs me the wrong way. How can you claim to be the fastest anything without a single benchmark? How can you claim to be a "scripting language" when you're statically-typed and compile to C++? What does "scripting language" even mean then? How can you say things like "it will be a bit slow the first time but subsequent runs will load much faster than any VM." Any VM? Are you really "much faster" than: $ t…

My "good enough" definition: a scripting language is a language that does not require you to write a main() function or define a class / object in order to produce output and features automatic memory management.

So Common Lisp and Fortran are scripting languages? This test seems to be more like "Is the language heavily influenced by C or C++?"

Re: Felix - a fast scripting language

#47
post #42

The web page rubs me the wrong way. How can you claim to be the fastest anything without a single benchmark? How can you claim to be a "scripting language" when you're statically-typed and compile to C++? What does "scripting language" even mean then? How can you say things like "it will be a bit slow the first time but subsequent runs will load much faster than any VM." Any VM? Are you really "much faster" than: $ t…

are you referring to the "The fastest scripting language on Earth" tagline? i saw that as a way to say "look, this is a compiled language that you can use as a scripting language" with a touch of whimsical humour.

Interesting. If that's the way it is intended I missed it completely; I'd definitely be much more receptive to that line of meaning.

Re: Felix - a fast scripting language

#48
post #8

Out of curiosity: How did you generate the slides?

The webserver, which is written in Felix, translates a particular format called "fdoc" to create the tutorial and slides, including embedded colourised hyperlinked Felix and C++ code. The translation is to a mix of HTML5 and Javascript. This link shows the source of the first slideshow: http://felix-lang.org/web/slides/language-overview.fdoc?text All the documentation and layout needs a lot more work. [BTW: I'm the p…

Yttrill, I see that Felix is 12+ years old. I remember reading about Felix on Lambda the Ultimate a few years ago. :)

Over those 12 years, what are some of the biggest changes (in the language or its implementation) you have made? Where the changes mostly evolutionary?

https://github.com/felix-lang/felix/commits/master?page=135

Re: Felix - a fast scripting language

#50
post #36
post #29

Earlier quoted context omitted.

You obviously have no idea what signal-to-noise ratio is about if you think semicolons are noise. Who are you trying to impress?

End of line is already encoded in source files as \n. Redundancy isn't noise, but it is redundant.

If end of line always means end of statement, by all means get rid of semi colons. If some non-trivial algorithms is used to infer end-of-statement boundaries that is more complicated than detecting end-of-line, then...there will be subtle problems.

I went through this transition before in Scala, the error messages got a lot worse after semi-colon inference was added. I wound up telling people to add semi-colons to their code when they were scratching their head at some sort of parse/type error message.

Post reply on HN