When comparing F# vs Rebol, the Slant community recommends F# for most people. In the question“What is the best programming language to learn first?” F# is ranked 30th while Rebol is ranked 51st. The most important reason people chose F# is:
F#'s syntax tends to be terse while remaining very readable and easy to understand without being a chore to write.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Concise syntax
F#'s syntax tends to be terse while remaining very readable and easy to understand without being a chore to write.
Pro Easier transition from other paradigms
Since F# is not a purely functional language, it lends itself to being more easily picked up by programmers that have experience with other paradigms.
Pro .NET Interoperability
Since F# runs on the Common Language Runtime or CLR, it has access to the entire .NET Framework, as well as libraries written in other .NET languages such as C#, VB.NET, and C++/CLI.
Pro Multiplatform, it runs on .Net Core
Forget Xamarin and Mono. F# now runs on the multiplatform .Net Core!
Pro You can run F# in the browser
Thanks to a project like Fable, you can write and run your client app in F# and run it over JavaScript. It allows you to share code between your server and client.
Pro Natively supported by Visual Studio
This is a .Net language natively supported by Visual Studio. Though it is not as tooled up as C# the support is still substantial. In particular, C# deployment scenarios can be enabled for it with small C# wrapper projects. Integration with Visual Studio provides: IntelliSense, debugging, projects an other features.
Pro Fall into the pit of success
F# directs you into a workflow where the right way is the path of least resistance.
Coming from a C# background, its restrictions might feel arbitrary at first (e.g., what do you mean my code has to be in dependency order!? Arbitrary alphabetical or bust!), but you'll soon realize that your code is cohesive, concise and consistent in a way that it never was before - and you can compile and run with confidence!
Pro F# is supported by Xamarin
Thanks to Xamarin, F# is a functional language that you can use to build for iOS, Android and Windows.
Pro Very simple syntax
Rebol's name came from "Relative Expression Based Object Language". Rebol is a functional language and everything is an expression that returns a value. Things that have to be baked into the grammar in other languages are simple function calls with block arguments in Rebol.
Pro Homoiconic
Code is data, and data can be code. Rebol is based on a simple block data structure, used both for data and for the code itself. Blocks can be manipulated programmatically, and then evaluated as code. This makes metaprogramming easy in Rebol.
Pro Human friendly
Almost natural language, for example: write %out.html read http://google.com
.
Pro Graphical user interface
Beginners are usually stuck making command-line applications in other languages, because GUIs are too hard. Rebol GUIs are easy enough to start with.
Pro Domain specific languages
Rebol's simple homoiconic syntax makes it easy to create "Rebol dialects"--domain-specific languages optimized for a particular purpose. The Rebol distribution includes many of these, and users are free to create more. These DSLs make tasks that would be complicated to express in other languages easy.
Cons
Con Has no ad-hoc polymorphism (á la Type Classes)
You have generics, you have interfaces, you have inheritance, you have a lot of things at your disposal but you don't have Type Clases. They can be emulated using some clever constructs but there's nothing like having the real thing.
Con Infested with OOP
Still relying on .NET OOP libraries.
Con Not (yet?) Free Software
Rebol 2's core is free (gratis) for commercial use, but the license prohibits modification, a violation of the DFSG. Rebol 3 is Free Software (Apache 2.0), but isn't production ready.
Con Very niche language
Small community.
Con No separators
A function call expression has no parentheses, and there are no separators between sequenced expressions, not even newlines. This means that you have to know the arity of every function in an expression to know how to parse it. It also means you can run into subtle, hard-to-find bugs if you don't provide enough arguments, since the result of the next expression will be passed instead.