7 ms·

It can through a thin bridge. See https://github.com/koute/stdweb https://github.com/koute/stdweb

by pohl 9y ago

mlevental 9y ago
so how mature is this tech? is this really feasible? writing browser client code in rust?
- pohl 9y ago
  I think stewed was announced about 8 months ago.
  - pohl 9y ago
    stewed -> stdweb Thanks, autocorrect.
    - ComputerGuru 9y ago
      Yesterday, I learned that the correct term for that is “autoincorrect” thanks to HN.
- makmanalp 9y ago
  If you can write frontend code in typescript or elm, why not rust indeed?
  - kibibu 9y ago
    Those transpile to JS though, not Web Assembly, don't they?
    - TuringTest 9y ago
      Javascript and Web Assembly are expected to run on the same engine, if I'm not mistaken.
- steveklabnik 9y ago
  The biggest holdout is non-Edge IE https://caniuse.com/#search=wasm https://caniuse.com/#search=wasm The story with Rust compiling to it is still younger; it works well at the moment, but is very fiddly. The early adopters and enthusiasts are working on making it all smoother. So for most people, it's still a bit young. Just depends on your temperament.
  - tomatsu 9y ago
    > The biggest holdout is non-Edge IE IE is discontinued. IE11, which was released back in 2013, only gets security-related updates. It's on life support. IE11 part of Windows 10 which EOLs in 2020 (mainstream) or 2025 (extended).
    - zacmps 9y ago
      Unfortunately not everyone stops using a project as soon as it is discontinued.
    - kevin_thibedeau 9y ago
      The problem is that MS won't port Edge to Win7.
      - therockhead 9y ago
        Why is that? Latest versions of Chrome and Firefox work fine on Windows 7 , so they have real competition in this area.
        psquid 9y ago
        Same reasons that IE versions only support certain versions of Windows: - they want to be able to switch to newer APIs when the underlying OS adds them (though in Edge's case it's more likely it was written from the ground up using newer APIs) - they quite possibly want to use "you can get the new browser only if you upgrade" as a carrot for OS upgrades (they explicitly did with IE, I haven't seen anything explicit for Edge but it wouldn't surprise me if they're still taking that approach)
013a 9y ago
Plus first class DOM support for wasm is coming at some point in the future, so I'd imagine any properly supported library could implement it once it is finalized.
- sspiff 9y ago
  I'm not sure I want this. I use WASM as a compilation target, but I rally enjoy the simplicity of the platform and how all connections from and to the Javascript world have to be explicit. Allowing more transparent access to the DOM would diminish this highly defined interface.
  - jakevn 9y ago
    The DOM is unrelated to Javascript.
    - sspiff 9y ago
      Sure, but it's still part of the outside world, so it's still opening a lot of extra interface surface to the platform.
      - steveklabnik 9y ago
        Wasm is specified in two layers; wasm itself and then the api the host provides. All of the "external surface" stuff is in the host, not in wasm itself, so wasm for another host doesn't get larger.

It can through a thin bridge. See https://github.com/koute/stdweb https://github.com/koute/stdweb

by pohl 9y ago

It can through a thin bridge. See https://github.com/koute/stdweb https://github.com/koute/stdweb

mlevental 9y ago

so how mature is this tech? is this really feasible? writing browser client code in rust?

pohl 9y ago
I think stewed was announced about 8 months ago.
- pohl 9y ago
  stewed -> stdweb Thanks, autocorrect.
  - ComputerGuru 9y ago
    Yesterday, I learned that the correct term for that is “autoincorrect” thanks to HN.
makmanalp 9y ago
If you can write frontend code in typescript or elm, why not rust indeed?
- kibibu 9y ago
  Those transpile to JS though, not Web Assembly, don't they?
  - TuringTest 9y ago
    Javascript and Web Assembly are expected to run on the same engine, if I'm not mistaken.
steveklabnik 9y ago
The biggest holdout is non-Edge IE https://caniuse.com/#search=wasm https://caniuse.com/#search=wasm The story with Rust compiling to it is still younger; it works well at the moment, but is very fiddly. The early adopters and enthusiasts are working on making it all smoother. So for most people, it's still a bit young. Just depends on your temperament.
- tomatsu 9y ago
  > The biggest holdout is non-Edge IE IE is discontinued. IE11, which was released back in 2013, only gets security-related updates. It's on life support. IE11 part of Windows 10 which EOLs in 2020 (mainstream) or 2025 (extended).
  - zacmps 9y ago
    Unfortunately not everyone stops using a project as soon as it is discontinued.
  - kevin_thibedeau 9y ago
    The problem is that MS won't port Edge to Win7.
    - therockhead 9y ago
      Why is that? Latest versions of Chrome and Firefox work fine on Windows 7 , so they have real competition in this area.
      - psquid 9y ago
        Same reasons that IE versions only support certain versions of Windows: - they want to be able to switch to newer APIs when the underlying OS adds them (though in Edge's case it's more likely it was written from the ground up using newer APIs) - they quite possibly want to use "you can get the new browser only if you upgrade" as a carrot for OS upgrades (they explicitly did with IE, I haven't seen anything explicit for Edge but it wouldn't surprise me if they're still taking that approach)

013a 9y ago

Plus first class DOM support for wasm is coming at some point in the future, so I'd imagine any properly supported library could implement it once it is finalized.

sspiff 9y ago
I'm not sure I want this. I use WASM as a compilation target, but I rally enjoy the simplicity of the platform and how all connections from and to the Javascript world have to be explicit. Allowing more transparent access to the DOM would diminish this highly defined interface.
- jakevn 9y ago
  The DOM is unrelated to Javascript.
  - sspiff 9y ago
    Sure, but it's still part of the outside world, so it's still opening a lot of extra interface surface to the platform.
    - steveklabnik 9y ago
      Wasm is specified in two layers; wasm itself and then the api the host provides. All of the "external surface" stuff is in the host, not in wasm itself, so wasm for another host doesn't get larger.