Even then, one of the great things with PHP was the shared-nothing architecture. A whole class of bugs simply do not exist when there is no concept of shared memory between requests.
People would be terrified of it now but patching a change by copying a single file over FTP was the norm in the 00s. The change would be picked up on the next request.
Want to roll it back? Just rename `file.php.bak` to `file.php` and you're golden.
I grew up building random stuff using a hodgepodge of incomplete Lego sets that my parents got from car boot sales. Later they bought me some new sets as well, but sooner or later all the pieces ended up in the big box anyway.
I don't think I would have become a programmer, if not for those weekends when I would sit in front of a desk-sized box of bricks with no instructions and imagine what I could build.
35 years later, I still browse the local Lego store from time to time. But most of the sets I find nowadays are only intended for a single configuration, usually associated with a specific IP like Star Wars or Harry Potter. Too fragile, too many stickers and custom pieces. I'm glad that the proceeds from these collectible sets help Lego stay profitable in the smartphone age, but God I miss those random Lego weekends. Brb, gotta ask my dad whether he still has that box of old bricks in his attic.
I've purposefully bought a lot of the old lego technic universal building sets second hand for my son. They come with multiple ideas and the type of design is less finished and more prone to modifications.
I want my son to play with legos by creating his own designs, not by following a set and then shelving it
They still sell large boxes of general-purpose bricks at toy and grocery retailers around the United States. They likely don’t sell nearly as well, but every time I’ve gone to buy legos there has been one “plastic tote” box of legos for sale, no instructions just bricks.
Keep a few throwaway Hotmail/Outlook addresses in your password manager, in case you need to use a Windows PC that demands a Microslop account. That's about the end of their usefulness.
Just like Internet Explorer used to be the program you used once -- and only once -- to download a proper browser.
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. :)
How old this this framework? Sounds like they never got the news that opcache has been part of PHP since 2013.
reply