-
I dig this example for a couple of important reasons, the structure is sensible, extensible and quite great. The big problem that I have with it is that a few of the core technologies are baked in ve…
-
Right now, some storage logic is done "directly" in the GUI, it should ideally be more separate, and data dissection like this should be done elsewhere so that GUI is not subject to changes in the way…
-
In my opinion, it would be better if this library focused solely on parsing chunk blocks/packets. (and keyframes?)
The consumer (possbily another loldevs lib) should be responsible for maintaining ga…
-
In GitLab by @maufcons on Jan 25, 2022, 11:09
We are using vuex as store management. However, there are still components that directly request the database. For a clear separation of concerns, we sho…
-
It is desirable that the MPI code is as separated as possible from the domain logic, for clarity.
From our email conversation:
> Perhaps, we can extract the MPI part even more by defining a fall…
-
[Seperatation of concerns]( http://deviq.com/separation-of-concerns/) is a programming concept relates to breaking up your application code. When you are talking about separating concerns in a web pag…
-
See `src/command/mod.rs`. One problem is that in its signature the `treat_event` function accepts `State::Exit`, but in the implementation it causes it to panic. I suggest removing the `Exit` variant …
-
This is becoming more of an issue than we thought, unfortunately, and may require more re-architecting.
Here's a sample workflow:
> The owner of a listing answers a question. The client understands…
-
We filmed a little show this morning where I spoke about this proposal. I had a hard time working out how I was going to explain what the number part of the proposal, I think that's because it's a sep…
-
When writing code it is good practice to separate your concerns as this makes your code more readable both for yourselves and others coming to look at your project. Separation of concerns is applicabl…