Recruiters are getting smarter

Received $1000 bill from google because my navigation app used google maps and the places search/autocomplete API to allow users to search for a place.

Switching to mapbox maps and places api.

#%$£€@&?

fuck this shit.
fuck the pile of arcane shit that is ARCore.
fuck the fucking pile of overcomplicated shit that is mapbox.
fuck the idiotic frankensteiny steaming pile of shit that is "arcore+mapbox lifesized maps unity project" or how is it called.

fuck this retarded scammy culture when a company is doing meetups with investors before even having a working prototype.

fuck this stupid fucking culture where there's no time for some actual, sensible, creative work, just grab these two repos from github and ducktape them together and we'll call that our demo which we will present to inverstors.

fuck every fucking molecule of this fucking world.

i just wanted to be creative. to CREATE stuff. CREATE, not pile up dumb half-baked nonprojects made by someone else on top of each other until the smell is too strong for anyone to see if it's actually reasonable or not.

i wanted to create stuff. make games. design and make them. actual interesting ones which have actual value (because fuck the retarded gaming industry who's imagination doesn't go beyond "u a dude who does pew pew to other dudes", but that's a different rant).

fuck this disgusting, retarded, idiotic, boring, lonely, cold, lobotomizedly stupid world where the only way to succeed is a shitty pile of shit scammy scum.

fuck me for not being able to learn how to be scammy scum, so I could be successful too.

working with Mapbox and so far everything works except displaying custom svg pointers for single points while clustering the multiples.
the documentation is only semi useful.
and my work-at-home coworker keeps meowing at me like that guy who wants to talk about TV shows whenever I'm working
I want a nap!

A simple sequence error made me suffer for 2 hour . Normally we think location sequence works as lat then long. But for mapbox ,they work in reverse.

A prototype I'm working on has a feature that fetches thousands of db rows. feature is running 'slow' according to everyone except me and my pc. I can speed up one section slightly by splitting a JSON array into two parts to reduce calls for the 3rd party assets because that's probably the cause.
Still doesn't 'work', says the hapless technoweenies. more troubleshooting.
The cause is Mozilla on a single computer chokes on a 3rd party api, in this case Mapbox.

How do I 'make mapbox run faster' on Mozilla?