bbsimonbb

11 ms·

1.
by bbsimonbb 1y ago
If anyone's tempted to visit, the home page is in French. Click on "Chiffrer un produit" and you're into the configurator which has English translation (top right). All the magic is on the third screen, after selecting a
2.
by bbsimonbb 1y ago
https://simplyfirst.fr . We're off and running, making the world's best configurators for complex products. Our first clients love us. Our configurators implement some very personal ideas about front-end state managemen
3.
by bbsimonbb 2y ago
This is worth meditating! The American empire, like the British before it and the other european while we're at it, are flashes in the pan compared to the Romans, the Byzantines, the Ottomans. It could be that hypocrisy, racism and jus
4.
by bbsimonbb 3y ago
Good suggestion.
5.
by bbsimonbb 3y ago
I like and use MobX. I "come from" Vue, and I like mutability (though I concede its dangers). For my needs, the limitation was reactions. In mobx, reactions shouldn't update other observables. In Octopus, chaining is the whol
6.
by bbsimonbb 3y ago
So xstate implements state machines. This is quite a different concept from DAGs, though there may be a DAG underneath. This isn't mentionned anywhere though. The concepts you work with are state machine concepts.
7.
by bbsimonbb 3y ago
I looked at and rejected state machines, because I didn't like/understand the need for the formalism of defining every possible state.
8.
by bbsimonbb 3y ago
That looks really remarkable.
9.
by bbsimonbb 3y ago
I'm not doing this for fun. Especially since I'm fundamentally lazy (and more of a practitioner than a comp-sci person). I'm looking at custom configurators for complex made-to-measure products with dozens of options, with ma
10.
by bbsimonbb 3y ago
Are you talking about this? https://patents.google.com/patent/US7865872B2/en
11.
by bbsimonbb 3y ago
I put a concrete example in the sample app. "pizza" depends on "size" and "base". So a DAG, as you point out, is less constraining than a tree. When you shoehorn your state and orchestration into react componen
12.
by bbsimonbb 3y ago
That sounds very cool indeed.
13.
by bbsimonbb 3y ago
No. Signals work with a weak map of references, not a graph. So in my Pizza example, when pizza changes, totalPrice would recalculate twice: once on a signal from pizza, once on a signal from tip. Explicitly constructing the graph dramatica
14.
by bbsimonbb 3y ago
That looks interesting, and totally new to me. Thanks.
15.
by bbsimonbb 3y ago
Have a look at the node code. It's biblically simple. I would say it's much simpler than any comparable solution. You can forget about reducers, thunks, computed, even useState, useContext, useEffect and props are rare. I've
16.
by bbsimonbb 3y ago
The graph framing is essential. I use typescript graph libraries for the topological sort and for the visualization. I did much less work than either of those two libraries !
17.
by bbsimonbb 3y ago
As I've just written above, React components form a tree that mirrors the DOM. A graph is a much better fit. Nodes in my DAG ressemble "computed" in Vue, where they watch a value and recalculate when it changes, but... in Vue
18.
by bbsimonbb 3y ago
It's very different. Your react components are organized in a tree that mirrors your DOM. If you're using React without an additional state management package, you need to hoist your shared state to a common ancestor, then prop dr
19.
Show HN: Octopus – a directed acyclic graph for app development(github.com)
84 points by bbsimonbb 3y ago|47 comments
20.
by bbsimonbb 3y ago
https://en.wikipedia.org/wiki/Lesson_of_the_widow%27s_mite
21.
by bbsimonbb 3y ago
Cone looks fantastic. You're going to make me buy an IPhone.
22.
by bbsimonbb 3y ago
Sorry for the trouble you had to go through to get there, but that looks really useful.
23.
Show HN: A directed acyclic graph for managing state in SPA's(github.com)
1 points by bbsimonbb 3y ago|1 comments
24.
by bbsimonbb 3y ago
I found state management too boilerplatey and full of concepts. I thought the distinction between state and computed was unhelpful, and I thought the methods were all over the place. I remarked that the subjects our UIs handle generally hav
25.
by bbsimonbb 3y ago
Tis a little disconcerting to see master called master. I thought we'd all changed that?
26.
by bbsimonbb 3y ago
> Basically everyone who utters the question “.. but how technical are they?” in that particular tone of voice is a shitbird. Software is a new industry, we're only just starting to get it right, and put behind us a litany of failed
27.
by bbsimonbb 3y ago
datagrip in pycharm seems to be on a similar trip. The SQL stays in string literals, but datagrip looks inside the string literal to validate and propose auto-completion.
28.
by bbsimonbb 3y ago
The wikipedia page says exactly the opposite. "EOF abstracts the process of interacting with a relational database by mapping database rows to Java or Objective-C objects. This largely relieves developers from writing low-level SQL cod
29.
by bbsimonbb 3y ago
also zapatos, scala-slick (see type-checked sql statements) and yesql
30.
by bbsimonbb 3y ago
This thread only underscores the total mindshare dominance of ORMs. The implicit alternative to ORMs in almost every comment is raw sql in string literals in app code. For 6 years now, we've had tools that let you use sql as a language

More ›