<ryanstout>
is it crazy to try and build a simpler sprockets replacement?
<ryanstout>
I don't need a lot of it for volt, and it seems like sprockets isn't being maintained and is really bloated
<adambeynon>
ryanstout: I had a simple Builder class before I moved to using sprockets by default
<adambeynon>
was like, 200 loc maybe
<adambeynon>
and could handle requiring ruby and js assets
<dragonkh>
evneing adambeynon
<ryanstout>
yea, I just need to be able to do a few pipelines, scss, css compress, opal compile, js compress, concat, and handle source maps all of the way though
<dragonkh>
adambeynon: I've written the whole user interface for one of our projects at work in opal
<adambeynon>
nice. using opal-jquery directly?
<dragonkh>
yeah
<dragonkh>
the back end is scala json feeds and the front end is opal jquery
<dragonkh>
it blew the minds of the rest of my team !
<dragonkh>
I'm working on some D3 visualisations that will plug into it
<dragonkh>
I'm going to release one part of the project - it's a datatable library - which has drill down functionality, sorting, searching etc a bit like datatables.js
<adambeynon>
:D sounds good. its funny, I always thought that opal would be the ideal thing for people using ruby on the backend, but Im finding more people are using alternatives, like scala, but still like opal frontend stuff
<adambeynon>
dragonkh: nice. let me know if/when you do. I have a couple of data intensive apps that need some better data methods on them
<dragonkh>
my personal project I'd use ruby on the backend for sure - but it's extremely hard to get that kind of thing going when the rest of the team is java and scala
<dragonkh>
java and scala devs firmly object saying that ruby runs like a dog
<dragonkh>
and leaks memory
<dragonkh>
and rather than jruby they want to use scala
<dragonkh>
but hey - java and scala for the bills and ruby for the soul
<dragonkh>
right better go - things to do - if you know anyone interested in the opal meetup - please feel free to invite them