Видео

What makes Theo overlook AdonisJS? Is it the allure of Vercel’s sponsorship? or the convenience of the built-in S3 integration that scares him? 🤔

I like the idea behind Elixir/Phoenix, but the language is not widely adopted. In my previous startup incubator, it's now forbidden, only Python and TS are allowed (to maintain consistency).

Thanks for your wisdom

Love it, thank you for sharing!

AFTER: You're absolutely right about the attitude - that is what makes or breaks this whole thing, and everything gets derived from that.

BEFORE: 10x developers are overhyped, but there competency is a spectrum. A person is good at some things, and really bad at others. For example I'm decent at figuring out what stakeholders want, and then couple together libraries and tools to build the features and functions to suit their needs. But ask me to do some low-level graphics programming and I'll just go and cry in the corner instead.

Awesome. Exactly right. Logical architecture first

Great content Daniel. Visually very clear. Null vs nil...null like seaGULL, nil like blackPILL...

Thanks, keep up with the elixir content, the internet is already full of js content, its hard to find some good content like yours!

My opinion on this and what i'v been looking lately is more coding content, because the syntax is unfamiliar so we need to adapt our way of thinking to solve problems. Advent of Code is a nice one, but we need more side projects coding to show how to solve problems in a elixir way.

estou estudando ruby on rails e é delicinha

skill issue

One important feature you left out that I found interesting is the Inertia.js package. It allows you to bind your view pages with your backend without using rest api or graphql. I believe this eliminates the need for cache handling and pending states.

Great video!@

I actually understand this now! Nice video! Really enjoying the elixir content.

Whats crazy about this video is that at any point you tried to read the docs...

Thanks for all your elixir videos. The problem with Elixir/ Phoenis is that if you want to learn it, you almost immediately have to pay for courses, because there is far too little available for free on RUclips. Especially when you look for free Phoenix tutorials, you will see far too few. I would like to learn elixir/phoenix and live view, but I don't feel like throwing 100 euros or so on it right away. Don't get me wrong, I think you should pay for quality, but there should be a free step where you learn enough to start your own app from coding to installing it on a VPS. Unfortunately I don't see it and that's why I'm busy learning Rails because there is plenty out there about it. Rails has a complete framework including installation on a VPS. I think that's the path elixir needs to take as well if you want to get new "lonely" coders. I just think it's a shame that you don't have any content on Rails, because something about you makes you a great instructor

As the years go by, I increasingly believe that the web is heading in the wrong direction, trying to solve problems that have already been solved, creating new problems to justify this! Of course, there are scenarios where tools like Next.js are a possible solution. However, I believe that it does not exceed 10% of the market! The rest is the same as microservices: it became the standard because they thought it would be better.

To be honest Nuxt 3 js isn't any better. it also has it's bugs.

So good content! I'm happy to have discovered it today:)

I am really struggling with understanding the use case for next.js and I run next.js in production with paying users.

Just move to Vue/Nuxt. There are many jobs, at least in the north east of the US, and all of this crap doesn't happen much at all.

The fix is in the docs, you can find it in route segment config, it states: The values of the config options currently need be statically analyzable. For example revalidate = 600 is valid, but revalidate = 60 * 10 is not.

JS ==Just ShootMe

What are the theme and font that you use on vscode?

ive had similar problem i didnt find a way to make page static with timer on revalidate only way i find to update the data was making page dynamic that wasnt what i wanted but didnt find other solution that worked. Tell me if you find out!

Have you tried sveltelive and Phoenix?

I cannot express in words the amount of frustration i've had when creating a personal project to learn Next, I had so much problems with cache in dev server that I didn't even want to see how it would work in production, just this experience alone was enough for me to quit on next/react ecossystem

you can try using the revalidatepath which i think should invlidate the cache and fetch the new data

Put nextjs in trash and use Astrojs

While watching, I wanted to say if it does not work then you should apply for a new job as a Senior NextJS Ambassador / DevRel person. 😁 So that's my take at this point. 😁

Does using Tanstack Query or Redux solve this? I'm new to Next.js and finding that anything specialised by Next.js is better handled by Tanstack or Redux, such as validation and caching.

Try to use the next 14 with the pages router. It doesn't try to look like a frontend and backend framework; it's just a frontend framework with a small BFF layer, and that works just fine.

Next JS 15 will solve all your problem, because now the default of all Next JS caching is "no-store"

I come from a Ruby on Rails background, which has received a lot of criticism over the years for being opinionated. Sure, Rails has many complex default behaviors, but you can easily override or skip them, and in over 10 years of running production applications, this has never been an issue. Next.js, on the other hand, takes being opinionated to another level. There are many things you have to do exactly the way Vercel devs intended, or you won’t be able to do them at all.

I'm feeling the same. But I'm feeling super homeless in the JavaScript ecosystem. I'm thinking of saying fuck it and going to Laravel/Django and doing it the old-fashioned way.

Theo the terrible

What is driving me crazy is that you didn't just do a git revert when changing back the code 😂

E o inglês tá o fino do fino

Another reason I use Angular, its so under rated now, definitely recommend you try it :)

have you thought about using remix

I noticed you are using next.js 14.x.x, they recently made version 15 stable and think they fixed many of these cache issue

Going through the same thing at work with NextJS. It never acts the way you expect it to. It's always different.

Heres what i thought was going on, export const revalidate is just a "syntactic sugar" for cdn caching using the s-maxage, but then you changed to ssr for courses route and it worked. Wait what ??? 😭. It shoudnt have worked and now i am even more confused. Specially now there is a fking "use cache" thing thats a one for all thing, thats more confusing to me as i know there cant be a one for all thing, because there are multiple types of caching, from server caching on redis(or any other external source like KV), then there is http caching, cdn caching, route cache. I think it was better earlier everyone started to understand it but now i am fu*ked 😡

I moved from next to tanstack start and never looked back. It's been amazing. Highly recommend it!

"Cached data is persisted across deployments, unless invalidated through revalidate or programmatically calling revalidateTag or revalidatePath. It is not updated at build time. When invalidated, it will be updated at run time with the next new request to the path that was invalidated." The data cache is working as intended. Just because you added a revalidate on that fetch call doesn't mean the request changed... the vercel data cache layer still recognized the fetch (likely just by the url path as the cache key) and served up the cached data. It's the framework's job to bust the cache and tell vercel's data cache to serve updated data. After you built again with the revalidate added in and then when you visited to live page the Next.js server started its timer to revalidate the data cache in ONE DAY from then. Which means the next request to hit that page will cause the next.js server to re-render that "static" route and serve it up from the cache until the next revalidate call.

Well, in development we have to delete the .next folder in case this caching bug happens, idk how to do this i production in vercel.

I think the problem is that you're not using nvim. Thank me later

Boa pronúncia do inglês e bom video, topp