nohuhu

8 ms·

1.
by nohuhu 6y ago
> The better ones are often tied to company-specific frameworks. That is because to implement accessibility in a grid/tree widget to a meaningful level, you need a lot of underlying code. Even in modern browsers. Source: implement
2.
by nohuhu 6y ago
> Redux is fantastic and it's quite a simple library. ... and it's an extra library. You can do without it in React, you know. > The rest is what gets you into trouble. Exactly. My biggest beef with Redux (and React, too) ha
3.
by nohuhu 6y ago
> it's the only way to go to build products. This! Back-to-front is a good way to build a scalable, performant, cleanly designed software . Front-to-back is the only viable way to build a usable product . > Users just do not ca
4.
by nohuhu 6y ago
> If that works with your model of the world that's great. Wouldn't kick it out of bed for farting. Oh I see, entity naming could also be improved. ;) > For me, the easiest way to handle async and effects in Redux is to writ
5.
by nohuhu 6y ago
One viable alternative for thunks and sagas that I came up with is using async functions and explicitly getting/setting state: https://github.com/riptano/statium#viewcontroller Still a long list of chores to impro
6.
by nohuhu 6y ago
> I could see a barn find in bad shape suffering a lot more than that. Yeah well, in between being a bottom feeder and looking for fun, machines usually come to me as project pieces rather than usable tools. :) I'd never opted to re
7.
by nohuhu 6y ago
I haven't gotten to measuring wear on the ways yet, don't think I'll need to scrape them but that's a possibility. This is a pet project of mine, a barn find that was in a pretty bad shape when I got it: rusty, crusty, w
8.
by nohuhu 6y ago
Thanks for submission, a really interesting read! I'm into restoring old woodworking machinery, and hand scraping is one of the methods for truing lathe ways that I've read about. Could possibly be required for the Walker-Turner l
9.
by nohuhu 6y ago
A framework is usually the foundational code for an app, for sure. In this case it was a bona fide JavaScript framework, Ext JS. It is that big because it implements a lot of things that other frameworks don't even try to try thinking
10.
by nohuhu 6y ago
> You still keep it all in your head, but the compiler errors protect you from small mistakes. It is interesting how "protecting from small mistakes" is touted as "solving our API woes", innit? At some point it is lib
11.
by nohuhu 6y ago
> I'm sure that class of bugs is relevant for Typescript programmers, because they never develop the skills to not implement those bugs in the first place. This rings true, especially given that in my experience, most of the static
12.
by nohuhu 6y ago
Ext JS is the framework in question. The last time I worked on it (Oct 2018), it was about that size shared between two major versions: Classic toolkit and Modern toolkit, including tests and examples. It could be more than that now but I h
13.
by nohuhu 6y ago
> Funny, I usually see type haters claiming that they don't actually make the kinds of mistakes that are fixed by strong typing. As your typical type hater, my preferred argument is: yes, static typing prevents a certain class of bu
14.
by nohuhu 6y ago
Not my blog but I find it fascinating: https://technicshistory.com Really surprised nobody mentioned it yet...
15.
by nohuhu 6y ago
When people ask me what my wife does for a living, I tell them she's working as a full time mom to our 4 kids. She likes that a lot more than being a "housewife". :)
16.
by nohuhu 7y ago
This makes total sense to me. If you can solve the hardest problems, it is reasonable to expect that you can solve the rest as well. If you fail at solving the hardest problems, the system will not work anyway. The science, then, lies in id
17.
by nohuhu 7y ago
So I guess this is how living in the 1960s felt like? :)
18.
by nohuhu 7y ago
> I'm not familiar with either of them, but that seems like a lot more code! Sorry, I should have been more forthcoming with explanations but got paged at $work. Almost nobody is familiar with Statium yet, it's very new. :) It
19.
by nohuhu 7y ago
This is what Statium and Urlito are for: import ViewModel from 'statium'; import stateToUri from 'urlito'; const defaultState = { foo: 'bar', qux: { time: Date.now(),
20.
by nohuhu 7y ago
No generation gap here. I was building my first web apps in early 2000s as well, with Apache and mod_perl. That was exactly the point of that experiment: hey I recall this stuff was _easy_, I don't need it fancy, let's take the mo
21.
by nohuhu 7y ago
Everybody is different. You might be more productive at doing stuff the "Rails way", somebody else might not be. I know I won't be, simply because I don't know Ruby and/or Rails enough to be productive in it. Not ev
22.
by nohuhu 7y ago
How does that play with Redux Hooks for example? https://react-redux.js.org/next/api/hooks If you are using hooks in your components, you need the global store instance. To call this unit testing is too big a stre
23.
by nohuhu 7y ago
> The ~100ms between submitting a form and getting error messages isn't that big of a hurdle, in my experience. The issue here is not the length of time it takes for the response to come back, rather the fact that there is any delay
24.
by nohuhu 7y ago
> Clicking "save" and getting that feedback in ~100ms is not, in my estimation, worth the massive extra overhead of using a front-end framework, duplicating your validation requirements, etc. Is it worth spending more developer
25.
by nohuhu 7y ago
> The server still needs to validate, no? Client input should never be trusted. Server needs to validate, but that doesn't mean client shouldn't validate as well. > I've never seen a form that really benefitted from cli
26.
by nohuhu 7y ago
How do you test individual components in isolation if they depend on the global state store?
27.
by nohuhu 7y ago
Another way of doing controller stuff is by actually using a Controller: https://github.com/riptano/statium#viewcontroller . Example: https://github.com/nohuhu/react-statium-realworld-example-ap...
28.
by nohuhu 7y ago
Check out Statium: https://github.com/riptano/statium , and the RealWorld example that I threw together in a couple of evenings: https://github.com/nohuhu/react-statium-realworld-example-ap... . The
29.
by nohuhu 7y ago
(shameless plug!) ... or you can use something like Statium's ViewModel, which is basically a hierarchically linked, locally scoped state container component: https://github.com/riptano/statium RealWorld example:
30.
by nohuhu 7y ago
IMO this "Jira clone" is way beyond the middle ground, it's way too complex for that. Might be a lot closer to a product than you think. ;) For technology showcases the RealWorld example is pretty popular: https://

More ›