ChrisRus

5 ms·

1.
by ChrisRus 5y ago
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 and reusable stuff.
2.
by ChrisRus 7y ago
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 reason in the world
3.
by ChrisRus 7y ago
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 shared state at runti
4.
by ChrisRus 7y ago
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 this over H
5.
by ChrisRus 7y ago
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.
6.
by ChrisRus 7y ago
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.
7.
by ChrisRus 8y ago
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
8.
by ChrisRus 8y ago
How does this differ from Firebase?
9.
by ChrisRus 9y ago
Need to know. Members of the kernel team generally have zero knowledge of what happens in the build lab between the sources and the product that's released to the world.
10.
by ChrisRus 9y ago
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 shared state requirement
11.
by ChrisRus 9y ago
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 further conv
12.
by ChrisRus 9y ago
I wrote ARCcore.filter to solve many of the issues discussed. And, because it works at the JavaScript function level to normalize/validate function I/O it works well with _everything_ to solve the runtime data problem. And, it ope
13.
by ChrisRus 9y ago
I totally believe distributed systems should be modeled using declarative circuit metaphors.
14.
by ChrisRus 10y ago
> From Jack Reeves he cites the epiphany "that in fact the source code is a design document and that the construction phase is actually the use of the compiler and linker." Ha. That is laughable. If it were so, then we would be
15.
by ChrisRus 10y ago
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 in recent yea
16.
by ChrisRus 10y ago
I have been working on a moon-shot project for more than a decade that seeks to model distributed systems as if they were digital logic circuits. One of the natural areas of interest is of course FSM's - in particular declarative speci
17.
by ChrisRus 10y ago
#1 on HackerNews is worth it. Congratulations, man!
18.
by ChrisRus 10y ago
> HW design is not that different from SW design. Shouldn't be. But it is.
19.
by ChrisRus 10y ago
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 code has be
20.
by ChrisRus 10y ago
will not be swallowed
21.
by ChrisRus 11y ago
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 actually in
22.
by ChrisRus 11y ago
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 li