Component libraries are the major reason I’m still using React.
It would be so much nicer using something like Elixir LiveView for the kind of apps I’m developing. But having to implement so many basic components from scratch just doesn’t make sense.
I mean I can fully see the downsides of introducing big 3rd dependencies into a codebase but not using them would be (in my opinion) a huge waste of time.
Isn’t this a problem for other people (that aren’t using component libraries) as well?
How can anyone be productive with non React/Vue stacks for that reason?
I’d really wish there would be other solutions (web components) so I hadn’t rely on React.
Just keep in mind that after all the hard work you’ve done over the years, having good reviews etc. if Upwork (or whatever else platform you’re on) terminates your account—and you have no other income/client acquisition stream—you‘re screwed.
Happened to me years ago. After struggling to get clients on Upwork I finally got gigs and good reviews. Put in a lot of hard work and earned some sort of „trusted freelancer“ badge (don’t know what it was called) that helped me to promote my profile.
I was very happy… only to find out a few days later that Upwork suddenly terminated my account for a (supposed) breach of their rules. They didn’t want to tell me the actual reason but said that I have mentioned „PayPal“ in a message to my clients (and accusing me of wanting to move my clients away from Upwork).
Never did I wanted to do that. I don’t know if I ever mentioned PayPal—and if so then only to talk about payment processor integrations on clients websites.
I messaged back and forth for days with them. In the end it wasn’t worth my energy.
Just be careful and get control of your income streams and diversify as much as possible.
Are other languages/runtimes also that risky as Node with npm?
npm packages seem like a cardhouse.
I know that the node_modules folder is often times criticized for its sheer amount of 3rd party libraries. Is it because of JavaScripts "missing" standard library?
Well it occurred to me after reading this thread that I could edit my Obsidian vault via vim. Of course, that's only for basic text editing capabilities everything else has to happen inside Obsidian.
I don't get it. It's still not possible to use next/image (without some fancy loader or 3rd party service) when exporting a SSG build.
Are people really not using responsive images when exporting a static site? Seems quite ridiculous to rely on some 3rd party service for image optimization when the images could be generated locally when exporting the site...
This sounds like the „textbook definition“ of social anxiety which is understandable growing up lonely—and not learning social skills which many people take for granted later in life.
Maybe you want to take a look at improving this aspect of your life so everyday tasks like calling a stranger etc. doesn’t cost you that much energy.
For me classic exposure therapy helped in that regard and reflecting on the specific situations that I was thrown into afterwards (calling someone, asking for something in the store etc.)
Still no option to export a static site when using next/image without relying on 3rd party services, right?
The only option that comes to my mind is using Vercel to host the site but then every image is transformed on demand which results in horrendous loading times.
Is this really how „everyone“ uses Next when exporting static sites?
At the moment I'm using Gatsby but the client side js bundle turns me off. However, one thing I really like about Gatsby is the dynamic image component.
Is there any way (or are there any plans) for generating responsive images when using Astro? As Astro is framework agnostic, I don't think so, right?