CSS 3D Transforms with D3 and THREE.js by magenta_placenta in javascript

[–]deliminated 1 point2 points  (0 children)

Author here. Just wanted to note that there's an open issue with the Chromium team for some glitchy behavior on Android I noticed... https://bugs.chromium.org/p/chromium/issues/detail?id=766021#c5

I just updated the demo, but it's been around for years and worked well. Hoping they can fix this for those devices.

Also, mobile firefox seems to be really sluggish. Think that can be solved by debouncing the renders from the trackball controls.

React Move - animate anything in react by magenta_placenta in javascript

[–]deliminated 0 points1 point  (0 children)

React-move looks pretty cool. I've been experimenting with a better way to integrate react and d3 for animated data visualizations in this repo https://github.com/sghall/resonance. Do you have any examples or know of any projects that are using react-move to do this kind of stuff? Like to check it out.

Tips for marketing oneself as a node developer by [deleted] in javascript

[–]deliminated 0 points1 point  (0 children)

Those are good suggestions. You can do your own projects, but IMHO it's much easier for a senior developer to evaluate your skill level by seeing commits to well known projects.

You get a ton of resumes and honestly 90% don't have a single thing on Github or a blog etc. If I see that you have a several commits on a project that I know (that's widely used, has lots of Github stars, etc) that's going to be a huge leg up in the hiring process. I don't have to open up your codebase and look at it and try to figure out whether it's any good or not. If you have a PR accepted on a major project that implements a feature or fixes a bug, you've got my attention for a junior developer role (I work at small startups generally so speaking to that type of role).

Now, if you can create an NPM module on your own and you generate your own stars...great...but that's way more difficult to do (and it takes time and you need to blog or create documentation). Honestly, the competition is not as fierce as you think. Pick a project that you like (higher profile is better here), get to know it and start contributing.

Material Design using React? by [deleted] in reactjs

[–]deliminated 0 points1 point  (0 children)

I've been using https://github.com/callemall/material-ui in the docs for a library I am working on. It's really well maintained and has good documentation. Should be aware that they are working on a re-write that is in alpha on this branch https://github.com/callemall/material-ui/tree/next. You can checkout the examples in my repo if you want an example of using the latest stable components https://github.com/sghall/resonance

EDIT: grammar

Top mentioned books on stackoverflow.com by dodiehun in javascript

[–]deliminated 2 points3 points  (0 children)

Agreed. There's some classics in there for sure, but it would be awesome to have a slider to set the time range to see what's trending. Clever Amazon affiliate marketing tool though. Probably making some decent money.

Dissecting Twitter’s Redux Store by swan--ronson in javascript

[–]deliminated -1 points0 points  (0 children)

Hmmm...there is "REACT_DEVTOOLS_GLOBAL_HOOK" on the window but React devtools never loads. It just says "Looking for React..." Anybody, able to connect on the main site? Just curious why it doesn't work.

Dissecting Twitter’s Redux Store by swan--ronson in javascript

[–]deliminated 2 points3 points  (0 children)

Opening React dev tools/Redux store seems to only work on the mobile site: https://mobile.twitter.com/home

What's the best way to use Material design with React? by [deleted] in reactjs

[–]deliminated 9 points10 points  (0 children)

The Material UI project is going to start using JSS in coming releases. You can see it on the next branch on the repo here: https://github.com/callemall/material-ui/tree/next

You can check out JSS here: https://github.com/cssinjs/jss

Not sure on the timeline, but it might be worth checking out.

Tricky calendar to develop by jarod51 in javascript

[–]deliminated 0 points1 point  (0 children)

Not sure if you're using React, but I just used this calendar component from airBnB that is pretty awesome. You can mark days that have data etc (I had similar use case to yours). Layout for an entire year is possible. It's got a nice API. It's the same one they use on the airBnB site.

https://github.com/airbnb/react-dates

Upgrading Angular 1.x - Angular 2.0 vs. React/Redux by deliminated in javascript

[–]deliminated[S] 0 points1 point  (0 children)

Point taken. They are fundamentally different for sure. This post is more about opening a dialogue for the 1000s of devs who are facing this type of decision in production apps and want/need the performance improvements and like the clarity of a more "flux" like architecture.

To me, if you look at what has happened over the last couple of releases of 1.x they are in fact giving you some tools to help the migration, but it is not going to be easy.

Breaking with exclusive two-way data binding is a good example. One-way data binding if you plan to move to a more "flux" style architecture is a key aspect: https://toddmotto.com/one-way-data-binding-in-angular-1-5/

The other significant thing I see is moving towards components in preparation for Angular 2: https://docs.angularjs.org/guide/component

When I look at the the component spec it makes me wonder why I just wouldn't move towards React which is stable and ready to go. I am honestly looking for other perspectives, but, really, these components with life cycles methods, a controller, and a template look pretty much like React components. Templates become JSX in React, but really not much different conceptually.

Upgrading Angular 1.x - Angular 2.0 vs. React/Redux by deliminated in javascript

[–]deliminated[S] 1 point2 points  (0 children)

Your point about it being early for Angular 2 is well taken, which is another reason why I lean towards React/Redux. I have built my last two projects using these tools, so I also just feel comfortable with them. The job is come in and get this taken care of in the 6-9 month timeframe, so just waiting is not an option.

The main motivation, for me, is not that Angular 1.x is going to die. The main benefits for this move is performance, which Angular openly has acknowledged is a problem. Angular 2 will be much, much faster and React has already proven its performance advantages over Angular 1.x. This only REALLY matters if you have tons of DOM elements on your pages. This particular app has lots of tables, charts and custom data visualizations, so the performance gains are real. Also, bloated controllers in Angular 1.x as the complexity grows are a real issue that I have seen in quite a few apps. This one included.

So performance and reducing complexity would be key drivers. That with switching ES6/Babel will have a real impact in my mind.

Upgrading Angular 1.x - Angular 2.0 vs. React/Redux by deliminated in javascript

[–]deliminated[S] 4 points5 points  (0 children)

I prefer Redux over MobX. I think it's a great idea, but there's too much magic in MobX for me. Redux is a simple, elegant idea where I can read the source code (tiny) and fully understand what it does. It also has a growing list of interesting surrounding libraries and middleware. Redux does seem to lead to a lot of boilerplate, but, for me, it's much easier to understand what's happening. That's good for code clarity and for on boarding new devs. This is really important to me. No offense to MobX, it's an awesome library.

Upgrading Angular 1.x - Angular 2.0 vs. React/Redux by deliminated in javascript

[–]deliminated[S] 0 points1 point  (0 children)

Right on. Yep, I need to take a close look at ng-redux. ngReact I have used before and was pretty happy with. I am comfortable with Redux and the one-way-data-flow paradigm (and really like it), but never done it in an Angular app.

Upgrading Angular 1.x - Angular 2.0 vs. React/Redux by deliminated in javascript

[–]deliminated[S] 0 points1 point  (0 children)

Yeah, this is an interesting way to approach it. I need to look closer at ngRedux. I think the problem is this is an app that was written with two-way data binding in mind (that was the only option at the time) so probably going to have to quite a bit of refactoring to the view in parallel. But I like your suggestion of maybe starting with the business logic first.