Timeline for Goodbye, Prettify. Hello highlight.js! Swapping out our Syntax Highlighter
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2020 at 21:44 | comment | added | Oded | Main thing that changed is that Prettify has been discontinued. If that had been the case when I was going through my analysis, it would certainly not have been a choice and I would have had to evaluate a few different options. I trust @BenKelly made the right call here, and I am certain the architecture team assisted with that to ensure minimal impact. Fact is - a discontinued library is something that has to be replaced. | |
| Sep 11, 2020 at 19:21 | comment | added | Sonic the Anonymous Hedgehog | @rene Don't entirely think that was responsible. My later post in June about Prettify being discontinued by Google wasn't responsible either, in my opinion, as it originally alluded to creating a new home-grown SE syntax highlighter, which probably resulted in that post being internally demoted. I think the real trigger was Ham Vocke's post on CommonMark, on which someone had asked if syntax highlighting would be changed, to which Ham's response was "we'll think about it once CommonMark is fully rolled out", and I think it was placed on their internal radar at that time. | |
| Sep 10, 2020 at 14:13 | comment | added | Ben Kelly StaffMod | I've seen this post and have not forgotten about it. I'm touching base with our Architecture team to draft up a satisfying answer since they are the ones that made the final decision on the changes, given the benchmarks and size delta. | |
| Sep 10, 2020 at 10:51 | comment | added | Vogel612's Shadow | I assume a very large factor was the matter of prettify not being available as a "modern" package and no longer being maintained. That has a major impact on the maintainability of the application that's not directly obvious. The caching infra also changed between 2016 and now and four years are quite enough time for an OSS team to improve performance... | |
| Sep 9, 2020 at 20:08 | history | edited | jtbandes | CC BY-SA 4.0 |
added 3 characters in body
|
| Sep 9, 2020 at 19:22 | comment | added | rene | What also happened is Yaakov. I've managed to get some low-hanging fruit Prettify FR past him in January and that might have triggered him enough to realize they were on a dead-end. We're blessed with him as Community Advocate. | |
| Sep 9, 2020 at 18:00 | comment | added | Sonic the Anonymous Hedgehog | Well, for one thing, version 10 was released, which users EC2015, which is not supported by IE. However, as SE has long retired IE support (and removed all IE-specific code last year), that's not an issue. | |
| Sep 9, 2020 at 18:00 | history | edited | jtbandes | CC BY-SA 4.0 |
added 81 characters in body
|
| Sep 9, 2020 at 17:54 | history | answered | jtbandes | CC BY-SA 4.0 |