Live data from Hacker News

Viewing profile — flexterra

flexterra

HN member
Joined
Fri, Oct 31, 2008, 12:52 PM UTC
HN karma
1,648
Public activity
286 items

About flexterra

No profile information was provided.

Recent public activity

  1. comment
  2. story
  3. comment
    Comment #33223654

    Here's the sortable example: https://htmx.org/examples/sortable/ IMHO something slightly more complex than this example (more client side stat) will require using something like Re…

  4. comment
    Comment #33220288

    Validating data on the client and not doing it again on the server will lead to security vulnerabilities. At the very least you will end up duplicating that validation code.

  5. comment
    Comment #33219928

    IMHO this approach is better for most apps. Remix is bending the curve here. They make it extremely easy to progressively enhance a small part of your UI with all the power of Reac…

  6. comment
    Comment #33219901

    The difference in programming model IS THE advantage of HTMX. Changing from react to preact is a perf optimization. If you are doing the SPA thing correctly you must duplicate busi…

  7. comment
    Comment #33219710

    The programming model is totally different when working with HTMX. The server returns HTML instead of a JSON API which is the usual solution when building apps with React/Preact an…

  8. story
  9. story
  10. comment
  11. comment
    Comment #27032768

    HTML could and should do more

  12. story
  13. comment
    Comment #26959456

    I've been using this for years. Is really good and the best feature is that diagrams don't look like crap by default, which is not the case for most code to diagram tools out there…

  14. story
  15. story
  16. comment
    Comment #11549397

    what is the average size of a native mobile app?

  17. story
  18. story
  19. story
  20. story
  21. comment
    Comment #10272585

    https://downdetector.com/status/facebook

  22. story
  23. story
  24. story
  25. comment
    Comment #9143866

    Ember's templates allows the framework to determine which portions of the DOM will never change, and so only needing to analyze the portions that might. Hello World {{name}}