If & Else - Latest Comments

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Ryan Burnette — Sat, 06 Jan 2018 16:09:13 -0000

I tried to use this but it was too hard.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

.. — Mon, 22 May 2017 01:55:17 -0000

Thanks for explaining this so clearly; great teaching

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

div — Sat, 13 May 2017 23:23:00 -0000

Definitely the best read on this topic. Greatly helped me in understanding the design behind creating your own libraries.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

englishextra — Mon, 09 Jan 2017 11:16:07 -0000

yeah, that's what I have to rearrange with every third-party lib.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Dima Beznos — Mon, 09 Jan 2017 10:54:16 -0000

you can path instead `this`: `typeof window !== 'undefined' ? window : this`

Re: Like My Grandpa, With a Big Lawn

Jim Cowart — Mon, 05 Dec 2016 16:11:43 -0000

Thank you! It's an ideal I strive every day to live up to...

Re: Like My Grandpa, With a Big Lawn

Benny Neugebauer — Mon, 05 Dec 2016 09:23:56 -0000

This post made me your Twitter follower. I think you spoke for so many of us (humorous & patient) programmers.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Akos — Thu, 29 Sep 2016 07:58:53 -0000

> Placing this burden on the build system is completely ignoring the huge number of developers that aren't even using a formal module system like AMD or CJS - either by choice or because they're support legacy code.

I completely agree. Only a few lines and app developers can spend more time developing their apps instead of fixing someone else plugin. I'm constantly returning to James Burke's Gist and using it as a template whenever I decide to "fix" a plugin.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

englishextra — Thu, 25 Aug 2016 21:01:08 -0000

How about babel’s changing ‘this’ to ‘undefined’ trouble?

Re: Know When to Walk Away

Michael Terry — Wed, 02 Mar 2016 14:36:21 -0000

Coward of the County?

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Roland Hegedus — Fri, 19 Feb 2016 11:15:59 -0000

// CommonJS
var postal = require("postal");
// yay, postal is available
// AMD

*** define([ "postal", function(postal) { ***
//yay, postal is available
});

*** you need a closing ] after ["postal",

Re: Using ReactJS and KendoUI Together

rippo — Fri, 03 Jul 2015 12:43:07 -0000

Fantastic, lot to learn here.

Re: machina v0.3.8 Released

Erik Schoel — Thu, 04 Jun 2015 07:15:08 -0000

Great piece of work! I have spent the past 1.5 year creating a "core engine" that manages setTimeout, RAF and setImmediate into something that should be able to deliver the power and stability required to create a (near?) native IOS user experience on Mobile using JavaScript. I am currently rebuilding the core for the I-don't-know-how-many-time-in-a-row. This time I use your state machine to manage all inputs and "calibrate" the engine. Would you be able/willing to spend half an hour on Skype for this? Feel free ignore, I thought I could ask.. cheers!

Re: Using ReactJS and KendoUI Together

housecor — Thu, 16 Apr 2015 16:44:30 -0000

Great work Jim! This was very helpful for me. The similarity to React and WebForms is erie, but having the lifecycle methods makes integrating with third parties possible.

Re: Like My Grandpa, With a Big Lawn

netaisllc — Fri, 13 Mar 2015 17:58:28 -0000

Really -- blindness, omg!

Re: Like My Grandpa, With a Big Lawn

netaisllc — Fri, 13 Mar 2015 17:58:10 -0000

+1 Mr. C. So well said.

Re: I'm Not Good Enough to Be an Impostor

Jim Cowart — Sun, 08 Mar 2015 11:55:04 -0000

Marcus - thanks so much for the reply. I really relate to what you've described. The more time goes on, the more convinced I am that one of the most important skills to cultivate is being able to determine what I don't know...closely followed by who can I Iearn from to fill the gaps. So often it feels like leaving harbor with a vague destination, and hopefully enough supplies! :-) You said it very well: "I think moving towards trying anyway is the way I'd like to more often go." This is the attitude I want to have as well, and the one I want my kids to see me live out as well.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Marcus Stenbeck — Thu, 25 Dec 2014 07:15:58 -0000

Thanks for this write up! I was facing this a while back, and while I did see how jQuery did it I pushed back on implementing for the project I was working on then. I've bookmarked this page and I'll try it soon.

Re: I'm Not Good Enough to Be an Impostor

Marcus Stenbeck — Thu, 25 Dec 2014 07:11:53 -0000

This puts into words things that I deal with every day. One major consequence of having to tackle these obstacles has been, for me, to always try to find "the person" who knows what I want to know. At times they exist, and there are great resources available. Other times it takes a while before I'm able to realize that the specific combination of knowledge isn't out there, or at least not in concentrated, easily digestible form. Sometimes I'll tackle the problem anyway, other times I'll wait until the information is available. I think moving towards trying anyway is the way I'd like to more often go.

Re: It's Not Hard: Making Your Library Support AMD and CommonJS

Stepan Riha — Sat, 25 Oct 2014 08:03:35 -0000

Continuing with the global discussion, I appreciate it when a library that sets a global (which might be clobbering a previous definition) also exports a noConflicts() method that restores the global. Underscore, Backbone, jQuery and others do this.

I use AMD modules. When I run unit tests on my code, I first call noConflicts() on these modules to remove them from the global scope and ensure that my code is explicitly requiring them.

Re: Using ReactJS and KendoUI Together

gregmiller — Sun, 12 Oct 2014 11:48:55 -0000

Very helpful. Thanks.

Re: I'm Not Good Enough to Be an Impostor

Derek Kaneshiro — Thu, 07 Aug 2014 16:49:02 -0000

Awesome post

Re: UMD For Everyone

Šime Vidas — Fri, 25 Jul 2014 11:02:52 -0000

Not sure how big of an issue the performance impact of polyfills is. In my opinion, as long as it (technically) works in old IE, management should be content. *** I’m all for graceful degradation but it has its limits, it seems. E.g. I suggested using Flexbox layouts and have old IE fall back to a single-column (but still functional) layout, but people tell me that’s not acceptable with their company.

Re: UMD For Everyone

Jim Cowart — Fri, 25 Jul 2014 10:45:55 -0000

Given the amount of cross-frame work I've done, I'd *love* to see anything < IE9 die a fiery death as soon as possible. :-) Last I checked, IE8's share of avg traffic was 4% or less, so we're on the way, at least. You're right, though - a lot of older browsers could be in the mix if we transpile for their sake.The difficulty would be other APIs that are either hard to polyfill for or the performance hit of the polyfill is too much. Ideally, we could handle those situations by allowing a functional, but degraded, experience in legacy browsers. I've yet to encounter that as the norm with most teams, unfortunately. That's one area I'm planning to do some research in this year to see if we can simplify that process where I work. I will admit, though, that most of my "old browsers need to die" angst is from both working at, and developing products used by, enterprise orgs (where the time-to-upgrade process often exceeds the support lifecycle of dead browsers).

Re: UMD For Everyone

Šime Vidas — Fri, 25 Jul 2014 10:16:16 -0000

“ We just need old browsers to die.” - Do we? :-) Old IEs and stock Androids are very unlikely to die (fingers crossed for IE Enterprise Mode). As soon as ES6 support is near-complete in Firefox/Chrome, we can start feeding them with ES6 code directly while maintaining a transpiled version for legacy browsers (via build step).