I'm glad you started this with raw CSS, and how to use it in a real world scenario with lightning. Showing how CSS can be done without JS build systems or typescript
Nice overview! I think those three are probably the best options today. I'm still mostly using CSS modules as they solve most of the past headaches, but I'm also looking into Tailwind and StyleX. CSS modules solve the naming collision problem of plain CSS, and with colocation with the components, they make it easy to get rid of unused styles. Drawbacks: you still have to come up with names, and it you're building a shared ui library with it, you will always ship the CSS for all modules, even when consumers only use some. Tailwind makes it easy to get started quickly: By shipping a nice design token system, you are likely to get consistent styling without much effort. You also don't have to name classes. And with extreme colocating, it helps with code reviews. Drawbacks: convoluted JSX code, and getting overridable styles right (often needed for shared ui libraries) is not easy. Also, you lose access to a lot of CSS features, and you have to learn the system, but to use Tailwind effectively, you still need to know CSS to choose the best layout approaches. StyleX is more complex to begin with. But it really seems to be made with shared ui libraries in mind! In contrast to past solutions in its family, you get fine-grained control over how ui library consumers can override component styles, along with type safety. Drawbacks: I personally don't like writing CSS rules in JS objects, there's quite a bit of boilerplate code needed, and you still have to name things like with CSS modules. So, in conclusion, all three are great. CSS modules are great if you know CSS and want access to all its features without getting lost in naming conventions. Tailwind is great to get started quickly with standalone projects, and StyleX is awesome for use in different projects with a shared ui library.
I personally really like CSS Modules, but they aren't perfect. I've been using them for last couple of years, but recently switched to Tailwind and I think I'm not going back.
@@rand0mtv660after all this css and scss modules i tried tailwind and was amazed by it. 99% of the arguments people use against it they don’t really understand the right way to using it. If u use something like React its just perfect for now
Hey lee, preety cool stuff , i would love to have an indepth overview on Metadata api introduced with app router , specifically the og stuff and twitter images , best practices , ps: love this video , love you , thanks for amazing content
Love the vid, one thing I hate about stylex (besides the name), is that you have to use the spreads a lot, which, IMO, makes the code unpleasant to read. With tailwind people can always create variables that express the intent or wrap everything in a single class.
Styling engines built with a static / build time css-in-js architecture, like stylex or panda-css, is a generational leap ahead of tailwind. They provide the developer experience of css-in-js and remove the bundle cost and runtime in browser tradeoffs. UI libraries that build on top of these types of styling engines will be the new hotness in 1-2 years.
Great video. Only part I think was missing would be if you were to go beyond simple styles into design systems & style variants, as Tailwind does start to resemble StyleX when you want to have variants
Another great plugin I use is Tailwind Typography, I use it after tailwind resets all the css. it allows me to achieve consistent typography across the entire app and different browsers without additional setup on my end. And the cool thing is that I can opt in/out at anytime with the prose classname. I have it on by default and disable when I need to. The plugin was initially created for html that's coming from external sources but I find it really good in my mentioned use case as well.
StyleX and Astro seem similiar. One of the things I hated about pre-2010 web was inline styles, which I still dislike and Tailwind basicaly is that. Just instead of writing style="..." it is class/className="".
One issue I get with css modules (at least in react/next projects) is critical chain warning. Always huge when using modules for all pages and components
I want to ask for you advice 🙏 I am now at point that i can work very well with css and can say i understood mostly everything , but i have no idea of boostraps and that tailwind thing and the other things , i want your advice what should i do next ? (My ultimate goal is to make amazing websites that is responisive)
Learn css html and js then have the AI help you code extensive functions and the back end. You must know how to communicate with the AI in describing what you need. Without terms and some understanding of how things work you won’t be able to use AI to resolve. If you learn frameworks you will always be a T the mercy of those frameworks, there is a pro and con. Getting up to speed is very frustrating as breakage happens. I think AI is stunning frameworks, reason being is you can have AI create only the js needed, avoiding all the extra code that goes unused.
That's perfect, knowing CSS is always an advantage over knowing a framework. You can build everything you want with pure CSS and it has great features to make your websites responsive and you can easily debug it with dev tools in your browser. Frameworks come and go like trends come and go. Maybe in 3 or 5 years everyone says, "get rid of tailwind, it's the biggest crap we ever made 😂" ... and i'm pretty sure that day will come, like it came for other super trendy trends. CSS will still be there and it will have even more amazing features than it has now 😉
@@otto3225 this what i though too , right now i am taking lessons in boostrap , and i cant stand it specially that i can do everything it does with pure css , but now i need to remmber the names of classes just why lol But just as you said as lobg i understand the core which is css , i can adjust with time
Generated by Merlin AI 00:02 CSS is easier and more powerful with new features. 01:46 Write maintainable CSS with good developer experience 03:19 CSS queries allow for dynamic styling without additional tooling 04:52 Streaming CSS is important for on-demand styling. 06:35 CSS modules and Tailwind CSS are popular options for styling in 2024. 08:17 Tailwind CSS allows for generating a CSS file based on used class names. 09:47 StyleX is a zero-runtime CSS and JS solution. 11:27 CSS in 2024 offers easier styling with improved tooling and cross-framework support.
Hey Lee, nice video! I got a question related to Next tho. Is it fine if I store my reusable components or services (functions I use to retrieve data from my DB) in folders that are prefixed by _ in my app directory? Or can this practice potentially impose routing performance issues if they get heavy? Thanks in advance!
irdk who stylex is for, because even lets say a brand wants to make the style consistent accross platform, its simply too much busiwork to implement some additional basic styling for the consumer, which is far easier to write and read with tw
Not everyone wants to learn all the tailwind shorthand, have long class strings in their markup, and bring in additional libraries like cva for variants. StyleX has a minimal API surface area, so if you know CSS you can learn StyleX in 10-20 minutes. I'm not necessarily sold one way or the other; just two different approaches with different tradeoffs.
@@TheBswan thats fair actually, if you had to pick one poison stylex might be easier to down for the uninitiated. i think longer term, tw is faster to pick and iterate with, but yeah if tailwind is discontinued then that's a lost knowledge. btw, i agree, cva and tw-merge should be built in to tailwind. that said, i think inline styles, as long as it makes "class", is more readable and configurable than ...someStylex. but preference pretty much.
Can Next please allow loading non .module .css and .scss files in to components, Next can handle the loading and leave the worrying about name collisions to me, I want to have non hashed class names which I when needed can reference contextually in other files and I don't want to always load those styles globally which is the only option next provides.
I'm not sure if I fully understand what's your issue but do you know that you can create css/scss file and import them inside a specific component file? It essentially works like a module.css. It gets imported only when the corresponding component is used, and you get to keep clean class names. The only diff would be that these classes, once loaded by there component will be accessible by the whole page and not just scoped to that component like with module.css. Actually, using module doesn't scope the classes for a specific component, it just uses hashed class names so no matter how you named it in your file, it will end up as hashed to avoid conflict with a class named identically in another module that would happen to be loaded on the same page.
why do you need stylex what does it give that you need along side tailwind? I am currently using MUI and I want to switch to Tailwind but stylex is very like MUI so I am torn
@@SCK-47 I like writing styles, it's a personal preference. I'm just saying I really like Tailwinds robust Design System with spacing, colouring, etc, but hate actually using Tailwind. So I'd much rather start a fresh project using their design system but writing my own styles with a zero runtime CSS-in-JS tool. Also MUI is a component library and stylex is not, I wouldn't be comparing them.
Is there any advantage to having css variables for more than just colour? We currently only use them for colour but I’ve seen other sites that use them in greater detail.
really love this new css @scope foo @scope { :scope { background-color: red; } .foo { background-color: blue; } } also big fan of Name .card { --my-special: "card" } @container style(--my-special: "card"){ .name { color: red; } }
11:20 I dislike most css in js solution, but this is at least more readable and clear compared to something like styled-components where every little style is a component so you always jump back an forth to see what's going on, plus that styles can compose from other components etc. To me personally, it was one of the worst experiences I had writing CSS.
Styled components can be done with different APIs and is not limited to only create components from styles. It's useful for creating reusable wrapper components for default styles, like buttons, etc. which forwards all props from a base html tag. Another example is Stitches which allows you to define variants and expose those as props (rather than exposing arbitrary CSS attributes as props). It scales the same as StyleX, because each CSS attribute + value becomes its own class, so it scales linearly. As with other styled-component like APIs it also exposes a `css` function which can be used for creating class names from styles, like StyleX' API. So the only difference API-wise is that StyleX doens't allow cascading and doesn't provide an API to create wrapper components.
@@dealloc how is that base/default component different compared to using a stylex defined style here that you just put as first and those are your base styles and then you add a prop called "variant" for example to expose different variants of that component? I mean, maybe I didn't explore styled-components fully, but everything I had contact with when working with SCs was just a horrible experience. I respect that many people might like them, but I'm not one of those.
@@rand0mtv660 I wasn't talking about styled-components (the library) specifically, but Stitches which is/was another "styled" component library. It has its own problems-e.g. passing props can end up duplicating CSS at runtime. In Stitches (and APIs like it) you get a nicer API around defining variants with zero logic, and produces deduplicated styles, since they utilize CSS variables (for tokens) and generates class per attribute. For variants you just define an object with keys that are the prop names, which defines an object of values mapped to the style they represent. These are then exposed on the resulting React component. For example say you have a Button component and you add 2 variants, one "kind" where its values can be a string of "confirm" | "destructive" | "default", each defining their own style, extending from and can override from) the base style, and another that maps a boolean value (e.g. true) to specify an outlined style. You can choose to either use CSS variables directly (using var(--... syntax)), or create compound variants to create the combination of variants so they can be used with different permutations of those variants. The point here is that styled components doesn't have to be limited to only creating components from CSS with custom handling of passed props using template strings.
I've been in the web industry for over 15 years. I went from Bootstrap to Tailwind. Haven't written a single CSS line of code since. And like Lee said, coming back 2-3 years later you'll immediatelly recognize the APIs, text-sm, font-semibold etc. I'm never going back to writing CSS ever again!
Looks like it's made to build a shared ui library and using that across different projects. That's where it shines because you can define how component styles can be overridden by ui lib consumers in a much more granular way than ever before. For standalone projects, it's likely to be overkill.
Scale that up, add a few hundred devs and try to touch that one css file without breaking things. I’ll be busy shipping tailwind in production while someone sweats that monster file and debates Bem naming standards of a giant oversized css littered with unused classes and all those classes that were supposed to be reusable but end up being nonsensical because of the cascade.
@@thegrumpydeveloper CSS modules was invented in 2015 I guess. Plus do not mix class scouping and CSS design system. You can have own design system that adopted for your needs instead of tons of tiny CSS classes. Example: you can have one ".toolbar" that adopted for many usecases instead of each time describe the same via Tailwind. You can define react component of cource, but you need react in that case. Poor design system provocate to use a tons of libs.
StyleX? Really? How much did meta pay you to say that? StyleX literally came up couple of weeks ago acting like they invented the term “zero runtime” while all other libraries like PandaCSS / vanilla-extract / KumaUI had it years ago 😂😂
Not completely dead, but a lot of things will go no code. Knowing how to prompt, that isn’t say knowing your language functionality and the terms to use AI in development will be key. I’m thinking frameworks will be used less by the new generation, since most js needed can be produced by AI and it can do back end. You will need to understand functionality and terms. There will be many no code solutions. I have a custom GPT producing sites with one word, obviously they’re simple sites but. One word such as “mechanic” produces images and the content, SEO, for a website for auto mechanic and the code. CSS happened to be hard for AI, not in explaining but in creating good visuals. We’re six months in and they say the next six months with exponentially increase in intelligence. Not dead but there will be a lot of easy methods to develop some pretty in debt stuff.
I'm glad you started this with raw CSS, and how to use it in a real world scenario with lightning. Showing how CSS can be done without JS build systems or typescript
Thank you for always being so active in the community.
🖤
Nice overview! I think those three are probably the best options today. I'm still mostly using CSS modules as they solve most of the past headaches, but I'm also looking into Tailwind and StyleX.
CSS modules solve the naming collision problem of plain CSS, and with colocation with the components, they make it easy to get rid of unused styles. Drawbacks: you still have to come up with names, and it you're building a shared ui library with it, you will always ship the CSS for all modules, even when consumers only use some.
Tailwind makes it easy to get started quickly: By shipping a nice design token system, you are likely to get consistent styling without much effort. You also don't have to name classes. And with extreme colocating, it helps with code reviews. Drawbacks: convoluted JSX code, and getting overridable styles right (often needed for shared ui libraries) is not easy. Also, you lose access to a lot of CSS features, and you have to learn the system, but to use Tailwind effectively, you still need to know CSS to choose the best layout approaches.
StyleX is more complex to begin with. But it really seems to be made with shared ui libraries in mind! In contrast to past solutions in its family, you get fine-grained control over how ui library consumers can override component styles, along with type safety. Drawbacks: I personally don't like writing CSS rules in JS objects, there's quite a bit of boilerplate code needed, and you still have to name things like with CSS modules.
So, in conclusion, all three are great. CSS modules are great if you know CSS and want access to all its features without getting lost in naming conventions. Tailwind is great to get started quickly with standalone projects, and StyleX is awesome for use in different projects with a shared ui library.
CSS modules is just so simple and perfect
I personally really like CSS Modules, but they aren't perfect. I've been using them for last couple of years, but recently switched to Tailwind and I think I'm not going back.
@@rand0mtv660same
@@rand0mtv660after all this css and scss modules i tried tailwind and was amazed by it. 99% of the arguments people use against it they don’t really understand the right way to using it. If u use something like React its just perfect for now
@@rand0mtv660 what are the issues you faced with them that tailwind solved
@@rand0mtv660 what was your issue with it?
Hey lee, preety cool stuff , i would love to have an indepth overview on Metadata api introduced with app router , specifically the og stuff and twitter images , best practices , ps: love this video , love you , thanks for amazing content
Good idea!
Oh that's a pain !
tailwind gang, comment with a "woot woot"
Woot Woot 😂
Woot woot 😅
woot woot
woot woot
Woot Woot 😂
Great content as always!
I really liked how you explained things, specially your storytelling style
Love the vid, one thing I hate about stylex (besides the name), is that you have to use the spreads a lot, which, IMO, makes the code unpleasant to read. With tailwind people can always create variables that express the intent or wrap everything in a single class.
Styling engines built with a static / build time css-in-js architecture, like stylex or panda-css, is a generational leap ahead of tailwind. They provide the developer experience of css-in-js and remove the bundle cost and runtime in browser tradeoffs. UI libraries that build on top of these types of styling engines will be the new hotness in 1-2 years.
Great video. Only part I think was missing would be if you were to go beyond simple styles into design systems & style variants, as Tailwind does start to resemble StyleX when you want to have variants
Yeah, StyleX seems really powerful here. Agreed.
Another great plugin I use is Tailwind Typography, I use it after tailwind resets all the css. it allows me to achieve consistent typography across the entire app and different browsers without additional setup on my end. And the cool thing is that I can opt in/out at anytime with the prose classname. I have it on by default and disable when I need to.
The plugin was initially created for html that's coming from external sources but I find it really good in my mentioned use case as well.
What an amazing video, thanks Lee
I've been in Tailwind camp for a while now.. but StyleX looks like a really strong alternative
StyleX and Astro seem similiar.
One of the things I hated about pre-2010 web was inline styles, which I still dislike and Tailwind basicaly is that. Just instead of writing style="..." it is class/className="".
Why would you not use the CDN for production code? Ref. the part at about 8:20 about Tailwind CSS.
Thank you, always for amazing content
One issue I get with css modules (at least in react/next projects) is critical chain warning. Always huge when using modules for all pages and components
How i'm writing css:
"hey chatgpt, what's the code to give my text a Red background?"
Panda/CVA is looking super strong
I love your videos Lee but could you change the cam video placement? it's often above the content you're showing and talking about 😅
I want to ask for you advice 🙏
I am now at point that i can work very well with css and can say i understood mostly everything , but i have no idea of boostraps and that tailwind thing and the other things , i want your advice what should i do next ? (My ultimate goal is to make amazing websites that is responisive)
Learn css html and js then have the AI help you code extensive functions and the back end. You must know how to communicate with the AI in describing what you need. Without terms and some understanding of how things work you won’t be able to use AI to resolve. If you learn frameworks you will always be a T the mercy of those frameworks, there is a pro and con. Getting up to speed is very frustrating as breakage happens. I think AI is stunning frameworks, reason being is you can have AI create only the js needed, avoiding all the extra code that goes unused.
That's perfect, knowing CSS is always an advantage over knowing a framework. You can build everything you want with pure CSS and it has great features to make your websites responsive and you can easily debug it with dev tools in your browser.
Frameworks come and go like trends come and go. Maybe in 3 or 5 years everyone says, "get rid of tailwind, it's the biggest crap we ever made 😂" ... and i'm pretty sure that day will come, like it came for other super trendy trends.
CSS will still be there and it will have even more amazing features than it has now 😉
@@HumanoAI very eye opening thank you very much🙏🙏
@@otto3225 this what i though too , right now i am taking lessons in boostrap , and i cant stand it specially that i can do everything it does with pure css , but now i need to remmber the names of classes just why lol
But just as you said as lobg i understand the core which is css , i can adjust with time
Generated by Merlin AI
00:02 CSS is easier and more powerful with new features.
01:46 Write maintainable CSS with good developer experience
03:19 CSS queries allow for dynamic styling without additional tooling
04:52 Streaming CSS is important for on-demand styling.
06:35 CSS modules and Tailwind CSS are popular options for styling in 2024.
08:17 Tailwind CSS allows for generating a CSS file based on used class names.
09:47 StyleX is a zero-runtime CSS and JS solution.
11:27 CSS in 2024 offers easier styling with improved tooling and cross-framework support.
StyleX isn't compatible with NextJs 🙁
this is a cool video.thanks!
Hey Lee, nice video! I got a question related to Next tho. Is it fine if I store my reusable components or services (functions I use to retrieve data from my DB) in folders that are prefixed by _ in my app directory? Or can this practice potentially impose routing performance issues if they get heavy? Thanks in advance!
irdk who stylex is for, because even lets say a brand wants to make the style consistent accross platform, its simply too much busiwork to implement some additional basic styling for the consumer, which is far easier to write and read with tw
Not everyone wants to learn all the tailwind shorthand, have long class strings in their markup, and bring in additional libraries like cva for variants. StyleX has a minimal API surface area, so if you know CSS you can learn StyleX in 10-20 minutes. I'm not necessarily sold one way or the other; just two different approaches with different tradeoffs.
@@TheBswan thats fair actually, if you had to pick one poison stylex might be easier to down for the uninitiated.
i think longer term, tw is faster to pick and iterate with, but yeah if tailwind is discontinued then that's a lost knowledge.
btw, i agree, cva and tw-merge should be built in to tailwind.
that said, i think inline styles, as long as it makes "class", is more readable and configurable than ...someStylex.
but preference pretty much.
styled-components is the best for me
I can't check css module import error with next lint .
You didn't mention Panda CSS. I wonder why
Panda looks interesting as well!
What's the font you're using in your VS Code ?
Edit: My bad, I just realized it's CodeSandbox.
5. No popups, unless critically essential to the end user. The popup on blur should be penalized.
Can Next please allow loading non .module .css and .scss files in to components, Next can handle the loading and leave the worrying about name collisions to me, I want to have non hashed class names which I when needed can reference contextually in other files and I don't want to always load those styles globally which is the only option next provides.
I'm not sure if I fully understand what's your issue but do you know that you can create css/scss file and import them inside a specific component file? It essentially works like a module.css. It gets imported only when the corresponding component is used, and you get to keep clean class names.
The only diff would be that these classes, once loaded by there component will be accessible by the whole page and not just scoped to that component like with module.css.
Actually, using module doesn't scope the classes for a specific component, it just uses hashed class names so no matter how you named it in your file, it will end up as hashed to avoid conflict with a class named identically in another module that would happen to be loaded on the same page.
I think my ideal would be using Tailwinds design system along w/ a StyleX alternative like PandaCSS
why do you need stylex what does it give that you need along side tailwind? I am currently using MUI and I want to switch to Tailwind but stylex is very like MUI so I am torn
@@SCK-47 I like writing styles, it's a personal preference. I'm just saying I really like Tailwinds robust Design System with spacing, colouring, etc, but hate actually using Tailwind. So I'd much rather start a fresh project using their design system but writing my own styles with a zero runtime CSS-in-JS tool.
Also MUI is a component library and stylex is not, I wouldn't be comparing them.
Working at Next.js must be cool.
Is there any advantage to having css variables for more than just colour? We currently only use them for colour but I’ve seen other sites that use them in greater detail.
Font sizes? Padding? Margins?
is styled-components dead?
Dead? It gets updates nearly every week, and still just behind Tailwind on the popularity chart.
Is it bad practise using Tailwind css with modules?
I am using @apply with "tailwindcss/nesting": "postcss-nesting",
You should avoid using @apply unless absolutely necessary. If your css is in a separate file, you're doing it at least a little wrong 😊
panda css ❤
really love this new css @scope
foo
@scope {
:scope {
background-color: red;
}
.foo {
background-color: blue;
}
}
also big fan of
Name
.card {
--my-special: "card"
}
@container style(--my-special: "card"){
.name {
color: red;
}
}
11:20 I dislike most css in js solution, but this is at least more readable and clear compared to something like styled-components where every little style is a component so you always jump back an forth to see what's going on, plus that styles can compose from other components etc. To me personally, it was one of the worst experiences I had writing CSS.
Styled components can be done with different APIs and is not limited to only create components from styles. It's useful for creating reusable wrapper components for default styles, like buttons, etc. which forwards all props from a base html tag.
Another example is Stitches which allows you to define variants and expose those as props (rather than exposing arbitrary CSS attributes as props). It scales the same as StyleX, because each CSS attribute + value becomes its own class, so it scales linearly.
As with other styled-component like APIs it also exposes a `css` function which can be used for creating class names from styles, like StyleX' API.
So the only difference API-wise is that StyleX doens't allow cascading and doesn't provide an API to create wrapper components.
@@dealloc how is that base/default component different compared to using a stylex defined style here that you just put as first and those are your base styles and then you add a prop called "variant" for example to expose different variants of that component?
I mean, maybe I didn't explore styled-components fully, but everything I had contact with when working with SCs was just a horrible experience.
I respect that many people might like them, but I'm not one of those.
@@rand0mtv660 I wasn't talking about styled-components (the library) specifically, but Stitches which is/was another "styled" component library. It has its own problems-e.g. passing props can end up duplicating CSS at runtime.
In Stitches (and APIs like it) you get a nicer API around defining variants with zero logic, and produces deduplicated styles, since they utilize CSS variables (for tokens) and generates class per attribute.
For variants you just define an object with keys that are the prop names, which defines an object of values mapped to the style they represent. These are then exposed on the resulting React component.
For example say you have a Button component and you add 2 variants, one "kind" where its values can be a string of "confirm" | "destructive" | "default", each defining their own style, extending from and can override from) the base style, and another that maps a boolean value (e.g. true) to specify an outlined style.
You can choose to either use CSS variables directly (using var(--... syntax)), or create compound variants to create the combination of variants so they can be used with different permutations of those variants.
The point here is that styled components doesn't have to be limited to only creating components from CSS with custom handling of passed props using template strings.
I personally don't like Stylex as it can get very confusing.
styled components go brrrrr
I've been in the web industry for over 15 years. I went from Bootstrap to Tailwind. Haven't written a single CSS line of code since. And like Lee said, coming back 2-3 years later you'll immediatelly recognize the APIs, text-sm, font-semibold etc. I'm never going back to writing CSS ever again!
I prefer to use Tailwind or Styled Components.
5:50 - "NFL"
Vanilla extraaaact
Pues igual que antes, con el teclado
stylex is overengineered just like most things from those companies
Looks like it's made to build a shared ui library and using that across different projects. That's where it shines because you can define how component styles can be overridden by ui lib consumers in a much more granular way than ever before. For standalone projects, it's likely to be overkill.
The same as in 2023, so change the title of the video so it's not misleading
tailwind-variants
Traditional CSS has much less issues than CSS in JS, Less/SASS. Tailwind is horrible thing.
Scale that up, add a few hundred devs and try to touch that one css file without breaking things. I’ll be busy shipping tailwind in production while someone sweats that monster file and debates Bem naming standards of a giant oversized css littered with unused classes and all those classes that were supposed to be reusable but end up being nonsensical because of the cascade.
@@thegrumpydeveloper CSS modules was invented in 2015 I guess. Plus do not mix class scouping and CSS design system. You can have own design system that adopted for your needs instead of tons of tiny CSS classes.
Example: you can have one ".toolbar" that adopted for many usecases instead of each time describe the same via Tailwind. You can define react component of cource, but you need react in that case. Poor design system provocate to use a tons of libs.
Bringing css to js was a big mistake of all the time
StyleX? Really? How much did meta pay you to say that?
StyleX literally came up couple of weeks ago acting like they invented the term “zero runtime” while all other libraries like PandaCSS / vanilla-extract / KumaUI had it years ago 😂😂
Codding is dead.... AI is taking over!
Is a waste of time...
Not completely dead, but a lot of things will go no code. Knowing how to prompt, that isn’t say knowing your language functionality and the terms to use AI in development will be key. I’m thinking frameworks will be used less by the new generation, since most js needed can be produced by AI and it can do back end. You will need to understand functionality and terms. There will be many no code solutions. I have a custom GPT producing sites with one word, obviously they’re simple sites but. One word such as “mechanic” produces images and the content, SEO, for a website for auto mechanic and the code. CSS happened to be hard for AI, not in explaining but in creating good visuals. We’re six months in and they say the next six months with exponentially increase in intelligence. Not dead but there will be a lot of easy methods to develop some pretty in debt stuff.
Coding is dead, AI si taking over!!!