Welcome to December, friends of Red. It’s an intent and focused time of year as we wind down 2019, and the core team is making important moves (sometimes literally!) to set us up for an ambitious 2020. But first, here are just a few things that happened in November. First and foremost, it’s always great when community members help compile resources for use by others, and we’d like to acknowledge @rebolek for his excellent compendium of historic automatic builds: https://rebolek.
Posts categorized as "update"
What made the fast-lexer branch a priority? Several things. It started when @dockimbel looked into ticket #3606, which was impossible to fix currently, and we didn’t want to give up on the auto-syncing between /text and /data facets. So he had to consider bigger options, including how to make the lexer instrumentable. It was not easy, because the current lexer is not re-entrant, so having the lexer emit events to a callback function could have caused serious problems.
Over the last few weeks the Red Lang core team drilled down to make some truly great progress on Red’s fast-lexer branch–while we also gained valuable support from the contributions of Red doers and makers as they consolidate a world of useful information and resources. Fast-Lexer Benchmarks In the fast-lexer branch of Red, you can see lots of new work from Red creator @dockimbel (Nenad Rakocevic) and core teammate @qxtie.
Hello to all the great makers, doers and creative people who are using Red, helping the Red Language grow and improve! As always, there’s a standing invitation for you to join us on Gitter, Telegram or Github (if you haven’t already) to ask questions and tell us about your Red-powered projects. Here are some recent highlights we’d like to share with you: 1. Tickets Get Priority In the last month, our core team has closed a large number of tickets.
We are releasing today the version 0.4.0 of the RED Wallet with several major new features. As a reminder, the RED Wallet aims to be a simple and very secure wallet for the major cryptocurrencies (BTC, ETH, and ERC-20 tokens). Safety is enforced through the mandatory use of a hardware key (Ledger or Trezor keys), which protects against any failure of the wallet app (being it a bug or an attacker).
As part of the R&D work on port! datatype in port-type branch, we have implemented a GPIO driver for Raspberry Pi boards, as a gpio:// scheme (no third-party library needed). This work helped define the low-level API for ports written in purely Red/System or a mix of Red and Red/System. The Raspberry Pi is a very popular board with millions of units sold, so this is a market where Red could be potentially helpful to developers.
If you are an active member of the Red community, you will have likely been keeping track of Red’s progress through our Gitter rooms and Github repositories, but we wanted to officially bring everyone up to speed with a shiny new blog post. The team has been busy since January on many fronts, multiplexing its efforts on many different branches of development. Here is an overview of what we have been cooking and what is coming.
Stepping-up 2019 started with continued advances in the main development branch, implementation of features, and triage of pending tickets. For example, smart merging of a style’s actors with the actors of a particular face instance was introduced in the VID dialect. Example: view [ style my-button: base on-down [face/color: face/color / 2 do-actor face event ‘click] on-up [face/color: face/color * 2] my-button "Say hi!" red on-click [print "hi"] ] But this is just a tiny drop in the January ocean, and nothing special in the grand scheme of things.