1,331 karma · joined July 31, 2014
Websites have been doing this for .. 20 years?
It's quite a different paradigm, yes.
I guess it's also just more instances to manage in total, instead of 1 + n it's 2n.
You _could_ run the dbs on the same instance but not using the same DB process, via containerisation perhaps. That way you could reduce your instance count while still keeping (somewhat) operational separation..
It's also not just the money. It's credibility by being invested in mozilla (and an investor who is invested in you having more successful funding rounds), it's the marketing and hype that come with it, it's the opportunities to employ people, it's the connections that come from being acquainted with investors and a tech giant, etc.
Firstly, this probably isn't correct, see this recent report from Finland: https://twitter.com/rcbregman/status/1258336749828419584
I'd also point out that the current situation forces an "all or nothing" employment system. In Aus, if you're working part time you don't quality for any benefits, so the incentive to work while on unemployment is lowered. However, with UBI, there _is_ incentive to work. You can double your income by taking up a part time job, instead of getting the same amount from working as you would from unemployment.
I'd also challenge you and say why do think reduced working hours is a bad thing?
Also, what about all the people with a lot of money who don't work?
All your arguments have been made before and discussed in depth.
> The problem being that our economy depends on these people performing such jobs.
The economy should serve the people. Shareholders may depend on it though :)
Your "inflationary spiral" theory is also unfounded, and has been shown previously.
> Why work overtime at McDonalds when your rent is already paid up for the month and there are so many fun video games to play?
This is a terrible strawman, but also maybe MCD should pay better or offer other incentives? They're not owed employees.
Someone suggested just nuke it and bring it back up on a fresh instance. Problem was gone! Everything running smoothly again..
You can't walk away from your day job at $BIGCO, start your own company and expect to get paid like you used to, it doesn't work like that (at least at the beginning).
Your pay is having a large % ownership in (what you think will be) a valuable company down the line.
This should be months, up to a year for 1-2 founder team.
Netflix has a (relatively) small number of large content pieces, and a CDN node would hold the hottest items.
IA has 430 billion individual pieces of data, on average much smaller than a piece of Netflix content.
So each "byte" transferred from IA is "more work" to produce, and less likely to come from some kind of cache.
Kind of how you'd say you have a dashboard for your business to see metrics in real time (as opposed to some kind of daily report).
I think that usage of real time is very common outside of a pure engineering sense, so you're being a bit of a stickler by being annoyed at this specific instance ;)
> One concern about the move from TCP to UDP is that TCP is widely adopted and many of the "middle-boxes" in the internet infrastructure are tuned for TCP and rate-limit or even block UDP. Google carried out a number of exploratory experiments to characterize this and found that only a small number of connections were blocked in this manner.[3] This led to the use of a rapid fallback-to-TCP system; Chromium's network stack opens both a QUIC and traditional TCP connection at the same time, which allows it to fallback with zero latency.[17]
QUIC is a standard, it will be stabilised in time.
TCP can't be improved on much at this point, and there are some pretty massive flaws in it that QUIC solves.
TCP isn't going away any time soon, or being "replaced" by QUIC, but for certain applications QUIC is going to be a massive improvement, albeit and an increased complexity and application size cost.
There are over 10 implementations of QUIC at this point in time, you don't have to go with Google's approach, https://en.wikipedia.org/wiki/QUIC#Source_code.