Profile cover photo
Profile photo
Terrence Miao
154 followers
154 followers
About
Terrence's interests
View all
Terrence's posts

Post is pinned.Post has attachment
Apache Spark Survey 2015 Infographic - Preparing for the Next Wave of Reactive Big Data

Press release: http://www2.marketwire.com/mw/release_html_b1?release_id=1219120
Spark primer: http://dbricks.co/spark-primer
Databricks primer: http://dbricks.co/db-primer
Photo

Post has attachment
Top 50 Developer Tools of 2016

from stackshare.io

Post has attachment
Photo
Photo
2/17/17
2 Photos - View album

Post has attachment
The four kinds of bullshitters

Read more: https://withoutbullshit.com/blog/4-kinds-bullshitters-trump-fits
Photo

What is the average lifespan of software or framework?

That's a million dollars question.

Post has attachment
That is why the sport is the best form of Reality TV
PhotoPhotoPhotoPhotoPhoto
2/7/17
5 Photos - View album

Post has attachment
I think what you asking here is why would i use smaller components like the view-only library react (probably with some event module like flux) over a full-fledged MVC framework like angular?

• Small components usually do one thing very well.

• There will never be a perfect framework so you can just hack the most relevant features together using npm.

• Small libraries have simple documentation and they are easy to set up and use.

• Any problems and there’s no waiting for the next release of the entire framework, you simply throw up an issue, the authors fix it, push it and then bam it’s on npm for everyone else and no other components have been disturbed.

• If you find you don’t like the templating language or error handling, you don’t have to rethink the entire project, you just hot-swap the component for another and you’re on your way again.

• By using small libraries – components with a dedicated purpose and a small surface area – it becomes possible to pick and mix, to swap parts of our front end stack out if and when they are superceded

• New projects can replace only the parts that matter, whilst core functionality whose designs are settled – routing APIs, say – can stay exactly the same between the years.

• You can move your legacy projects to new technologies incrementally, rather than rewriting everything, providing you stick to good practices and wrap those libraries carefully.

• When different problems are answered by different libraries, their solutions can compete directly. If Framework A does X well and Y badly, compared to Framework B’s great Y and shaky X, you’re stuck. But if Library A and B both try and do X, they can compete in a direct fashion in discrete and measurable ways.

https://www.quora.com/Why-would-I-use-React-over-AngularJS

Photo

Post has attachment
Poker computer trounces humans in big step for AI

Post has attachment
AngularJS is going to continue to succeed for some time. But change is inevitable.

Web Components are coming.

WebComponents create the ability to do all the sorts of markup-driven programming like AngularJS, ReactJS, but less ecosystem dependent. Because DOM is integration point for all the kinds of JavaScript frameworks. Web Components make it MUCH easier to interoperate between components.

The future isn't here yet, but it will change fundamental assumptions about how a JavaScript framework should act and what it should be responsible for. Those shifts in assumptions frequently cause frameworks will drop out of the ecosystem quickly than expected.

Post has attachment
My Blog

Personal blog. hexo.io, a powerful blog framework, generates static content at speed. With Content Search feature built-in. hosted on github.io.
Wait while more posts are being loaded