>accessing nil in the 21st century? not my problem
>map(), fliter(), reduce() for arrays? do it yourself like it's the 1970s. Not my problem
>enums and sum types? not my problem
>concurrency over OS threads? not my problem
>pattern matching? not my problem
>functional features? not my problem
>error handling in the 21st century? not my problem
>conditional compilation? not my problem
>a non retarded way to use c code and syscalls? not my problem
>unused var? this is dangerous, sorry can't compile. Accessing nil? not my fucking problem.
>half the size of your binary is unnecessary because we don't know how to write a compiler? not our problem
>extending your types with traits? not my problem
>readonly function params? not my problem
>function overloading? not my problem
>slower regex than even python? not my problem
>macros? not my problem
>want to use a single function from an imported package? all the package code is going to be embedded in your binary. Not my problem
>inlining? not my problem
>map(), fliter(), reduce() for arrays? do it yourself like it's the 1970s. Not my problem
>enums and sum types? not my problem
>concurrency over OS threads? not my problem
>pattern matching? not my problem
>functional features? not my problem
>error handling in the 21st century? not my problem
>conditional compilation? not my problem
>a non retarded way to use c code and syscalls? not my problem
>unused var? this is dangerous, sorry can't compile. Accessing nil? not my fucking problem.
>half the size of your binary is unnecessary because we don't know how to write a compiler? not our problem
>extending your types with traits? not my problem
>readonly function params? not my problem
>function overloading? not my problem
>slower regex than even python? not my problem
>macros? not my problem
>want to use a single function from an imported package? all the package code is going to be embedded in your binary. Not my problem
>inlining? not my problem
