Content pfp
Content
@
0 reply
0 recast
0 reaction

Deployer pfp
Deployer
@deployer
Why are you using next.js ?
11 replies
1 recast
21 reactions

​woj pfp
​woj
@woj.eth
super easy to deploy every library supports it well funded team that continues developing it
2 replies
0 recast
7 reactions

Deployer pfp
Deployer
@deployer
Any notable pain points? My biggest concern is the vercel lock in.
4 replies
0 recast
2 reactions

​woj pfp
​woj
@woj.eth
yeah vercel lock in is real, if you need to handle a lot of traffic for pennies it may not be the best choice ive heard about self hosted options but never played with any
0 reply
0 recast
2 reactions

  pfp
@undefined
one issue i ran into today the framework is quite opinionated & does too much work for you, which can be a double edged sword https://github.com/vercel/next.js/issues/22319
0 reply
0 recast
2 reactions

zoo pfp
zoo
@zoo
im using next on cloudflare pages and its pretty easy peasy
0 reply
0 recast
2 reactions

Andrei O. pfp
Andrei O.
@andrei0x309
There are a few pain points like: 1 Doesn't have a SPA only mode 2 Vercel lock-in 3 Pretty heavy in terms of dev resources 4 Not the most performant stack out there Probably for more users benefits are more important: 1 Huge community 2 Probably most jobs because of React 3 Relatively simple to use 5 Great if you're a React lover ( this can be a drawback too if you hate React) 6 Huge amount of libraries and UI components out there 7 Good support for running code on the server 8 Can be used as a full stack tech 9 Can share logic with Expo if you're in the RN camp 10 Comes with a bundler that has almost no need to be configured 11 Pretty mature and well funded
0 reply
0 recast
2 reactions