[Coco] Drivewire development

[Nathan Byrd]

James,

Any way I can talk you into contributing with this Java refactor?  That
streams idea sounds awesome.  I think there is probably room for both
improvements to the current Java as well as another server in Go - in fact
when I started looking at this I considered just using Go as well, though I
think there is some use for still having the original project that targets
the JVM as well.

As to your point about clarity, I totally agree. One of the possible
changes that I was thinking about for long term is to convert it to Kotlin
for a more modern source base, with a DI framework like Koin or Dagger2,
etc and do some big code refactoring (hopefully after getting some unit
tests in there 🙂)

If you are at all interested, let me know - I've setup a GitHub
organization and am currently migrating the codebase over (minus some of
the detrius.) Even if you just want to put the Go version under the same
organization that would be cool too. If you or others are interested let me
know and I'll invite you to the project.

Thanks!

On Thu, Jul 19, 2018, 10:15 PM James Jones <jejones3141 at gmail.com> wrote:

> I grabbed the Java source and took a look at revising it to take advantage
> of streams (after all, Java 8 has been around for quite a while) and some
> other stray changes. I haven't tried it out yet.
>
> I'm going through the spec to make sure I understand it. One impediment: it
> looks like the end of the description of the WRITE transaction got chopped
> off. (What is it that the CoCo might send on CRC error?) My goal is to
> implement, ideally based just on the spec, a DW4 server written in Go, with
> an eye towards simplicity and clarity.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>