Highcharts JS VS sourcegraph

Highcharts.js

For background, our environment is hosted in AWS and our data warehouse is in redshift. We currently use [High Charts](https://www.highcharts.com/) to render simple, in-app reports. We are pretty happy with High Charts, it is highly preferred over the other solutions by our dev team. We use [SciSense](https://www.sisense.com/) for the more advanced dashboards/reports both in-app and in a reporting app. I will simply say we are not happy with SciSense for a multitude of reasons. Finally for internal facing dashboarding and reporting we use MS Power BI. We will not use this solution for customer facing applications due to it's numerous UX "paper cuts" (a bunch of little things that combined make it a less than ideal UX, in our opinion).

Yep, the JS package is owned and maintained by Highsoft (www.highcharts.com), while the Python package is owned and maintained by one of my companies (HCP LLC). I’ve partnered with Highsoft, which means that you can get both the JS libraries and the Python package (which is a paid add-on for commercial use) from them ( https://shop.highcharts.com ).

My team plans to use High Charts https://www.highcharts.com/ . I don't believe they are Angular native, but easily wrapped with Angular.

Hey u/philthenin, thanks for the reply, yeah highcharts is also a cool library. Seems it is open source: https://github.com/highcharts/highcharts

its not php/composer, but if you can send the data to an html file, you can use HighCharts to turn the json data model into various nifty charts. It's javascript.

I would recommend Highcharts. It can be a bit overwhelming to begin with but it lets you build whatever kind of chart you want.

I am searching this repository

https://github.com/highcharts/highcharts

for Series.drawPoint and expecting a direct hit for

https://github.com/highcharts/highcharts/blob/29d2a83a5a997b...

practically I tried "Series" and "drawPoint" also.

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...