Unfortunately, even though 320px iphones look to be less than IE users for us, 320px may we'll be required for a long time for WCAG (400% zoom at 1280px).
Unfortunately, I _think_ the majority of it comes down to the exchanges more-so than the data brokers.
I can't speak to exact numbers, but I believe we were quoted like 6 figures/year for JSE and I think we pay like 4 figures/year now…? Exchanges can and do charge whatever they want…so when you need realtime data explicitly, even if you skip the data brokers, you'll just have to pay. You legally cannot use data for profit from some exchanges (if I recall, JSE is one). Some exchanges seem to have a majority of their revenue coming from data licensing.
Oh, then don't get me started on ISINs and all the failed "open source" attempts to not use ISINs and how some ISINs can be used without licensing while others require it.
---
My company is mostly AU/NZ (mostly because of tax, but quickly growing), so most of these data services didn't even support us until the past few years. We use a combo of like 10 data brokers to piece together coverage and we're still missing huge datasets (unfortunately Finnhub doesn't seem to cover any of them, but will look).
Luckily I focus on the Frontend/UX of our product and avoid this drama, but do feel free to reach out (contact via profile; I'm easy to find).
Good luck! I do like the idea of education, will follow. Even though I've worked in this industry for 5 years, I still find new stuff on the retail investor side of things. We'd love to educate more in our product, but we just partner with people instead..
My company pays a lot of figures for xignite and we cannot make this data publicly available without some restrictions (it would cost a lot more to do so).
My purely non-legal take is we can distribute price and metadata for instruments relative to a user's portfolio or a defined demo set of data or charts to yours, etc, but not freely distribute price data without an attribution behind it. I _suppose_ a user could add literally all 300k instruments we support to get the price data and that would violate our agreements (similar stuff has happened before, just watch it), but we'd just have to deal with the user via our TOS.
Good luck, unfortunately the next level of APIs for financial data and licensing fees can be annoying, from almost free to like 6 figures overnight. Some exchanges are much worse than others, like arbitrary pricing based on how large your company is…
I think if you use them 100% of the time alongside eslint dependency arrays are really hard to get wrong. If you rarely use them, you always get them wrong.
Nope, I have a repo consuming 10+ workflows, 3 shared actions, and a handful of private workflows (the way private workflows sucks now though, don't recommend–basically just a git clone into your Github Action).
This is all non-Enterprise, private repos, no clue in GHEC/S.
Absolutely agree. Docs are either perfect (5%) or…completely obscure (95%). I can't tell the difference between Github Actions and API documentation in places, but I desire functional examples. No clue where I built it up, but I'm comfortable now…lots of trial and error.
For a lot of Github Actions, I actually follow the Github Roadmap through to implementation as the PRs actually have good examples in them… https://github.com/github/roadmap/projects/1
I use a lot of composite actions in the same repo as well as composite actions across repos.
Eg. `workflow1` and `workflow2` both call `composite/action`:
.github/workflows/workflow1.yml
.github/workflows/workflow2.yml
.github/actions/composite/action.yml
The only missing bit in that is a bit more support in a composite action: `if` and a few other keywords. Also, it's a bit annoying to access private across across repos.