you know what i was just thinking about? programming syntax and international developers. Between PHP and jQuery, how do european and british developers deal with the $ symbol? I imagine the $ is not directly on your region-specific keyboard. Does your IDE map the € or £ to the $ when you code? Do you just use second keyboard with a US layout? You’ve gotta use the $ symbol hundreds of times a day, so it needs to be easy
“Haha lol banks use 60 year old programming languages!”
Yes, young whippersnapper, that’s because they need things to be reliable and not change all the time, the code probably has to run for another 60 years.
“Modern” devs could learn a lot from not trying chase every trendy new framework and every shiny new programming language.
@thomasfuchs@nattiegoogie Sheesh, people love to rag on #Javascript so much and turn a wilful blind eye towards all the effort put to improve the language.
Wouldn't you agree that ES6 is nothing like the JS of yesteryear, just as #php 8 is nothing like the php 5.4 shit I had to write when I first entered the industry?
Do you own or work for an organization looking for promotion opportunities in the PHP, Drupal, and Symfony communities? If so, please contact us. https://www.symfonystation.com/Contact :symfony: :drupal: :php: #Symfony#Drupal#PHP
#PHP
now we have the ability to properly type properties and with @Crell & @ilutov 's property hooks RFC, that I hope will pass (https://wiki.php.net/rfc/property-hooks),
I wonder if, at some point, it will become possible to declare properties in an interface....
Or am I the only one who thinks that makes sense ?
Bathing in the #Stripe docs these days and they have just an avalanche of low-level information & #API docs but what I really need is a high-level "these are the general steps you'll take" which then lead into those detail pages.
Tried out a bit of #Pest today. A bit weird to write that less but get so much. I think I have to get used to this. But I see me writing more tests with Pest. Looking forward to work more with it!
I found myself using dark magic to modify a protected variable from a library that doesn't allow any configuration. I feel that this is one of those "to break the rules you need to know them first" cases. I very well know this isn't good practice, and I know why, but I don't want to fork the whole thing only to change 2 urls on 2 protected variables when the rest of the library works fine.
#Psalm was all, like, “I found some MissingParamType issues. I’ll be happy to fix the types for you.” So, I ran it with --alter, and it proceeded to change mixed parameter types (that conform to an interface) to stringd.
That’s not my typo; there is a “d” on that end of that type name.