- This topic has 12 replies, 6 voices, and was last updated 16 years, 3 months ago by
.
-
Posts
-
Yahoo! Messenger – Chat, Instant message, SMS, PC Calls and More
Scroll to the bottom of that page for a list of the international versions of YM.
@gt8ost4l 230302 wrote:
thats not what i meant i meant lik what programming languages
Probably mostly C++, why does it matter?
@gt8ost4l 230317 wrote:
cause i wanna design my own messenger and i dont know what languages to start from
Any language will do, but I think you are quite a way off from building an IM client if you don’t know one language or another already.
I’d suggest going to your local library and getting an intro book to programming.
@gt8ost4l 230321 wrote:
i dont need an intro book to programming i know the names but i dont know which one to start from
Right, and perhaps an introduction to programming would teach something like that, as well as the constructs and concepts that will apply to every language.
But no, you don’t need that, you just need someone to tell you what Yahoo messenger is written in, and I told you, C++. With this one tidbit you are now capable of writing your own messenger. Reverse-engineering the Y! protocol, understanding and implementing socket communications, encryption and handling Windows UI messages is the easy part.
@VvWolverinevV 230328 wrote:
Man, take it easy, David. Does it hurt you if he wants to try to write his own client?
It hurts the industry if he tries, and fails and gives up forever. Anyone, Everyone is better off reading an intro book before diving in. There is far more to writing an IM client than (perhaps) meets the eye, no amount of Googling to figure out each component as you arrive at the time to implement it will yield a successful and usable piece of software. I’ve been down that road, I’ve seen others go down that road, it’s not worth it. Read a book and start out right. 🙂
From designing my own website – I agree with David. I can’t tell you how many times I’ve revised and redone, because I learned on my own, and then found better ways of doing things. I found this mostly from reading after the fact. It’s not only a big time waster, but often difficult to resdesign anything after the fact.
In any programming (and it’s been many years since I’ve done any) planning is key. Outlining your objectives for each module, and deciding how they will be implemented, as well as possible predictions (althougth the impossible to predict ones crop up unexpectedly) on how they will interact and affect one another are very important. Having a roadmap is key or one will flounder around aimlessly ending up with only a half functional product.
There is no harm in trying to write one’s own program (instant messenger or anything else for that matter). Indeed some of the best programs out there have sprung from someone who was not satisfied from the existing software. But I think what David is saying is not to necessarily meant to be discouraging, but simply not to choose anything (programming language or otherwise) based on what’s out there already. Take the time to look at resources available, and make the best determination for the level of programming skill as to what will work best for the programmer.
Where programming skill is lacking – it’s better to take the time and and brush up or learn new processes ahead of time. Practice is what leads to learning. If one doesn’t have all the basics in place, debugging is difficult if not impossible, and you end up with a product full of band-aids to fix the problems. This does not result in quality product.
Take the time to read, learn, learn more and plan more. Then attack the final objective. It’s more likely to return a personally gratifying result and a higher quality software program.
Just my personal opinion…take it or leave it.
Writing a chat/im client is not the hardest thing to do but what makes it work is simply these points.
1. Your work will always been in beta/unstable release state because it depends on a service you cannot control.
2. It’s time consuming to keep up with a corporation and their tweaks and changes.
3. You will have a userbase to please and will have to please a good many people, will you be able?
4. Yahoo are slowly moving to encrypting their files and source and will change logins and captcha authentications on a regular basis, you can’t depend on login dll’s (dynamic link libaries) to handle your login and other stuff.
5. Are you willing to have an unstable application out there that could leave users exploitable to various attacks because you made an flimsy attempt at a software on a learning basis?
..If you wanna learn i suggest working on a client/im on your own and finish it on your own and test it on your own and verify it works 100%, but i can guarantee you will get bored way before that.
- You must be logged in to reply to this topic.