What's a front-end dev doing writing Go and why is the FBI here?
summary
A front-end dev prototypes a browser and Node pipeline that styles maps so only water pixels remain using the Google Maps Static API, scans outward with an Archimedean spiral to find the nearest safe-water pixel, converts pixel->world->lat/long via Mercator math, and ports the whole thing to pure Go (no external Go libs). Node takes 5–10s vs 5ms per location; the Go daemon runs at scale, fixes many MaxMind entries, and stops location-based harassment.
AI-written summary · about
chapters (9)
- 0:00The Kansas farm incident
- 2:26Understanding IP geolocation
- 4:48Correcting the data
- 6:41Developing a technical solution
- 9:00Mapping and coordinates math
- 12:13Building the tool in Node.js
- 14:06Transitioning to Go
- 17:07Performance results and benefits
- 18:17Interesting geographical facts
related talks
20mFrom Node.js to Go
37mSay No(de) to the Browser: Testing your Webapp Frontend Code Using Just Node
30mJavascript @ Uber
28mWriting and Debugging a Web-Based Multi-Player Game
46mArchitecture of a Modern Enterprise Node js Application
32mUI @ Flipkart: A Node Direction
45mFront-end keynote
01h 13mModern Backend for Frontend on Node.js