4 ms·
Wouldn't the value of education oriented languages be that educators can avoid specific complexities that get in way the of teaching core concepts? Once a stud
by sqeaky 10y ago
Wouldn't the value of education oriented languages be that educators can avoid specific complexities that get in way the of teaching core concepts?
Once a student has core concepts, then they have something they can build on with other languages that have more issues (potentially complex) stemming from practical problems. This prevents needing to learn two complex things at the same time.
Does pyret have easier to understand errors around syntax and typographical errors than Python? Most real languages won't search for similar identifiers to one that is misspelled and make suggestions, does pyret do anything like this (Other teaching tools do)?
- threatofrain 10y agoI rephrase your post in my head: The value of an education-oriented programming language is a boost to X education outcome relative to competing alternatives, and that "avoiding specific complexities" would be the mechanism by which to achieve your outcome. Therefore, (Pyret intervention) -> (educators don't struggle with language complexities) -> (education outcome) But first I want to know that there's even a difference between (Pyret intervention) and (Python intervention) on (education outcome).
- sqeaky 10y agoI think you are intentionally simplifying my statements, and the intents of educators, in an intentionally disingenuous way. If you are not being malicious, then I apologize, but the only way I can interpret you seems to indicate you have an axe to grind. Let me provide an example of a language complexity that hinders education, presuming education cares about things common to many languages like function, types, control flow, classes and objects. In C++ there is a strong separation of declaration and definition, this is required for silly, technical and mostly historical reasons. Teaching all of the concepts needed to make sense of why the compiler cannot elide definitions included twice is not useful when trying to teach about anything other than C++. Another example, in Java there is much boilerplate and an implicit package scope when scope specifiers are omitted. Most languages need little boilerplate and in order to understand why the implicit package level specification is bad (or good if you disagree with me), one must understand the concept of public and private already. For each language I know I can highlight such things. There is plenty of room for simplified teaching languages then extra courses to cover language specific things. None of this should be taken as a general defense of how programming is taught. I just mean that whatever problems there are, seem not to stem directly from the use of education oriented languages. I even think that classes focusing on specific languages should more closely resemble the real world, but not all people are ready for such detail.
- threatofrain 10y ago> I think you are intentionally simplifying my statements, and the intents of educators, in an intentionally disingenuous way. You're telling me that: (Pyret intervention) -> (educators not struggling with complexity) -> (education outcome) was so bad you think I'm dishonest? And you think that's the "only way" you can interpret the situation? And just in case you're wrong -- sorry? 1. Proposing a causal relationship: (independent variable) -> (dependent variable) 2. Proposing complexity: (independent variable) -> (mediating factors) -> (dependent variable). This is a fucking good start to any policy conversation. Where else do you find this online?
- sqeaky 10y agoI wanted to give you the opportunity to rebut, but instead you have degenerated to swearing, red herrings and an inappropriate breakdown to formal style rational logic. This discussion clearly has too many factors to be argued by formal proof. We cannot prove our premises nor prove an argument is formally sound. Therefor we must rely heavily on induction as many trades do, both software development and teaching are trades in many regards. Each often requiring action without the time or ability to formally prove and instead relying on large scale informal experimentation. The very existence of unit tests demonstrates how clearly practical programming cannot be formally proven and the existence of the whole fields of psychology and sociology ought to serve as basis for teaching impossibility to formally prove. This seems so obvious I hadn't felt the need to state it previously. I presumed you capable and understanding and knowing this. I inferred that someone choosing to represent the argument in such way must see the situation is too complex to break down like this and must be misrepresenting the facts or they must not be competent to discuss this topic. Because I presumed your competence I felt you must be misrepresenting the situation, I now see I was mistaken.
- matt4077 10y agoYour point wasn't completely absurd in the beginning, but now you're wilfully misunderstanding the arguments. It seems you're hedging some sort of grudge against educators?