160 reputation
6
bio website fresheneesz.110mb.com
location
age
visits member for 3 years, 3 months
seen Sep 9 at 23:49

Aug
19
revised Keep a programming language backwards compatible vs. fixing its flaws
added 40 characters in body
Aug
19
revised Keep a programming language backwards compatible vs. fixing its flaws
added 934 characters in body
Aug
19
answered Keep a programming language backwards compatible vs. fixing its flaws
Jul
16
comment What negative consequences can arise from this language design rule?
@jco You might be interested in the SO chatroom I started talking about my programming language Lima chat.stackoverflow.com/rooms/57376/lima
Jul
16
revised Is duplicate syntax for defining named functions a bad language design decision?
deleted 1 character in body
Jul
16
answered Is duplicate syntax for defining named functions a bad language design decision?
Jul
15
awarded  Commentator
Jul
15
comment What negative consequences can arise from this language design rule?
This is definitely an issue that has caught me a few times in javascript. I think this rule would be a good addition. I do agree with doval, tho, that the inconsistency of allowing hoisting for functions but not for variables is a downside. In fact, javascript doesn't always hoist functions (ie when they're declared as variables). The variable is hoisted yes, but the value isn't. In my programming language, Lima, any constant variable is hoisted. I'm gonna add this check in my language, thanks!
Jun
23
comment Is spying on tested class bad practice?
"I want to test the complex function .. without having to provide sane parameters for the sub functions" - I don't get what you mean there. Which sub functions? Are you talking about the internal functions being used by the 'complex function'?
Jun
21
answered Is spying on tested class bad practice?
May
24
awarded  Critic
May
24
comment try-catch in javascript… isn't it a good practice?
I can't disagree more. Try-catch is one of the biggest advances in programming expressibility in the history of programming languages. Node.js missed the boat on good error handling by using callback-style errbacks. What they should have used are futures.
May
6
comment If null is bad, why do modern languages implement it?
+1 for enumerating all the possible ways the problem can be solved
May
5
comment If null is bad, why do modern languages implement it?
Ah i see, so you're not saying that requiring values to have a default value is bad in any way. You're saying allowing only one default value (null) is bad.
May
5
comment If null is bad, why do modern languages implement it?
Well, one root non-primitive type at any rate. Why is this a weakness from a language perspective? I don't understand why this fact requires that every type have a default value (or conversely why multiple root types would allow types to not have a default value), nor why that is a weakness.
May
4
revised If null is bad, why do modern languages implement it?
added 410 characters in body
May
4
answered If null is bad, why do modern languages implement it?
May
4
comment If null is bad, why do modern languages implement it?
Null is not evil. If you watch his misleadingly named famous speach "The Billion dollar Mistake", Tony Hoare talks about how allowing any variable to be able to hold null was a huge mistake. The alternative - using Options - does not in fact get rid of null references. Instead it allows you to specify which variables are allowed to hold null, and which aren't.
Jan
30
answered Teaching logical/analytical thinking
Feb
10
awarded  Supporter