400 karma · joined April 2, 2013
With Phpstan and Psalm already in the space I'd like to see more differentiator features than 'written in Rust' - there are certainly advantages to that, but the disadvantage of not using PHP is it's harder to get contributions from the community using the tool.
Cool project overall!
I'm probably guilty of some of the bad practice: I have fond memories of (ab)using XSLT includes back in the day with PHP stream wrappers to have stuff like `<xsl:include href="mycorp://invoice/1234">`
This may be out-of-date bias but I'm still a little uneasy letting the browser do the locally, just because it used to be a minefield of incompatibility
Is it really that hard to grill bread? Nope, but you have to pay attention somewhat to stop it burning.
Once you hit a certain volume of usage, an automatic device makes a lot of sense.
Amazing to see it's still going!
There are N-1 red balls out of 99 remaining, so the probability the next ball is red is (N-1/99).
The possible values of N are evenly distributed [1...100] (we discount the N=0 case because we drew a red ball)
The total probability that the next ball is red is the sum of the individual probabilities divided by cases:
P = SUM[1...100](n-1/99) / 100 = SUM[1...100](n-1) / 99 * 100 = SUM[0...99](n) / 99 * 100 = 4950 / 9900 = 5.0
So red or green are equally likely
In the UK you dialled 2580 from your (non smart) cellphone, it would hang up after a few seconds and you’d get an SMS right away with the ID of the track
We have different ideas what 'microservice architecture' means, I guess.
One of the key points of UUIDs is to be able to generate (probably) non-conflicting values without coordination
If high-speed electrified rail links exist between cities, they can become much more attractive than long car trips.
On-demand transit can fill a lot of gaps in rural areas (e.g. on-demand bus routing)
Poor guy
You... don't think you can install your own software on MacOS?
As you point out, the lack of properties solves that. The use of a singleton probably relates to the identity issue
> at this point you may just as well skip the entire object part as I don't see why exactly it's needed for an identity check.
PHP only has 8 types (string, int, bool, float, array, null, resource, object) and they're not likely to be added to (resource is largely deprecated).
Given that, object is the only one that's not likely to be abused by relying on the actual scalar value. Keeping it as a singleton ensures that === will still work (it requires 'same instance')