Leaderboard

+1 that I mostly use package browsers for search and end up browsing packages based on the search. ie search for json and open the six "top results" in new tabs and start comparing them. For actual browsing of packages the tool I have gotten the most value out of is curated "awesome-lists". For example this awesome-json list. It's nice because it stretches the boundary around the packages; not only are packages for specific languages listed but similar technologies, helper tools around the concept, tutorials. You get a nice collection not just of the specific package but the ecosystem around the technology the package is related to. Would be interesting to build that curation into the package discovery experience.

I don't think I would find myself browsing packages without first looking for a specific package but I do like using tags as a way to find alternatives I didn't find in a direct search. As an example, at some point I got to the following VS Code plugin page which seemed nice but also had a set of tags on the right which I used to look at a bunch of different alternatives. https://marketplace.visualstudio.com/items?itemName=vscode-icons-team.vscode-icons

After living with this for 5 years, I have finally figured out the solution for the yellow plots. The root-cause of the yellow plots appears to be that the standard 256 color palette contained in a cluster coming out of an invoke node (FP.Get Image) become corrupted by the application builder on Mac OS X. The colors when running source code vs. when build into an application are very different. My workaround is to bundle the 256 colors directly in the source code. Of course, I am using 8-bit color. I would assume that if a higher bit-depth is needed, then a different set of reference colors would need to be bundled but I have not investigated that. I also suspect the yellow icons are similarly corrupted but I don't know how or if I could solve that. But at least now I can save my plots using LabVIEW 2020. I hope this helps someone else that has been frustrated with this. A screenshot of the work-around is below. I also have attached a screenshot showing the yellow icon.