BlackhatMentor:


That guy is annoying

I know Dey talk agian

LikeAking:
@XXLDICK, I am waiting for your reply..

To the best of may knowledge tailwind is written inside the HTML tags, any other funny invention of writing tailwind is a waste of time..


As long as I will write tailwind inside HTML tags, I reject it, cos it will waste my time and be hard to maintain..

It better to separate all in different files @ JS, HTML, CSS, then ….. U know what to do.

Secondly writting CSS that way is slower, although nether difference can’t be spotted on smaller projects..

I no sabi everything, I stand to be corrected..

Tailwind CSS is not written inside HTML. You only write the class names there.

Tailwind compiles everything to a CSS file. It is not inline styles.

Writing CSS the tailwind way is way faster than Vanilla CSS. You only write class names, while Tailwind helps you write the CSS.

LikeAking:


In reality I have rejected such jobs..

It’s will be very hard to work with and maintain.

That’s my only Problem..


Leave that writing JS with HTML thing. Even some devs hate that pattern.. React self carry plenty these, no need to add more these on top..

Oga go try react route splitting, then tell me Wetin you think.. If you never do route splitting for react you no go know the dangers of using React u guys cherish so much.

Go sleep

Before I go Next JS would have been the best JS frame work to me, but them too carry their own gbese.. The devs always make senseless updates and above all Next Js is a predatory software owned by vercel…

U can’t use hooks if you want to use SSR..

React without hooks, get as e be..

Nesting routes with page.js no too make sense to me.. It’s just a big confusing and time waster..

Although Next JS fast die, it’s good for big projects with big bucks..

LikeAking:




Abeg tell me Wetin be tail wind?



Tailwind is slower, it’s online to verify and I have personally tested both …

No sane dev will use tailwind for a large project..

It’s very hard to maintain..

Tailwind is not inline CSS Oga


It's just shorthand for writing classes


Same classes you would have written yourself


You add tailwind class to class='.......'


Not style='.........'



You can even create your own classes with tailwindConfig nawaoo

XXLDICK:

Tailwind CSS is not written inside HTML. You only write the class names there.

Tailwind compiles everything to a CSS file. It is not inline styles.

Writing CSS the tailwind way is way faster than Vanilla CSS. You only write class names, while Tailwind helps you write the CSS.

Is faster to write, or faster performance wise. Pls specify..


Don’t u think you are contradicting your self at the bolded..

When I say you write tailwind inside HTML tags you and I know what, talking about.. Abi make I say u write the tail wind classes inside HTML?

We all know how tailwind is written na.

The over hyped tailwind..

LikeAking:
Before I go tailwind would have been the best JS frame work to me, but then too carry their own gbese.. The devs always make senseless updates and above all tailwind is a predatory software owned by vercel…

U can’t use hooks if you want to use SSR..

React without hooks, get as e be..

Nesting routes with page.js no too make sense to me.. It’s just a big confusing and time waster..

What did you smoke?

XXLDICK:

What did you smoke?

Sorry Next JS….

Although Next JS fast die, it’s good for big projects with big bucks..

Don’t use Next JS, if you want be hosting on Vercel and also building a SSR application.

LikeAking:


Sorry Next JS….

When you want to use hooks, create a client component and use it there. You can pass it into the server component or pass the server component as a child into the client component. It depends in what you want to achieve.

Once you understand Next 13/14, you will never use 12 again.

I was about leaving NextJs until 13 came out and threw me off my feet.

LikeAking:
Although Next JS fast die, it’s good for big projects with big bucks..

Don’t use Next JS, if you want be hosting on Vercel and also building an SSR application.

At times, it kinda seem like you are just trolling.

You can use Nextjs to create static sites.

For only hosting on Vercel, it is only a matter of time before other platforms such as Amazon Amplify and Netlify will be able to run Nextjs 13 and 14.

XXLDICK:

When you want to use hooks, create a client component and use it there. You can pass it into the server component or pass the server component as a child into the client component. It depends in what you want to achieve.

Once you understand Next 13/14, you will never use 12 again.

