madmaniak

10 ms·

91.
by madmaniak 8y ago
You have whole chain of implications showed in presentation which all together makes a big mistake. If you made a small mistake thinking DOM is slow and you build whole technology on top of it making more small mistakes on your way and it a
92.
by madmaniak 8y ago
The huge part of presentation is about mistakes of React - if you already know about it go on and safe your time. Unfortunately original title was censored.
93.
by madmaniak 8y ago
Maybe because it's older than Babel.
94.
by madmaniak 8y ago
Props are definitely a data you want to display somewhere in your component. If you need to pass it all the way through, you create a whole unnecessary structure inside of another layer. Like I said in the video, it's direct implicatio
95.
by madmaniak 8y ago
It's 30x faster than anything. Check scrimba.com
96.
Rubylike Frontend [video](pivorak.com)
64 points by madmaniak 8y ago|19 comments
97.
by madmaniak 8y ago
Another Virtual DOM thing - which is obviously wrong.
98.
by madmaniak 9y ago
OK great. So can you link the offer?
99.
by madmaniak 9y ago
Some people read documentation, some tests (lol) to know what's going on. I read code - and Imba has really nice code to read. Also they are responsive on Gitter. But as I said. It's a pity.
100.
by madmaniak 9y ago
It has a syntax dedicated to DOM operations. Doesn't change principles from React perspective - it's component based. So what I do for example: I can copy and paste react code, quickly parse it to Imba notation, and the result is
101.
by madmaniak 9y ago
It's lacking the best - Imba. The rest are just funny toys. Sad it's lacking documentation. Hope it will change soon because it kills with performance and developer experience.
102.
by madmaniak 9y ago
I just disagree with declaring paths with kind of regex pattern matching set of rules. This approach is flexible and natural. It will not stop you when your application became complex and even with simple cases it's faster - you touch
103.
by madmaniak 9y ago
Oh yes. I was considering that. I've stayed for a while with a convention solution - write and toggle replaces, but go adds to the history. You can build on top of that, but I think it's reasonable now. It manages for you what you
104.
by madmaniak 9y ago
1. Please explain me what you'd like to know. Router is one layer of SPA / PWA so you need it if you want to make one. It's framework independent and I'd not like too add more dependencies to your project for such a smal
105.
by madmaniak 9y ago
Thank you for your advices. What can I say - I am and I will be in a rush for a while. I have also bigger personal projects. I'm glad I was able to ship it now. I have good feedback and I'll make it better thanks to your comments.
106.
by madmaniak 9y ago
I serve it as a static file. There is no problem with server rendering if that's your question :)
107.
by madmaniak 9y ago
Yay! :D
108.
by madmaniak 9y ago
Game is a complex thing and it would handle it perfectly. Believe me it handles really well also simple cases. For me it's not a first iteration on the idea of routing automation. It gives you freedom and is really handy. Even if you n
109.
by madmaniak 9y ago
Thank you for all advices. I'll host it properly. But what do you think about the library?
110.
by madmaniak 9y ago
It's a joke from stupid buzzwords - kind of "serverless". You don't define routes with pro-router - you just use a store which serializes to url.
111.
by madmaniak 9y ago
You have a valid point about # and that it works on static site. I'm aware of that and I'll add this as a feature so you'll be able to choose on init(). Please explain me the part about back button on example.
112.
by madmaniak 9y ago
Obviously I failed with preparing a proper flexbox css. I had one day to make this website. I'll polish things too look well. If you can ignore the layout you'll find neat art project for frontend routing :)
113.
by madmaniak 9y ago
Thank you for kind words and sorry for being so enigmatic. Step 1: Attach pro-router Step 2: R.init(root: 'helloworld') Step 3: R.write('foo', 'bar') # url changes from '/' to '/hellowo
114.
by madmaniak 9y ago
Nice one :) You decide what you keep in url. Use case of google map when you're scrolling a map and you want to share a location with your friend is not vulnerable, right? Now it's easier
115.
by madmaniak 9y ago
Thank you, I'll improve it
116.
by madmaniak 9y ago
You can use anything with this router (redux too). I agree react router is a nice tool - but in a classic paradigm. The difference is - you don't define routes. If you create a component and it needs a data you just ask the url store f
117.
by madmaniak 9y ago
as you see it's a small tool you can use with any framework
118.
by madmaniak 9y ago
Thanks for recommendation. I've linked it to my domain http://router.maniak.pro:3000 right now. I'll change the port to standard http soon.
119.
by madmaniak 9y ago
Will fix. I was in a rush.
120.
by madmaniak 9y ago
Treat url as a store. Serialize to url and deserialize to objects.

More ›