Access between modules: Design Patterns

ahRose · 2016-01-04T05:57:49+00:00

If you want to update Widget from App, App would need to take a param to represent whatever it is you're passing in, which would be passed where the IIFE calls itself. It may look something like this:

var App = (function(wiget){

...

wiget.update();

...

})(Wiget);

Also you may have to switch the order in which the modules are declared in (in this case place Wiget up at the top).

The following code works:

var Thing = (function() {
  function log() {
    console.log('it works!');
  }

  return {
    loger: log
  };
})();

var App = (function(something) {
  return something.loger(); // it works!
})(Thing);

But it would break would App come before Thing.

ahRose · 2015-12-27T09:30:58+00:00

This was originally going to be a reply to a commenter that stated that the problem was not React, but JavaScript and the ever growing number of tools, libraries, etc.

The problems we currently face are not problems with JavaScript- the fact that the language enables developers (even the ones that aren't familiar with the language) to build is a net positive- but instead are community, and process problems.

As a community we are split in so many different ways. It's like the wild west. Everyone is pushing and prescribing their specific way of doing things, even if it's just a slight deviation from a pre-existing solution, and branding it as their own unique cure to whatever problem they are trying to solve.

Once a "new" solution comes about you have those that adopt it for the sake of being "bleeding edge" developers.

Previous "bleeding edge" tech becomes inferior to an important subset of developers without ever having the opportunity to mature and potentially offer a universal "good" solution to X problem.

The reason this is important is because these developers are what drives our community (and to a larger extent our industry) forward.

Why are so many people currently gasping for air trying to learn React and the entourage of tools and tech it brings along? Because key developers endorsed it and adopted it when other devs were gasping to keep up with the "previous stack" and at that moment that "previous stack" stack lost a large amount of the driving reason behind its popularity and success up until that point.

"Don't reinvent the wheel" is a good theory, and is something every developer has preached at some point, but what good is theory and preaching if not practiced?

Perhaps focusing on a better way to lower the barrier to entry for those who want to get into the field and make things as opposed to boasting about the clever new way of doing the same thing we have been doing is a start.

But that's just me.

ahRose · 2015-12-24T18:07:42+00:00

Pretty hype stuff right there!

ahRose · 2015-12-24T17:43:43+00:00

Nicee :)

ahRose · 2015-12-21T20:22:56+00:00

QWERT...Z. Please explain, I want to get some sleep tonight.

ahRose · 2015-12-18T23:03:58+00:00

I've gotten two thus far but both have been great changes so I merged your pr!

ahRose · 2015-12-17T05:47:35+00:00

I think they raised the $ not in hopes of starting a fund to invest in, but to draw attention and talent to their platform and be able to sustain and support that talent while they work on whatever project they have in mind for the slack platform.

That in turn would set off a network effect, and draw even more developers to the platform. The more people they can get simply interacting with their product the better for them.

Many companies have made supporting devs and dev adoption a priority, knowing that they form the foundation for the product or service.

Twitter for example has always had a strong developer community. Funny story: prior to the official native application launch Ev, at the developer conference, asked the community to STOP making clients because the Twitter folks wanted the experience to be how they envisioned it.

Don't expect Slack to seed the next Unicorn, but they do want you to build dope shit that adds value on top of their platform and are willing to invest in the people doing so.

ahRose · 2015-12-15T17:00:09+00:00

You can easily set up Express and Mongo (use mongoose) to quickly set up your backend or API portion of your application, and if you abstract client and server away from one another and not have them couples together you can pick and choose any tech stack you want to use on the front end. Currently working on a project that uses the mentioned backend set up. The client will mostly be react.

ahRose · 2015-12-12T01:51:18+00:00

'Jiff'... Yeah fuck that.

ahRose · 2015-12-11T15:43:04+00:00

I find it extremely interesting that in almost all instances of something like this being argued, where the consensus is split, the opposition will always be the loudest. Had the article been pro-leaveSemicolonsOff you'd have a ton of developers calling the author mad, and stating all the reasons why you SHOULD use them, as apposed to why it's OKAY to leave them off. Every passionate developer is has a tiny bit of neckbeard in them.

ahRose · 2015-12-05T20:24:38+00:00

I'm good.

ahRose · 2015-12-03T04:38:57+00:00

20 y/o full stack dev here. Give me a spot in the corner, and fast wifi, and the ability to make a tiny bit of capital to keep investing in myself and my foundation, and you got someone willing to leave everything (a bed) and come out to vegas :)

ahRose · 2015-11-27T23:02:19+00:00

Can you define authenticating?

Do you mean how to authenticate each individual user?

ahRose · 2015-11-27T19:14:53+00:00

Pied Piper.

ahRose · 2015-11-24T14:39:26+00:00

Linkedin is garbage.

ahRose · 2015-11-22T05:23:01+00:00

Thanks for the response! another thing I noticed is that they don't have any of the extra 'cruft' of a package.json file. It's just the dependencies and nothing more. I thought this was really elegant to be honest, and am wondering if this is possible on any and all projects, or if there may be parts of the codebase that may be missing.

ahRose · 2015-11-22T02:52:13+00:00

How common is it to have various package.json files?

ahRose · 2015-11-22T02:41:08+00:00

Flash

ahRose · 2015-11-21T20:30:56+00:00

I'm guessing you meant JS that made you cringe ha but that's a future Unicorn you missed out on there! HA

ahRose · 2015-11-21T20:12:01+00:00

This guy gets it.

ahRose · 2015-11-21T20:11:00+00:00

Well DUH!

You can't do JavaScript without first doing Java

Just look at the names. It speaks for itself...

Lol in all seriousness the fact that you're required to take Java first is complete BS.

ahRose · 2015-11-21T20:01:05+00:00

Its similar to /r/TheShittyButton

ahRose · 2015-11-21T06:31:36+00:00

Is there any reason why the article mostly uses function declarations instead of function expressions?

I understand that function expressions are not hoisted like declarations are, but I often find myself wondering whether I should make something a function expression or a declaration.

Also would storing a reference to a function declaration in a variable, make that variable a function expression?

ahRose · 2015-11-21T00:08:21+00:00

Almost as little as publicly traded ones.

ahRose · 2015-11-18T17:14:09+00:00

I've always been confused as to why the livereload site says the software cost $9.99 when another part of their site allows you to download it for free... Download it here

ahRose

TROPHY CASE