2,272 karma · joined May 2, 2014
I even took a class from a professor who regularly testified to congress on the topic.
Paper ballots all the way.
Too bad too, since the half of undergrads who weren’t cheaters were the nicest, brightest, salt-of-the-earth people.
So if western B2C companies have to pick just one platform to start with, it will almost always be iOS. This lets them then port that initial app to Android once they are established with western audiences, so they can also serve the (much larger, much less profitable) rest of the world.
https://www.wired.com/story/signal-mobilecoin-cryptocurrency...
Works great for the upper classes - keeps the price down for those fancy Michelin dinners.
Swift async/await is quite nice.
The Actor stuff is IMO way oversold - reentrancy issues make it not actually useful for the things that they claim, like querying a database. It’s still a useful construct to have, you just need to be aware of what it does or doesn’t provide.
It's not super resource-intensive if you run it yourself, but I can imagine how a "buy vs build" decision for other apps could easily lead to a $$$ monthly subscription with a specialized 3rd party.
It’s the cost of the developers who fix bugs and keep the product moving forward. Those cost a lot more, and you need them regardless of where your instance is hosted.
I have 500-600 users on my app and have never paid. Maybe it’s different at scale?
From what I can tell, the average is about $8/user/month. And no, I don’t understand it. For my former employer, a large public university, these services would cost about $240k/month before any special discounts. For that price you could hire a whole team to build and run your own product. Make it make sense.
This guy found an underserved market opportunity, built something, got some success marketing it, and made a whopping total of $40k.
Meanwhile the FAANG guys are making that every two months, without all the risk.
This gets exploited all the time when companies use FOSS licenses to get traction, then pull the rug and switch to a more restrictive license once customers are locked in.
On the flip side, if a company tries to be honest from the beginning by using BSL (or similar) they get endless grief from religious zealots.
AGPL is the magic unicorn license that is just restrictive enough to protect you from your competitors, while still passing the FOSS religious purity test.
One example is that the Matrix project recently took a budget hit when the core team apparently lost a big bid to a "large system integrator" who seems to have used their own open source code to bid against them.