706 karma · joined July 4, 2014
Then you want phpstan or psalm. They do actual type checking and static analysis rather than style linting, and do it quite well.
If you do want an alternative for linting, Slevomat Coding Standard adds a huge number of highly-configurable and useful extra rules to PHPCS. I'm a big fan.
So I help with their implementation instead. Instead of building useless tech demos or starting primitive games I'll never finish, I look up the projects I do actually find useful and see what they need help with.
I would have bought an updated SE if they had been available at the time, but I don't regret the XR purchase.
At least now with the virus I'm 100% work from home, which gives me an extra 90 free minutes a day from not commuting.
Most developers seem to like them (brevity, locational grouping of concerns), so they tend to get treated as a default, but they're not the only option or the only one treated as a first-class choice. Like much of new-PHP, this also seems to be something largely borrowed from the Java world, it's hardly something new or invented by PHP.
I would think that's more due to the huge boom in Postgres popularity than any failing of Maria. For the projects that do still use MySQL, all the ones I know of are on Maria or Aurora rather than the Oracle implementation.
Not to even get into the ways that tests can help guide sensible architecture, especially for junior devs, because "this is hard to test" is the single most straightforward code smell for "this probably needs to be simplified or broken up".
The Closure example works because all your foreign symbols are coming from namespaced imports, which is to say you have a Module architecture and your only polymorphism lever is altering the namespace mapping to point to an equivalent module.
With Java and the like you have a Service architecture, so rather than importing symbols you're injecting services. Things that would otherwise be exported as bare functions tend to be written as classes so that they can be used as services.
While some languages can support either (i.e. JS is typically modular but there are things like Bottle if you want to write JS in a service-based way), it's not typical that a given application is going to support either simultaneously. Most languages have a clear idiomatic choice that you're likely not going to want to stray from to avoid headaches integrating 3rd party dependencies and developers other than yourself.
If we can accomplish such a shift, there are already much more worthy ends to put the money and political will towards: increased public transportation, rebuilding of streets to safely support non-vehicle traffic, public ev infrastructure, etc. Spending massive amounts to subsidize the few rich who could afford autonomous cars would just be further regressive policy.
Our newer applications are using litespeed instead, and we've found it to be significantly better. You basically get the features of a nginx + apache + varnish stack in a single easily managed service and with better performance too.
This was a major selling point for us when we switched to Algolia. The business people want to be able to manage things like search without having to go through the programmers, just like they manage GA/GTM and such.
Acting like everything is some kind of abstract theater designed to divide people on internet forums shows a disturbing detachment from the real effects that real events have on real people.
Perhaps some kind of... clearing house, which could be automated?
In the US we have a dozen startups for you to send money to your friends. In most of the world you just do a bank transfer.
I pay my rent and utilities with ACH, but I know people who still don't have that option and are stuck in the dark ages of checks or credit cards with processing fees.
I have accounts with multiple credit unions, and one doesn't permit online ACH transfers and another takes 3+ days to do it. I'm currently trying to consolidate those accounts but even that's a huge hassle. It's nearly 2020 and the form the payroll company my employer uses wants a voided check from me to change where my direct deposits go! I don't have checks and haven't written a personal check in probably 15 years.
We keep scratching our heads looking for that magic future tech solution to our problems (AI! AI for everything!) when we actually just need to fix adoption of the freaking 45 year old standardized solutions right in front of us.
Checks have always been an almost entirely American aberration and a bad solution on all sides. It took us almost 15 years after Europe to adopt chip cards, and we're still swiping in places and almost nobody requires a pin for security. NFC adoption isn't great either outside affluent areas. We're not lacking new financial solutions, we're lacking proper adoption of the solutions we already have and the rest of the world is happy to use.
You can write tomorrow's JS and CSS today while explicitly supporting whichever of yesterday's browsers you know you need to, and have the delivered code improve over time as older browsers are phased out without you having to rewrite it.
Not only is the human/societal cost high, consumers directly suffer as well as untrained contractors working irregular routes rush to meet unrealistic deadlines. Every day a different person in a rented van pulls up to throw armloads of packages at my building, may or may not be the right entrance, they don't know the place and have no time to check, before racing off to the next location.
Is HTML a monopoly? Is JS a monopoly?
Thankfully my tastes have grown since then, but I can't blame kids today for doing the same thing I was doing (though I can grumble that they have fancy cases and led controllers and aio coolers where I had beige boxes and holesaws and custom wiring and fish tank gear).
If it does, it means the process is struggling to produce chips at that speed, so the headroom is incredibly low and you can forget about overclocking.
Types just make everything easier to do right the first time.