Working on a new spin on domain models and software product line engineering, in JavaScript, for data scientists that need to build sophisticated process pipelines, and complex interactive visualization UX --- from data…
Note that the idea here is sound; identify and specify the roles of various actors in detail specifying explicitly that they are not actual _classes_. Effectively, this is high-level block diagram and there's every…
OOP is not a helpful paradigm for modeling systems. If it was, we would design digital circuits with classes. But, of course that's not possible. Because classes are absolutely a horrible metaphor for representing…
This looks very interesting indeed. I am currently working on a system that allows hierarchical system modeling and evaluation of so-called "observable process models". I can easily understand leveraging something like…
I am going to watch the whole thing. I guess now it will be largely review. But, the fascination is in the instruction; this is not an easy topic to teach.
Soon it will take less time and be more cost-effective to commission the integration of an SoC for your application than to risk your business to software basket weavers.
JavaScript developers interested in this should also take a look at https://encapsule.io/docs/ARCcore/filter that makes it simple to implement bulletproof JSON validation and normalization. Advanced application of this…
How does this differ from Firebase?
OO is absolutely the wrong paradigm; at its most elegant OO exceeds at encapsulating one very simple form of automata. But is utterly worthless of modeling hierarchical automata systems with complex dependencies and…
The more you look at microservices, the more you'll appreciate basic TTL logic design with buffers, blocks, latches, and sequential logic. I wrote a paper about this subject a long time ago. Everything I've seen since…
I totally believe distributed systems should be modeled using declarative circuit metaphors.
Cool! Thanks for the links and the reply. > I have felt this train of thought could be useful for a general purpose approach to software engineering beyond distributed systems interop One of the best articles I've read…
#1 on HackerNews is worth it. Congratulations, man!
> HW design is not that different from SW design. Shouldn't be. But it is.
I doubt that Windows will ever be open sourced. I think it's more likely that they continue to integrate Linux API's into the commercial OS product and slowly morph into a their own Linux distro when most of the legacy…
will not be swallowed
I've added comments to the OP but to summarize: OO inheritance is useful for codifying a limited set of real-world models. But to truly generalize, we need to stop pretending that it's feasible to make progress without…
Begging the question: http://www.nizkor.org/features/fallacies/begging-the-questio... Almost _never_ a valid reason to use this phrase. Using it incorrectly signals (a) you're reaching (b) not so cunning a linguist…
Working on a new spin on domain models and software product line engineering, in JavaScript, for data scientists that need to build sophisticated process pipelines, and complex interactive visualization UX --- from data…
Note that the idea here is sound; identify and specify the roles of various actors in detail specifying explicitly that they are not actual _classes_. Effectively, this is high-level block diagram and there's every…
OOP is not a helpful paradigm for modeling systems. If it was, we would design digital circuits with classes. But, of course that's not possible. Because classes are absolutely a horrible metaphor for representing…
This looks very interesting indeed. I am currently working on a system that allows hierarchical system modeling and evaluation of so-called "observable process models". I can easily understand leveraging something like…
I am going to watch the whole thing. I guess now it will be largely review. But, the fascination is in the instruction; this is not an easy topic to teach.
Soon it will take less time and be more cost-effective to commission the integration of an SoC for your application than to risk your business to software basket weavers.
JavaScript developers interested in this should also take a look at https://encapsule.io/docs/ARCcore/filter that makes it simple to implement bulletproof JSON validation and normalization. Advanced application of this…
How does this differ from Firebase?
OO is absolutely the wrong paradigm; at its most elegant OO exceeds at encapsulating one very simple form of automata. But is utterly worthless of modeling hierarchical automata systems with complex dependencies and…
The more you look at microservices, the more you'll appreciate basic TTL logic design with buffers, blocks, latches, and sequential logic. I wrote a paper about this subject a long time ago. Everything I've seen since…
I totally believe distributed systems should be modeled using declarative circuit metaphors.
Cool! Thanks for the links and the reply. > I have felt this train of thought could be useful for a general purpose approach to software engineering beyond distributed systems interop One of the best articles I've read…
#1 on HackerNews is worth it. Congratulations, man!
> HW design is not that different from SW design. Shouldn't be. But it is.
I doubt that Windows will ever be open sourced. I think it's more likely that they continue to integrate Linux API's into the commercial OS product and slowly morph into a their own Linux distro when most of the legacy…
will not be swallowed
I've added comments to the OP but to summarize: OO inheritance is useful for codifying a limited set of real-world models. But to truly generalize, we need to stop pretending that it's feasible to make progress without…
Begging the question: http://www.nizkor.org/features/fallacies/begging-the-questio... Almost _never_ a valid reason to use this phrase. Using it incorrectly signals (a) you're reaching (b) not so cunning a linguist…