AWS S3 Is Having Some Serious Issues...
10:48
The End Of StackOverflow
9:18
20 сағат бұрын
React's New Controversial Override
13:02
The Problem With UUIDs
25:53
Күн бұрын
React Removes `fetch`
19:20
Күн бұрын
AWS’s Future is…Q?
16:15
Күн бұрын
Was I Wrong About Rust?
37:31
Күн бұрын
This should have happened years ago...
22:33
React 19 Is FINALLY Here
39:09
14 күн бұрын
Vercel Gave Up On Edge
17:50
21 күн бұрын
Why WebAssembly Can't Win
19:38
21 күн бұрын
We need to talk about this benchmark
42:25
The Biggest Lie In HTML
23:56
21 күн бұрын
I Finally Understand Load Balancing
17:53
Пікірлер
@TheUnknownFactor
@TheUnknownFactor 13 сағат бұрын
I'll pass on having the server keep track of all of my client's opened/closed state for every dropdown on every page; and having every user without amazing internet wait 200ms every single time. There's a bunch of value in having a bunch of state on the server. There's also a bunch of value in still having some on the client.
@austincodes
@austincodes 13 сағат бұрын
Those saying that PHP already did this don't get it...
@silentdebugger
@silentdebugger 13 сағат бұрын
19:27 I always love hearing someone argue "We don't need to care about optimizing code anymore because computers are so much more powerful these days!"
@elenamikhaylova5086
@elenamikhaylova5086 13 сағат бұрын
great explanation, i feel like i just leveled up as a UI dev
@mrleblanc
@mrleblanc 13 сағат бұрын
Can we use this with a templating language that is not horrible ?
@pencilcheck
@pencilcheck 13 сағат бұрын
aha, ruby moneky patching in real time for server frontend application lol sounds really cool though
@NaranuCS
@NaranuCS 13 сағат бұрын
Great tutorial btw, I'm starting to branch out towards next.js and react coming from Java and PHP (not together but from my last two jobs) so is extremely exciting to see how powerful all these tools are!
@amirhosseinahmadi3706
@amirhosseinahmadi3706 13 сағат бұрын
This is all fun and games until every UI interaction takes 2 seconds to react because the server is overloaded.
@awksedgreep
@awksedgreep 13 сағат бұрын
Good luck overloading beam to an unresponsive state.
@awksedgreep
@awksedgreep 13 сағат бұрын
Google 1m websockets elixir chat. Still <2 seconds with 1m people in chat
@amirhosseinahmadi3706
@amirhosseinahmadi3706 13 сағат бұрын
This is all fun and games until everything UI interaction takes 2 seconds to react.
@user-lc3un9jw8t
@user-lc3un9jw8t 13 сағат бұрын
I appreciate your content Theo, but could you please leave religious cuss words out of them.
@eu_maxinne
@eu_maxinne 13 сағат бұрын
Hey look, they just invented JSF again! What a time to be alive folks, 😂😅
@fronix5060
@fronix5060 13 сағат бұрын
Anyday now we will get something done after rewriting all our codebases
@sayemprodhanananta144
@sayemprodhanananta144 13 сағат бұрын
feels a lot like livewire in laravel
@mitchrivet
@mitchrivet 13 сағат бұрын
absolutely loving elixir and phoenix- feeling much more productive than nextjs
@hopecomingsoon
@hopecomingsoon 13 сағат бұрын
not my thing. separation of concerns bro
@Aleksander-Prokopowicz
@Aleksander-Prokopowicz 13 сағат бұрын
Hmmm... JSON BAD??? So why We don't have DCSS (Dynamic Cascading Style Sheets) yet? Why such fundamental thing like element styling have to be updated using JavaScript or other scripting language? Just make a protocol that allows a stream of CSS commands to update the page on the fly! Hey there can by 2 different streams. One that replaces inline style attribute and second one that replaces content of style tag.
@peterjansen4826
@peterjansen4826 13 сағат бұрын
I use UUID to mount partitions on my Linux-system. Frankly, I have no idea how those keys are generated, I just know that the same partition will always get the same UUID-key, no matter what I do.
@roei7111999
@roei7111999 13 сағат бұрын
2:26 External CSS = Fetching CSS from another file Internal CSS = Using the style tag Inline CSS = Using the attribute (<div style="color: blue"></div>) Although inline CSS is naturally faster to load, it's impractical to build a website like this. You can use some magical JS compiler that will add the inline CSS to every element, but then the argument will be that the library takes time to compile... It all comes down to "Is it easy enough to maintain while keeping the outcome fast"
@cold_ultra
@cold_ultra 14 сағат бұрын
Ok, NextJS feels like stone tools now. Im just not a fan of string literals for html and I suspect integrations with existing clientside libraries will be a bit iffy But im willing to ignore all of that if that realtime deployment stuff really works that well.
@wusswuzz5818
@wusswuzz5818 14 сағат бұрын
1. pnpm run db:studio 2. information: Drizzle Studio requires a new version of Drizzle Kit Please install the latest version and try again 3. Installed latest version (pnpm add drizzle-kit@latest -D) 4. error: Invalid input Please specify 'dialect' param in config, either of 'pg', 'mysql' or 'sqlite' 5. tried to update drizzle.config.ts and it does not accept a dialect parameter.
@jenreiss3107
@jenreiss3107 14 сағат бұрын
just a note for the rust+wasm haters: Figma in the browser uses WASM :)
@Qrzychu92
@Qrzychu92 14 сағат бұрын
so the reason .NET is there, because we have the exact same thing as this LiveView - Blazor Server Side. It's basically Vue.js, but through WebSockets (backed by SignalR), but in C# with direct access to your DB, usually through THE BEST ORM on the market. It comes with its own set of issues, I bet the same apply with LiveView - if the connection is spotty, or you just get straight up disconnected, you get a banner saying your website is not available, please try again. Since LiveView claims to free all resources after a web socket disconnect, you also loose your state, at least the part not stored in the URL or local storage. Fun fact about Blazor, it started out as an experiment, because there was this guy who compiled the dotnet runtime (analog to the JVM) to WASM. So you can just take your standard C# program, and run in the browser, just like that. So, another mode for running Blazor is Client side, where everything runs on the client side, just like React or Vue, but you get to use C#. Last year, they made Blazor United, so you mix and match - you can define per-component whether it runs on the server with WebSockets, or on the client in WASM. You can even run in Auto mode, so that it's server side until the dotnet runtime gets downloaded (it's around 1MB, I know it's a lot, but it's a frikin fully functional runtime!), and then it switches to WASM. It's awesome. Sadly, not for public-facing sites, still too much too download or too big lag for those with weak connection. The same applies to LiveView, don't forget. But for you company dashboard? Some admin panel? Forms over data? It's so perfect. Probably LiveView is a better tech, but both are quite impressive
@delamberty
@delamberty 14 сағат бұрын
Also the Productivity level with Phoenix+Ash framework feels illegal.
@AlanPCS
@AlanPCS 14 сағат бұрын
What do you mean by “needing to auth 3 times”? We usually just use a JWT that is signed with a BE secret.
@upsxace
@upsxace 13 сағат бұрын
You have to decode the JWT and verify the signature every time genius. And that's if you're using JWT. There is other types of authentication, and tbh most services nowadays leave the auth part for an external service, so you will have to do 3 requests to those external services.
@aarholodian
@aarholodian 14 сағат бұрын
Impressive, very nice. Let's see Paul Allen's reinvention of PHP
@banikaritra5328
@banikaritra5328 14 сағат бұрын
Make and deploy a new web application using this. Please make a Tutorial.
@SM-ok3sz
@SM-ok3sz 14 сағат бұрын
It’s no wonder so many people burn out in this industry.
@peterkrau4486
@peterkrau4486 14 сағат бұрын
I dont agree with the premise to move rendering to the server. I like to keep concerns separated so that different teams can work on them. In addition i would not put all the load on the server nor would i want to restrict the user to what UI they use. I keep things seperate: API backend and letting the client render thr UI however it seems fitting for the user. This is also beneficial wrt to scaling and state handling. So tja, i know this is a hot take right now. convince me otherwise.
@osman3404
@osman3404 14 сағат бұрын
Keeping realtime web socket connection comes with lots of issues
@LeeK301
@LeeK301 14 сағат бұрын
Im probably misunderstanding so if someone can please clarify that would be great; if S3 bucket names have to be unique across all regions within a partition, how is it that this developer was able to create a bucket with the same name as another bucket already existing by the company that generates their backups?
@vikkinn
@vikkinn 14 сағат бұрын
I swear the JS community has amnesia. We're basically just back 15 years.
@user-co5bp8nq7e
@user-co5bp8nq7e 13 сағат бұрын
they have clip thinking like tik tok generation nowadays. young js devs are incapable of learn something well (understand deeply) cause their attention is constantly switching. no wonder i dont see 40+ frontend devs that much, because js experience becomes irrelevant very soon. too many paradigm shifts and insane amount of tooling switch, whith that npm small libs culture. it is horrible.
@whophd
@whophd 14 сағат бұрын
Freaking evil things. I never felt comfortable with the rise of Windows Registry in the 1990s. There's something supremely lazy and failing to benchtest - just an avoidance of manual design of relational databases, and the "boring" job of taxonomy. Yeah yeah scalable. But "without knowledge" is indicative of other issues. If you knew your space, you'd automatically be wanting to spew out naming suggestions.
@BorisBarroso
@BorisBarroso 14 сағат бұрын
Wow this is incredible I haven’t used phoenix in a long time and I want to go back to it🎉 Amazing
@MadsterV
@MadsterV 14 сағат бұрын
This looks terrible. These are solved problems, why are going back to old concepts that were proven to be problematic? - Hot reloading can run into state problems. Can the server really update the state meaningfully between changes? no. Just full reload, man! Design your systems to be more easily tested by not nesting too deeply or you can hardcode some state for the duration of development and take that scaffolding down once you're done. - server side rendering drove server costs up in the past. Cached client code is great, why are we rendering on server again? might as well go back to PHP, there's a lot already built back there. - "planet wide" and "all over the world" are meaningless. If your servers are spread among a few machines in your local network, your code is EXACTLY THE SAME. The heavy lifting is done by our dear Internet. If the point is scale, 10 servers is not very meaningful and location doesn't matter again, only count and speed, and what comes into play is architecture, not lines of code. I'd stay away from this.
@freedo201
@freedo201 14 сағат бұрын
Elixir and Phoenix LiveView are so great! I’ve been developing in Elixir for almost a decade now and seen how much the ecosystem and tooling has evolved. It’s truly unmatched what you can do with it and not just how fast it is to build stuff, but also how maintainable the end result is.
@johnodonoghue651
@johnodonoghue651 15 сағат бұрын
You think news sites are accurate? Interesting.
@Leonhart_93
@Leonhart_93 15 сағат бұрын
Except that sending rendered UIs to the client is almost always a larger payload that just some underlying JSON which sometimes can be very small. If one of your stated reasons was "bad internet connection", then all the more reason to keep the data transfer to a minimum.
@AllysonTS
@AllysonTS 15 сағат бұрын
@DanielBergholz está tendo um orgasmo vendo esse vídeo 😂😅
@tinymints3134
@tinymints3134 15 сағат бұрын
let's go trans hackers (I'm assuming your trans, sorry not sorry)
@winchesterdev
@winchesterdev 15 сағат бұрын
elixir mentioned
@LoneIgadzra
@LoneIgadzra 15 сағат бұрын
For me, where Phoenix really shines is in the real-time features. Streaming updates of things that other users are doing. This is not easy with Rails. *It's also completely unnecessary for lots of really good SAAS products. Request/response and separate pages is actually simple and intuitive for users too.* I think the email SAAS you keep dunking on has quite good UX (note that they ship a web and two mobile apps with a very small team), and for most folks reading this comment is not going to be slow. Plain old web pages pages and request/response are severely underrated.
@jrdn5206
@jrdn5206 15 сағат бұрын
I listen to your videos with my 2 year old prior to switching to toddler music in the mornings….. it’s a matter of time before he starts saying f*ck
@0xedb
@0xedb 15 сағат бұрын
It's a No.
@shaggygoat
@shaggygoat 15 сағат бұрын
“1−e^(−ct)”, the value of the lerp parameter u = 0..1, describes the charging or discharging of a capacitor (through a resistor) to some new voltage where 1/c is the “time constant”, the number of time units that will pass before about 63% of the ever-slowing progress is made towards a new state. You sometimes see a time constant being the thing to set for smoothing function of a variable speed drive for controlling an electric motor.
@brokebull
@brokebull 15 сағат бұрын
Does he get paid to promote it?
@SamOween
@SamOween 13 сағат бұрын
No
@aghileslounis
@aghileslounis 15 сағат бұрын
It's so good! I'm so exciting. Thanks Theo, for covering this news! I can't wait for Elixir to become a fully typed language like TypeScript as fast as possible. I swear it will be one of the best language and tech to build APPLICATIONS in general. Web/Mobile/Embedded....... They have a remarkable "base" features no one truly has
@iopyrb
@iopyrb 15 сағат бұрын
just leave it bro
@HugoPineda83
@HugoPineda83 15 сағат бұрын
Svelte-Kit
@thekingdev4675
@thekingdev4675 15 сағат бұрын
I'm Brazilian, Elixir was developed by a Brazilian coincidence? I have been programming elixir for over years
@arthur-zhuk
@arthur-zhuk 15 сағат бұрын
Recently picked up Elixir after being in JS for a decade and have to say it feels revolutionary.