worace
But that doesn't really matter when we talk about "replacement" because these people don't "do" they simply "own".
They're not concerned about being outpaced at some skill they perform in exchange for money...they just need the productive output of their capital invested in servers/models/etc to go up.
But the problem is, once they exclude all that stuff, there's just not a lot left. So you end up with inane garbage like this account being the most popular content on the platform. Like the whole platform is just Ben Shapiro and drop-shipping scammers. Really paints an "emperor has no clothes" picture of what's going on on Facebook these days.
You may remember Foursquare from that check-in app in the early 2010's. The check-in app is still around but these days we are focused on building best-in-class data and analytics products for working with location. A few highlights include:
* Global POI dataset representing rich attributes for 100mm+ venues in the world
* Pilgrim SDK for powering location-aware mobile app development
* Unfolded Studio (recent acquisition) for stunning visualizations and fast spatial analytics in the browser
In 2020 we completed a big merger with Factual (https://www.factual.com), and recently added the excellent team from Unfolded (https://www.unfolded.ai) to the fold (badum-tss). I've been an engineer here for 4.5 years and have gotten to work on a ton of great projects in that time. If you're interested in location and geospatial data problems at internet scale, it's a great place to be.
We're hiring for a ton of roles across all disciplines of Software Engineering and Data Science: https://foursquare.com/careers/. I'm happy to speak to anyone who's interested. If I don't know about the role you're looking for I can route you to the person who does. Email me at horace at foursquare.com.
The problem with this is it still requires a running server process colocated with that sqlite db in order to service requests for individual tiles, like what you'll receive from a client-side mapping library.
This project has a lot of different parts, but one of them is a spec for serving this type of data at low latency without a server by combining a custom packing format with S3 range-get requests to read individual tiles direct from blob storage. So that is certainly interesting for this kind of use-case.
> You need to open a JIRA ticket to get a namespace, create GPG keys, register keys in a keyserver, and add SBT plugins just to get a manual publishing process working. Itβs a lot more work than publishing to PyPI or RubyGems.
It's a little annoying to have to go through that, but you only have to do it once per domain, and the turnaround from the people who manage the sonatype jira is usually pretty quick. In return the ecosystem gets a lot of protection from the kind of exploits you mentioned.
I'm happy with my Emacs setup, and in particular I spend a lot of time editing code in other languages as well as text docs like markdown or org. In the past, while this workflow was great for most things, I'd usually have to switch over to IntelliJ for serious scala editing. But now I don't have to any more!
I know it's all old hat to the IntelliJ crowd, but I just don't like using an industrial IDE if I can help it. Metals lets me stick with a lightweight editor like Emacs or VSCode while keeping the great tooling that a powerful type system like Scala's enables.
I still fire up IntelliJ from time to time for certain types of mechanical refactoring, but as Metals has improved I find those cases come up less and less.
Big props to the Metals team, and thanks for all the hard work.
To quote from the NYT article lede: "WASHINGTON β The Federal Communications Commission voted 3-2 on Thursday to invite public comment on a set of proposed rules aimed at guaranteeing an open Internet, prohibiting high-speed Internet service providers from blocking or discriminating against legal content flowing through their pipes. "
Am I reading this wrong or does that seem to say the opposite of what WaPo is saying?
Here's a blog with a little info on the practice: http://reykjavikdailyphoto.blogspot.com/2008/10/could-not-be...
Basically the same principle except in this case the transport system was the river and the land usage is optimized to give as many people access to it as possible. Interesting to see the idea cropping up again in reference to modern public transit.