saiojd

15 ms·

1. 121.▲
   by saiojd 6y ago

   Out of curiosity did you push for a raise? Not criticizing btw, just wondering how things played out
2. 122.▲
   by saiojd 6y ago

   Agreed, upvotes are a failed experiment, especially for comments.
3. 123.▲
   by saiojd 6y ago

   Lots of us here have wasted our youth playing games and are uncomfortable with the fact that it was, indeed, a waste.
4. 124.▲
   by saiojd 6y ago

   Thanks, that makes sense!
5. 125.▲
   by saiojd 6y ago

   Ok, that makes more sense. The part I still don't get is how we can pick a number x such that s2 < x < s3 without directly assuming that [0, 1] is uncountable.
6. 126.▲
   by saiojd 6y ago

   I don't follow why Bob can play any legal move when s_n is not possible. The proposition is that, if S is countable, Bob has a winning strategy. Suppose S = (s1, s2, s3), which is finite and therefore countable. On turn 1 Alice picks s
7. 127.▲
   by saiojd 6y ago

   I wish all languages just adopted ML syntax for function application.
8. 128.▲
   by saiojd 6y ago

   For starters people are intrinsically motivated to accomplish video-game tasks while most people are only extrinsically motivated to accomplish work tasks. I'm having trouble believing you aren't being disingenuous.
9. 129.▲
   by saiojd 6y ago

   Yes it does seem to be a very difficult problem. That being said, some hard problems deserve hard solutions!
10. 130.▲
    by saiojd 6y ago

    I agree. Something must absolutely be done about the orphan rules, IMO they are Rust's biggest wart. They damage composition in a fundamental way, and gimp the otherwise extremely expressive trait system. I find it hard to believe that
11. 131.▲
    by saiojd 6y ago

    I'll concede that it's not charitable but if anything I think UI needs to change more, and in ways which aren't superficial like switching icons. Compare this to Mac OS 9, is it really that different? Have we really not figur
12. 132.▲
    by saiojd 6y ago

    People on this site always comment negatively on literally anything related to UI except if it looks like it was made in the 90s. Absolutely zero sense of perspective or open-mindedness.
13. 133.▲
    by saiojd 6y ago

    Thanks. Batching was more efficient with diffing because you can avoid keeping track of which array indices changed within the same batch?
14. 134.▲
    by saiojd 6y ago

    That makes sense. It is mostly the O(n) rerendering which is expensive, not the array copy. With regards to superficial/syntactic issues now, I just don't see the advantage of: `setState('list', state.list.length, newIte
15. 135.▲
    by saiojd 6y ago

    Thanks, that makes a lot of sense (basically Mobx but fine-grained). When I mentioned diffing, I meant for updating state objects like lists. Your `<For/>` element only updates if a new list is created, but only re-renders the ch
16. 136.▲
    by saiojd 6y ago

    I'm not sure I understand your argument in favor of setState correctly. By splitting the state into two parts (a read-only view, and a setState function to update it), isn't the opposite being accomplished? It is now possible to p
17. 137.▲
    by saiojd 6y ago

    I've been playing around with your library for the last hour and so far it's excellent, pretty what I had hoped for after working with React for a while. The performance of individual renders is one area of improvement but I think