I was about leaving NextJs until 13 came out and threw me off my feet.

Na long story, a reason I dumped it..

Next updates will carry something totally different agian..

Do this and do that and don’t do that..

EEIA:

It's obvious you have never worked on a large project before.

You young developer should learn how to talk because it is a special skills that will take you far in the industry

Do u think it is only web development is the only field is software engineering


How many large project had you build and how many of them do you know the memory it consumes


Just from the comment alone I know u be JavaScript fan boy

XXLDICK:

The boiler plate code it ships with is for CSS reset.

I am aware vanilla CSS will be more lightweight for a site that is too small. That's why I said Tailwind will be more lightweight most of the time, not all the time.

A clean written CSS will be just exactly as Tailwind does it (atomic) and that is almost impossible to achieve without a framework like Tailwind.

Tailwind should be a must for everyone. Everyone who understands Tailwind can easily modify styles without even inspecting the classes.

Exactly my point not all project needs all those css reset. So its not specific and gives you unnecessary code.

A clean written css is not almost impossible to achieve. Its very much doable. You just need the right convention and more importantly experience writing vanilla. One thing is to learn css the other is to learn to write it effectively which is doable not impossible at all.

I don't conform to this or that is a must. I remember working for a company last year and one of the devs never wrote tailwind once all his classes were beautifully crafted and named that I even had to start using them under certain conditions instead of tailwind classes. Because they were quite frankly so much more efficient. The only downside was the lack of intellisence.

Theres no one size fit all, yes tailwind is easier as it handles all the hassle for you but it doesn't mean its a must. Infact I rather a newbie go through the pain of writing vanilla and learning how to write it effectively than just jumping to tailwind. That's how I learned personally as it makes you very versatile.

That said I will always recommend tailwind for large teams to avoid problems. If not possible ensure your team has a working naming convention, and always have core reusable classes they save you alot of time.

XXLDICK:

What is better than NextJs aside from Qwik?
Is there any framework that makes caching easier?
Yes, SSR improves SEO. Is there any framework that can easily get close to 100% lighthouse score compared to NextJs aside from Qwik?

NextJs may have it's disadvantages like vendor lock-in, but their SSR is the best I have seen. Only Remix comes close.

Astro is also good too. You can get good lighthouse score easily but their routing is a major problem. I really like the idea of their islands giving you the ability to use any js framework from react, vue, solidjs and the likes. But I sha couldn't deal with their use of a tag for routing. Not sure if they have fixed this though.

Next aggressive caching is one of the reasons I abandon it. They are now trying to fix it with their noStore function which is good. Their hot reload is not the best either, takes forever to load pages as the app gets bigger. They did promise their next turbo will fix these issues when ready, hopefully they do. There was this epic post I read on this hot reload issue on github. The guy was so blunt and asked some good questions. I will try to find it and send here, he literally spoke my mind and more.

Is Qwik any good? Granted last time I used it was before they got to version 1 but it was very slow to become interactive. I tried it out for a documentation I was writing, I remember once the page loads you will have to click the nav links more than once for it to respond. On Dev it works fine but in Prod na cast. I just jejely comot eye haven't gone back since.

silento:


You young developer should learn how to talk because it is a special skills that will take you far in the industry

Do u think it is only web development is the only field is software engineering


How many large project had you build and how many of them do you know the memory it consumes


Just from the comment alone I know u be JavaScript fan boy

You claim to know yet you just blurt out things as a novice would.

Sorry, but I very much doubt your self acclaimed proficiency.
Also you don't need to try so hard to be or feel relevant.
1
At least, from every intermediate developer ascending knows programming is independent of being bound to language (syntax).

2
Well, mostly, memory allocation is taken into consideration when using compiled languages and vice versa when regarding an interpreted language.

You refer me to be a script kiddie?
Well, let me know master Silento how much memory your last big project consumed.

If not that languages with automatic garbage collection exist you wouldn't have been able to come here to say garbage.

This time, please take measure, comprehend vividly before replying.

Shalom

truthCoder:


Weyrey.

