While I knew of the FIG, I wasn't aware of the full story behind it: you gave an excellent overview of its history and current events. It was also very enlightening to hear you explain what the newly passed FIG 3.0 structure is going to be like, including all the reasoning behind the changes. Plus your excitement for this milestone was just incredibly infectious, great job!
As someone who dips in and out of Fig, it was nice to hear about FIG 3.0. The fact that you only hear the drama, even when trying to avoid it, it was nice to know that the tech part was dealt with more at 97%.
Michael was enthusiastic, which was nice to see after all the crap these people have to deal with when trying to help a language and its community have a standardised approach to code implementation.
Thank you Michael, and thank you to everyone involved in the FIG!
Comments
Comments are closed.
thanks for giving the talk, very interesting.
Very interesting!
Engaging and informative discussion of the birth processes behind, and the need for FIG 3
Very nice overview of what the FIG is. Bit of history, bit of current affairs and a bit of the future. Thank you!
As much as I've left the FIG alone in the past, this talk inspired me to take look at it again. Thank you for the interesting talk, well brought.
Really insightful talk about how the FIG works internally and is able to overcome and resolve their differences.
While I knew of the FIG, I wasn't aware of the full story behind it: you gave an excellent overview of its history and current events. It was also very enlightening to hear you explain what the newly passed FIG 3.0 structure is going to be like, including all the reasoning behind the changes. Plus your excitement for this milestone was just incredibly infectious, great job!
As someone who dips in and out of Fig, it was nice to hear about FIG 3.0. The fact that you only hear the drama, even when trying to avoid it, it was nice to know that the tech part was dealt with more at 97%.
Michael was enthusiastic, which was nice to see after all the crap these people have to deal with when trying to help a language and its community have a standardised approach to code implementation.
Thank you Michael, and thank you to everyone involved in the FIG!