What about it?
So you don't really know what I was originally talking about yet you continue to act like you do? My point was in a response to the OP's implication that somehow the original OOP literature was perverted by…
>Maps can be represented 1:1 as e.g. JSON. Any JSON data is basically a big map data structure. It's one function call instead of hours of writing ORM classes or custom serialisation methods just to send some data over…
A poor model for computation that is pervasive in the industry. Poor models usually don't become pervasive.
My point is that earlier OOP documents did not implement generics. When they were finally implemented in OOP, it superseded the original intentions of OOP. The question is, are we now supposed to remove generics because…
Except for the fact that objects can be serialized and ORM's exist to convert your data into OOP. How do you think Entity Framework works? How do you think Rails works? You can build almost an entire ORM from a database…
Just because prior literature exists, does not mean it should not be superseded. For example, generics wasn't even a thing when OOP originally started and yet LINQ and basic list ADT's wouldn't be as powerful without it.
How has the church of OOP failed? Nearly every used language is based almost entirely on OOP. OOP makes organizing software and code reuse incredibly easy. The only real downsides to OOP is that its arguably slower and…
Companies have very poor development processes and scheduling which is what makes coding, in any language or framework, difficult because half the time you don't even know what you should be writing. Even worse, asking…
Laplace transformations are differential equations so I fail to see your point. They're just in a different domain. However I do see your point with numerical methods since most complex problems are simulated anyways…
The problem is math is entirely abstract. So you must learn the abstraction before applying it. Otherwise, you learn how to add 2 + 3, but you don't learn how to add n + m.
"Such a teacher will be successful if at the end of the course every one of his or her students feels they have taken “a good course,” even though they may not quite be able to pin down anything specific they have…
You need to learn the math before applying it. You don't apply things that you don't understand.
If you consider analyzing an RL/RC circuit as a "toy problem" then I guess you're right.
Except the article still says its out of Africa, just not from a single region in Africa.
The problem is automation is never truly automated in most jobs. There's always things that go wrong, always changes being proposed, always explaining needing to be done. Sure, you may find it easy to automate a report…
What about it?
So you don't really know what I was originally talking about yet you continue to act like you do? My point was in a response to the OP's implication that somehow the original OOP literature was perverted by…
>Maps can be represented 1:1 as e.g. JSON. Any JSON data is basically a big map data structure. It's one function call instead of hours of writing ORM classes or custom serialisation methods just to send some data over…
A poor model for computation that is pervasive in the industry. Poor models usually don't become pervasive.
My point is that earlier OOP documents did not implement generics. When they were finally implemented in OOP, it superseded the original intentions of OOP. The question is, are we now supposed to remove generics because…
Except for the fact that objects can be serialized and ORM's exist to convert your data into OOP. How do you think Entity Framework works? How do you think Rails works? You can build almost an entire ORM from a database…
Just because prior literature exists, does not mean it should not be superseded. For example, generics wasn't even a thing when OOP originally started and yet LINQ and basic list ADT's wouldn't be as powerful without it.
How has the church of OOP failed? Nearly every used language is based almost entirely on OOP. OOP makes organizing software and code reuse incredibly easy. The only real downsides to OOP is that its arguably slower and…
Companies have very poor development processes and scheduling which is what makes coding, in any language or framework, difficult because half the time you don't even know what you should be writing. Even worse, asking…
Laplace transformations are differential equations so I fail to see your point. They're just in a different domain. However I do see your point with numerical methods since most complex problems are simulated anyways…
The problem is math is entirely abstract. So you must learn the abstraction before applying it. Otherwise, you learn how to add 2 + 3, but you don't learn how to add n + m.
"Such a teacher will be successful if at the end of the course every one of his or her students feels they have taken “a good course,” even though they may not quite be able to pin down anything specific they have…
You need to learn the math before applying it. You don't apply things that you don't understand.
If you consider analyzing an RL/RC circuit as a "toy problem" then I guess you're right.
Except the article still says its out of Africa, just not from a single region in Africa.
The problem is automation is never truly automated in most jobs. There's always things that go wrong, always changes being proposed, always explaining needing to be done. Sure, you may find it easy to automate a report…