This happens when microsoft does not make phone os

The big internet players have nothing to gain and too much to lose by adopting Solid protocols, so it's safe to assume it's reliant on a killer app to be attractive to personal users. I hope it does well, though.

Web components, are very well suited to migrate legacy projects as they allow incremental migration of the UI. With React, this would be much harder to achieve

The last two fairly big commercial projects I worked on asked me to switch their existing code base to Web Components. So it's probably the latter.

Just getting started, if you ask me. I’m starting a project with them as we speak

if this protocol anonymizes the user to the entity accessing the data, that would be something... otherwise, there is still only "trust" that big corps won't store your data anyway, and sell/use it exactly like they do now. i don't get how accessing this protocol changes any of that.

Before watching this video I was thinking about how, in my spare time projects, I like to go down one level of abstraction from how things are normally done. And that I've got this fairly simplistic chunk of JavaScript on the front page of my blog... so, yeah, I'm most certainly going to give "naked" web-components without Vue or React a try.

I have seen React apps, and it is pushing towards frontend Monolithic with confused client and server side rendring. Web components provide huge power, speed, and open architecture, which makes it a future candidate of Micro frontend.

Can we use functions rather than classes for creating custom elements? I'm not a huge fan of classes.

Another issue I have with this is that, if I own and have access to my own purchasing history for example, what's stopping me from adding "fraudulent purchases" but will be accepted by the pod given that I know how to modify the data that lives on my pod? That's just one example, I can potentially tamper and introduce any information in my pod.

Old-fashioned web apps very naturally use CDNs to serve all their static content, especially if they have a world-wide audience. They are also often paid-for per-use, and they also often use cloud databases, sometimes even directly from the browser. I don't understand how pushing all of this back to server-side is supposed to make anything better. Browsers today are very well standardized and are very capable -- even across cellphones -- so why not take advantage of their CPU and memory? Why push this back to the server again, like they did pre-1990's? Maybe I am missing some key piece of information. Please, anyone, tell me what I am misunderstanding. I may sound argumentative, but I want to be corrected.

Whenever I hear that web components are lacking or pointless if there are frameworks like React, it blows my mind. Web development isn't limitied to throwing all kinds of heavy libraries on your own platform: We're building content that can be used as ads or included as regular imteractive content anywhere on any website, so we're limited in which and how many ressources we can use. Because web component are native and don't require a backend or a heavy library or compiled JS, they're often the best solution to include our pieces without causing any conflicts on a website (we might not even know on which websites our service will be used).

I just started learning JavaScript on the first of September of this year, so take my opinion with a grain of salt, if you will. I think the best way to teach JavaScript is through functional programming. There are literally no courses that teach JavaScript like that, so I must be wrong.

How can a steaming pile of web garbage pretending to be actual software, be a threat to actual software. It’s like asking is a five year old’a finger painting a threat to a Picasso? It’s not even close.

I've been making PWA's since before that phrase was coined. Reaching a massive audience is often not the goal of most people. Most of the time the goal is offering some bespoke functionality to a targeted set of people often as a complimentary app versus the 'next big thing'. This audience is vast.

once i tried astro i was hooked! its really a better approach for multi page sites than having an SPA imo

I never heard from your company but I have a charge for $145.00 from my bank account. I would like my money back. I am a 67 year old woman and I am not interested in your products

Thanks for making this video 3.0

great content!

There is no way to prevent multi billion dollar tech companies from copying and using your data. Does this use blockchain? If so, that is the end of anyone's privacy on the web - everything is tracked and put on a ledger. Let's watch out for a "new web" to have absolute surveillance of the world. Of course, it wouldn't be advertised that way, it would be sold as "you control your own data".

The only way the browsing experience on iOS can improve is if Apple allows third-party rendering engines such as Blink or Gecko. This would allow Google and others to give iOS users a richer browsing experience. After all, Blink is just plain better than Webkit. Everyone knows that.

Very clear explaination and clear separation of API's that web components based on. Although I have already written some web components, I had not thought before that these are different APIs. In this respect, it is a very valuable video for me, thank you.

Great stuff - love your style - thanks and subscribed!

Where is the supporting facts that says nobody uses functional programming? Click bait?

They don't have to use safari and you can warn your users about using chrome instead.

thank you very much

For anyone confused by the first example, createVerificationMessage is supposed to take the output of checkAge, not checkAge itself

Apple are bastards, period. They've deliberately made PWAs slow, clunky and harder to use than necessary. They work seamlessly on a piece of shit <$200 android phone, there is no excuse. Can't wait til Apple have their Nokia moment!

Nice video. Learned lots of new things. Thank you.

Awesome video, thanks

Is learning Flutter dead end, or it will it be worth it in the future for android/ios development ?

I can save some websites to my iPhone and it work just like the app, so more websites need to make their apps have this functionality.

Terrific, clear explanation of the key benefits of Astro. I wonder if there are any concrete functional use cases for using Astro vs SvelteKit, as they seem quite similar (SvelteKit cannot claim to ship 0kb js!), or perhaps it's just wonderful to have choices! Thanks for making these vids

❤ Super easy explanation ! Regards from 🇮🇳

Never heard is pronounced "caysh" in 20 years - but really nice video, thanks.

Thanks a lot

sorry but this is total garbage. every "known" js framework nowadays offers ssr (prerendered or cached) with rehydration. a bit sad that you present astro here as the "ultimate solution", whereas this technique or lazy loading is nothing new.

Great overview.

Nice one Anthony. Btw, do you have Iles (vue-based static site generator supporting partial hydration) in your list? Would love to hear from you on it! Cheers!

Can you make a video how to use functional programming in the DOM?

+1 like

This is one of the best introductions to tailwind that i have seen so far! Thank you

The greater than function is hard to read. One, I'd use better variable names, and 2, I'd mitigate the use of arrow functions here. All of that makes this really hard to understand what is happening.

astro is just shitty svelte kit at this point

Good video, the only remark is that js is prototype oriented, not Object. OOP operators in it are just syntactic sugar

Interesting. Thanks for reminding me about these. For my current app I need all the performance bonuses I can get, so the gains there would be the main draw card. My other considerations would be a solid UI library, a thriving community, and some sort of store (like vuex).

This gets an award of the dumbest idea of 2022.

Is this English? What language is this?

🤔👂🏿

Telling you what I think in the comments: Good content, boring delivery