If no one in your clan can write easy-to-comprehend comments, don’t assume your defects are commonplace.

Go through my posts and maybe you might learn how to communicate your thoughts through words.

If you want to accuse me of plagiarism, be ready to come with evidence or i will roast your microscopic balls for a simple biology experiment.

It wasn't you I wanted to reply?
Wrong post.












Wait oh! You wan barbeque my ball sack and 2 precious stones on top comment.

Haba.

Congratulations!!! You don officially chance "Moloch" for devil high table.

EEIA:

You claim to know yet you just blurt out things as a novice would.

Sorry, but I very much doubt your self acclaimed proficiency.
Also you don't need to try so hard to be or feel relevant.
1
At least, from every intermediate developer ascending knows programming is independent of being bound to language (syntax).

2
Well, mostly, memory allocation is taken into consideration when using compiled languages and vice versa when regarding an interpreted language.

You refer me to be a script kiddie?
Well, let me know master Silento how much memory your last big project consumed.

If not that languages with automatic garbage collection exist you wouldn't have been able to come here to say garbage.

This time, please take measure, comprehend vividly before replying.

Shalom

When I said knowing how to talk is a special skilled some will think I was yabbing , just see how u vomited total rubbish without making a point , I met people like you everyday , 😔 na for mouth your power dey , do u even know what memory means , do you even know you css, html and JavaScript work under the hood

Go back and finish your lessons because from the reply it is so obvious you don't know anything about the programming in general

silento:


When I said knowing how to talk is a special skilled some will think I was yabbing , just see how u vomited total rubbish without making a point , I met people like you everyday , 😔 na for mouth your power dey , do u even know what memory means , do you even know you css, html and JavaScript work under the hood

Go back and finish your lessons because from the reply it is so obvious you don't know anything about the programming in general

Looking at how you write, it's no surprise that you are bound to lack comprehension talk more of to understand concepts.

XXLDICK:


How can you call Tailwind an inline CSS?

Tailwind is slower?

Tailwind is for very small projects?

I have never seen as much misinformation as this in just a few paragraphs.

Even the person you quoted will shake his head at such ignorance you spill with confidence.

I swear down.

EEIA:

Looking at how you write, it's no surprise that you are bound to lack comprehension talk more of to understand concepts.

Seriously bro go and find better things to do with ur life programming is not your calling

I will bet 50k bring any project u have done before , I will ask you 10 questions out from it if u can answer 5 I will dash you the money

Na back in 2018 we deal with people like u for this section before we got busy , I only comes here occasionally just to read news

silento:


Seriously bro go and find better things to do with ur life programming is not your calling

I will bet 50k bring any project u have done before , I will ask you 10 questions out from it if u can answer 5 I will dash you the money

Na back in 2018 we deal with people like u for this section before we got busy , I only comes here occasionally just to read news

2018

5 years from them and all you can muster is this?

By the way, what programming languages do you even write?

EEIA:


2018

5 years from them and all you can muster is this?

By the way, what programming languages do you even write?

Bring project and earn 50k

silento:


Bring project and earn 50k

Normal Tantrums of a script kiddie wannabe techie who hasn't passed one but wants a share in the glory of being called a seasoned developer.

jikins:


Exactly my point not all project needs all those css reset. So its not specific and gives you unnecessary code.

A clean written css is not almost impossible to achieve. Its very much doable. You just need the right convention and more importantly experience writing vanilla. One thing is to learn css the other is to learn to write it effectively which is doable not impossible at all.

I don't conform to this or that is a must. I remember working for a company last year and one of the devs never wrote tailwind once all his classes were beautifully crafted and named that I even had to start using them under certain conditions instead of tailwind classes. Because they were quite frankly so much more efficient. The only downside was the lack of intellisence.

Theres no one size fit all, yes tailwind is easier as it handles all the hassle for you but it doesn't mean its a must. Infact I rather a newbie go through the pain of writing vanilla and learning how to write it effectively than just jumping to tailwind. That's how I learned personally as it makes you very versatile.

That said I will always recommend tailwind for large teams to avoid problems. If not possible ensure your team has a working naming convention, and always have core reusable classes they save you alot of time.

