Just from skimming some of the relevant docs (not having written a
driver for Apache Ignite before), some thoughts:
* It does indeed look like there is enough info, both as documentation
and example code, to write codecs and drivers for Ignite
* The formats and protocols look rather
Glad to hear these suggestions, @Geoffery.
I also have a question, this product has a clear binary protocol, do you
know how to port it to perl or perl6?
https://ignite.apache.org/docs/latest/binary-client-protocol/binary-client-protocol
I was using their python/ruby clients, but there is not a
I love doing binary codecs for Raku[1]! How you approach this really
depends on what formats and protocols you want to create Raku modules for.
The first thing you need to be able to do is test if your codec is
correct. It is notoriously easy to make a tiny mistake in a protocol
As long as I'm trying to follow topics, related to continuous testing with
github actions, I always see ubuntu-based scenarios. What about macOS and
Windows? Do we have rakudo images for these?
Best regards,
Vadim Belman
> On Jan 1, 2022, at 5:14 AM, JJ Merelo wrote:
>
> Try the new GitHub
Rakudo v2031.03
Have I been asleep for a decade?
My Rakudo is v2021.12.
I'm not sure what context you are using, so why you are getting errors.
POD6 commands do not work with REPL.
Here is the contents of a test file, which can be run with 'prove6 -v
t/config.t' assuming the following
> raku is now my tool of choice when
* manipulexity is important
I had to look it up
Larry Wall: Manipulexity and Whipuptitude - Fortune
If you were a Unix programmer you either programmed in C or shell. And there
really wasn't much in between. There were these little languages that we used
on
