Timeline for Google Code Prettify has been officially discontinued; it's time for SE to maintain their own highlighter
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2020 at 22:57 | vote | accept | Sonic the Anonymous Hedgehog | ||
| Sep 24, 2020 at 16:24 | history | edited | Ben KellyStaffMod |
edited tags
|
|
| Sep 24, 2020 at 16:24 | answer | added | Ben KellyStaffMod | timeline score: 8 | |
| Sep 21, 2020 at 12:51 | comment | added | Vadim Kotov | @JourneymanGeek And it's done | |
| Sep 2, 2020 at 1:47 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
deleted 10 characters in body; added 4 characters in body
|
| Aug 26, 2020 at 6:34 | comment | added | Journeyman Geek | I would guess it would be moving to highlight.js | |
| Aug 26, 2020 at 5:43 | comment | added | Sonic the Anonymous Hedgehog | @YaakovEllis What are the plans? Will SE begin maintaining a fork of Prettify on their own? (As you tagged this as planned rather than as under review, I'm wondering what the plans are.) | |
| Aug 26, 2020 at 5:30 | history | edited | Yaakov Ellis |
Planned
|
|
| Aug 25, 2020 at 7:59 | answer | added | Mizux | timeline score: 12 | |
| Jun 1, 2020 at 21:40 | comment | added | Nick Craver | I see a lot of discussion of forking here - for what it's worth that's effectively what happens every time we update our copy, hosted on our CDN...which is the case. If we did nothing, everything will continue working. Practically speaking, we'd most likely change this if and when it's a problem. I'd have a hard time saying it's a priority otherwise. Us being maintainers for not us (publicly) is a lot of weight/time (I know this far too well) - it's more likely we'd change to another project (e.g. highlight), but those have weight, perf, etc. that all needs investigation, and again: time. | |
| May 13, 2020 at 7:38 | comment | added | Cody Gray - on strike | I agree it's long past time to move beyond Google Prettify. As animuson said, it's been effectively unmaintained for years. Even pull requests that have been submitted to fix bugs and add features have been ignored. Certainly no maintainer has been actively fixing bugs or adding features themselves. But your justification for why SE needs to maintain their own syntax highlighting engine makes no sense. It would be far better and easier for it to be maintained by the community, where SE devs could just pull the latest version. This could be a fork of Prettify or some alternative. | |
| May 12, 2020 at 17:14 | comment | added | This_is_NOT_a_forum | Why would it go any faster with Stack Exchange? Why not a public open source project? Stack Overflow has counted 40 million software developers; it must be possible to recruit some of them (though offering stock options may no longer be "free" after Enron - I am looking at you, MDS). | |
| May 11, 2020 at 22:18 | comment | added | Sonic the Anonymous Hedgehog | @Makyen See above comment. | |
| May 11, 2020 at 22:18 | comment | added | Sonic the Anonymous Hedgehog | @animuson I've re-edited this to be a request to maintain an internal fork of Prettify. If this has already been triaged in the internal tracker, please reconsider this and re-triage it. | |
| May 11, 2020 at 22:16 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
deleted 212 characters in body; edited title; deleted 1 character in body
|
| May 11, 2020 at 22:02 | comment | added | Makyen | @SonictheStay-HomeHedgehog As currently written, it sounds like you're asking for way more effort than SE just forking a project and using the fork. Saying things like "make the highlighter home-grown" give the impression you're asking for complete development of a new highlighter. If what you're really asking for is that SE use an existing highlighter, but you just want SE to control the repository, that's a much different ask then how I read what you've written here. Frankly, as this is currently written, I'm surprised it hasn't gotten a hard "no". I'd suggest rewriting to clarify. | |
| May 11, 2020 at 19:33 | comment | added | Sonic the Anonymous Hedgehog | @animuson I've edited the post to list it as a possibility. Hope this request hasn't been internally demoted as a result of not mentioning it in the initial post. | |
| May 11, 2020 at 19:31 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 79 characters in body; edited title
|
| May 11, 2020 at 19:30 | comment | added | animuson StaffMod | I don't see why not. We do that with a bunch of other tools we use. | |
| May 11, 2020 at 19:28 | comment | added | Sonic the Anonymous Hedgehog | @animuson Can't it be possible for SE to set up and maintain their own fork of Prettify, so that they don't have to switch to a different one yet can maintain it actively? | |
| May 11, 2020 at 19:26 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 1206 characters in body
|
| May 11, 2020 at 19:21 | comment | added | animuson StaffMod | And... you expect it to take less time with a different solution? It's not like we're going to hotlink to the JS file elsewhere. It would still require a dev to take the time to deploy modified files. | |
| May 11, 2020 at 19:19 | comment | added | Sonic the Anonymous Hedgehog | @animuson I don't see why SE should stick with a highlighter that was only being inactively maintained. Bugs with it would take a long time to resolve because only random people did so randomly, and when they were resolved, it would take a lot of time for it to eventually get deployed in SE. The whole process would be drawn out and take 6-8 months-years. Also, now, with the archival, there's no longer a centralized effort to maintain it, so new fixes might just end up in a bunch of independent forks. For those reasons, SE should switch to a highlighter that is actively maintained. | |
| May 11, 2020 at 19:15 | comment | added | animuson StaffMod | I imagine that someone is simply going to fork this away and maintain it separately. To be clear: that hasn't been maintained by Google in many years. It was maintained by regular users who wanted to contribute to it and make it better. Nothing is stopping them from doing it somewhere else. And I see literally no reason to move away from it at this time, because what benefit does that achieve? Some random Google employee archiving it doesn't break anything. | |
| May 11, 2020 at 19:04 | history | asked | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |