- Oct 9, 2013
- 3,482
- 14,530
An IDE is also a Client, because you are accessing server data. In this case API. And my question was in regard to API. Hence, Client. The way I see is, we are both right. We just misunderstood each other.
I have been coding since 1997 as well.I have been using linux for I don't remember when.
You read your first AI book in 1998? Din't know you were such a big shot.![]()
No, an IDE is not a client.
Don't double down on your mistake here. Client/server architecture is a very specific thing.
A client has to belong to a server.
A web browser is an HTTP client because it pairs with an HTTP server.
An FTP client is a client because it pairs with an FTP server.
An IDE is an application that contains code editors, debuggers, compilers and more. Compilers are not clients.
An IDE can contain client frameworks to communicate with servers. It's also not really correct to say "acessing server data. In this case API". You use an API to retrieve data from a server, and that API is implemented over HTTP.
So the client portion you are saying an IDE is, would in fact be an HTTP client. An IDE is absolutely not an HTTP client.
Even if we ask chatgpt, who loves to agree with everything we ask it doesn't agree with this :-

P.S. Life is not MMORPG, that you think you are more skilled with age. A 15 year old kid will beat you at many things AI.
Sorry, but this is an utterly ridiculous statement.
I remember when I was 15, and my skill and experience back then was miniscule compared to what it was at 25, which is in turn miniscule compared to what it is today.
If what you said was true, companies would be hiring 15 year old kids over 30 year veterans.
Experience is a hard limiter in everything in life.
A pilot who has 15,000 hours is going to be significantly more skilled than a 15 year old who's had a few lessons, but is a genius.
Even a 15 year old with a 160 IQ is not going to be able to outperform me in dev. You cannot compensate for 30 years experience. It's A LOT LOT LOT. I was literally in the 90's doing the job of chatgpt by answering programming questions for people on a daily basis. It's one of the things I did to get good fast. Then add decades of writing code, building projects, working in teams and studying more on top of that. I have written several million lines of code in my life. I can craft designs and structure code in my head without writing anything down. This is not something I could do after 2 years of coding.
There's a reason companies hire senior engineers with 10 to 15+ years of experience and don't ask for teenager whiz kids.
Most of those engineering veterans were teenage whiz kids, but now have the experience to boot.
It's just ignorant to say a 15 year old kid is going to beat me at most things AI. I've come across so many coders in my time. I've never met a 15 year old that's at the level of a 15-20+ year dev, let alone 30 years.
Go check out this guy here - https://www.youtube.com/@InternetOfBugs
He's a 30 year industry veteran. 35 years in fact. There's no 15 year olds that are going to "beat him" in dev.
If you've really been in the industry since the 90's, you wouldn't even entertain that idea.
And to be fair, if you'd made the statement that an IDE was a client with me in 1996-1997, I'd have explained the difference back then. That's a very simple thing to confuse. You really shouldn't be mixing up terms like that if you understand client/server architecture, networking and the tcp/ip framework of protocols.
