JS 생태계는 선택지가 너무 많아 개인 개발자가 제품 대신 발판 조립에 많은 시간을 씁니다.
제품 방향
무엇을 만들 수 있나
An opinionated full-stack template with hosting: auth, payments, email, admin included.
검증 방법
원글의 댓글을 끝까지 읽고 반복되는 구체적 상황을 적어 두세요. 반복이 곧 수요의 밀도입니다.
"full-stack / DX" 관련 기존 도구를 검색해 어느 한 단계만 커버하는지 확인합니다.
한 줄 랜딩 페이지를 만들어 Hacker News에 공유하고 가격을 묻는 사람이 나타나는지 봅니다.
기존 대안
RedwoodJS, Blitz, Next.js + Prisma 模板
스레드의 목소리 · 인기 댓글
인기 댓글은 기계 번역입니다. 원문은 원본 스레드에서 확인할 수 있습니다.
My experience having written all of the above is that JS is significantly more fragmented, and also has to deal with a frontend-backend severed line. Rails, Flask, Django (and PHP, purely server side JS that generate HTML with templates like express) are basically all "backend serving frontend and templating". Front end JS is more of a "frontend + backend with frontend serving backend" in the form of server side rendering being more akin to running a browser, loading the frontend, and then serialising that to a page. This is the complete opposite of the above. It's kind of a different mindset,
I think it's simply that (and this is from my memory only): Node.js was THE first back-end JS thing, and its "micro" philosophy kind of set the precedent for everything else that follow in that space. It was the time when people started to feel Django/Rails are cumbersome for some of their needs, too, so the MVC approach never caught on for JS devs. So I think it's just popularity. Pick whatever tool you deem suitable!
At the start of node.js, I frequently saw full web applications written in it "traditionally", fetching data and writing it into pug/haml/jade/handlebars/whatever else templates (during the callback-pyramid-hell days). It was pretty much just another stack like a less opinionated django. People used express, returned HTML, etc. Then the SPA frameworks came into the fray, and I never really saw node.js being used server side like that much anymore.
스레드의 목소리 · 인기 댓글
인기 댓글은 기계 번역입니다. 원문은 원본 스레드에서 확인할 수 있습니다.
원글 열기