New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

TJ Holowaychuk: Components

By K -
TJ posted on his blog about interesting idea to bring all connected content about eg. Popup and store it within one folder (or component). From that folder to component is easy to create some kind of package, package manager like npm (or I think that we can just use npm for this).

More about idea: http://tjholowaychuk.com/post/27984551477/components

There are things that we must think before we create universal component (that can be used with jQuery, MooTools, YUI...). Make them extensible enough to use in big projects.

TJ mentioned that at LearnBoost they use similar idea with server and client code in one component, this is really interesting but if such modules would be in npm registry then they would have dependencies like Express or jQuery, or some kind of MVC library.

Another fragmentation issue is AMD vs Common.JS. I also think that Common.JS are more elegant but still now we have them both in community. I think about it with some kind of MVC and not only for browser but also for server. I can think of two libraries that want to integrate it: Derby and Meteor.
I think that we must think about not only client-side components but all of them, client-side(ender), server-side(npm), and mixed. Components alone need some kind of glue code to make them usable, maybe if there will be some kind of spec for them existing libraries will just start supporting them?

From:
http://tjholowaychuk.com/post/27984551477/components
http://blog.izs.me/post/27987129912/tj-holowaychuk-components - response
https://github.com/component/spec/wiki - wiki about TJ components

Comments

Post a Comment

Comments:

Popular posts from this blog

How to use NPM packages from private repositories on bitbucket

By K -
Image
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Read more

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:
Read more