₦airaland Forum

verminnel:
lol I've not had any complain yet

As it should be

verminnel:
okay there's that also.

Hope you are good cook though?

verminnel:
OK just what if she travelled and was only thoughtful enough to have ordered the food for him ? Did u think of it that way?

Still if she was a better cook the guy won't even think twice. There's nothing like constantly having heaven in a plate.

verminnel:
She dodged a bullet. He never was her's !!!

Obviously he belonged to the girl that can cook

MindHacker9009:
See how your fish brain is seeing your fish mouth on this thread. You are so clueless, just because software development is not regulated like architecture, structural engineering etc has given people like you that should that should not have any business with programming, the chance to be exposing your fish brain online.

Damn dude is pained love to see it

Sultan5:
I would love to hear where he saw react releasing 2 versions in a year. But looking back at all his comments its clear his empty head pounded for a bit and drop that point. Because this has never happened in the many history of react. One of the many reasons you should give him his W make him go sleep. The amount of rubbish he has spill on this thread is alarming.

Lol I saw that na why I call am dump of cluelessness. He just opens mouth waaaaa and dumps trash effortlessly.

Sultan5:
Give him his small W na. He is clearly desperate for it. At least even if we all know nothing dey him head . Let him have this one that jquery is the best js framework to use nowadays.

Nothing really is in his head. People like him is what a prof in school call stony dull. No atom of intelligence. I have been waiting for an intelligent responds for ages all he does is copy ai chat message and dump. The Ai message is even contradicting him with the Instagram thing he still post am thinking he is making sense. I have lost several braincells talking to this dude. I will definitely just follow your advice.

MindHacker9009:
When clueless people like you have been defeated online you turn to insults because you still have the brain of a fish.

You cannot even respond to this but can insult your fish brain : React that is releasing on average 2 versions yearly to fix an issue yet you have to rewrite the frontend again to use the new version and then wait for the next version to fix the current version. See the your fish brain!

See mouth like defeated .

You defeated yourself long ago I am just here for the endless dump of foolery. Man how can someone have this low an iq that he thinks he has any W anywhere damn! Not one single point did you get a W. The thread is full of your endless Ls. You should work in the circus thats where people like you belong not in intellectual discuss. React uses signals men that line broke me

MindHacker9009:
You are so clueless now that you are just typing crap not surprised when you prefer React that is releasing on average 2 versions yearly to fix an issue yet you have to rewrite the frontend again to use the new version and then wait for the next version to fix the current version. See the level of your cluelessness!

continue with the dump of cluelessness. Not point engaging you, you have the iq of a toddler.

MindHacker9009:
You are the clueless one mentioning js signals which has no deliverance to this thread. You and your 100% clueless brother here are the ones that will spend years on a project as you have to keep waiting for a new version of your crap React to fix an existing issue, now your React is on version 19. which was only first released in 2013.

You and your brothers' cluelessness is the reason you use React for projects that can be completed in one month with jQuery but ends up: "Over a year later, what started as a simple medical appointments platform has become a cautionary tale of modern software development gone wrong. The unnecessary complexity introduced by poor technological choices has led to delays, increased costs, and frustrated developers - exactly the problems I’ve outlined above."

Yet another dump of cluelessness. So classic no evidence of higher brain function

Sultan5:
He literally just proved us right lol no need to stress more than that

Lol he has been proving me right since the beginning of this thread its nothing new. From signals to issues with react and jquery. Its just been an endless dump of cluelessness

MindHacker9009:
You are the illiterate that does not know that serious companies have never used your React crap so they have not reason to return to jQuery as they have always used jQuery.

you and those companies will be fine las las enjoy jquery brother

MindHacker9009:
None because no serious company will use those crap new frameworks you and your brothers are using to mess up frontend development.

Case closed thank you

MindHacker9009:
You are the one that learnt nothing at school and when given a calculation will only use the minus key because to you all the other key are out dated.
You are an illiterate that does not have a clue of what software analysis and design is all about, all you know are the crap new frontend framework your brothers tell you to use just to help them promote their crap.

Well done our resident illiterate still waiting on the 1 company that changed from react to jquery even if na Nigerian company we go manage am

MindHacker9009:
The creators of these new frameworks just want trend and because they control the tech space they have to use you and your brothers to push their crap new frameworks on every frontend project.

