Видео

Thaaaat's why I couldn't simply add a line of db write to accessLog without await, just before returning the response in Vercel..

for js deno deploy is strictly superior for such characteristics

Fortunately I've never used a UUID as a database table primary key. I use them for other things but only V4. I didn't know there were so many convoluted versions.

The video is not sponsored by vercel BTW

hash in css filaname is a no-no in my book, it is a nice way to pollute the browser cache. if you have a CSS file of 500K and deploy it 10 times without changing the css, only some text in app.. voila 5MB in disk usage for next month or how long browser keeps the cache.

Not every use of the word "version" means "incremental improvement over the previous version". In this case it's more like "variant number", so you have different variations for different purposes, identified with a number. MD5 was shown to be too limited in certain cases, and have a too-high possibility of collisions for certain uses. So I'm guessing that's when a new version was added to allow for SHA1 hashing. If that happened after v4 was already out, well yeah, now it's going to be numbered v5.

turning a 5min spot talk to a 30min it's a talent by itself

WebAssembly ultimately struggled to gain widespread adoption due to its lack of direct access to the Document Object Model (DOM). This limitation made WebAssembly cumbersome to use, as developers had to rely on JavaScript proxy functions to interact with the DOM, introducing an additional layer of complexity that hindered its adoption.

The whatever service you are wondering about is most likely Cloudlfare.

I seriously thought his little talk was merely a satire.

Here we have a bunch of people acting like they know what software development is, without actually knowing at all.

You talked React Server components as a new thing just to realise .Net had them 10 years ago. :D

What can you really expect from a JavaScript developer anyway?

Why not just use a $500,000 VPS?

I always wanted something like this, but I didn't even think about making my own architecture on top of lambda, I'm a noob. It just makes sense to do what you need to do, send response, and then finish any extra stuff like updating cache, logs etc. Not to mention streaming.

Classic example of first creating the problem and then "fixing" it. 😂

Solving a pain point that doesn't really exist. Coolify + VPS = Freedom. Screw this VC funded companies

logging, sending emails, writing stuff in db the user don't need, There are so many times I wanted to have those and it frustrated me because "it worked on local dev though"

This is absolutely the most stupid talk masquerading as "intelligent" that I've ever heard. Absolute dogshit.

For confused non-js devs like me, I understod it like this: const is like final, const = Object.freeze is the closest to real const and let is a normal variable. Or in rust terms rust const doesnt exist const = Object.freeze -> static const -> let let -> let mut

Jack Harrington made also a video about this, where he nicely lists the arguments of the talk, which makes it a bit briefer than watching the whole talk.

The installer is bullshit. It is a 30+ GB zip file that you have to decompress before running the installer. Then you run the installer and it downloads EVEN MORE HUGE FILES.

So like Cloudflare Workers?

`.repeat(1024)`, to fudge gzip, was header -> 'accept-encoding: identity' not an option?

Sounds like you should just use a server

it's crazy seeing this video because I just spent my entire weekend figuring this out. - Vercel should keep this same behaviour in dev (drove me crazy) - Also having issues with adding this to multiple requests

I didn't realise SO was bleeding users. it's still my goto for any programming questions. thing is, I barely ever have to actually create questions since so, so many have already been answered

I believe that Lambda function doesn't die after it serves sync invocation request. It is kept around for ~15mins to potentially serve more requests.

woah this is very nice

I currently have a project that could use this. I'm holding back the client response artificially to wait for something it shouldn't need to wait for. Cool.

Lambda isn't that much different from CGI of old, right?

Dreambirb is an amazing meme Lang

Dax is anti vercel because he suggest there's already an alternative in place? oof

Lambda ( response ) -> SQS -> Lambda ( wait until task ) = 🎉🎉

This whole const vs let is such an L take no matter how you look at it. In practice , you should use const to signify errors in your IDE if you try to overwrite it where it's not intended. In theory, proper utilization should make computation faster because, as an immutable, the CPU is free to lookahead whenever it encounters it because it knows that the declaration should never change. People arguing about its proper use in workflows just don't understand the CS fundamentals as to why these declarations exist in the first place.

ruclips.net/video/UiUPb-SYDxM/видео.htmlsi=5wtXrGfsJq32wK8F

Random ids also have the disadvantage that for a large table, if you need to access 1000 rows, they'll be stored in 1000 different pages, even if the rows are conceptually consecutive. Non random ids instead create hotspots during inserts. So a semi-random index would tick both boxes, but every use case is different.

Moar AI content plz

It's essentially a debate between: 1. Use `const` for what it does. It prevents variable re-assignment. 2. Save the `const` keyword for actual constants. I don't think either way is completely awful. But if using "2.", it must be in the style guide your team is using. This is one area that I really like about rust. "let" variables are immutable at EVERY depth in the structure and cannot be re-assigned. "let mut" variables are completely mutable, and can be re-assigned. Your struct definitions don't contain any "readonly" annotations. Mutability is decided when you declare variables.

why don't you just use a 5 dollar vps

Couldn't you already do this in edge runtime with context.waitUntil? I'm pretty sure I've done this on a project

waitUntil(...) -> but don't wait too long. Go and ask her out.

"LSD has wrecked many lives" (X) Doubt

Why this even exists? If no value change - const. Value mutates in code - let. Simple as that.

28:00 I think a lot of back-end devs start to realize that MVC doesn't work and the Component are the correct way to abstract, I think Django have them and Laravel also

Whenever I see a video on this channel I usually expect the information to be bad or pointless. Glad to see it still doesn't disappoint.

Yes, immutability would be nice. But if no reassignment is all I get, then I will take it. And I generally don't append to arrays or objects....

2024 and people still arguing about variable assignnments 😂

Never used const in my live. The day i learnt about it, i thought, god that is fucking stupid.