All your points are correct.

,

jikins:


Astro is also good too. You can get good lighthouse score easily but their routing is a major problem. I really like the idea of their islands giving you the ability to use any js framework from react, vue, solidjs and the likes. But I sha couldn't deal with their use of a tag for routing. Not sure if they have fixed this though.

Next aggressive caching is one of the reasons I abandon it. They are now trying to fix it with their noStore function which is good. Their hot reload is not the best either, takes forever to load pages as the app gets bigger. They did promise their next turbo will fix these issues when ready, hopefully they do. There was this epic post I read on this hot reload issue on github. The guy was so blunt and asked some good questions. I will try to find it and send here, he literally spoke my mind and more.

Is Qwik any good? Granted last time I used it was before they got to version 1 but it was very slow to become interactive. I tried it out for a documentation I was writing, I remember once the page loads you will have to click the nav links more than once for it to respond. On Dev it works fine but in Prod na cast. I just jejely comot eye haven't gone back since.

NextJs caching works well now. No issue again.

Qwik is stable now. Resumabilty over hydration.

The only downside of qwik is when you click a button or link just immediately after the site loads, it may not respond immediately, just a few milliseconds delay.

XXLDICK:
,
NextJs caching works well now. No issue again.

Qwik is stable now. Resumabilty over hydration.

The only downside of qwik is when you click a button or link just immediately after the site loads, it may not respond immediately, just a few milliseconds delay.

NextJs cache has worked well that wasn't what I saying. My problem is that its too aggressive. I feel it should be something you opt in for rather than it being the default state. I had a terrible experience. To opt out you have to individually opt out for the many cache from full route cache to data cache and memoization which are sever caches and also in memory router cache on the client. There was an article I read from one of the guys working on remix on why he doesn't use nextjs and he pointed out this pit fall too. Their new unstable_noStore function trys to fix this and I believe template files too. Haven't use next 14 to confirm if it works but its very much needed.

For qwik yes that milliseconds delay was too obvious and even more than a milliseconds self way back. But if they have improved on it to make it largely unnoticeable that will be good.

jikins:


NextJs cache has worked well that wasn't what I saying. My problem is that its too aggressive. I feel it should be something you opt in for rather than it being the default state. I had a terrible experience. To opt out you have to individually opt out for the many cache from full route cache to data cache and memoization which are sever caches and also in memory router cache on the client. There was an article I read from one of the guys working on remix on why he doesn't use nextjs and he pointed out this pit fall too. Their new unstable_noStore function trys to fix this and I believe template files too. Haven't use next 14 to confirm if it works but its very much needed.

For qwik yes that milliseconds delay was too obvious and even more than a milliseconds self way back. But if they have improved on it to make it largely unnoticeable that will be good.

I prefer the opt-out approach because more often than not, I need the cache for optimisations.

You can change the default behaviour in your vercel.json file.

Below is a picture of a reset I did when I had troubles with caching because I didn't understand it.

XXLDICK:

I prefer the opt-out approach because more often than not, I need the cache for optimisations.

You can change the default behaviour in your vercel.json file.

Below is a picture of a reset I did when I had troubles with caching because I didn't understand it.

Sounds good will try it out whenever I return to nextjs. Thanks

XXLDICK:

You are wrong.

You will get a more lightweight CSS using Tailwind instead of vanilla CSS almost every time.

Tailwind is atomic. And no repeating yourself(DRY).

Exactly..


I didn't even see this post earlier.



Abeg chop virtual knuckle. 👊🏾

LikeAking:


Make we leave arguments and hype one side..

Why will you put everything in one place?

The best option is to separate both..

It’s easier to work with..

Let’s leave clout and bad blood out of this.

Most of you are word press guys, looking for the easy way..


Writting css alongside html is a taboo..

Bundling backend and front end together is a taboo. I know say una go argue on it..

Understanding certain concepts is not easy for certain people.
Understanding and comprehension too.

🤦🏾‍♂️🤦🏾‍♂️🤦🏾‍♂️