by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 04 2016 12:52
    benjimouse commented #29
  • Nov 04 2016 12:24
    alanshaw commented #29
  • Nov 04 2016 12:24
    alanshaw commented #29
  • Nov 04 2016 09:17
    benjimouse commented #29
  • Nov 02 2016 16:16
    erperejildo commented #29
  • Nov 02 2016 16:10
    erperejildo commented #29
  • Nov 02 2016 16:10
    erperejildo commented #29
  • Oct 31 2016 12:54
    MastaBaba commented #29
  • Oct 31 2016 12:29
    reddog commented #29
  • Oct 19 2016 09:10
    bmordan commented #29
  • Sep 30 2016 13:04
    olizilla commented #29
  • Sep 30 2016 12:17
    mrw34 commented #29
  • Sep 30 2016 12:15
    MastaBaba commented #29
  • Sep 30 2016 12:09
    olizilla opened #29
  • Sep 30 2016 12:08
    olizilla closed #28
  • Sep 30 2016 12:08
    olizilla commented #28
  • Sep 29 2016 13:31
    ynotrusso commented #28
  • Aug 30 2016 16:18
    bmordan edited #28
  • Aug 30 2016 16:15
    olizilla commented #28
  • Aug 30 2016 16:15
    olizilla commented #28
Oli Evans
@olizilla
yes
we're digging out the greatest hits
so
we could abletone
!
The plan is to layout many ideas, to nudge people to come up with more
Chris Waring
@cwaring
great to see y'all last night! @olizilla @alanshaw @liamwooding
MLDN top hits all in one event :)
forgot to ask, did you guys have ideas about a Meteor Camp or similar?
Howard Tang
@aychtang
we can go camping?
Oli Evans
@olizilla
@cwaring @aychtang RAD
Richard Silverton
@richsilv
HAPPY METEOR 1.2 DAY EVERYBODY!!!
Oli Evans
@olizilla
1.2 KLAXON
Chris Waring
@cwaring
Woop
Oli Evans
@olizilla
BREAKING CHANGE KLAXON
I'm gonna go upgrade some things
Alan is quivering with semver rage
Chris Waring
@cwaring
I made a 1.2 app at the weekend with my packages and it didn't set on fire, time for a bigger upgrade today. So far so good
Oli Evans
@olizilla
can we see what you made for buzzjamz?
they didn't really get it
but red bull should have their video content live soon :)
Chris Waring
@cwaring
we're actually doing a live show tonight at dotdotdot, if you fancy it? onedotzero.com/calendar/dotdotdotv5
Chris Waring
@cwaring
I spoke too soon, all my build plugins are fked
don't forget to explicitly add ecmascript if you want to use the new shiny
it'll magically work without it on the client if your browser supports the shiny you use, and then blow up in a difficult to debug way when you try and build it for production
es5-shim sounds like a good idea too
Oli Evans
@olizilla
@richsilv can you remember where that AMA is that talked about the future of blaze/angular/react for meteor UIs
Richard Silverton
@richsilv
hmm, give me a sec...
you mean where they basically said that blaze wasn't going to be a focus?
if so, here is the answer Sashko posted that wouldn't all fit onto Crater: https://gist.github.com/stubailo/9296dbd39fad0d6bbf58
So what we’re planning to do is to build templating on top of React, and to encourage Blaze users to upgrade to it (or, for those that prefer it, to plain React JSX). We think that this is the best possible “Blaze 2". If you choose to upgrade you’ll have to port your templates, but that’d probably be the case no matter what direction we go with Blaze 2. And your porting effort will be richly rewarded with access to React’s in-browser debugger tools18, vibrant component ecosystem31, and more. Today’s Blaze will continue to work but MDG’s development efforts will be focused on the new React-based templating option, React JSX, and on Angular.
from Geoff Schmidt, the CEO
then
Evan You, creater of Vue.js will be leading the charge
of note
So instead of keeping the old API and treating React as a low-level implementation detail, we want to embrace its strength (the component model and related JavaScript API) and providing on top of it what people like about Blaze (templating / reactivity).
Oli Evans
@olizilla
I think Abigale puts the case for the concerned app maintainer well: https://forums.meteor.com/t/next-steps-on-blaze-and-the-view-layer/13561/31
Seriously, don't change the existing API if possible. Not right now. The API isn't perfect, but that doesn't matter. Use the existing API as a baseline; swap out the underlying functionality; and make sure it's feature compatible. It's a classic refactor. It's not as fun and glamorous as producing new functionality or stomping out bugs; but it's the boring, responsible, professional, and trustworthy thing to do. Once Blaze 2 is proven to be feature compatible with Blaze 1, then lets start adding new features in Blaze 2.1 and later.
Richard Silverton
@richsilv
yes, that is totally the right thing to do
Richard Silverton
@richsilv
this is interesting: https://github.com/meteor/method
Simon Mansfield
@Siyfion
@alanshaw just watched your Arrow fn talk, did you get all the answers to why it was behaving the way it was?
Alan Shaw
@alanshaw
I haven’t had a chance to look into it further tbh
Simon Mansfield
@Siyfion
Ah, well I think I know what was going on, and why... If you're interested?
Alan Shaw
@alanshaw
Totally am
Simon Mansfield
@Siyfion
Meteor 1.2 introduces official support for many features of ECMAScript 2015 (formerly called ES6) on client and server, such as classes and arrow functions, using the popular Babel transpiler. ECMAScript 2015 is the new official standard for JavaScript, and the new features are already being rolled out in web browsers. You can use many new features today, with little to no impact on code size or performance, thanks to source-to-source transforms that turn the JS you write into JS the browser can run.