-
-
Notifications
You must be signed in to change notification settings - Fork 4
Bad
The following ideas for the Angle language need some serious reconsideration:
But before condemning some progressive ideas as bad, ask questions about how to resolve ambiguity etc
Cleverness in code starts working against you as a code base and organizations scale
Overuse of significant whitespace
ambiguity in braceless function calls:
fibonacci number = if number<2 : 0 else fibonacci number-1 + fibonacci number-2
Could easily be a read as (fibonacci number)-1, resulting in infinite recursion :(
While Using Emojis in Mathematical Notation can be cute, it is certainly a bad idea to promote: Unicode is full of invisible character, potential diacritics, similar-looking glyps, control character that can break the display in a lot of annoying ways. Here is one way to fix it: Automatically all Unicode operators to their textual representation.
Are there situations in which broadcasting is detrimental? If so could it be mitigated by overloading the function?
Writing bad or ugly code should be discouraged systematically:
- by making dangerous and ambiguous constructs ugly.
- by giving compiler warnings
- by giving compiler hints of how to transform bad code into good code
Most Everything in computing is a trade-off. Identify yours!
Not everything in computing is a trade-off. Identify your false trade-offs, and break through established falsehoods