Comments (20)
@substack from IRC:
[06:52am] substack: feross: your thing should just do uint8array, don't worry about the fallback
[06:52am] feross: substack: okay, i can remove that
[06:53am] feross: substack: will you just do that check in node-browser-builtins?
[06:53am] substack: no it's probably best to just not check and push that choice onto the user
[06:53am] substack: no reason for everybody to suffer with a vastly larger bundle size
[06:54am] feross: okay, cool
[06:54am] feross: that's perfect
I'm pretty new to the browserify
community so I don't know what people have come to expect. But I vote for dropping old browser support since life is too short to spend it supporting old software. browserify
is for mad science!
from node-browser-builtins.
If it can be supported with simple shims (via es5-shim or similar) then making the code free of browser nonsense is a win. The users that don't care about older browsers (more and more every day) will benefit from a smaller and more maintainable module and the module devs wont be burdened with debugging stupid browsers if they don't care about them. It is not hard to just add a note to the readme about "legacy" browsers. Really this comes down to the decision of the module authors. If you don't care about supporting old browsers (and you absolutely don't have to care) then just tell people to use a shim. There isn't a right or wrong here.
from node-browser-builtins.
We don't really need a universal support policy. In this particular case the downsides to old browser support (a much bigger bundle size) outweigh the benefits for this particular module. Other times it's rather easy to inline a little Array.isArray() function and everything works.
from node-browser-builtins.
Just to clarity, when I say I don't care its because I don't support IE8 in my own personal projects. However I'm still the one there gets the angry emails when things don't work and that I care about.
from node-browser-builtins.
Tell them to use a shim. If they are writing an angry email to a volunteer
project maybe they should think about sending you some money first.
On Nov 18, 2013 10:46 AM, "Andreas Madsen" [email protected] wrote:
Just to clarity, when I say I don't care its because I don't support IE8
in my own personal projects. However I'm still the one there gets the angry
emails when things don't work and that I care about.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37#issuecomment-28708639
.
from node-browser-builtins.
What does this change mean to Testling? Testling browserifies test bundles and runs them in older browsers, such as IE6, 7, and 8.
from node-browser-builtins.
@pkrumins This will only affect modules that use the Buffer
global. None of the modules in the testling stack should be affected.
from node-browser-builtins.
We really need to get rid of this global use of browser and process. I
think it just takes a bit more convincing but the end result will be better
for us. It isn't like node doesn't introduce breaking changes, they just
pretend not to.
On Nov 18, 2013 12:04 PM, "James Halliday" [email protected] wrote:
@pkrumins https://github.com/pkrumins This will only affect modules
that use the Buffer global. None of the modules in the testling stack
should be affected.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37#issuecomment-28716576
.
from node-browser-builtins.
@substack great!
from node-browser-builtins.
I'm okay with supporting three latest versions of IE 9, 10 & 11. I would speculate that node stack is mostly used by startups and personal projects who don't often support IE8 and lesser. Those who need to support would be able to polyfill and get it work with a bit of extra effort.
I would love to have a paragraph in the readme talking about this.
Thoughts?
from node-browser-builtins.
Other times it's rather easy to inline a little Array.isArray() function and everything works.
Its actually a huge maintenance burden! @substack would it be possible to drop IE8 & 9 support entirely?
I'm okay with supporting three latest versions of IE 9, 10 & 11.
It will need to be IE10 & 11, since typed arrays isn't supported by IE9.
I would love to have a paragraph in the readme talking about this.
I'm thinking:
This module supports only IE 10+. This decision was made to reduce the maintenance and allow usage of more advanced browser features such as TypedArrays. Please do not supply pull requests there adds support for legacy browsers. Instead we recommend that you use the necessary polyfills for legacy browser support. Should you be willing to start your own complete browser-builtins polyfills project, then feel free to contact us for tips and hints.
from node-browser-builtins.
I've made a branch without legacy browser support so you can tell us how huge the impact is.
from node-browser-builtins.
Nobody have said anything and the new buffer constructor is almost done, so both #40 and #36 will be merged tomorrow. It will be a new major release so no worries :)
from node-browser-builtins.
Sounds great! Im in favor or dropping old IE support.
from node-browser-builtins.
@alexgorbatchev please publish version 3.0.0
By the way a single shims is needed in order to support IE11 :(
from node-browser-builtins.
Do we have automated CI browser testing setup for this repo to avoid breakage?
from node-browser-builtins.
No and you are welcome to tell us how :)
PS: @alexgorbatchev is the one with admin rights.
from node-browser-builtins.
3.0.0 has been published
from node-browser-builtins.
I added travis, however it fails because of firefox...
https://travis-ci.org/alexgorbatchev/node-browser-builtins/builds/14818705#L444
firefox --no-remote -CreateProfile browser-launcher-62a8eb2 exited with code 1: Error: no display specified
from node-browser-builtins.
What is being used to launch Firefox? Is that something that Travis or testling provides?
from node-browser-builtins.
Related Issues (20)
- querystring & url do not do what node core does HOT 2
- Publish HOT 5
- you get all the shims whether you want them or not HOT 9
- Add another maintainer HOT 5
- fs throwing on require breaks brfs HOT 5
- No checks for the presence of console HOT 5
- 2.x breaks browserify with multilevel HOT 10
- add a new empty module for "module"
- Traced problem with browserify back to browser-builtins. HOT 1
- separate out assert and util HOT 7
- missing Travis-CI and saucelabs linking HOT 1
- npm publish 3.1.0 HOT 3
- question: change name? HOT 1
- Missing files? HOT 2
- Failing travis build HOT 3
- `process` should resolve to browser.js instead of index.js HOT 2
- Use external modules and fix them such that the tests passes
- https.js missing? HOT 2
- events.js is missing HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-browser-builtins.