These are chat archives for JasperFx/jasper

10th
May 2018
Miguel Cudaihl
@Miggleness
May 10 01:56
My pitch to use JasperFX failed. My company still wants to use WCF because “devs may not understand” anything not WCF. Heck, dont even want to consider .net core even with plans to move to cloud.
Jeremy D. Miller
@jeremydmiller
May 10 01:58
@jokokko I got it up, but there’s an unrelated problem I introduced, so there’ll be a 0.9.6 in the morning to fix that
Jeremy D. Miller
@jeremydmiller
May 10 02:05
@Miggleness I feel your pain, but for me it’s always something like that from database guys stuck in the 1980’s
Miguel Cudaihl
@Miggleness
May 10 02:11
@jeremydmiller i still intend on pitching doing cloud deployment right. The current plan is to use traditional VMs, but the cost and operational maintenance savings for using PaaS shouldnt be ignored. At least, I hope it doesn’t.
Phillip Haydon
@phillip-haydon
May 10 05:15
@Miggleness time to move on to new company
one of our clients write an API end of last year, they custom wrote the payload in go-lang in a completely non-standard way makes integration so hard, we have to proxy the request via AWS Gateway API -> Node JS -> Reformat -> Send to our API
Miguel Cudaihl
@Miggleness
May 10 05:17
Well, there are perks that i do enjoy. But after a year, we’ll see. Im taking this time to learning since the job isnt as demanding as the one i had last year.