"Why didn't you just use [insert your favorite library here]?"
-
Yes - but open source software tends to get hacked about to get a specific feature added, with no overall "target" in mind. Libraries tend to be a bit more focussed and intended to "do X" rather than "do most of X and some of Y because I could use that". Having said that, I do use OS apps: Freemake Video Converter, Handbrake, and Libre Office for example. But Gimp I don't like - I pay money to Corel instead ( :sob: ).
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
My question is what makes you think I know about every library of code that might fill a particular need? Or that it fills MY need? Or that I would rather deal with someone else's bug-ridden code rather than my OWN bug-ridden code? People are really funny. Of course, I could just be too old-school... Maybe it's time to retire...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013People like to show off. For me a library is non-intrusive well documented collection of code that is designed to solve a single generalization of a common problem. Unfortunately, a lot of libraries are just out of idea collection of random advanced code collected from random application that solves author's issues, namely "your application should look like mine application, otherwise you have the wrong idea".
-
glennPattonInThePUB wrote:
bailing wire
When I grew up, we only used bailing twine, not wire... Then, working in a pulp and paper facility, the pulp bails were held together with wire, so I then understood how it was used. Still prefer the twine, though. We'd gather it, tie them end-to-end, get three lengths and braid them to make rope.
When I was growing up, it was No. 8 fencing wire. (NZ has a lot of wire fences) It's just on the edge of being bendable by hand and then use a tool for final tightening. Since it was always on hand, you'd use it to make makeshift repairs from saddles to tractors, as gate latches, snip and sharpen to use as nails, large loop as a tow rope, loop and hang slaughtered sheep on a tree, staple a snapped fanbelt back together...and that's just the things off the top of my head.
-
My experience there was different, as I went from C++ to Java for a bit. C# was like a breath of fresh air, and LINQ sealed it for me. These things have spoiled me; going back and working in C++ for anything past low-level protocol work feels like a drag. So...yeah. About 7 out of 10 (LINQ solidified that for me).
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
I used to use C++ MFC for everything but when it became merged with .Net I moved on to C#. I still feel a little nostalgic but I seem to have forgotten almost everything I learned. Oh well...
We're philosophical about power outages here. A.C. come, A.C. go.
-
glennPattonInThePUB wrote:
spit & bailing wire
That's real old school. :laugh:
It was broke, so I fixed it.
Vines and sticks is REAL old school.
-
My question is what makes you think I know about every library of code that might fill a particular need? Or that it fills MY need? Or that I would rather deal with someone else's bug-ridden code rather than my OWN bug-ridden code? People are really funny. Of course, I could just be too old-school... Maybe it's time to retire...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Your question is one of the first signs of realistic thinking in the software profession I have seen in quite a long time. You are quite correct to ask how this or that framework or paradigm will satisfy the requirements you have for a particular project. The majority of the freely available, open source frameworks, no matter the targeted platform are the results of agendas seen by the developers as universal. This may be from experiences they have had while working on other projects, books they may have read, lectures they may have attended, promotions by colleagues, or some combination of the aforementioned. This is not to say that such frameworks are bad; just often limited in what they can provide. As a much older software engineer I see the current rush for new tools, paradigms, and frameworks as a sense of floundering within the profession as even vendors in the Microsoft Community try to promote the latest "silver bullet" to everyone. Interestingly enough, the Java Community does not seem to suffer these same issues to the same extent. If you review the "jaxEnter" community site you will note that much of what is presented are refinements to existing and older technologies that work quite well for their needs. One area where Java developers have excelled at is with the development of the web with the MVC paradigm. This is because this was always the way that Java web applications were developed. However, you also have to understand that the Java Community also grew out of academia and scientific areas where Microsoft was more of a "developer's" vendor from the start. Currently, our side of the fence is littered with tools, frameworks, and paradigms all claiming to be the best and right way to do something. If that is the case how did we accomplish anything back in the 1990s or the early 2000s when such offerings were not really available? What we did was simply use sound concepts to built applications with the basic tools we had. And we did quite well at it. Your question brings up another question then. Would it may be better to return to those basic techniques and skip all the hype? You may find coding much easier, more enjoyable, and less constrained by the limitations of the current psychological pressures to develop in certain ways. I never moved on with the younger crowd when it came to technologies. I still program the way I have always done and with few defects in my work, practically none of which ever make it into production releases. The next time you have
-
My question is what makes you think I know about every library of code that might fill a particular need? Or that it fills MY need? Or that I would rather deal with someone else's bug-ridden code rather than my OWN bug-ridden code? People are really funny. Of course, I could just be too old-school... Maybe it's time to retire...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013For this very reason, I am so happy with the GitHub era. Recently, when I have needed a library, I have found via NuGet and it's source was on GitHub. On a few occasions the library might be buggy. If it is on GitHub, I fork it, fix it, request a pull request. If they don't pull my change, no matter, because I have my own GitHub repo. I can move on with life.
-
My question is what makes you think I know about every library of code that might fill a particular need? Or that it fills MY need? Or that I would rather deal with someone else's bug-ridden code rather than my OWN bug-ridden code? People are really funny. Of course, I could just be too old-school... Maybe it's time to retire...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Ah, it's nice to be the firmware department where I work. Nobody pushing of the latest framework, language, etc. Just plain old C/C++ and an IDE for me. And the only libraries are the ones I've developed over 40+ years of embedded development and the standard C/C++ libraries.
-
Your question is one of the first signs of realistic thinking in the software profession I have seen in quite a long time. You are quite correct to ask how this or that framework or paradigm will satisfy the requirements you have for a particular project. The majority of the freely available, open source frameworks, no matter the targeted platform are the results of agendas seen by the developers as universal. This may be from experiences they have had while working on other projects, books they may have read, lectures they may have attended, promotions by colleagues, or some combination of the aforementioned. This is not to say that such frameworks are bad; just often limited in what they can provide. As a much older software engineer I see the current rush for new tools, paradigms, and frameworks as a sense of floundering within the profession as even vendors in the Microsoft Community try to promote the latest "silver bullet" to everyone. Interestingly enough, the Java Community does not seem to suffer these same issues to the same extent. If you review the "jaxEnter" community site you will note that much of what is presented are refinements to existing and older technologies that work quite well for their needs. One area where Java developers have excelled at is with the development of the web with the MVC paradigm. This is because this was always the way that Java web applications were developed. However, you also have to understand that the Java Community also grew out of academia and scientific areas where Microsoft was more of a "developer's" vendor from the start. Currently, our side of the fence is littered with tools, frameworks, and paradigms all claiming to be the best and right way to do something. If that is the case how did we accomplish anything back in the 1990s or the early 2000s when such offerings were not really available? What we did was simply use sound concepts to built applications with the basic tools we had. And we did quite well at it. Your question brings up another question then. Would it may be better to return to those basic techniques and skip all the hype? You may find coding much easier, more enjoyable, and less constrained by the limitations of the current psychological pressures to develop in certain ways. I never moved on with the younger crowd when it came to technologies. I still program the way I have always done and with few defects in my work, practically none of which ever make it into production releases. The next time you have
Well said!
-
My question is what makes you think I know about every library of code that might fill a particular need? Or that it fills MY need? Or that I would rather deal with someone else's bug-ridden code rather than my OWN bug-ridden code? People are really funny. Of course, I could just be too old-school... Maybe it's time to retire...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
