วีดีโอ

Good luck in your journey!

@FrontendRoad but I was interested in function component not the old class base stuff in React

I've updated in the following videos :) and do not worry, I use hooks and modern React in the videos

No, as I focused on the programming logic and not interface/UX, I didn't implement a drag and drop. Maybe a small challenge for those who followed along? 😁

I'd love to do that, it's great idea, thank you!

No networking/matchmaking planned to be honest, because the idea of the project is to focus on programming logic. However, the CPU component, I have to say I'd very much wish to do so, it's quite a nice suggestion, but I think this deserves a project of its own, specially as the series is already quite big (although nearing the end of it).

@@FrontendRoad Got it. Hopefully you'll dive into those in another series. Ever thought about building the AI opponent on top of this current project? I think I'd be interesting to see a new feature like that get added to this already existing base.

Thank you! 😊

Thank you for the support!

Good luck on your learning journey!

Good luck with your course!

@@FrontendRoad thank you brother 🙂

Thank you! Will do!

So glad it's been helping you! Thank you very much for the support!

Much appreciated! I don't have much experience with Python, so my advice for framework would be flawed unfortunately. However, what I would do is pick a framework only for the visual parts of it - be it desktop (like Flask) or web based (like Django) - and write in full the logic of the app by yourself. The purpose here is to practice the programming logic, if you would like to develop a real world chess application, then you should use one of the many already created chess engines for it. In summary, don't focus about the framework, but focus on writing the logic yourself :)

Thank you! Will do!

Thank you so much for the support! I can't the precise number yet, as I didn't finish editing all of them, but the full series spans around 10 more videos, the next 4-5 ones should cover most of the chess application, and then we are going for the weird movements (like castling, en passant, etc) and some refactor.

@@FrontendRoad superb!Will be eagerly waiting.

Yes, exactly. Although you could access the value via vanilla JS, for 99,9% of the cases you don't want to do that.

@FrontendRoad I'm trying to understand why I should use useRef, because I don't find it that useful, I understand that you access elements and that it doesn't cause re-renders. Other than that what can I use it for? Internet says animations but I don't know...

Overall you won't use that much. Overall I just use it whenever I can't do something easily with the other hooks. For example the focus function in this video. Sometimes when you use 3rd party libraries you will need it to reference the element. You could also use for fields in the form, because you can get the values only once on submit, without re-rendering all the time due to useState hook. Several examples, but the truth is: You use it when you need it, and you will notice when the moment comes

Nice!! Wish you success in building your app (and your chess matches!)

@FrontendRoad not me. I am just a viewer. Anyway, will take a look. Tks~

Thank you very much for the support! I try my best to explain the thinking process behind the decisions

That's great to hear! Part 2 is coming tomorrow!

Thank you!! 😊

Oops 😶😶

Also a good answer 😅

Glad to help! 😁

I feel you, it's definitely not easy. Some codebases can be extremely frustrating to work on 😵‍💫😵‍💫

It's a pleasure to read this and know I could contribute a bit with your dev journey! Wish you all the best 🙌

Indeed, I used the wrong terminology in the video. Well spotted! Also, it was well spotted that I'm trying to teach others, even if I make mistakes 😉

No, it's not the same. That's the magic of clamp with vw, it won't happen on specific screen sizes, but all of them. That's the reason we use vw, we are setting a font size relative to the screen size. How the conversion from vw to px happens is a topic for another video 😆, but that's the main idea. Is it clear?

@FrontendRoad I see, this is a more dynamic way to do the scaling. Fair enough. I'll look forward to that video then. St the moment the numbers seem kinda arbitrary.

You are right! I'll keep this in mind for the next videos!

Yes, let's say it had its peculiarities 😅

There are 2 scenarios here then: First if the item is duplicated in your data and you don't want/can't clean it. Second if you want to show any item more than once, even if it's not duplicated. In either case, the best solution would be to generate a random ID for each element you want to show, using libraries like uuid, for example.

@@FrontendRoad yeah Thanks for the response..

Hello! I'm using Atom One Dark for this video :)

Every library/framework has it's quirks, unfortunately React is no exception. If you don't mind me asking, which framework you prefer to work with?

That's good! Hope that the video helped you and maybe you will apply this in the future 😁

Totally understandable. I know some other developers who also are not a big fan of ternary operators. I, myself, quite like them as long as they are not nested. For this particular example, I think 2 returns are a bit overkill, but in a more complex component with other logic, it can be a good solution indeed :)

@@FrontendRoad I had similar issues in the past, I personally like to see what is new on the language and use it. But the newcomer on the language will have the basics (when it have it), so the simpler the code, the easier it is to maintain. Regarding the ternary, they are evil. It starts with a single ternary, a bad code review and you have a nested ternary, the next person that will iterate on the code will not even question and append another ternary option there, and the cycle repeats. Seen this too often to be good.

@@ShinSpiegel I can understand where you are coming from. That's why I think it's so important to have a good pipeline and branch protections in place, with tools like Sonarqube running and preventing any bad code (for example nested ternaries) from going into the default/main branch.

@@FrontendRoad Agreed, but when it's Friday, the regular dev just wants to push the code, things get disabled "because we need to push". So I work on the other side, avoid this in the first place.

​@@ShinSpiegeljust because you don't know how to use ternary operators does not mean that they are bad 😂

Yes, precisely. As I mentioned, this happens in other programming languages as well, however I didn't mention IEEE 754, so thanks for adding that! :)

I'm currently preparing some exciting content to allow you to go from complete noob to your first job as a developer. So stay tuned :)

You know the idea of such video is to bring clarification on a specific topic, right? I'm not showing any real world application code here