qtxie on master
FIX: macOS: crashes when settin… (compare)
I was working on this Atomica stuff back in 2010, so trying to refresh my memory climbing over the Altme archives, and came across this historical conversation. It's @dockimbel , @gchiu and I discussing the pros and cons of cloning Rebol. Interesting read.
but when deeply experienced Reducers push back on your idea, you tend to push forward with the same request again
Greg, I didn't read this part. Why I ask a second time ? I see in my this vision the RED documentation chapter on Select with an example like mine and new developers all thinking: "great I can search in a blocks like I actually do in databases table, what a great language!". This because in the example you will show them intersects with what they are used to manage day after day. Do you know that showing to the potential adopters, in the very first moments, an operational framework similar to their usual one increases the adoption chance? I am a developer too and I remember when I have chosen something because of that something interacting with my needing. These are the reasons that would drive the request to reconsider that
/pos refinement: its a MARKETING one other than a functional one.
However, thanks to your reply came the idea of creating a page about using RED blocks as database tables in programming.red.
Select is one of the core instruction of Red.
It is not a fundamental "instruction", it is just a convenient syntactic sugar for
second find on series to cover the common bias towards key/value pairs. You can build your own specific
select-nth variation trivially (
pick find ... nth), there is no need to bloat the runtime environment with such construct.
Every company needs a goal, a one-liner, and that goal should be displayed above the white board of the board room. Every decision, product, direction etc should be to kick the ball towards the goal. Most of the staff I've worked with think the goal is to 'make money', which always the wrong goal.
So, what's Red's goal?