Sure Carlos, that's just my view. There are definitely more approaches to 'typing' json than there used to be (I did not use protobuffer yet but it seems interesting). I think the case for AMF becomes stronger for 'new' projects if there is an easy way to move to other things without major changes. But for the record I do like amf :)
On Fri, Mar 8, 2019 at 10:17 AM Carlos Rovira <[email protected]> wrote: > Hi Greg > > El jue., 7 mar. 2019 a las 20:41, Greg Dove (<[email protected]>) > escribió: > > > > > I think AMF in general should be considered legacy support. I would be > > surprised, for example, if lots of people start using AMF remoting in new > > projects simply because Royale supports it in javascript. I suspect they > > are more likely to use json or protobuf etc for newer projects. > > > > > don't want to "un-focus" the thread, but I continue thinking that AMF is > far better for structured programing. > JSON still lacks typing, and that seems to me a big problem. > Maybe speed, nowadays could be almost the same (although I think when I > search about this topic few months ago that AMF still was more performant) > So, if people uses Royale, and AMF is working great as we have now...don't > see a reason to not go with AMF as a first option. > > Just my 2! ;) > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > > > > >
