It sounds plausible, but they really need to spell out exactly what the formatting requirements are, because it can make a huge difference in how efficiently you can write the json out.
An unchanging community is a dead community, period.
Attempts to "preserve" a community, both online and offline, tend to end up preserving unhealthy power dynamics within the community as well, which would have been slowly replaced with something else if you had just let the community evolve (or disappear) naturally.
Often, members of the community who benefit from the status quo are the ones who cry the loudest for such preservation.
That looks like a rather flat trapezoid for something that fell from high above.
With a fast-moving object, we can usually tell its trajectory across the map much more accurately than we can tell where along that trajectory it impacted the ground. See: MH370.
Maybe fits the "DoD is shooting something at some kind of incoming drone" explanation - they know they're shooting _from_ the top of the trapezoid but in terms of direction, only that they're vaguely facing south. (Doesn't really explain why the TFR doesn't extend into Mexico though.)
So while most of the software is open source rather than proprietary, you still have a fair point that customers pay for support (as they do with most enterprise products). One could theoretically use the product without first-party software updates, managing the open source oneself... but that would have practical impediments (and runs counter to the all-in-one simplicity that customers value in the Oxide product).
Two points about your last point. First, software improvements benefit all customers; as the business grows, the effective cost per customer shrinks. Also, most customers grow their Oxide deployment or will replace hardware after a depreciation cycle. The sustainability of investments into the software (and the product generally) is on solid ground.
Back in the 90s and 00s, lots of companies churned out software products that were sold once, supported forever. It was a sort of Ponzi scheme, supporting old customers with money from new customers. Which was okay during a period of high growth. But sooner or later the market matures, growth plateaues, and the cost of ongoing maintenance becomes a much bigger problem.
Right now you're growing fast and swimming in VC money, so this is probably not an issue. At some point, though, you might find that even hardware depreciation cycles don't provide as much of a cushion as you hope they will. In an economic downturn, people might suddenly realize that Oxide hardware actually remains serviceable much longer than they expected. :)
That's not enough. As the article explains, SVGs can reference external resources. So you also need to prefetch those external resources, recursively, if you want to be thorough.
OP here. Roughly 50GB in db size. Fairly standard queries (full-text search + filters). Most queries are on the order of 10-100ms. Some more complex ones involving business logic exceeds 100ms.
This is well within my budget, but it sounds like there might be room for improvements?
https://en.wikipedia.org/wiki/Deviled_egg
reply