With these new framework crap their moto is: Move Fast, Break Stuff, Release a New Version.
When was React first released and now it has quickly reached version 19, yet those on version 18 cannot migrate to version 19, meaning they have to rewrite the front-end all over again before the can move away from the issues in version 18.

For Long-term stability, tell your React brothers to move to jQuery and forget about the new framework mafias pushing their crop on every project.

Still waiting name 1 company that moved from react to jquery

BlackManta:
The laughable things I heard about this movie ehn.

They said he beat Red Hulk by just talking to him. (This isn't who you are, let me help you type of speech)

After all the gbas gbos, he used the power of love and friendship to get a freaking Hulk to calm down and revert back to normal.

He didn't beat red hulk, infact red hulk kick his ass to kingdom come. This was his only last resort because if red hulk attacked him there he was dead.

Its not far fetched even the hulk has been calmed by words in the past.

Sultan5:
The guy you are talking to can't write frontend code to save his life. Let him keep advocating for jQuery, actual frontend dev will continue to use the better options out there no doubt about it. It's clear for everyone to see his 100% clueless about this. Even when he listed companies that left react he listed Instagram in the same post it was noted react was improved on to fix these issues by introducing server components. Anyone who know an atom will understand that the reason most of those companies left react has been fixed and addressed with server components that let you serve pages with very little js and with 100% SEO compatibility.

The fact he wrote that and still don't understand its implications and he think its a plus in his argument says all you need to know

These are things any FE dev knows its why I don't bother educating or correcting him again. He doesn't understand all these things you have said, he will just run to one chat ai to get outdated info and post here. Its sad that human beings like this exist despite going through school. It now begs the question of what exactly did he learn in school.

Sultan5:
Set up a simple react app now with nextjs or react router 7 you will see they are not defending anything but speaking facts. No way you can lie about tools developer use every day and go scot free. I see you are still arguing this easily verifiable claim they made. Proving you can't write any frontend code to save your life. If you can you will easily verify this and not be speaking out of your ass

Set up ke its like asking an illiterate to calculate 1 + 1 using a calculator. He doesn't even know where to start from.

MindHacker9009:
This is what you and your brothers projects ends up like after using React: Over a year later, what started as a simple medical appointments platform has become a cautionary tale of modern software development gone wrong. The unnecessary complexity introduced by poor technological choices has led to delays, increased costs, and frustrated developers - exactly the problems I’ve outlined above.

You are wasting energy just name 1 company please that switch from react to jquery. Just 1 we are still waiting

Karleb:
The repo has 2 layers, we are not consuming an external api.

Its the business logic and the ui layer which already have 2 separate github repos, now the dummy project manger created 3 repos per layer, making it a total of 6 DIFFERENT REPOSITORIES! Just because it has 3 dashboards.

That's the most rookie thing I have seen in my life and I have spent the past 3 posts explaining it to a guy who doesn't code on this thread why it's a terrible idea.

It just reminds me of how a guy was arguing with a lawyer on Twitter and when they asked of his law degree, he said he learnt everything off suits series.

The project uses 2 repos now because that nonsense cannot happen on my watch.

I saw what you did there

MindHacker9009:
If you cannot read my comments then you should forever hold your peaces in ignorance.

You mates that don't want to hear of jQuery are the ones adverting them not to use jQuery, just because they want to trend by saying they are using the latest frameworks, but does not want to admit that jQuery is better.

Event the Hotwire/Turbo one of them have moved to still have these issues:

Turbo aims to minimize JavaScript, but some applications with complex, dynamic interactivity may face challenges when trying to fully leverage Turbo’s model.
Problem: Highly dynamic UI elements (e.g., complex forms or components with lots of interactive states) that rely on client-side JavaScript may not fit well with Turbo’s server-driven approach.
Impact: It may require workarounds or introducing more custom JavaScript to handle specific interactivity that Turbo doesn’t naturally support.

Lol its simple na its not rocket science we don't need to call Elon Musk for this. You have friends na, I am sure your blog post brother has friends too. So just name one, I am not asking for alot here, name only 1 big company you and your friends have been able to convince to leave react and move to jquery. We are waiting

MindHacker9009:
These companies have dropped or avoided your React, but because they are been misinformed by your mates they don't want to go back to jQuery, so they are going to still be dropping the new frameworks they have moved to.

1. Airbnb (Partial Rollback of React & React Native)
Issue: Airbnb initially adopted React Native for mobile development but later abandoned it due to performance issues, integration problems, and developer experience challenges.
What happened?
Difficulty integrating React Native with native code.
Slower performance compared to fully native solutions.
Issues maintaining a unified React Native codebase across Android & iOS.
Result: Airbnb switched back to native development but still uses React.js for their web app.
Source: Airbnb Engineering Blog

2. Twitter Lite (Switched from React to Preact for Performance)
Issue: Twitter initially used React for its lightweight mobile web app but faced bundle size and performance bottlenecks on low-end devices.
What happened?
React’s large bundle size (~40KB) slowed down initial load times.
Increased JS execution time on slower devices.
Twitter needed a more lightweight alternative to improve UX.
Result: They switched from React to Preact, a smaller alternative (~3KB), improving load times and performance.
Source: Twitter Engineering Blog

3. Instagram (Struggles with React’s Performance in Complex UIs)
Issue: Instagram, owned by Meta (the creators of React), faced performance issues with React in their web app, especially with state-heavy components.
What happened?
Large component trees led to inefficient re-renders.
Complex animations and interactions suffered from React’s reconciliation process.
Memory usage spiked when handling extensive media content.
Result: Instagram had to optimize React performance aggressively and introduced server-side rendering (SSR) and memoization techniques to handle the issues.
Source: Internal reports & discussions from Instagram engineers.

4. Medium (Dropped React for Preact)
Issue: Medium initially used React but switched to Preact due to performance and bundle size concerns.
What happened?
React’s large bundle size slowed down page loads.
Heavy client-side rendering (CSR) caused delays in rendering content quickly.
Result: Medium moved to Preact, which provided similar capabilities with a smaller footprint.
Source: Developer reports & discussions.

5. Basecamp (Dropped React for Hotwire/Turbo)
Issue: Basecamp (creators of Ruby on Rails) initially used React for dynamic UI elements but found it too complex for their needs.
What happened?
React’s state management was overly complicated for their architecture.
Too much JavaScript overhead for an app that needed mostly HTML-based updates.
Result: They switched to Hotwire/Turbo, a server-driven approach that minimized frontend complexity.
Source: Basecamp Blog

6. GitHub Avoids React
What happened?
What happened?
Slow initial page loads – React’s client-side rendering (CSR) required downloading and processing large JavaScript bundles before displaying content.
High JavaScript overhead – GitHub’s UI is mostly static, and React’s reactivity system added unnecessary complexity.
Performance issues on large repositories – React’s reconciliation process slowed down rendering complex diffs and issue threads.
Security concerns – Using minimal JavaScript reduced the risk of cross-site scripting (XSS) attacks.
SEO challenges – Server-rendered HTML ensured that GitHub’s content remained fully indexable by search engines.

Do you know the funny thing everything you listed here only proves my point.

None not one even consider moving to jquery

I have always said there are alot of alternatives but jquery isn't one of them. Thank you for proving my point without a reasonable doubt.

Show us one company that moved from react to jquery oga. Or forever hold your peace

MindHacker9009:
All these new frameworks you want to die on are all built on JavaScript and the creators are just after making a name for themselves rather than coming out with something as stable as jQuery that can handle any task properly.

These are still the issues with the latest version of React 19 you want to die on:
Migration Challenges – The React 19 migration tool has bugs, making it difficult to upgrade from React 18. Some issues stem from the new JSX transform.
Suspense Behavior Changes – Suspense now prevents sibling components from pre-rendering, potentially causing performance issues due to sequential data fetching.
Dependency Conflicts – Some third-party libraries, like @testing-library/react, are still optimized for React 18, leading to compatibility issues.
Ecosystem Compatibility – Many React libraries and tools have not yet fully adapted to React 19, causing version conflicts and upgrade difficulties.

Lol so jquery is built on the moon not javascript. You are sounding less intelligent every single post you make.

Even with all these issues I will gladly die on the hill of react than step one foot on that of jquery. You cannot pay me enough to go through that torture.

But does react 19 have all those your many problems you have been listing upandan do well to ask chatgpt lets hear what it has to say.

As much as I hate react I still come back to it. I ran away to solid, to vue to svelte to astro to remix even to qwik trust me I have ran places. But react just feels like home, when I want to build scalable website react is my go to because its tested and trusted. When I want to build smaller website I experiment.

The only framework I haven't really experimented with well is angular. The battery of files the set up created when I first installed it was crazy I just didn't continue. However that was long ago before typescript became a thing in React. I was sha using it to show my self small for work that time because I had a little bit of experience with it in angular.

But you see your precious jquery, I use it for one site several years ago and I have never returned and will never returned. Although I did see they pushed a new update late last year. Made me think of giving it a chance but nah, when you can have chicken why settle for chewing stick

MindHacker9009:
You and your mates using React for every project without doing analysis as to which framework is best, but just use React are the ones that are ignorant and continue to show pride in your ignorance.

You still cannot describe projects you have worked on that jQuery cannot do.

Even with version 18: These are still the Issues Not Fully Fixed in React:
Performance Overhead in complex applications (deep component trees, frequent updates).
Bundle Size and dependency-heavy applications.
SEO challenges with client-side rendering (especially in dynamic apps).
Memory Leaks due to improper cleanup.
Overhead in simpler apps due to React's abstraction.
Fragmented ecosystem and tool/library compatibility issues.
Handling complex forms or large UI components with high performance.
Unpredictable performance with Concurrent Mode.

This one doesn't even know there is react 19

Thats all I will say about your delusion. You need help brother seriously this is troubling. The chat bot that is helping you isn't doing a good job at all

I don't use react for all my project thats why I listed several other js framework for you. There was simple site I did for someone some months ago I used Astro js.

Unlike you that want to die with jquery and that you can build every site with jquery. I will never use jquery for any website, because there are so many better options to pick from. React isn't the only kid in town them plenty and I recommend. But jquery you are on your own in that madness

MindHacker9009:
You are just spilling out trash dues to your ignorance. Bringing in js signals mean you don't even know what you are taking about and you are the one that had problem with English at school.

Let me lecture you on React you think you know but you are even ignorant of. In React, events like onClick, onChange, and onSubmit can be seen as signals.

Here are the key Downsides of React on the Client’s Machine
Increased initial load time due to large JavaScript bundles.
Memory consumption for rendering complex UIs and handling state.
Increased JavaScript execution time can cause slowdowns on lower-end devices.
Dependency on JavaScript—no fallback if JS is disabled.
SEO challenges without server-side rendering.
Performance overhead on low-end devices or for complex applications.
Difficult debugging in larger apps with deep component trees.
Fragmented ecosystem of React libraries can cause incompatibility issues.
Abstraction overhead can sometimes hinder performance for simpler apps.

You are running away from my question to describe what projects you have used React for that jQuery cannot do but to hide you ignorance you are jumping around show more of your ignorance.

You see another reason why I said you and your blog post brother are cut from the same cloth. When I mentioned server components and how it makes serving webpage at fast speed you didn't see it. Oh yeah I stated it in the post you are still using touch light to find . Sorry oh maybe I should stop answering so you stop disgracing yourself.

Every thing you mentioned are problems with create react app which has been deprecated already. Lemme guess you didn't know same way you didn't know React doesn't use signals . Oh right you thought it was Websocket... Sure sure

You are a joker I swear, you are trying so hard to sound like you know what you're talking about. But time after time you keep showing you are a lost puppy. With literally zero insight. Please do well do go to the official react page and set up a react project any of the ways they recommend and see if you will have these issues.

Ignorance is really a bad thing. But ignorance with pride is the worst.

MindHacker9009:
It you that has a problem with using jQuery in 2025. I have asked you to describe the projects you have done with React that jQuery cannot do but instead you are jumping around with your ignorance.

You do even know what JavaScript signals are. JavaScript signals can be just a click or keypress, but I was referring to advance JS signals like Signals in WebSockets. Shows you don't even know what all the different types of JS signals are.

I mentioned programing languages as well as they are not different from choosing the right framework to use for a project, but you were ignorance of these exaple.

You are the ones the blog writer is referring to that will just use a tool they only know for a project and will end up not being able to deliver the project or will deliver one that does not me the users needs.

Lol this guy is desperately trying to get a W . I am sorry I can't take you seriously any more. You have displayed your ignorance for all to see.

How will anyone who have their head together and knows the js ecosystems be thinking about Websocket when I mentioned signals and I even stated they aren't used in react. If your head cannot boot after hearing the context that you now have to bring wack narrative to safe face, I don't know. You don't have anything else to say.

I won't be surprised if you struggle with English in school. I literally address your first paragraph above when I quoted that message. But instead of addressing it like a normal human being you ran away and started drawing weird comparison of jquery with other languages when we are talking about frameworks in the same language. And then made the powerful claim that React js uses signals.

How will you even read my response when all you do is carry ego and spit trash. If you were speaking facts self eh we can manage the ego. But this one facts patapata you nor get. Na why you dey use touch light find wetin no lose. Na why you think FE dev should use jquery in 2025. Just vibes I swear, I can't take you seriously again brother

MindHacker9009:
So you mean because Fortran, C or C++ or Java are old means it should not be used anymore when there are new languages out now? This is the problem with the low barrier to entry in programming and the tech world, you see someone with a degree in maths, chemistry, biology etc or no degree at all but just a coding boot camp and they are all calling themselves Software Engineers. When the word Software Engineer should only be reserved for those with a degree in computer science or software engineering or computer engineering because these are the people who will first analyse a project requirement to determine which language is best for the software application before they will begin to code. But those without these degrees will just use any latest language or framework just because it's the latest not knowing what type of projects they are good for.

You can use React with JavaScript Signals for real-time updates. Means your don't even know much about React you are promoting here.

In 2025 you can die on your ignorance not knowing when and what each programming framework is good for.

React doesn't use js signals oga, react uses virtual dom. Try to learn things before spitting trash. Framework like solidjs use signals.

And who is promoting react? I am only responding to the massive ignorance on display. I even mentioned several other frameworks

How is JQuery synonymous to java and C and the likes. The level of mental gymnastics you have to do to relate both in this context is crazy. Jquery is a js framework others I mentioned are js frameworks.

I literally listed some few bone of contention in using jquery obviously you have no insight into the js ecosystem to respond to them, to even say React uses signals just proves you have no idea what you are talking about. You just dey open mouth waaa like your blog post brother. No solid ground of knowledge to stand on just vibes.

These are all again frameworks, the idea of jquery was to improve developer experience with vanilla js. Other framwork that came after did jquery jobs 10 times better. No project requirement will make any frontend dev use jquery in 2025, you can take that to the bank except they are like you with no knowledge no hands on experience just vibes and all talk.

You don't know something you will not ask questions and learn. Na to carry ego dey yarn trash. See how you disgrace yourself now. I even rated you high small but as you mentioned react uses signals I know say this one is gone, you have nothing to contribute to this discusss.

While at it yeah you and your blog post brother can tell node js developers not to use frameworks like express, fastify, nest, adonis but instead use vanilla nodejs because the project needs it.

MindHacker9009:
The blog post is not mine but I agree with many of his comments.

You mentioned signals in JavaScript, so describe the projects you have done with React that jQuery cannot do?

Oh I definitely knew it wasn't your post, which is why my comment weren't directed to you.

Your last paragraph is confusing, how is my mention of signals and project with React that JQuery cannot do correlate? React doesn't use signals. E be like say you and the blog poster are cut from the same cloth, no wonder you agree with him

Also I never said jquery can't be used for websites. But its an old technology, and the developer experience with it compared to newer technologies like React, vue, svelte, solidjs are miles away. You will almost always develop any website at faster speed and efficiency with these technologies than using jquery where you have to do the monotonous selection of dom elements before doing anything with them. To do a simple incremental count will see you jumping from one file to the other like a headless chicken. Manipulation of css even loading api data on the page require tedious unnecessary code setup. These are all done with ease in react. With the power of new technologies like server components, you can serve pages at lightning speed.

I mean its 2025 if you want to die on that hill feel free, each his own but the blog post writer is definitely out dated in his views. I can very much relate because I have actually worked with developers like him in the past. Too rigid to learn new things, too stiff to bend to modern approach. How can you be a developer and not be willing to learn,

MindHacker9009:
This blog is wrong on Kubernetes, as this should the determined by the number of servers needed for load balancing and not by the number of developers in the team.
But with the rest of the blog he is right.

From a blog post: A little over a year ago, a friend of mine hired an agency to build a web application for his business. The application is basically a simple online platform for medical appointments and consultations via video calls using Twilio. Since my friend doesn’t have that much technical knowledge, he asked me to help him validate what the agency was proposing. When I read the proposal, I was shocked. Not only because of the value they were asking but even more so due to the technological choices. It was clear to me right away that they were the typical agency where no one knew anything other than Javascript and MongoDB (thanks, Freecodecamp! 😠) - in other words, they know very little about proper software engineering.

They mentioned React, Strapi, MongoDB and GraphQL as the foundational technologies for the application. This made absolutely no sense:

Strapi is a framework to build CMS, not a framework or library to build a full-fledged web application.
MongoDB is a document store but this type of application will obviously be based on relational data and thus, it needs a relational database.
GraphQL is meant for scenarios where you have a lot of scattered data and you need to easily be able to fetch random pieces of data from random places.
React might be a good fit for large teams building very large and very complex frontends but this is a fairly simple application and the agency building it is very small. [Would suggest jQuery still for any size project]

In summary, none of the tools they chose were meant to solve the problem at hand, which was building a very specific and very well-defined type of web application. Sure, any of those tools could be used to build the application, just as you can also use a spoon to cut your potatoes and a fork to eat your soup - but does it make sense? Just because you can doesn’t mean you should.

All of those choices added unnecessary complexity, which meant unnecessary time spent building the application, unnecessary electricity spent and the accompanying carbon footprint, unnecessary money spent by my friend, and ultimately even unnecessary frustration for the developers who are working on it. Yes, “working”, not “worked”, because they still haven’t finished it and are way beyond their original estimation of three to four months.

I’m not sure exactly how we got here but I think it’s a combination of at least three things:

The “anyone can code” culture, which led to too many pseudo-programmers contributing negatively to the ecosystems.
Marketing folks pushing buzzwords to everyone’s mind.
Script kiddies wanting to use the cool tools from the big guys because they all want to be the next Zuckerberg, without understanding the problems these tools were designed to solve.

The vast majority of companies are small. Your company is most likely a small company. What huge companies like Google and Facebook do does not apply to you. Not only does it not apply, trying to replicate what they do on your smaller company is actually detrimental. You do not have the same problems they do, and certainly not at the same scale. And even if you did, you don’t have the amount of money or people to absorb the complexity of the systems and tools they use. It’s incredibly counter-productive to adopt, for example, micro-services and Kubernetes in a company that has 6 or 7 engineers. Such a company does not have the type of problem these tools solve, nor do they have the capacity to absorb the complexity that comes with said tools. And yet, this is exactly what many small companies do.

Returning to my friend’s project: over a year later, what started as a simple medical appointments platform has become a cautionary tale of modern software development gone wrong. The unnecessary complexity introduced by poor technological choices has led to delays, increased costs, and frustrated developers - exactly the problems I’ve outlined above. Through this series of posts, I hope to show that there’s a better way: one that focuses on choosing the right tools for the job, embracing simplicity where possible, and remembering that our goal is to solve real problems, not to chase the latest trends. Perhaps by examining these issues one at a time, we can start shifting our industry back towards more sensible, maintainable, and enjoyable software engineering.

https://www.borfast.com/blog/2023/06/19/software-engineering-is-broken/

So use jquery instead of react that obviously someone that hasn't done frontend in a very long time. Whats wrong with mongoDB? Also seems like someone who hasn't used mongoDB since 1700s. Mongoose makes mongoDB essentially a relational database.

All I see here is just an old programmer stuck in his ways, not willing and open to update his knowledge and understanding of technologies he so much criticise.

Even with jquery and a SQL database, if the developers don't know what they are doing which will likely be the case if they are building a website with jquery in 2025, they will still struggle to deliver.

I am pretty sure if you ask this guy what are signals in javascript he will have never heard of it. These are the dangers of living in your own little bubble, not willing to keep your self updated.

phr0nesis:
I think it's 3rd or 4th in the US box office this weekend.
The Anime fanbase is growing rapidly worldwide. I won't doubt the possibility of the movie making its way into Nigerian cinema.

It isn't an anime though.

abduleez1:
Wetin dey occur....


https://www.youtube.com/watch?v=mhQcpvKHis4?si=SOQhZmAXH6hd7WGg

Homelander terrorising the world in every universe.

GloriousGbola:
youtube premium does not work with any of my cards
spotify works with my zenith.
and it was abduleez1's post that made me remember i have a spotify subscription i am not using. i am on a family plan .it is mostly my kids who use spotify

for the past two years, most dollar denominated online purchases have been hit and miss
some are even a case of works today, not working tomorrow

i like video games
the following are platforms that you can buy vieo games licenses from

steam - the best but no regional pricing. used to be able to buy from there until sometime last year
epic games - not as goos as stem, but they had regional pricing - and i used to be able to buy from there
microsoft store - hit and miss and games you but from there are configured differently - however, they have regional pricing and IN NAIRA

summary even though games bought from ms store can be wonky, i usually buy games from them - because they are available and tehy are cheaper - though they also come with their own k-leg.

Kuda bank card works for YouTube premium.