Re:Making bracket pair colorization faster
by duxup on Wednesday September 29, 2021 @01:13PM
(#28696737)
>Curiously, some bits of code went kinda full circle in the process
"Oh I see why. .. yeah that's a better idea."
Happens to me all the time ;)
Re:Making bracket pair colorization faster
by int_19h on Wednesday September 29, 2021 @05:24PM
(#28700160)
Not in that sense. The VSCode extension didn't fork the debugger in question - it took the original code verbatim, and simply wrapped it into a DAP adapter.
Ironically, when we rewrote the Python debugger later, we did the same exact thing with pydevd (https://github.com/fabioz/PyDev.Debugger), and for the same reasons - why reinvent the wheel when you can take an existing one that's already better than anything you have? It's also better for the ecosystem, since improvements all flow upstream.
Re:Making bracket pair colorization faster
by sillysaurusx on Wednesday September 29, 2021 @05:11PM
(#28700013)
Code going full circle is the basis for multiplying coding estimates by pi: https://news.ycombinator.com/item?id=28667174
https://devblogs.microsoft.com/python/don-jayamanne-joins-mi...
This can still be seen on GitHub - if you look closely, the official repo at https://github.com/microsoft/vscode-python is a fork!
Curiously, some bits of code went kinda full circle in the process - vscode-python reused the (open source) Python debugger written at Microsoft for Python Tools for Visual Studio.