It's really sad most of the front-end community has moved from Redux. This could be coupled with Redux to give you possible transitions of interfaces or how a particular session has transitioned.
Fuzz Map
11–20 of 20 posts
Re: Fuzz Map
#12How is it able to test code coverage in the browser? Can JavaScript step through JavaScript?
I'll speculate. They add extra lines (most probably via AST, not lines of chars) to the code which register if code run. Can't confirm that with code or anything. I saw similar techniqies in test coverage tools.
Re: Fuzz Map
#13How is it able to test code coverage in the browser? Can JavaScript step through JavaScript?
I'll speculate. They add extra lines (most probably via AST, not lines of chars) to the code which register if code run. Can't confirm that with code or anything. I saw similar techniqies in test coverage tools.
True, if you rewrite the code, then that would even work via a simple injection of
_cover(123);
Could be a fun project to write a bookmarklet that does this to the current page, then lets you use it and then tells you which parts of the code have not been used.
Re: Fuzz Map
#14Looks great! Although with the example.. I couldn't get it to show the "you need to be 21.." message to appear as a state
Re: Fuzz Map
#15fascinating that ui-focused website has scrollbar overlapping with the X sign on the welcoming pop-up...
Re: Fuzz Map
#16It's really sad most of the front-end community has moved from Redux. This could be coupled with Redux to give you possible transitions of interfaces or how a particular session has transitioned.
What are they using now?
Re: Fuzz Map
#17It's really sad most of the front-end community has moved from Redux. This could be coupled with Redux to give you possible transitions of interfaces or how a particular session has transitioned.
What are they using now?
In early days React, which was also the time where SPAs were popular, Redux was popular, as with an SPA you usually have to manage a lot of local state, which is benefits a lot by having a central managed state.
With SPAs becoming less popular, more state moving to the server again (trying to keep local state in sync with remote DB state for a long lived session is a PITA), and React hooks making medium-size state management more accessible, bigger frameworks such as Redux became less popular.
Nowadays you have usually have a lot of individual sections of components with hooks-based state, rather than having everything connected to a central Redux store. You usually still have some form of global state management though, in the form of e.g. a shared react-query cache (used for data fetching). Besides that libraries like react-hook-form that handle state management for specific use cases have also become more popular.
Re: Fuzz Map
#18It's really sad most of the front-end community has moved from Redux. This could be coupled with Redux to give you possible transitions of interfaces or how a particular session has transitioned.
I found the concept of redux - a single source of truth for the state of your app - compelling. But the implementation cost was horrendous. As a developer I am constantly aware of the cost benefit of tools, libs, etc. The benefit of redux was very high. It reduced the theoretical complexity of my apps tremendously. But the cost of implementation complexity was even higher. There was too much additional code, boiler plate, and implementation complexity.
Later, I started using one single context wrapping the whole thing. This provided most of the benefit of redux - all the code was in DataProvider.js - at the cost of one file. I found that the organization provided (ha ha)less need to go down the whole immutable path. This was just a practical thing, but it has worked extremely well for me.
Re: Fuzz Map
#19Earlier quoted context omitted.
What are they using now?
In early days React, which was also the time where SPAs were popular, Redux was popular, as with an SPA you usually have to manage a lot of local state, which is benefits a lot by having a central managed state. With SPAs becoming less popular, more state moving to the server again (trying to keep local state in sync with remote DB state for a long lived session is a PITA), and React hooks making medium-size state ma…
Thank you very much for your lovely explanation, interesting developments!
Re: Fuzz Map
#20It's really sad most of the front-end community has moved from Redux. This could be coupled with Redux to give you possible transitions of interfaces or how a particular session has transitioned.
I don't know if it's a shame. I love using Redux today, much more than when it was the 'current thing', when you couldn't go on any front end forum without reading the same tedious debates and criticisms over and over. For those who like the Redux approach, and don't mind the trade-offs, I'd argue there's never been a better time to use it. Front-end is huge, so even now that most people have moved away from it, it's still got a relatively big community, i.e. doesn't feel like it's going anywhere, and it's now very mature, well documented, and more 'standardised' by Redux Toolkit.
After a couple of decades programming I've come to think the size/status of something like Redux is today (mature, stable, moderate size community of long-term users who are focused on actually building things with it) is the perfect kind of project to depend on. Projects that have survived the hype cycle are what you want, not projects that are currently in the eye of the storm. The fact that it seems like yesterday's thing is good, it puts off exactly the right kind of people.