5

"if compiler can infer this, there is no need to add "x ->" , simply use it" ..AAAGHH FUCK YOUUUUU KOTLIN!! what else should i fucking not write? why do't you take a number of my employee and ask his requirements, maybe add a ShoppingKartApp.kt in your compiler next time? it will be completely inferred when i write "Fuck you" in the gradle.

And fucking companies are promoting this! I wonder how those devs are living there

Person A knows only that lambda is
{name:Type,name:Type->code}, and thus writes a clean code.

Person B comes says "This shit suck", writes "{ acc, i -> acc + " " + i }" ,goes away

Person A : "wtf is this shit? why it works?"

Please for the love of god, follow some rules! My first language was python, i love its zen:

- Beautiful is better than ugly.
- Simple is better than complex.
- Readability counts.
- Special cases aren't special enough to break the rules.
- There should be one-- and preferably only one --obvious way to do it.
- If the implementation is hard to explain, it's a bad idea.
-...

I just wish it follows at least one thing from python's zen : "There should be one-- and preferably only one --obvious way to do it."

Comments
  • 3
    *laughs in perl*
  • 0
    better fucking example
  • 0
    Loving devrant
  • 0
    Trailing lambdas are a bit wacky. Look on the bright side though, it could be plain Java :)

    Edit: I think I had the exact opposite experience learning Python

    Me: *starts learning python* How the fuck do I type check this expression...
  • 0
    Python is cool 😎😎
Add Comment