111–120 of 133 posts
Glimmer is smaller and faster than React, with TypeScript supported natively. This is a game-changer for people who are looking for a lightweight rendering library that ships with great tooling support and a larger framework ecosystem behind it.
Glimmer is smaller and faster than React, with TypeScript supported natively. This is a game-changer for people who are looking for a lightweight rendering library that ships with great tooling support and a larger framework ecosystem behind it.
Polymer already fills that nieche I believe, except TS (it uses plain ES6).
And the lack of great tooling.
And the lack of a large ecosystem.
And the insane data model.
I regret every moment I used Polymer.
Earlier quoted context omitted.
Polymer already fills that nieche I believe, except TS (it uses plain ES6).
Except for the lack of speed. And the lack of great tooling. And the lack of a large ecosystem. And the insane data model. I regret every moment I used Polymer.
- Tooling is quite good, polymer-cli, gulp, grunt support to name the most common stuff.
- https://www.webcomponents.org/elements - Thats a vibrant ecosystem :-) Big enterprises like ING, IBM, USAToday participate and release their components. (7k developers on slack channel)
- Insane data model? I work with my polymer elements same as I do with angular and react components. If in doubt just use redux/uniflow-polymer.
I get that you might not like it, but the issues you raised here are hardly valid (unless you used 0.5 or fresh 1.0)
This is the way not to design a landing page. 1) Ui components for what? 2) "Attention to detail of ember" - is that a quality comparison, or is it only for ember framework? 3) UI project without a single screenshot? 4) Doesn't mention one actual feature or component 5) GitHub link doesn't go to a repo. Instead it's a list of repos that you have to click around in to find the main project. 6) API docs link goes to a…
This is an open source project. Probably there is nobody agonizing over anything on this site (not because they are spending all their time working on the project, but because they probably have full time jobs). It's also likely that if you are arriving here, you probably already know what this is. You probably got here through Ember. If you want to contribute. https://github.com/tomdale/glimmer-website
If a project puts out a marketing page that doesn't clearly answer the "why should I use this and how will this make my life better" question, they're going to get feedback and criticism.
I found this link on HN. I literally have no idea what this is about.
Earlier quoted context omitted.
"The fact that Glimmer templates are "just HTML" makes them accessible to people like designers who may not understand all of the fancy destructuring or array mapping happening in your JSX." isn't this like, at least a little backwards? JSX is HTML and JS. templating languages are HTML with some custom DSL. destructuring and especially mapping are pretty simple concepts. creating a new syntax to cater to people who c…
> JSX is HTML and JS (?) "JSX is a preprocessor step that adds XML syntax to JavaScript." http://buildwithreact.com/tutorial/jsx Whereas the templates in Glimmer are built on HTML. At the 10,000 ft view, my two cents: it looks easier to reason about what is going on with dynamic elements in the template via handlebars together with what is going with the html elements themselves in terms of rendering/appearance/css,…
i just can't convince myself "it looks less scary" is worthy of the technical tradeoffs (for me, at the very least).
This is the way not to design a landing page. 1) Ui components for what? 2) "Attention to detail of ember" - is that a quality comparison, or is it only for ember framework? 3) UI project without a single screenshot? 4) Doesn't mention one actual feature or component 5) GitHub link doesn't go to a repo. Instead it's a list of repos that you have to click around in to find the main project. 6) API docs link goes to a…
I still don't think I will ever use this instead of react but maybe someone else likes it.
Glimmer is smaller and faster than React, with TypeScript supported natively. This is a game-changer for people who are looking for a lightweight rendering library that ships with great tooling support and a larger framework ecosystem behind it.
Earlier quoted context omitted.
I can see where you're coming from, but I tend to bucket apps I write into either general use case, mostly business-logic apps, or highly specific services. (say, a network proxy or compositor or something) The general use case apps all tend to share a good deal of requirements (multiple pages, authentication, forms, etc) and while it would certainly be possible to pick and choose each component, it's nice to have a…
Oh, absolutely. I wasn't trying to comment on the difference between the monolithic and modular approaches of Ember and React respectively. I think the monolithic approach actually solves the problem I'm describing to some extent, because developers in those ecosystems are forced into using these tools and patterns, which gives people a vested interest in making sure they're actually good before going into the next r…
Thunks _are_ "action creators", in the sense that they are given `dispatch` and allowed to dispatch things. The word "thunk" is a long-standing CS term, per [0].
I addressed the `getState` question in my blog post "Idiomatic Redux: Thoughts on Thunks, Sagas, Abstraction, and Reusability" [1]. As a summary, yes, thunks (and sagas) give devs complete freedom to do what they want, and more "convention-driven" middleware can be useful, but they're also a level of abstraction that's not necessary, and sometimes you _need_ to execute arbitrary logic that doesn't fit a specific pattern like "REQUEST_START/SUCCESS/FAILED".
[0] https://en.wikipedia.org/wiki/Thunk
[1] http://blog.isquaredsoftware.com/2017/01/idiomatic-redux-tho...
For those that want to try it out, it looks like the released ember-cli version doesn't support it. To test it out, you can replace the first instruction on that page with: `yarn global add ember-cli/ember-cli` (edited for better command)
This will do the trick: yarn global add ember-cli/ember-cli
Earlier quoted context omitted.
This will do the trick: yarn global add ember-cli/ember-cli
I get this error when I type 'ember' in terminal "zsh: command not found: ember"
1. Add the following in my .zshrc file: export PATH="$(yarn global bin):$PATH"
2. "yarn global remove [package-name]" then "yarn global add [package-name]"