Comment by cheez | Hacker News Reader

Comment by cheez | Hacker News Reader

This is not exactly relevant to the post and is a bit selfish but... I'd like some feedback.

Things like things I have invented in the past (before they were public):

- React - Redux - This thing - Various other things

In fact, I wrote a UI framework that runs in Web Workers which does React+Redux better than React+Redux. Redux is terrible for real-time work, whereas my framework combined beautifully for real-time work. As real-time as you can get in the browser anyway. And I could throttle FPS perfectly as a result.

I know I'm not the only one who creates these things, and I know I'm onto something usually because the "old guard" generally are terrified of this new thing that I built.

I am old. And I think I am probably wrong when inventing things which terrify other people but I'd like to figure out how to find a more... amenable audience, not just in my work, which is mostly independent now.

How do I find people who see possibilities? Should I be talking about these things at meetups? How do things go from my own personal products/projects to being posted on HN?

Building something great is only half the battle. The popular tools you are competing with have been marketed to a large extent. Redux is a good example of something that was shown to a large crowd at a conference who wanted something just like what they were seeing. It didn’t stop there though. They took the time to write really clear documentation. Dan did free videos for egghead to teach people how to use it.

Some open source authors are already very well connected. Sometimes the projects are backed by a large company. There are several ways to get the word out.

I think the problem I've had is that I'm around people who don't like change, which is most people. So I believe that things I invent are not useful to anyone but me.

I need to have better ways to get the word out.

I was also in a situation at work where I found that redux did not work great for real-time code. Have you made your solution public?

Also related to this article, webworkers are great for offloading work from the main thread until you've got high data rates. It doesn't take a lot of data to get to the point where serialization across the worker boundary nullifies the performance gains of moving the work off of the main thread.

Nothing is public.

Regarding your comment about serialization: that's why I used websockets in the workers. It went pretty well except there was a bug in Chrome where the websocket in the webworker was still subject to the main loop. Something like that.

Anyway, the point of offloading everything to webworkers was to make sure that the main thread is free for rendering. So there was very little to serialize, aside from dom differences which are generally not significant.

How would websockets reduce serialization overhead (assuming no chrome bug)?

Slightly off-topic, but you might look into MobX. It can be more performant than Redux for particularly large component trees because it allows child components to update without going through their parent (and checking all their siblings, for that matter).

Sibling already asked if your tech was public (no, it's not), but do you want to make it public? Do you want to take money for the thing itself? Release under (A)GPL 3 and take cash from those that don't want to publish their app/to work on feature requests?

This sounds like something I might want to use for a project in my pipeline, with "thing that works well and terrifies the old guard" being in the spirit of "post-blub"[0] languages (think APL rarely using function definitions because the concise syntax[1] makes inlining more readable).

[0]: http://paulgraham.com/avg.html [1]: This is a single-file compiler. The logic is just the upper weird-symbol-laden part: https://github.com/Co-dfns/Co-dfns/blob/master/codfns.dyalog

Honestly, if you invent something good and it’s better people will flock to it. If they don’t, then usually it is not.

Look at angular, the full backing of google yet people moved to react... and now to vue which was basically made by one guy

It's hard for me to imagine people who know React moving to Vue. I'd have to assume different people, who've never known the beauty of React, are driving Vue's growth due to marketing.

I really like react, but I see the appeal of the .vue files in the vue framework. I think there are perhaps more people than you think who don't like how CSS integrates with react (CSS-in-JS) and prefer having the single file component, with super easy style scoping and with easy traditional css syntax highlighting support in a .vue file

Well, CSS-in-JS is just one option for styling React components.

Have you looked into Emotion (https://emotion.sh)? It supports several modes of usage that cover a lot of use cases pretty elegantly.

Dude, where are the code samples? You lost me by not having them. I want something nice like Svelte.

They are not too hard to find. I would use this one as a starting point: https://github.com/neomjs/neo/tree/dev/docs/app/view (since the docs app UI is written using neo.mjs).

On the repo you have an apps folder (RW2 is a better example) as well as an examples folder.

If you open the online examples => docs app, you can view into the code for all classes. If you use the docs app version with the Chrome flag, all available examples are included.

This sounds like a philosophical question :)

In general humans are afraid of radical new ideas (at least most). There is also the "riding the wave" phenomenon, which is slowing down innovations to some degree.

Meetups or conference sessions are a good start, since the audience ist mostly curious.

Reply on news.ycombinator.com