Offler

10 ms·

31.
by Offler 11y ago
You mean a grid? A component one is often asked to add to web applications for businesses. I've added 4 in the last week alone to apps I've worked on. It's bread and butter stuff.
32.
by Offler 11y ago
Adding 1,200 image components to a web app and never cleaning up the ones that aren't visible is a poor approach to building a mobile web application. It doesn't matter what technology you use, it's a bad idea. So he's b
33.
by Offler 11y ago
You mean web components? I'm not sure it's possible to pass in anything other then strings as values via their attribute changed callback. They simply aren't as well designed and powerful as React components.
34.
by Offler 11y ago
This might help explain where flux is useful http://briandipalma.github.io/flux-for-components/
35.
by Offler 11y ago
I don't find the fact a brand new browser already supports legacy 'webkit-' prefixes a fun fact...
36.
by Offler 12y ago
It might be a reference to Dart?
37.
by Offler 12y ago
They can be enjoyable tests. I have learnt new things while doing some.
38.
by Offler 12y ago
And Polymer.
39.
Flux without the singletons(briandipalma.github.io)
2 points by Offler 12y ago|0 comments
40.
by Offler 12y ago
Yes I think it depends on what level of complexity you are dealing with, Flux is an overhead for low complexity components. Once you get into higher complexity you need better abstractions and structure then what KO on it's own provide
41.
by Offler 12y ago
Getters have been in JS since ES5 and can do what you just wrote. Obv Proxy is more powerful/has more traps.
42.
by Offler 12y ago
> The only thing I've seen is that in bigger projects, if there are locations where huge amounts of binding might take place (such as drawing, tables, etc...) you don't use two-way-binding in that particular place. Sounds like
43.
by Offler 12y ago
Very easily if they use ES6 modules and a package manager like jspm that understands ES6 modules. One line install, one line import.
44.
by Offler 12y ago
> IMO they should be declarative, that is - in the HTML - but programmable, and that's the way things have been heading. Sounds like React. WCs templates aren't programmable that's a DSL that is specific to Polymer.
45.
by Offler 12y ago
I think the biggest problem with WCs is they are standardizing best practices from 2011/Angular early days. Things have moved on and mutable two-way state that binds to a stateful DOM is no longer state of the art.
46.
by Offler 12y ago
I can drop a jQuery calendar into a React component with minimum fuss. I think the interoperability issue only comes with components from large frameworks.
47.
by Offler 12y ago
SASS and LESS are CSS DSLs, you are doing limited programming with CSS, at that stage you may as well do programming in a Turing complete language like JS and reduce the number of tools in your tool chain.
48.
by Offler 12y ago
3. By using meaningful values and separating side-effecting functions from pure ones, we can more easily reason about our program I'm not sure how that's something that static typing provides, just seems like good functional progr
49.
by Offler 12y ago
Things are improving rapidly, depending on the scale you intend to build to mature solutions are available for you. As it stands I don't see a better view layer solution then React, but I think you'd be best served learning it wit
50.
by Offler 12y ago
He does mention React as being a library that hits some of the points, some of them are just your own personal UX/project decisions which a framework would have no say over.
51.
by Offler 12y ago
You can send a pre rendered HTML shell with text content, when using server side rendering with something like React, quite quickly. I think this gives users a very nice experience especially compared to staring at a blank page!
52.
by Offler 12y ago
I think people have different use cases that they aggregate under "web application". If you are building a desktop replacement application then I can see that initial load might not be such a big deal but if you are building a les
53.
by Offler 12y ago
It's not really a post-React framework though, it has been designed at the same time as React was starting to take mind share so it's not clear if they have built something that responds to what React + Flux provide.
54.
by Offler 12y ago
I've worked with developers who "just got it done", I would often spend months afterwards fixing up their messy code.
55.
by Offler 12y ago
Today https://github.com/google/traceur-compiler
56.
by Offler 12y ago
It sounds like they will add support for the same constructs as JS will have in ES7 https://github.com/lukehoban/ecmascript-asyncawait
57.
by Offler 13y ago
I think a lot of FE devs aren't fully aware of npm scripts https://www.npmjs.org/doc/misc/npm-scripts.html - it's a handy way of calling commands just like you would in make. Quite a lot of the tasks tha
58.
by Offler 13y ago
I would use npm scripts as the first way to execute build steps in a package and only fall back to Gulp when it's not powerful enough https://www.npmjs.org/doc/misc/npm-scripts.html
59.
by Offler 13y ago
Don't rely too much on Grunt, only use Grunt/Gulp when npm scripts doesn't do the trick. npm scripts has the same direct command invocation that make has so no need for plugins.
60.
by Offler 13y ago
It was basically create by people who didn't have much JS experience so that's why it looks like Java more then JS, in fact that's why it's Java and not node. You're right it could have been much simpler. It used to

More ›