it is possible to both make a browser and a search engine. So TheKingAndLandR1 doesn't really know what he is talking about.

you wouldnt necessarily NEED more than a browser and search engine to achieve your goal, so I somewhat disagree with morbo.

The thing is, this is an incredibly huge undertaking. Making a browser can be done, but its a LOT of work. Something one guy buy himself doing in his own free time probably wont get done before he dies. You'd probably need a team of people.

Another problem is that without categories being self-registered into a universally accessible database (which is probably TheKing..'s suggestion) you will need to develop a system that crawls websites, and attempts to judge intent and category. This is not impossible, but it is even harder than building the browser from scratch (unless you are willing to take massive shortcuts which will destroy the quality of the results).

So the question is.. how much money would you throw at this? and how do you expect it to pay for itself if the extreme majority of people who are willing to spend money on these things don't care to leave Chrome?

gah, its gets a little semantic here. Not all engineers are programmers (like Mechanical Engineer, for example). and not all programmers are programmers depending on what you mean with that word.

For instance, there are jobs with an "engineer" title, which require in depth programming experience, but where you would not actually do the programming directly yourself, instead you sort of carve out the work for "lesser" programmers to type up.

There are also IT Engineers that do no programming at all. Some of these might do tasks related to networking or security.

But I would say that all software engineers are programmers, when using the word "programmer" to mean "they make programs" even if they aren't the ones directly typing it up themselves.

I do designing of systems and I do programming too.

I am a programmer and a system software engineer. Not all programmers are called engineers, but many are. The title depends on the work.

I don't actually have a completed degree. I have like all but 10 classes (9 geneds) finished of a CS degree, but then I just decided to quit school and begin working.

"Styleometry" has its limits. especially if you are heavily relying on stackoverflow code.

unfortunately its a rather large package and includes multiple file parts

thanks for the tip

building a generic .jar package for sending and receiving xml posts. basically, the way I program in java, if I want to include an internal jar, I have to renam all jars to zip, fuck with the build file, and combine all these files into a giant zip, recompress, rename to .jar, and wala it works.

however, I use the apache httpclient for xml posting, and one of the cases I use has some 1k class dependencies inside an inner jar.

now, here is the real cute thing, if my main project contains a jar which also contains a jar, I only have to do the whole .zip switcheroo with the top level jar, not all the inner jars.

So i plan on making a very generic XML poster that covers all my use cases and includes this giant library, packaging that into a jar, and then including that jar into a program that sets up a generic library for interacting with the server api, and then I package that server api interaction program into a jar which I am going to include in the application all of our employees actually use.

that way, whenever I want to change a feature in the server interacting bit, I dont have to repackage all 1000+ files, just the 20 or so involved in the api interaction + the jar that already contains all those apache libraries.

confusing, right? yeah, theres a dent in the wall about the size of my head.