Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues from Switchback & RTTC #4730

Open
johnabrams7 opened this issue Mar 29, 2019 · 3 comments
Open

Issues from Switchback & RTTC #4730

johnabrams7 opened this issue Mar 29, 2019 · 3 comments
Labels
what do you think? Community feedback requested

Comments

@johnabrams7
Copy link
Contributor

johnabrams7 commented Mar 29, 2019


SWITCHBACK


image
Original post: https://github.com/node-machine/switchback/issues/7


RTTC


screencapture-github-node-machine-rttc-issues-2-2019-03-29-15_58_40
Original post: node-machine/rttc#2


screencapture-github-node-machine-rttc-issues-3-2019-03-29-16_01_32
Original post: node-machine/rttc#3


image
Original post: node-machine/rttc#7


@balderdashy balderdashy deleted a comment from sailsbot Mar 29, 2019
@johnabrams7
Copy link
Contributor Author

johnabrams7 commented Mar 29, 2019

Hey everyone, we're moving these issues to the main Sails repo for greater exposure to the community. Although we're not able to transfer the actual posts since they are from a different org, we've made screen-captures of them instead to follow-up with here in Sails. Hope these help out and feel free to add any further developments - Thanks!

@balderdashy balderdashy deleted a comment from sailsbot Mar 29, 2019
@balderdashy balderdashy deleted a comment from sailsbot Mar 29, 2019
@balderdashy balderdashy deleted a comment from sailsbot Mar 29, 2019
@johnabrams7 johnabrams7 changed the title Issues from switchback & rttc Issues from Switchback & RTTC Mar 29, 2019
@mikermcneil
Copy link
Member

  1. This will get addressed as part of the larger vuln/deprecation warning sweep.
    2 and 3. both of these are about making the browserified build size smaller for browser-side use cases (e.g. static analysis in a web browser / in electron-based native app)
  2. same as 1

@mikermcneil
Copy link
Member

If anyone has anything else to add re these points, feel free to comment. In the mean time, calling this a potential optimization because of 2 and 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
what do you think? Community feedback requested
Development

No branches or pull requests

3 participants