Live data from Hacker News

Viewing profile — thro1

thro1

HN member
Joined
Wed, Apr 29, 2020, 9:58 PM UTC
HN karma
196
Public activity
590 items

About thro1

No profile information was provided.

Recent public activity

  1. comment
    Comment #45925625

    There is no way to make JavaScript so limited in scope as XSLT is. But what I want only is XSLT on live DOM nodes, when editing. Simple templating good engine, and to stay. Not a f…

  2. comment
    Comment #45925596

    There is no way to make JavaScript so limited in scope as XSLT is. But what I want only is XSLT on live DOM nodes. Not a fancy stuff.

  3. comment
    Comment #45920481

    Edit: nRF52840 chip can have 12 Analog Inputs, ESP32S3 20 - e.g. ESP32-S3-WROOM-1 - but XIAO ESP32S3 and XIAO nRF52840 have 6 only, there are others with more pins (AFAIR up to ~12…

  4. comment
  5. comment
    Comment #45914062

    It looks like all Hall sensor or similar analog keyboards came after that ? (exception: Scrollpoint in IBM keyboards)

  6. story
  7. story
  8. comment
    Comment #45913405

    There are diodeless (no matrix) split keyboards ( https://www.reddit.com/r/ErgoMechKeyboards/comments/1dh9o8k/... ) like Cantor: https://github.com/diepala/cantor . They use chips …

  9. comment
  10. comment
    Comment #45880687

    For me, it happened in that moment when XMLHttpRequest was the only working common denominator for few "new" techniques browsers - as iframe was over everything you couldn't just l…

  11. story
  12. comment
    Comment #45864798

    Just.. and for so long: XSLT is WWW standard, JavaScript is not (it's ECMA standard) - and there is no JavaScript specification on W3C pages . ( https://www.w3.org/wiki/JavaScript …

  13. comment
  14. comment
    Comment #45864138

    https://www.igalia.com/chats/xslt-liam So basically browsers had this [..] the question now is there is no investment in this. None. And there hasn't been for a really long time fr…

  15. comment
    Comment #45861696

    https://github.com/whatwg/html/issues/11146#issuecomment-275... panos: next item, removing XSLT. There are usage numbers. stephen: I have concerns. I kept this up to date historica…

  16. comment
  17. comment
  18. comment
    Comment #45856970

    by definition XSLT is more secure than JavaScript.

  19. comment
    Comment #45856827

    That's our freedom of not being forced to use JavaScript for everything being taken away !

  20. comment
  21. comment
    Comment #45796359

    (?) - then more about the tactic: https://news.ycombinator.com/item?id=44994459 (web looks like nails for that tool we have) now how about that: Chrome voluntarily decides to disjo…

  22. comment
    Comment #45786482

    The standard so far is to respect existing standards still in use, peoples effort and work done already - but not to outsource bug fixing costs by forcing any of that to be redone …

  23. comment
    Comment #45785513

    - as in Europe, I don't see neither how taxpayers money or users time (if still alive) could be forcibly used to cover the costs of some far away corporation savings (on bug fixing…

  24. comment
    Comment #45784237

    Moreover: there is no JS solution being so stable and for so long as that standard: "25 year old version of XSLT" . Can be "made with JS" doesn't mean that by chance it would be in…

  25. comment
    Comment #45781209

    Wasn't the social contract that get the market share that you can use Chrome to browse all the web already existing as well as by using the other browsers - means not discriminatin…