Hacker News Reader

> I hate seeing talented development hours going to waste that could have been used to make an already existing project better.

They didn't go to waste. They made Deku and learned a lot along the way. Just because something exists, doesn't mean you can't build your own. And not everything has an immediate, positive outcome.

I wrote my own MP3 Player back when Winamp really whipped the llama's ass. That got my name in a local newspaper in India, which ended up being the small boost I needed for the Consul General to grant me a Student Visa to come to the US. A few years later, a fan of my MP3 Player messaged me and we became good friends. I interviewed for a job in Florida and ended up staying at his place for the weekend. A few years later, while I continued to work at the job in Florida, my friend and I built a scheduling webapp that made it to the front page of Wired during SXSW.

An incredibly long list of positive things that happened in my life, I can track back to spending a week or two writing that MP3 player in my youth. If you ask me, I'd do it all over again. So I'm glad they build Deku, regardless of how it compares to React.

Really awesome story. I agree with you wholeheartedly that there is always value in building things!

There may or may not be value to other potential users or even to the employer though and these seem to be the only perspectives addressed by commenters.

If the company's resources could have been better spent elsewhere than that is the company's (and its stakeholders') problem. Please stop discouraging others from creating and sharing because you don't find the creation better or worthwhile right this instant.

I am not invested in either framework but there are some very clear differences:

- size/complexity: React is a monolith that can't be digested by just skimming a couple small files

- API surface area: less room for major semver bumps

- modularity: React devs seem to fear dependencies

- versioning: React encourages the use of peer dependencies which is truly going to be a nightmare in 2 years with hundreds of UI modules across different conflicting React versions

- no singletons: React can only be required once, otherwise bats will fly out of your computer. This is compounded by the versioning issue.

- style: React uses and encourages a different programming paradigm

> Deku to me only has a few slight differences to React.js

This framework is genuinely different from React in how you use it. I know several JS programmers who prefer functional style, yet choose to incorporate React-style classes because React is really good at what it does. This gives them an alternative.

The components built with Deku will be different in programming style. And that's really, really significant.

https://github.com/Matt-Esch/virtual-dom/

virtual-dom is excellent.

Also check out mercury:

https://github.com/Raynos/mercury

Or better yet, fork mercury and modify the index.js file and package.json. It's a bunch of libraries masquarading as a framework (which is awesome because it means it's modular instead of monolithic)

What do you say about https://news.ycombinator.com/item?id=9529457?

React is really much more than just some virtual dom implementation.

Have you heard of omniscientjs: http://omniscientjs.github.io? It allows you to use react in a functional style.

I'm disappointed for a different reason. I'm just sick and tired of the delta new thing. Frontend dev as it is practiced today is horrible ... libraries and frameworks seem to have shelf lives measured in months!

I was watching a video posted this morning (how NYT uses Go) and the dev was mentioning how challenging their system used to be with different languages - Python, PHP, Java and Groovy ... so they decided to redo major chunks in Go. Seriously?

I don't pretend to have the answer ... stopping to innovate isn't going to cut it. But I increasingly feel that as a tech worker, I'm on a train careening towards a ravine without a bridge. But hey ... lets go faster and it'll be a fun ride!

> libraries and frameworks seem to have shelf lives measured in months!

What "shelf life"? If the library works for what you app needs it to do, there is no use by date.

> their system used to be with different languages - Python, PHP, Java and Groovy ... so they decided to redo major chunks in Go. Seriously?

Valid reason for a rewrite, especially considering the quality of one or two of those languages. A language can look and run OK when used for a script calling system code, but when those scripts are glued together and become the system, all sorts of problems can manifest. It's only sensible someone there looked at the sit and planned out a replacement.

Sorry, but did you read the article? They claim a 38% performance advantage over "other frameworks", which I assume includes React.

Even if the performance was at React's level, a first pass at Deku shows it as much preferable to React in terms of coder experience.

I think also the fact that Deku has a smaller file size than React.js is significant (10KB vs 118KB). That would have been more difficult with a fork.

If Deku looks solid enough I might consider using it. And hopefully it can influence React too.

But Deku gives them the advantage of not being bound to possibly devastating patent licenses.