Don't ad-block us - support your favorite websites. We have safe, unobstrusive, robotics related ads that you actually want to see - see here for more.
0 Members and 1 Guest are viewing this topic.
Many reasons, here's one - as you continued to program, you'd get tired of writing every detail and start replacing them with function calls. Then you'd get tied of looking at those functions cluttering up your code, you'd probably modularise them into other files hence you'd end up writing your own libraries.But, isnt' it easier if we're all using the same libraries? If lots of people are using them, more of the bugs will get spotted quicker. If a bug is fixed, everyone will benefit. You may not be using the code with the bug now but you might in future, hence you'll benefit, without even knowing it, from someone else having noticed that bug previously.We all benefit from using the same interface, I could use a squeezable furry dice mechanism to steer my car instead of a steering wheel, but if I did, you wouldn't be able to borrow my car! (plus I'd have terrible trouble when I wanted to sell it) There's a lot to be said for standard interfaces.
I'm sure there are multiple huge commands that webbotlib takes care of in one little tiny bit of code, I (in my very limited experience) however, have yet to find any.
I need a car to get to the shops. If I had to start off by building a car every time then I'd quickly get fed up and move to the city. So a library is just a 'tool' - just like the 'car'...Try writing your own code for something like the Blackfin camera (amongst other things!), or controlling 18 servos.