Nothing new; VS Code is “the recommended way” going forward on macOS for RhinoCommon development. It works out of the box for Rhino 8 using the C# Dev Kit extension, but does take a bit of configuration (creating tasks.json and launch.json).
We have yet to update our developer documentation but it is on my list.
I’m using the built-in script editor and quickly realized it’s not the be-all-end-all solution. But it’s pretty good especially for those who are good with Python (I am not there yet). I know the advantages very well from using AutoCAD and having the built-in LISP code editor. They also had a built-in VBA editor (similar to MS Excel/Word/etc…).
Seasoned coders prefer VS Code. For me so far it’s been a time pit. I haven’t used it for anything relating to Rhino yet. A lot depends on how well the plugin(s) work and how well they’re documented. AutoCAD’s achieve neither. They (AutoCAD/Autodesk) are trying to use it as a replacement for the built-in LISP editor. It takes time to figure out and once you figure it out it doesn’t actually retain nor include many of the features that were in the built-in LISP editor. I’d rather see McNeel focus on the built-in Python editor. Editing code in an active session for me equals 4x faster development.