mapbox-gl-js VS Oat++

Good. Brave's fiddling with WebGL causes >50% of my bug reports from 1% of users.

[1] https://github.com/mapbox/mapbox-gl-js/issues/10518

[2] https://github.com/mapbox/mapbox-gl-js/issues/8377

Laravel and Mapbox GL JS

It originated as an open-source fork of Mapbox-gl-js before they switched to a non-open-source license on 8th December 2020.

Do you have programming skills? MapboxGL JS is a great library for stuff like this, you can really easily add a layer of GeoJSON data to a map. If you're looking for something less technical Google map lets you create custom maps where you can add a bunch of pins.

From the latest commits (not released/stable yet): git clone https://github.com/mapbox/mapbox-gl-js.git yarn install yarn run build-prod-min yarn run build-css Then use the generated mapbox-gl.js and mapbox-gl.css files. See CONTRIBUTING.md for more details.

> too bad it doesn't come with some code

Mapbox changed the license of their code last year I think to a proprietary one. https://github.com/mapbox/mapbox-gl-js/blob/main/LICENSE.txt

It requires a mapbox user license with billing enabled to use this code, let alone make modifications. But the source is viewable on github.

The software stopped being open source from v2 onwards. The new licence makes it merely shared source.

This GitHub issue where this change is announced provides a number of more in-depth explanations why this is a bad thing for most users of the software: https://github.com/mapbox/mapbox-gl-js/issues/10162

It's a bummer mapbox isn't open source anymore, now you're (and lots of other peoplare) are stuck pre-2.0.0 :(

https://github.com/mapbox/mapbox-gl-js/blob/main/CHANGELOG.m...

I looked at oatpp and drogon, which are both great, but feel too high-level for my purposes. I tried drogon and got something working, but it feels like too much for my requirements, as in particular I'd like to slot in my choice of Json and message-body handling. C.f. the simple approach in Crow, which I easily understand and build on.

With the right libraries, C++ could be a good fit for applications that want to expose a fast web API to things that need lots of compute (simulators, for instance) or I/O (interactive editing of large datasets). Projects like Oat++ and Crow give me hope that we might see such an ecosystem develop.

Lots of other options have been mentioned, but I'll throw Oat++ into the mix. I used it for this purpose and it was reasonably painless.

https://github.com/oatpp/oatpp +WASM ;)

cd "some/temp/path/for/repositories" git clone https://github.com/oatpp/oatpp.git cd oatpp mkdir build && cd build cmake .. (sudo) make install

Maybe use something like https://oatpp.io to create a REST API: C++ in the backend with this library to create a REST server, and the JavaScript/TypeScript frontend to ask for the information.

I've used OATPP ( https://github.com/oatpp/oatpp ) which worked nicely for setting up simple rest interfaces. Supports things like swagger & websockets out of the box. It's also on Conan which is nice if you use cmake. I can't speak to it's performance but it has about a 1mb binary size footprint.

As for your web problem, I have only used https://oatpp.io/ in the past but I'm sure there are more frameworks like that on the internet.