Interview:
https://notamonadtutorial.com/interview-with-nenad-rakocevic...
I never understood stuff like writing "forgive spelling" or "sp?" when the correct spelling is a Google away.
Some folks might be on a mobile device with an interface that makes it difficult to switch to another window. Or perhaps they are offline when they're writing it. Or perhaps they have mobility / accessibility issues that makes switching a challenge. Those are off the top of my head.
To my mind, worrying about someone's spelling when I can understand them perfectly is one of those "life's too short" issues, speeking personaly.
There's also momentum. They want to go write a quick comment and type their thoughts as they come -- not stop and Google things.
Just to note that Rebol 2 is below 1 MB. Depending on platform, Core is normally below 300K and View is around 600-800K - http://www.rebol.com/downloads.html
Unfortunately Rebol 3 (Ren/C branch) is a little beefier at this moment :( The non debug version is usually between 1.2 & 1.9 MB - http://metaeducation.s3.amazonaws.com/index.html
This Rebol 3 size will shrink. Currently there is development on build & extension process which will help. NB. There's been a big refactoring/redesign of the Rebol 3 interpreter in last couple of years so there maybe (still) some artefacts from many forks/merging of codebase that could also be shaken out.
The old 32-bit K2 (K language) had a superfast ACID DB, GUI, GC, no dependencies (but also no compilter) and was 250K, so 4 independent platforms would still fit in under 1MB; Arthur is now working on KPARC, which has no compiler but does boot on metal and includes GUI, editor, db, filesystem, network, and a lot more, e.g. this http://kparc.com/edit.k is the implementation of native nano-style GUI editor. ; Last I heard, it was still <500KB.
Right now, it only compiles to 32 bit binaries (which can run on both 32 and 64 bit OS).
64 bit support will come after the compiler is bootstrapped.
> and cross compiles
Yup, easy cross compilation. You do not need different cross compilers for different platforms a la llvm and gcc, a single 1 mb binary can produce binaries for all supported platforms.
So, on one hand, there's massive cross-platform support. On the other hand, those platforms are all obsolete, or about to be. Even the mobile and embedded ones have all gone 64-bit.
Maybe backwards compatibility will be maintained for a few years. But it ruins the embed-red-in-C story already.
There are AFAIK no plans to add 64 bit support before bootstrapping phase because the current toolchain architecture isn't that great and will be heavily improved during 1.x cycle.
A bit more details here -
https://gitter.im/red/red?at=56ac45a1586242210ae0704d
and https://github.com/red/red/wiki/Question-about-contributing-...
ARM cortex-M (32 bit) has only recently been able to chip away at 8 bit platforms and gain major use
https://en.wikipedia.org/wiki/List_of_common_microcontroller...
Using the other meaning of embedded (I embedded a Lua script in my C application), compatibility libraries don't help. It simply won't link.
Yeah, me too. I tried reading the Red source code, hmm still couldn't figure it out. Could someone explain how Red achieve this?
Compared to GCC or FPC, Red is obviously very very very tiny :)