My weekend project

Languages and libraries

javascript engine wrapper

SHOW HN2011

5points
8comments
#977of 1,097 in 2011
Top 90%of 2011 by points

How HN took it

RoastedHalf or more of the comments are critical

0 positive, 1 neutral or asking, 0 mixed, 4 critical, out of 5 comments about the project. Thread score -0.35.

Performance: 0 for, 2 againstIdea: 0 for, 2 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

Objections

  • Wrapper hides engine-specific APIs needed for performance and GC control

    From 2 comments
    • I've tried to do this to some extent to prevent native code hooked up to the embedded engine from being tied to one implementation, but it doesn't work very well in practice.…
      apaprocki on HN
    • For simple things it might work, but if a library wrapper was written using your wrapper instead of the native API then there is a good chance it will not be as performance…
      apaprocki on HN
  • Abstraction leads to disjoint features and duplicated bindings

    From 2 comments
    • I've tried to do this to some extent to prevent native code hooked up to the embedded engine from being tied to one implementation, but it doesn't work very well in practice.…
      apaprocki on HN
    • For simple things it might work, but if a library wrapper was written using your wrapper instead of the native API then there is a good chance it will not be as performance…
      apaprocki on HN
  • Rooting approach would hurt performance

    From 2 comments
    • I've tried to do this to some extent to prevent native code hooked up to the embedded engine from being tied to one implementation, but it doesn't work very well in practice.…
      apaprocki on HN
    • For the rooting, you can't know if someone is storing you on the stack unless you get hack-y[1]. So you'd have to assume the opposite, that the caller is storing you on the stack…
      apaprocki on HN

Requests

  • Avoid copying strings and allow peeking at bytes

    From 1 comment
    • I've tried to do this to some extent to prevent native code hooked up to the embedded engine from being tied to one implementation, but it doesn't work very well in practice.…
      apaprocki on HN

Alternatives named

  • Adrian Boeing's PAL portable abstraction layer

    From 1 comment
    • Reminds me of this: http://www.adrianboeing.com/pal/ Great in theory, but not worth the effort, so very low rate of adoption.
      pagekalisedown on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/3147549)