kodroid

9 ms·

1. 1.▲
   by kodroid 4y ago

   Thanks. I love to see a description of that formalisation, if you ever get round to publishing it.
2. 2.▲
   by kodroid 4y ago

   Ha, I love that you mind went to that final analogy. I think you have correctly identified the important difference between the kind of applications I have been writing (mobile applications, which are relatively small and often have a good
3. 3.▲
   by kodroid 4y ago

   Thanks, removed.
4. 4.▲
   by kodroid 4y ago

   Great, thanks for sharing also and your experience makes total sense. With this approach: 1. What downsides have you encountered? 2. How easy do you find it to onboard people? 3. Does Android do the same at your place?
5. 5.▲
   by kodroid 4y ago

   Thanks. Others have said similar, but more of a request for an additional post expanding on that aspect. Until then, there is a little more information in a previous related post https://doridori.github.io/Android-Architectu
6. 6.▲
   by kodroid 4y ago

   Hey, I can't say I have ever worked on such a project, it sounds like an interesting problem space. I am assuming when a user interacts with one control button / dial / interaction it has a cascade effect on other controls &#
7. 7.▲
   by kodroid 4y ago

   I guess it depends what exactly you mean by "reactive paradigm". In my experience the commonality found between client side mobile applications and reactive principles is essentially everything is a stream, and the UI subscribes t
8. 8.▲
   by kodroid 4y ago

   Hey, Not targeted at the API crowd really no, more client side applications, but it seems similar principles have been applied in various places / frameworks as spoken about in other comments here. > Maybe this isn’t targeted for th
9. 9.▲
   by kodroid 4y ago

   Great thanks. > For me the difficult part was where the side effects fit in and how they're processed, what you call "commands" and "command handler" Do you mean difficult for you when designing, or difficult to
10. 10.▲
    by kodroid 4y ago

    Thanks for the input. Your totally right, it's pretty similar conceptually to Elm in many ways, amazingly I only discovered Elm in the last 8 weeks or so after writing applications in this way for the last few years, maybe not surprisi
11. 11.▲
    by kodroid 4y ago

    Thanks for your input > ... as a thought experiment it makes sense but it's not transferrable to the real world. For the record, it's certainly not a thought experiment, I have been using this in the real world for a few years.
12. 12.▲
    by kodroid 4y ago

    Hey, thanks for your input. I blame myself for this misunderstanding as I wrote the article. I certainly am not suggesting that an application is a function, rather an application can be represented by single function as its core . There
13. 13.▲
    by kodroid 4y ago

    Thanks for pointing this out, I had not heard of this one and yes sounds like it shares very similar ideals but for the BE.
14. 14.▲
    by kodroid 4y ago

    Hey, thanks for the input. > This kind of specification doesn't need to specify `State` at all, as we can simply refer to previous inputs. E.g. imagine a counter system with the inputs `Increment`, `Reset`, and `Get`. The functional
15. 15.▲
    Application-as-a-Function Thinking(doridori.github.io)

    83 points by kodroid 4y ago|78 comments
16. 16.▲
    by kodroid 5y ago

    Relevant recent post on BTC: Turning off Bitcoin’s inflation funded security model - wishful thinking? https://www.onionfutures.com/essays/turning-off-bitcoins-inf...
17. 17.▲
    Turning off Bitcoin’s inflation funded security model – wishful thinking?(onionfutures.com)

    3 points by kodroid 5y ago|0 comments
18. 18.▲
    by kodroid 9y ago

    https://www.shiftnrg.org/
19. 19.▲
    by kodroid 10y ago

    Agreed - I said the same elsewhere on this thread
20. 20.▲
    by kodroid 10y ago

    Not moronic. If your front door is open, how do I know who opened the door?
21. 21.▲
    by kodroid 10y ago

    Depends on the method of rooting
22. 22.▲
    by kodroid 10y ago

    I think your talking about bootloader unlocking rather than dev mode
23. 23.▲
    by kodroid 10y ago

    May have nothing to do with it but paying with CC details pretty much always has some traceable chain to the person who is gaining from the fraudulent activity. Contactless payment does not. Therefore a contactless scam could yield higher g
24. 24.▲
    by kodroid 10y ago

    It's a lot harder to attack at scale when targeting credit cards than an attack that targets mobile devices.
25. 25.▲
    by kodroid 10y ago

    Not only the OEM hacks but also supporting various hardware
26. 26.▲
    by kodroid 10y ago

    API endpoints could point to what apps are in use
27. 27.▲
    by kodroid 10y ago

    http://pca.st/m32F is a good interview with Michael Mann on this very subject
28. 28.▲
    by kodroid 10y ago

    Lets do a fusion kickstarter. All reward levels can be "carbon free energy".
29. 29.▲
    by kodroid 10y ago

    This would sort of negate the purpose of ASLR, as afaik the whole point is an attacker would not know the mem layout. The very fact its not reproducible is the solution and the problem!
30. 30.▲
    by kodroid 10y ago

    > but I encourage you to not get upset at imagined misunderstandings on behalf of others The problem is, global warming is largely an issue _because_ of the "misunderstandings on behalf of others", so in this case, it is a real