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
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.
So first up, all Meteor code is Babel transpiled
That means that there is (as yet) no "native" arrow function in your meteor code
so:
var test = () => { console.log(this); }
becomes:
var _this = this; var test = function () { console.log(_this); }
This is both the same on the client and server. Identical.
The reason why your client example worked is, that the added var _this = this: call at the top of the transpiled code assigned the window object, which obviously already has jQuery, so the selector worked, but is very dodgy. (I think you alluded to this in your talk?)
Alan Shaw
@alanshaw
yes
$(‘button’) could have been any button, but I only had one on the page so it was ok
Simon Mansfield
@Siyfion
Exactly
Alan Shaw
@alanshaw
ha nice
thanks for taking the time
Simon Mansfield
@Siyfion
If you'd have had one in the raw HTML before the template, it would have found that instead
;)
As for how to use arrow functions and retain the "this" being the meteor defined "this", I can't answer that one.. Not sure you can
Heh, no worries, glad to help out ;)
v interesting!
Oli Evans
@olizilla
oooh la
now there’s a thing
Carlos Baraza
@carlosbaraza
Hi everyone, I would like to ask for your help. Do you know the name of some companies working with Meteor? I am a Full Stack Engineer and I want to move to London. Could you also help me figure out the minimum wage I should accept? I did some numbers and it feels like I should ask for > 55k to live comfortably in central London.
Thank you everyone.
Oli Evans
@olizilla
We (https://tableflip.io/) work in meteor but we’ve not got any jobs at the moment. There are several companies who are building out their apps on Meteor that come to the meetup
Will Swannell
@ashburnham
Hi @carlosbaraza what good timing - we're hiring at the moment and working in meteor.
We've got two positions open so just get in touch if you (and/or a friend) are interested.
Carlos Baraza
@carlosbaraza
@olizilla, thanks for your message.
@ashburnham , thank you for the suggestion. It looks like an interesting application. I will apply as soon as I find some time :)
Babak Fakhamzadeh
@MastaBaba
Hiya. Together with a colleague/partner, I'm building a city-discovery app with a twist, in Meteor. Nick from Meteor in San Fransisco suggested to me to post here to perhaps get a presentation going at Devshop London. (One of us is in London, the other in Sao Paulo.) So... when's the next event? :)
Oli Evans
@olizilla
Hey @MastaBaba the events are announced over here
next one is the 28th
It’d be great to hear about your project
I think the line up for the Jan event is currently full, but there will be another meetup towards the end of Feb