51

Lord Of BackEnd

Comments
  • 3
    Others still exist too, PHP makes the most noise
  • 7
    What is the blue fat hamster? XD
  • 2
  • 36
    Petition to rename golang into blue fat hamster
  • 4
    @blindXfish I always hated the mascot for Go. It was almost like they tried 5o make it as obnoxious looking as possible.
  • 4
    @LotsOfCaffeine petition approved
  • 2
    Some people like me laugh in Erlang and elixir
  • 5
    I am pretty sure, Putin wouldn't have mixed naming schemes, argument orders and error result conventions mixed up in his standard library.

    PHP is just the C of the web: An ugly mess constantly trying to get you to shoot yourself in the foot.
    But i still somehow like it (and made my own standard library that wraps theirs - so most of the bad stuff doesn't actually affect me anymore).
  • 2
    @Oktokolo Yeah PHP isn't so bad with a good Collection library (like Laravel's, or the PHP7 DS extension) to replace Arrays.

    Although I still get annoyed about all the places where magic happens, and how it gets in the way of static analysis.

    For example, with a large enough codebase, even with a good IDE it's hard to detect which methods/properties are not being used anymore, because someone thought $object->${"get".$thing}() was a good idea.
  • 3
    @Oktokolo Basically, all the normalization features of Laravel are amazing (Str::, collect(), etc), but then the magic makes it awful again (->map-> proxy, model-bound policies, attribute resolvers, etc)
  • 2
    @bittersweet to be honest you can technically do the same in a compiled language like .NET using Reflection.

    I'd literally murder you if you submitted a PR using it, but you could do it.
  • 2
    @kwilliams Yeah even a very strict language like Rust has dynamic dispatch and metaprogramming features like macros, the issue is that with PHP, the magic is:

    1. Widespread. Pretty much every framework uses either __invoke/__call/etc methods (Laravel/Eloquent), or docblock annotations (Symfony/Doctrine).

    2. Difficult to analyze, easy to cause bugs. Macros in Rust are still type safe, and can be statically analyzed.
  • 2
    You forgot to add Python.
  • 6
    @darkwind

    Ah yes python 2 & 3
  • 0
  • 2
    @Wizard1997

    Phoenix Wright the attorney.

    honestly, I didn't know either until I played MvC. Not model view controller.

    Marvel vs Capcom
  • 2
    @bittersweet also, this wins the internet for tonight.

    Fun fact: I created my ign based off of Kim Jong Il, 15 years ago.

    FearlessLeaderNK
  • 0
    @bittersweet
    A really good decision was, to not go all objects when starting to create my standard library replacement/wrapper.
    On the lowest level, i have one file per native scalar and one each for arrays used as lists (keys are always ints and non-sparse) or maps (keys are always strings).

    Building on top of a core following a single code convention is so much easier than when you have to remember, that substr can also return false (!) in some edge cases and that Iterators have to be pristine to be able to use them with foreach...
  • 0
    Here it is
  • 1
    @Oktokolo what is the name if the library ?
  • 1
    @bittersweet it s the first time that i stumble upon ds extension thanks, any thing else like please
  • 0
    @tsouhaieb
    It is a closed source asset of the company i work for.
    Don't tell them, that i will certainly keep using it if i ever change jobs ;)
Add Comment