Isobuild: why Meteor created a new package system
1–10 of 54 posts
Re: Isobuild: why Meteor created a new package system
#2This is awesome.
With Isobuild and Cordova, you'll be able to add a camera package
to your app and use one simple Camera.takePicture() API to take a
photo, and then type one command to build your app not just for the
browser, but for the iOS and Android app stores too.Re: Isobuild: why Meteor created a new package system
#3This is awesome. With Isobuild and Cordova, you'll be able to add a camera package to your app and use one simple Camera.takePicture() API to take a photo, and then type one command to build your app not just for the browser, but for the iOS and Android app stores too.
Because running the cordova commands is so hard.
Re: Isobuild: why Meteor created a new package system
#4Everything about Meteor reads like a marketing article.
How about:
- It defines global variables. - The documentation is full of red warning messages and "this will be easier in the future" - The code is pretty unorganized and has some wild pieces in there. - do any of your friends use/heard of meteor?
Re: Isobuild: why Meteor created a new package system
#5This is awesome. With Isobuild and Cordova, you'll be able to add a camera package to your app and use one simple Camera.takePicture() API to take a photo, and then type one command to build your app not just for the browser, but for the iOS and Android app stores too.
As if anything is that simple. Where will the photo be stored? What effects will be applied? What format will it be in? How large will it be? What happens if it requires a permission request (e.g. in browsers and on iOS)? Will it auto generate the manifest file?
Re: Isobuild: why Meteor created a new package system
#6Sounds interesting, but the devil is in the details. To use their example, HTTP.get() will have to deal with CORS on the web, but not in apps. If you end up with dozens of "oh yeah well for X you just need to add Y" situations then the utility is kind of wasted.
And to be honest, I still don't get why this requires a new package manager. NPM (with a utility library, perhaps) could perform most of these functions.
Re: Isobuild: why Meteor created a new package system
#7off-topic (but perhaps related to the general usefulness of meteor): I browse with cookies and localStorage disabled by default. Every time I go to the meteor site to read something, the page just continually reloads itself without ever getting anywhere. I understand that some sites require cookies or localStorage to function (although I think it's nuts that that would be required for a site that is just displaying content and not an interactive application), but at the very least put up a message saying that cookies and/or localStorage must be enabled instead of just making my browser freak out. Thanks, can't wait to actually read about them without having to open a different browser :)
Re: Isobuild: why Meteor created a new package system
#8Sounds interesting, but the devil is in the details. To use their example, HTTP.get() will have to deal with CORS on the web, but not in apps. If you end up with dozens of "oh yeah well for X you just need to add Y" situations then the utility is kind of wasted. And to be honest, I still don't get why this requires a new package manager. NPM (with a utility library, perhaps) could perform most of these functions.
>> HTTP.get() will have to deal with CORS on the web, but not in apps
You can still use exactly the same code in the browser and on the server. Allowing stuff like server-side rendering on old browsers and JS rendering for the majority of users from a single piece of code.
Re: Isobuild: why Meteor created a new package system
#9Everything about Meteor reads like a marketing article. How about: - It defines global variables. - The documentation is full of red warning messages and "this will be easier in the future" - The code is pretty unorganized and has some wild pieces in there. - do any of your friends use/heard of meteor?
I don't think that's fair at all.
The whole point of Meteor is to play with different approaches to web development that will be required in the future (if you want to build big distributed, interactive web apps). It's not finished yet, and they're pretty upfront about that.
Re: Isobuild: why Meteor created a new package system
#10Sounds interesting, but the devil is in the details. To use their example, HTTP.get() will have to deal with CORS on the web, but not in apps. If you end up with dozens of "oh yeah well for X you just need to add Y" situations then the utility is kind of wasted. And to be honest, I still don't get why this requires a new package manager. NPM (with a utility library, perhaps) could perform most of these functions.
If npm had some kind of conformance flag, where you could tag your package with the platforms it supports, this would help considerably.