101–110 of 148 posts
This is super cool. If I worked in React I would love the ability to build most of an MVC through a GUI like this and avoid the waste of time. I really hate React, though. Throwing logic into HTML and JSX... just feels so hackish. Like, if I want to alter states on a thing in the DOM, I want all that logic in the JS in one neat class, not mixed with control flow in a template somewhere else. /rant Still, I think a fr…
Sorry, I could not go farther in the video after watching the narrator trying to accurately click on all those inputs, dropdowns etc. simultaneously saying "writing this in code would be annoying". In my opinion using mouse pointer to click things on screen is annoying when it comes to programming.
I don't believe we need an IDE for React, it will end up dead like Dreamweaver or FrontPage. BUT, a Vscode plugin that visualizes self-contained components with all its styles intact would be nice: like I open MyComponent.tsx and in the right pane I see it visually, without running the actual webpage or server.
I'm a bit fed up with those "IDE" for web attempts. Every 9 Month or so , we get a new attempt at fixing Web Dev lack of Visual Feedback and productivity issues. The typical coder behind this type of project get "Mental Fatigue/ Coder Exhaust" after 6 Months as they generally ignore the complexity behind building such product and end up abandoning the project.... There is a google graveyard , but we should also build…
No design principle, no explicit constraints on code base, no explicit supported scope. Surely there is some kind of React component that won't work well with this, the unsuspecting will discover this too late.
That is extremely impressive.
Earlier quoted context omitted.
> I strongly dislike Tailwind and similar tools because they prevent this kind of coding/debugging No they don't? I use the inspector all the time to figure out what values to set. Granted, I then translate those to Tailwind in my head, so there is an extra step compared to directly copying the style but that's a very small price to pay for all the advantages that I get from Tailwind.
What are the advantages, really? I used to use tailwind for my site, but then I realized I was essentially writing plain CSS in some DSL. Writing the plain CSS directly and using a few CSS variables for things like color and spacing simplified the whole thing greatly.
Earlier quoted context omitted.
I even have the browser and code on the monitor at the same time. And with pretty much all modern web frameworks you have a dev server that automatically does hot module replacement, so you instantly see your changes without reloading anything yourself.
I've never seen a hot reload that worked fast enough to not be annoying. React does it all quickly when all it's re processing is css but anything js related and it seems not to be able to treeshake down to bare minimum updates. We're talking 750ms to 1.5s, and I admit it's still a marvel compared to things I used to have to deal with, but it's still enough to feel cludgy. Flutter is another example of this. It's not…
Then you, my friend, have never used Vite.
Earlier quoted context omitted.
I even have the browser and code on the monitor at the same time. And with pretty much all modern web frameworks you have a dev server that automatically does hot module replacement, so you instantly see your changes without reloading anything yourself.
I've never seen a hot reload that worked fast enough to not be annoying. React does it all quickly when all it's re processing is css but anything js related and it seems not to be able to treeshake down to bare minimum updates. We're talking 750ms to 1.5s, and I admit it's still a marvel compared to things I used to have to deal with, but it's still enough to feel cludgy. Flutter is another example of this. It's not…
These projects only recompile the code that changes, then via chunking the browser only reloads a tiny specific .js file that contained that one component matching the vue-route, so usually 10-30kb refresh (and it loads about ~10x small .js files per page), which happens before I can tab back or notice when widescreened.
Previously when I used the slower Webpack without chunking it started to take time when the project grew large. But that was long ago (3 years ago?).