Folks who do #aspnetcore development with a #javascript frontend framework (#vuejs, #angular, #react), is your frontend code part of the #dotnet solution, or have you split the backend and frontend into separate isolated folders?
I have thoughts, but would love to hear what your thoughts are. Boosts are appreciated.
If there was an #HTML element that changes it's content when users interact with other elements on the page, what name would it have?
PLEASE NOTE: I am not suggesting that this element needs to exist; I am only asking what it would be called. I'm building a CustomElement, I just want it to have a name that makes sense.
Vote and suggest others in replies. Please boost for reach!
Am I ever... ever going to be able to fundamentally understand what I'm doing? In #React, or any "modern" framework-based #frontendDevelopment for that matter?
I feel like I'm swimming in a mass of imports, props and hooks and the ((mysterious) => ({ useOf({ so, many }); }, [brackets, braces]);
I know people say knowing the web fundamentals will serve me beyond the current transient trends, but there's such a lot of this particular trend to learn, and frankly, it's paying my bills.
The new #github based on #react is an abject failure to improve the user experience. On every count it is objectively worse than previous iterations.
Page load time is poor, interactivity is gated seemingly on very large JS loads. Initial page layout is broken on mobile and randomly resizes the width of the viewport after loading. The number of micro-annoyances seem to be adding up daily.
This is like an object lesson in what not to do to your successful webapp.
Are there any tools similar to #Redux in #React for #Python regarding database caching? I want to basically have a local copy of API results. If a result is not locally available, it is pulled from the API. If it is already locally available, it should return the local cache without calling the API again.
Frontend Devs, where are we currently standing in the debate React vs. Vue.js? Or is something entirely different already taking over (SolidJS, Ember.js, Svelte, ...)?
For years, it seemed like React was almost the only way to go. Now I feel like the winds are changing and other frameworks/libraries are gaining traction.
What do you all think?
Debating with myself whether <Flex> and <Stack> components are an antipattern... I keep finding spots in our app where we've ended up with like ten nested flexboxes where one or two would accomplish the exact same result.
Is this just a devs-not-knowing-CSS problem, or does the abstraction invite abuse?
My colleagues work with React. I do too. I've also been banging the #a11y drum since I got the job in November.
While they see it's important, I was talking (as most of us do, because it makes sense) at the HTML level, about testing with a screen reader, etc. Usual, good stuff - but hard to immediately implement.
Anuradha Kumari (@miracle_404 on twitter) stood up on front of them for 20 mins bashing out live React code examples and boom. They get it.
I currently do a number of local government projects. Unfortunately they use #react which I personally hate but OK, someone made that choice before I got my hands on the code.
But Vercel's effective takeover of that framework and their ownership of NextJS, coupled by their carelessness with customer data, should make anyone pause when using React in future projects.
Created 65 tickets to migrate from class components to functional , some are small and should be relatively easy others are 2000+ mono components that render whole pages. Legacy #React is such a trip (I’m sure I’m also responsible for similar code in a past life)