Content
@
0 reply
0 recast
2 reactions
Mats
@mats
If I built dune.com from scratch again I would do it in Ruby on Rails and not NextJS Shoot me.
5 replies
0 recast
15 reactions
atlasmoth
@osuji.eth
Why tho? I get why Next sucks balls, but what's so great about Ruby?
2 replies
0 recast
1 reaction
xh3b4sd ↑
@xh3b4sd.eth
Proof that you need neither taste nor soul to make money.
0 reply
0 recast
1 reaction
Haardik
@haardikkk
Elixir
1 reply
0 recast
1 reaction
redbeard
@hbrbssa.eth
i feel very similarly with python, however my concerns: 1. perf, ik it doesn’t matter usually. But sometimes getting single digit response matters and is hard. 2. lack of web3 lib support. default lib support for crypto stuff is ts and the pythonic implementation lags behind. 3. concurrency.lack of concurrency primitives is severely frustrating. but ya the ecosystem is insane for rails and others, wanna replace db, active records got your back. queues, whats that? sidekiq to the rescue. server components? hotwiring all the way. have found writing express/next js route very painful/repetitive. it almost feels like loosing a magical wand.
0 reply
0 recast
0 reaction
ܙܟܪܝܐ’s🧠
@zef
The sanest take. The only reason NextJS will likely dominate this cycle is the sheer amount of (crappy NextJS codebase) data baked into LLMs… until devx-specific implementations arrive. Or maybe it’s already too late. There’s also the economic entanglement i highlighted here https://x.com/zakelfassi/status/1878497612011327974?s=46
0 reply
0 recast
1 reaction
