klysm

17 ms·

1. 271.▲
   by klysm 2y ago

   It’s not literally a pure exponential function but it might have exponential terms as opposed to polynomial or linear terms
2. 272.▲
   by klysm 2y ago

   Not true in practice for a lot of materials
3. 273.▲
   by klysm 2y ago

   This is what you get when you buy security as an add-on product
4. 274.▲
   by klysm 2y ago

   Syntax is so much less important that semantics that it isn’t even really worth talking about in my opinion
5. 275.▲
   by klysm 2y ago

   I was surprised to see this as a library at all - isn’t it trivial especially for small collections?
6. 276.▲
   by klysm 2y ago

   > if we are concerned about the underlying data shifting when the collection is actually enumerated I’m not sure what you mean by this. You can fulfill the IEnumerable contract without allowing multiple enumerations, but that doesn’t rea
7. 277.▲
   by klysm 2y ago

   This isn’t a great example of what linq is good at. There’s no reason to do ToList there, and the ForEach isn’t particularly idiomatic
8. 278.▲
   by klysm 2y ago

   This might be a bad take, but I think developers should also consider exactly which users are using their app. If it’s the entire internet, then absolutely you need to consider backwards compatibility. If it’s an internal app, then consider
9. 279.▲
   by klysm 2y ago

   Incredible marketing blurb! Not a single bit of detail about how this works
10. 280.▲
    by klysm 2y ago

    React itself is not huge
11. 281.▲
    by klysm 2y ago

    It would be really nice if we had a versioning scheme that enabled developers to get secure by default and opt into performance tradeoffs
12. 282.▲
    by klysm 2y ago

    So the universe is left handed?
13. 283.▲
    by klysm 2y ago

    Then the c toolchain needs to also be considered from a bootstrapping standpoint
14. 284.▲
    by klysm 2y ago

    That’s a weird performance measuring stick to use, and I don’t see how it’s related
15. 285.▲
    by klysm 2y ago

    They themselves might be “simple” but every real usage I’ve seen has been an impenetrable shitshow.
16. 286.▲
    by klysm 2y ago

    gcc/clang isn’t really sufficient though right? Usually there is another build system on top
17. 287.▲
    by klysm 2y ago

    I’ve never seen a real project that doesn’t use make, cmake, or some other glue on top of gcc/clang. Dependency management is absolute hell as well
18. 288.▲
    by klysm 2y ago

    C toolchains are the most painful to set up in my experience and have incredible bloat. Familiarity is not simplicity
19. 289.▲
    by klysm 2y ago

    Unrelated concept
20. 290.▲
    by klysm 2y ago

    Yeah definitely, I’m more referring to the bending process, material selection, fastener types, etc. It seems like quite the art form
21. 291.▲
    by klysm 2y ago

    How do you guys go about doing sheet metal design? It looks pretty clean
22. 292.▲
    by klysm 2y ago

    How exactly is this an improvement over VMs?
23. 293.▲
    by klysm 2y ago

    So it’s a VM?
24. 294.▲
    by klysm 2y ago

    Say “it’s probably fine” and hope that the people building the foundational systems are protecting us
25. 295.▲
    by klysm 2y ago

    You serialize the keys on every row which is a bit inefficient but it’s a text format anyway
26. 296.▲
    by klysm 2y ago

    Outputs are used as inputs later. If everything is deterministic, you can actually cache everything by hash
27. 297.▲
    by klysm 2y ago

    One of the big advantages from my perspective is you can cache a lot more effectively throughout the build process when things are deterministic.
28. 298.▲
    by klysm 2y ago

    Agreed but this really depends on what tools the language gives you for modules. Some languages have the module structure directly coupled to the file layout like JavaScript, where others are a lot more flexible.
29. 299.▲
    by klysm 2y ago

    Okay but that’s a separate concern
30. 300.▲
    by klysm 2y ago

    I love that this _doesn't_ have a persistence layer. Authorization _should_ be just a library