Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Just had a blast testing out Jev this weekend and here's my thoughts on how useful it actually is.... I tested browser use and data analysis with real requests for Vibecode Here's what worked and how you should think about building with it

19,164 görüntüleme • 16 gün önce •via X (Twitter)

7 Yorum

Vishal Dubey profil fotoğrafı
Vishal Dubey16 gün önce

Check out the full video here

Ansh Nanda profil fotoğrafı
Ansh Nanda16 gün önce

@vibecodeapp Finally a real use case for Jev

Jatin Garg profil fotoğrafı
Jatin Garg16 gün önce

@vibecodeapp Which parts held up beyond the demo? The latency overhead is the make-or-break for anything that loops.

AGTP profil fotoğrafı
AGTP16 gün önce

@vibecodeapp We actually went deeper on how Jev handles these types of logic tasks here:

Am.E profil fotoğrafı
Am.E16 gün önce

@vibecodeapp

khonsu profil fotoğrafı
khonsu16 gün önce

@vibecodeapp The browser-use/data-analysis split is helpful. Which failure did you have to redesign around first: tool state, verification, or context drift?

Jason · ChatterBeam profil fotoğrafı
Jason · ChatterBeam16 gün önce

@vibecodeapp The useful distinction seems to be browser control vs. reliable decision loops: once requests are real, retries, auth boundaries, and structured outputs matter more than the demo. Did Jev handle failure recovery cleanly, or was that still the brittle part?

Benzer Videolar