Archived messages from: gitter.im/red/docs from year: 2022

gltewalt
01:51I saw the split comparison doc. Surprised you didn't look at haskell.
https://hackage.haskell.org/package/split-0.2.3.4/docs/Data-List-Split.html
greggirwin
16:43We can add it. Just can't cover everything. I, personally, didn't think of Haskell because any time I look at Haskell examples, it seems they don't use words. :^)
16:45Link added.
16:53And when they do use words, they're things like "strategy transformers" and "derived combinators". I'm just a simple man. splitWhen is a really nice name though, using "when" for "When you encounter...".
gltewalt:matrix.org
20:58Yeah, I've only made it to understanding about 50% of the egghead stuff, but their utility functions mostly make sense, and that community geeks out with 50 different ways of solving everything.
greggirwin
22:07> that community geeks out with 50 different ways of solving everything.

They're catching up to us! ;^)

GiuseppeChillemi
21:49Red is a readable language, you understand what it does since the first reads.

gltewalt
00:10Depends on how you write.
meijeru
12:35@dockimbel @greggirwin
In the most recent blog post I read (to my satisfaction) the planned work item:
Red Language Specification (Principles, Core Language, Evaluation Rules, Datatype Specs (including literal forms), Action/Native specs, Modules spec.
Let me reconfirm that the work I have put into the specification document [here](https://github.com/meijeru/red.specs-public/blob/master/specs.adoc) is fully available for use in progressing this work item, in whatever way is thought appropriate.
greggirwin
20:44@meijeru absolutely. I imagine that will be the foundation we work from. We want to a) make it clear what parts of Red have a hard, unchanging (as much as we can), spec; b) firmer style guidelines for things like custom datatypes (not including new lexical forms) and how to make sure contributions (including those from the team), align with the big design picture. Finally, c) I'd love to be able to treat specs as data where we can, for more interactive tools, including analysis for new work. e.g. if we have specs we can apply as rules, how do we do that?

In any case, your work will be an important aspect, and we'll certainly reach out to leverage your knowledge and expertise.

meijeru
12:18I just (re-)discovered https://w.red-lang.org/en/. What is the status of this doc-site now?
Red-Beginner
17:51@meijeru It looks like a fan site. Probably it copied from the original documents.
greggirwin
18:53That was @x8x's work, but doesn't seem to have been kept up to date.
meijeru
21:04 It seems to be derived from https://github.com/red/docs/tree/master/en/, which I hope IS up-to-date. Maybe @x8x can tell us what the status is.

greggirwin
05:04Yes, I just don't know if it's kept up via automation.

dsunanda
14:52I do all my Red development under Windows. But now I want to compile/encap a GUI app, and then run it on Linux (Fedora initially, probably).

Is there a handy, easy, how-to type guide for such things? (All I can find is how to install a dev environment under Linux - not want I want; just want a runtime environment).

Thanks!
rebolek
15:16just add -t Linux when compiling
15:17-t means target
dsunanda
18:50Thanks .... And then just copy over the executable? No libraries need? That simple!?
greggirwin
18:53Be sure to set the executable bit for the binary on the target system.
dsunanda
18:53Thanks. So that simple +1 bit :)
greggirwin
18:54If you don't add any external dependencies, that's the magic of Red. It does still need 32-bit support libs from the OS, if you're Linux doesn't include them you'll need to install those.

gltewalt:matrix.org
15:53https://roadmap.sh/
GiuseppeChillemi
22:02Nice link

loziniak
12:30Hi! I added links to GitHub repo in Red-By-Example . Can someone from the team publish the site?
https://github.com/red-by-example/red-by-example/commit/a95eeac11157043fdc1398ea60f6eafc17702213
greggirwin
19:14I don't remember who is doing that job now.
loziniak
21:58At the time of transitioning from Arie and Mike you [↑wrote↑](https://gitter.im/red/docs?at=5e5303dcdafa3029f64ca385) about @x8x .
greggirwin
22:39OK, he's not around much these days, so if he doesn't respond we'll have to figure out a new plan.

mikeparr
09:19Let me know if I can help.

greggirwin
03:48Will do. Thanks.