At least he went down fighting (https://archive.is/M4nek, the op-ed referenced in the article). That's an impressively dignified response to a gobsmacking shift in public opinion. In his position, I might have given up and gone full Two-Face.
My local family owned tacoria now sells a $14 burrito in LA. The rest of the prices outlined in this article are also on par with LA pricing. It's hard to find a more expensive place to live the California.
That would make logical sense; instead we will tax oil company profits and disincentivize increasing refining capacity. It's pretty amazing our governor didn't care about this issue until it was an election year. Now all of a sudden he is sick and tired of this price gouging.
I think the governments all still want strong encryption, but with a man-in-the-middle style eavesdrop point at the tech company where the NSA or whoever can perform their inspection on all the communication flowing through the service. This is certainly not to protect the children but more likely for terrorist monitoring with the added bonus of vacuuming up your dick pics. It should be more secure than back-dooring AES/RSA/ECC, but it still has the potential to compromise quite a bit of information and basically does away with what little privacy any end user has left.
Of course they do. They want a mathematically perfect, impossible to crack system, that also happens to have a common key that works for everything, that they alone own. And by 'they', I mean their government. Not enemy governments.
What happens when (not if) that common key leaks or is abused is not their concern. Until, of course, it invariably happens, and they find their citizens having their bank accounts siphoned, their agents being discovered and blackmailed for their basic 'civilian' internet use, etc.
There is no common key in the MITM scenario. It's still securely encrypted using over the counter algorithms, but instead of the end users exchanging keys, you exchange with the MITM and different key sets are used by both parties.
Honestly I've had the opposite experience. With so many community actions available, I've had little trouble finding anything I could dream up. Sure, some of the actions features are a little immature but they are improving with time. The uptime issues are annoying and I feel like the lack of transparency is not helping that situation, but as far as CI solutions go, I feel like my move to actions has been a great way to get up and running with far less effort than other offerings like Code Pipeline.
This is one of the primary reasons most people hate PHP. Let me ask a simple question: What does the documentation for your homegrown framework look like? Having worked for several organizations that decided to roll their own framework in PHP, it is an absolute nightmare. No one else knows how it works or how to use it and it usually comes with no documentation. Furthermore, you don't get any updates or bug fixes unless you write them, taking time away from working on the project that is being held up by your homegrown solution. There are plenty of fast, low bloat, PHP frameworks to choose from: Phalcon, Slim, Luman and Silex just to name a few. I guarantee they all have better documentation and support. If you need some custom functionality, extend one of these existing solutions to suit your needs. Please, please stop reinventing the wheel for production code.
I agree with everything you've said, with the exception that it doesn't fit our usecase.
We run and maintain several Symfony applications, we're very familiar with frameworks, how they work, their strengths and weaknesses.
This was a carefully considered route:
We wanted to be writing PHP code with high performance and strict response time requirements, as such:
* Symfony was instantly ruled out.
* We knew we would struggle to do this with raw PHP but didn't want to retrain the team to learn a new language (our thinking being we would likely write something inferior and insecure).
* We considered Phalcon and Swoole and ultimately decided on Swoole as we found Phalcon a bit too opinionated. That being said, Swoole's documentation isn't great so we've had to internally document it. (We will probably push a few documentation PRs for swoole-src when we're done).
* We didn't trust a big framework to have zero memory leaks, which is a key issue for long running Swoole processes, since it's not a typical issue for the single-use PHP processes we are used to.
With regards to documentation, it's very well documented (with documentation explaining the reasoning behind each class, usage, pitfalls and how it fits in to the larger application, and documentation for the wider ergonomics of the application, debugging, performance considerations, etc), with a 96% test php-unit coverage for the Framework.
Your concerns are very well received and are concerns we have had from the beginning. Constant vigilance and a deep respect for my co-workers is what keeps this little project on the straight and narrow.
It's part of a live video platform for a gaming company which needs extra information to be overlaid on top of their live stream (for the customer in-video frame performance is incredibly important: the stream run at 30fps (so a maximum of 33ms per frame) and the overlay information has to be generated in 11ms or less)
We did originally consider writing it in Rust (it would have been my personal preference) but the consensus was that since the rest of the tooling for this customer is in PHP we didn't want to add a skillset they didn't have internally if they were to move away from us in the future (we aren't big on needless vendor lock-in and prefer to compete on quality and service).
We experimented with PHP7.4 and Symfony / Laravel and found that we didn't have the performance leeway we needed, even with preloading / opcache.
We opted for Either Swoole or Phalcon, tried them both and found that Swoole was more to our liking and was somewhat more performant than Phalcon in our real-world testing.
We are exposing Swoole directly to them within their VPC, so we were able to do away with NGINX as a reverse proxy as well and have Swoole handle the HTTP request phase and HTTPS. We were able to make heavy use of Swoole\Table to save superfluous trips to Redis and run a Redis synchronisation process in a coroutine thread when the concurrent number of network tasks drops below 16.
Our end service response times (including network overhead) are around here:
- Mean response time: 4ms
- Fastest: 2ms
- 99th percentile: 9ms
- 999th permille: 10ms
One unforeseen side effect is that it has a crazy amount of scalability built in by default, the 8core machine the process runs on can easily scale up to 15,000 concurrent requests (as in 15,000 requests per second) without going over 15ms for response times, and can scale up to 45,000 concurrent requests before things start to "break".
Also: Our issues with Laravel / Symfony weren't just performance, but also statefulness and memory leaks. Circular references, etc, which persist throughout multiple network requests. In a normal PHP flow using php-fpm or apache-php-cgi this isn't an issue: The PHP process is created, used and thrown away. For a Swoole setup, these memory leaks quickly get out of control and cause performance issues, instability and very occasionally superfluous garbage collection runs.
I would actually argue there's a good chance the person you're replying to is "doing it right":
- they're using Composer packages
- they're using the fairly well-documented, popular Fastroute for routing
- they're using the well-documented, PSR-11-compliant PHP-DI dependency injection container
- they're using the well-documented Swoole for async programming
In other words, they're rolling their own framework not from scratch, but on top of well-understood components that largely follow -- and largely require programs that use them to follow -- what's considered to be "best practice" in the PHP world.
I get that there's a lot of crap PHP out there, historically, and that frameworks have helped dramtatically reduce that. But it turns out you don't actually have to start with a framework in order to write well-structured, well-commented PHP code -- you just have to have a commitment to doing it.
I'm working on my own PHP microproject right now and I'm pretty flagrantly violating some "PHP the Right Way" conventions; the project doesn't even Composer and -- horror of horrors -- the autoloader isn't technically compliant with PSR-4. I'll pause for everyone to recover from the fainting spell. I don't think anyone else is going to ever have to maintain this -- but I'm also pretty sure that when I'm finished, it will actually be more understandable and maintainable than some Symfony and Laravel projects I've worked on in the past. It's not the fault of those frameworks that people build inscrutable undocumented modules on top of them, but it still happens.
And frankly, I understand why someone can appreciate Symfony and Laravel and friends and still say, "Wow, that's... just... a whole lot." (If you initialize a new Symfony 5 project, before you have written a single line of your own, your project is already at around 160K lines of code.) And they can look at microframeworks, especially modern we-must-comply-with-all-PHP-FIG-mandate ones, and say, "That isn't a whole lot, yet it kind of feels weirdly heavyweight for what comparatively little it does."
> Please stop reinventing the wheel...
You learn a lot by reinventing a wheel. Sometimes what you learn is that a lot of the existing wheels are actually monster truck tires, tank treads, or jet skis.
Friend of mine. Slim framework not updated anymore. Cannot make it work in recent php versions, so a fragment of a big corp needs to be maintained and isolated. I know, happens everywhere
If you mean the framework named Slim, its last point release, according to their web site, was less than a month ago, and it says that the minimum PHP version requirement is 7.2. It's possible your friend isn't able to upgrade the application to a supported version of Slim?
Does this require installing google play and other google services to work?
Edit: https://grapheneos.org/usage#android-auto