Hacker Newsnew | past | comments | ask | show | jobs | submit | thinkxl's commentslogin

If React implodes because of bad architectural decisions, Vite should fork it.

It's crazy that the best React DX is provided through Vue's community projects.


Why don’t we just switch over to Vue? If DX is such a driver for deciding to use a web framework, Vue kicks React’s ass, and that’s just objectively speaking.


I did switch over to Vue.

Well not technically switch, I never learned React properly because I didn't like it when it first came out and by the time I gave it a second look there were already a gazillion React devs so I just stuck with Vue.

Vue just seems much more intuitive and sane to me. Sane is relative for front end frameworks of course. Don't get me started on Angular I got PTSD and couldn't code for a couple of months from a large Angular project with an offshore team.

I do get the benefit of using these framework for teams, and they are nifty once you get what is happening, but I still scratch my head when I see all the steps and files to do simple things I used to bang out in a few dozen lines of jQuery.


One of the greatest things of the Vue community is that they are not dogmatic about a technology choice. They welcome everyone, and proof of that is that they are building tooling that benefit everyone not only their community. So, we can switch over to Vue whenever we want. I personally prefer React and I'm super grateful of Vite and their ecosystem.


I came to reply this. They have been building very cool CLI projects and those projects end up composing new bigger projects. This is their last one (That I know of) which use most of the other projects they created before.

They didn't do it flashy for this project specifically (like Claude Code, which I don't think is flashy at all) but every single one of their other projects are like this.


Well, the answers to your questions don't sell books, right?


Additionally, the explanation might work for the exec asking the question, but not for others.

I don't like that executives don't have to put in the effort to communicate their concerns and put pressure on the people who already have the pressure of researching, validating, and presenting the solution.

I'm probably going deeper than I should. Still, if the executive asking the question isn't technical, he could direct the question to the executive who's supposed to have a technical background that earned their position in the company. You know, people making decisions should have an understanding of what they are building/selling.


One common leadership trend is to give minimal feedback like “this is not cool” and rely on competent people directly under the executive to guess what that means.

Competent people can often lead themselves in the right direction, especially with the use of copious after-meetings in which everyone tries to interpret the executive’s feedback.

After all, the executives are busy and hard to get access to.


I agree. You describe how it happens; however, I still don't find a justification for these:

- rely on competent people directly under the executive to guess what that means

- after-meetings in which everyone tries to interpret the executive’s feedback

- the executives are busy and hard to get access to

Imagine having a riddle as feedback in which people from different backgrounds and cultures gather to decipher a meaningful direction.


I think using Aider[1] with Google's models is the closest.

It's my daily driver so far. I switch between the Claude and Gemini models depending on the type of work I'm doing. When I know exactly what I want, I use Claude. When I'm experimenting and discovering, I use Gemini.

[1]: https://aider.chat/docs/llms/gemini.html


Juan Olvera

Location: Houston, TX

Remote: Remote, Hybrid, On-site

Willing to relocate: Yes

Technologies: React, TypeScript, Next.js, Python, Node.js, Go, AWS, Linux, PostgreSQL, Kubernetes

Résumé/CV: https://github.com/j0lvera

Email: inbox [at] jolvera.com

I'm looking for a Go, Python, or React position. Most of my expertise is in leading front-end projects, specifically with React.

I've been involved in building teams and modernizing legacy platforms, and most of my work has been with SaaS enterprise applications.


You probably already know, but in case you don't, python has phidata[1]

[1]: https://docs.phidata.com/introduction


Juan Olvera

Location: Houston, TX

Remote: Remote, Hybrid, On-site

Willing to relocate: Yes

Technologies: React, TypeScript, Next.js, Python, Node.js, Go, AWS, Linux, PostgreSQL, Kubernetes

Résumé/CV: https://github.com/j0lvera

Email: inbox [at] jolvera.com

I'm looking for a Go (microservices), Python (data engineering), or React position. Most of my expertise is in leading front-end projects, specifically with React.

I've been involved in building teams and modernizing legacy platforms, and most of my work has been with SaaS enterprise applications.


i don't want to be the "get off my lawn" person or "old man yells at cloud," but i couldn't get to what the tool does because the landing page is so overwhelming with colors, the background, the borders, things moving around.

the CTA buttons across the site are inconsistent in shape, form, and color.

the text color in the footer has awful contrast, so it's hard to read.


Thanks for the feedback old man! I'm going to improve the aesthetic of the dark mode. You can try the light mode which should be easier to read right now.


>the text color in the footer has awful contrast, so it's hard to read.

Dark grey on white is awful contrast these days?


… I'm not them, but in dark mode, it's <50% grey on black, and for the headers, <32% grey on black. (#374151 on black, I think.)


Dark mode. There's your problem. The site has been up for a week and people are already complaining they haven't properly adjusted for dark mode users.

https://memelogy-images.s3.amazonaws.com/b004cc18-b980-4e4e-...


I do something very similar, I create a directory as YYYY-MM-DD-keyword, e.g., 2024-09-12-todo-app/ then inside create other two:

- assets/ where I drop all markdown documents, images, database dumps, or any file related to the project that shouldn't go into git.

- src/ it's a directory that contains repositories with source code.

edit: format


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: