Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
thenewestkid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
31.
▲
by
thenewestkid
9y ago
Sure, I know about MobX. I use ES6 Proxies instead of the getter/setter based transparent reactivity they use. It allows me to have less edge cases in exchange for narrower platform support. MobX is also moving in the Proxy direction w
32.
▲
by
thenewestkid
9y ago
Valid point. You can move that logic to the component and leave the store for pure data manipulation and handling only. I do that for bigger projects, but in this case I wanted to make things short. The goal of this series is not to teach p
33.
▲
by
thenewestkid
9y ago
Passed around local state vs global state is indeed an interesting topic. Honestly I think both are nice in good hands. The library I made supports both of them, but I did not mention local state management for the sake of simplicity. You c
34.
▲
by
thenewestkid
9y ago
It is actually ES5: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... In a nutshell: it is used for computed properties, which compute their value on 'get' operations instead of s
35.
▲
The Simplest React Stack – Part 1: Bootstrapping and State Management
(medium.com)
73 points
by
thenewestkid
9y ago
|
31 comments
36.
▲
The React Stack Challenge – Part 1: Bootstrapping and State Management
(medium.com)
1 points
by
thenewestkid
9y ago
|
0 comments
37.
▲
Show HN: Quick fix for unwanted duplicate history entries in web apps (GitHub)
(github.com)
3 points
by
thenewestkid
9y ago
|
0 comments
38.
▲
by
thenewestkid
9y ago
React Easy State is a simple library, which provides balance between local component state and global stores. It uses a modern version of transparent reactivity (similarly to MobX) with ES6 Proxies under the hood. Please check it out and gi
39.
▲
Show HN: Simple, Balanced State Management for ReactJS with ES6 Proxies (GitHub)
(github.com)
2 points
by
thenewestkid
9y ago
|
1 comments
40.
▲
by
thenewestkid
9y ago
Easy State provides a healthy balance of local and global state management in a simple, scalable way. It consists of two functions only with no hidden complexities. Please give it a try if you have 5 minutes to spare (:
41.
▲
Show HN: Easy State: Simple, Balanced State Management for React with ES6 Proxies
(github.com)
1 points
by
thenewestkid
9y ago
|
1 comments
42.
▲
by
thenewestkid
9y ago
Great, I would be happy to check you library! Just send a link here or pm me on twitter (@solkimicreb1) when you can share it. PS: your argument about MobX got me thinking. I decided to add a new function to v2, that creates MobX like exter
43.
▲
by
thenewestkid
9y ago
This is my personal opinion. Structure wise: Having a singleton app store and separate component states together is the best pattern. Hidden details of a component's functionality should go into its own state. App level data (like the
44.
▲
by
thenewestkid
9y ago
You are right. It does use ES6 Proxies and they are not polyfillable. IE and React native is not yet supported because of this (it's mentioned in the platform support section).
45.
▲
by
thenewestkid
9y ago
I understand why you might feel like this, but don't judge too quickly (; Easy State can do (pretty much) anything MobX does. It just does it in the background without the extra explicit syntax (observable, action, observble modifiers,
46.
▲
by
thenewestkid
9y ago
I actually think that simpler syntax is a big win. See the key features section for the other advantages (no async issues, optimal shouldComponentUpdate). About the cost: see the performance section for a third party benchmark. I think you
47.
▲
by
thenewestkid
9y ago
Brief summary (from the repo): Easy State aims to make React's state management simpler without adding new syntax. To achieve this it makes the following modifications. It replaces React's setState() with plain native JavaScript.
48.
▲
Show HN: Easy State: simplified state management for React (learn in a minute)
(github.com)
6 points
by
thenewestkid
9y ago
|
11 comments
49.
▲
Show HN: Easy State: replace ReactJS's setState with direct state manipulation
(github.com)
1 points
by
thenewestkid
9y ago
|
0 comments
50.
▲
Show HN: Easy State: improves React's state management without externalizing it
(github.com)
2 points
by
thenewestkid
9y ago
|
0 comments
51.
▲
Show HN: Easy State: A library that replaces React's setState with plain JS
(github.com)
1 points
by
thenewestkid
9y ago
|
0 comments
52.
▲
Show HN: Easy State: A library that replaces React setState with plain JavaScript
(github.com)
2 points
by
thenewestkid
9y ago
|
0 comments
53.
▲
Show HN: Easy State: A library that replaces React setState with plain JavaScript
(github.com)
1 points
by
thenewestkid
9y ago
|
0 comments
54.
▲
by
thenewestkid
10y ago
Yes, it is a GitHub hosting issue and it works when the project is run locally. I am aware of the GitHub SPA hack, but I decided against it, since it would introduce unwanted complexity. My main goal with the repo is to teach how to use the
55.
▲
by
thenewestkid
10y ago
Its a framework demo, the goal of it is to teach how to use the framework. After reading all the comments, I think I should clarify it in the repo readme (:
56.
▲
by
thenewestkid
10y ago
Its just a feature demo, but I actually think that list animations between page changes add value. It makes it easy to spot which stories made it to the top when you switch from new to top for example. (Those stories are animated to their p
57.
▲
by
thenewestkid
10y ago
Hi! I am the author of the NX framework and this example. Thx for posting this here (: The clone is not intended to be HN alternative, it is an introductory project for the framework. The redirection issues are because of the GitHub hosting
58.
▲
Show HN: NX, the modular front-end framework enters beta 2
(nx-framework.com)
2 points
by
thenewestkid
10y ago
|
0 comments
59.
▲
The Google Analytics Setup I Use on Every Site I Build
(philipwalton.com)
3 points
by
thenewestkid
10y ago
|
0 comments
60.
▲
Concurrency and Parallelism: Understanding I/O
(blog.risingstack.com)
3 points
by
thenewestkid
10y ago
|
0 comments
More ›