Fork me on GitHub
#off-topic
<
2017-05-04
>
Jon04:05:41

New site for Respo "a virtual DOM library in ClojureScript" http://respo.site/

qqq04:05:00

What is the current state of FPGA dev tools? Is there a completely open source toolchain yet, or is it still a bunch of proprietary software

romain15:05:42

@jiyinyiyong Nice, do you have any comparaison with other solutions (reagent, quiescent, om, rum...) ?

Jon16:05:55

@romain No. It's like more difference than similarity. Respo is totally built with ClojureScript and implemented a simpler DOM diff solution. Reagent has component life-cycles methods, Respo only has the render function. Reagent has component local states, Respo manages with states by dispatching to Store(with help of a cursor path). Reagent may use components from React, in Respo we need to implement components by ourselves.

Jon16:05:11

The good part is I can experiment new ideas with Respo because I control it. Also it's more pure and more consistent when it's not based on a JavaScript library.

john16:05:15

@jiyinyiyong Are you familiar with freactive? https://github.com/aaronc/freactive How might Respo differentiate from that?

Jon03:05:03

john: Respo is too simple compared to freactive. I never saw freactive, but it's cool by reading the README.

Jon03:05:59

Respo does not support transitions, and I'm not very confident about the performance.

Jon03:05:35

I found it's still different. Freactive is depending on React https://github.com/aaronc/freactive/blob/develop/project.clj#L6-L9

Jon03:05:35

Respo is not based on React.

akiroz20:05:53

Sadly, it's probably not gonna go in this direction unless sillicon vendors release some specs / documentation. I've heard of project IceStorm for some Lattice devices built by reverse engineering stuff but I've never used it before.

akiroz20:05:25

FPGA development (or anything hardware related for that matter) is just absolutely painful mainly because of horrible tooling... that's why I switched over to the software side of things

mobileink21:05:11

nice post about announcement msgs: https://hisham.hm/2017/05/04/writing-release-announcement-emails/ Only thing missing, which I need, is the appeopriate way to (un-)announce a project that is ready for alpha-testers and people generally interested in the topic, but not quite there for a Grand Announcement. E.g. a one-man show that could use some help.