The only thing I know of Star Control are the ripped mods. I've been listening to those for many years without ever even playing the game. For some weird reason I never thought of even searching for the game. Hmmm, weird.
light is a radio source. Also you don't need a CCD to pick it up. You just need a tuned circuit and a dish. I don't see the advantages to this. You can focus microwaves as easily as light waves (and I believe that the higher frequency microwaves actually diffuse less than visible light).
The only reason their data is like this is because its London, where charge/unit time services are still everywhere. In America, where we already have unlimited internet people get it for the broadband and always on.
Hey dumb fuck, voxels are volume elements. You know, exactly what these scientists are trying to visualize. These points are voxels. This scientist didn't do anything original. He just discovered what has been around for many years now.
MP3s have an ID3 Tag right?? Thats an interface (although simplistically it would not be called an ID3 tag). You can search on Artist, Title, anything in there. This concerns both programmers and users alike. A user is not oblivious to certain properties associated with the files they use. The interfaces are intrinsic, they require no code they only define a set of properties which can be used to identify an object. That is all in this case.
sorry DOS doesn't win on the prompt issue. In order to get the path to the left you have to enter in the command PROMPT $P$G. I remember doing that back when I was a little one.
OK, I'm not saying objects having names is a bad thing. Essentially I'm saying the current path mechanism can sometimes be quite limited read my above comments on the ability to add names to Objects. Mainly I'm just saying that we should classify documents instead of creating an adhoc folder hierarchy. Again read my above comments. And as far as the task oriented view goes. Different tasks can be done with different programs. Every object that implements the required task interface can be enumerated if need be. And the applicability of the "text editor" in all the areas you mention above just shows the systems lack of common interchangeable effective text editing objects (I've mentioned in another article a while ago that the most ideal computing environment would be to get rid of programs all together and just have a large set of interconnectable objects.). Although, one of the tasks could very easily be query objects. If you just want to do a bunch of "of the moment" operations. Also, this is very data oriented, it essentially turns every file into an object with properties, as in you just deserialize it and go (ideally). Read above, I'm making a prototype client using java and Swing. Rest assured I'll post something on slashdot when its runnable to the point at which people will at least partially understand what I'm getting at.
I understand what you are saying, but I think you misunderstood me slightly. I have nothing against names, and the ability to supply named properties and values would accomplish the same point (Especially if there are predefined views or Collections of objects). Also, I left out of my above posting that, everything is classified to the extreme, and that interface names would take the place of folders. For example: Say you have a set of images that you want to associate with project4. Well instead of making a new folder to store it all in, you define a couple of interfaces (provided with a gui method) such as a Project4 interface (which could extend other interfaces). Then when you save the images, you don't save them in a folder. You define which interfaces it implements besides its standard JPEGImage class or whatever its object classification (along with the other interfaces you associate with JPEGImage). After you define every interface it implements, you set all the values (there can be different frames for each interface, and some interfaces could be filled in automatically by the program). After its saved it would be a simple query to determine all of your Project4 files or just return a single object. And if you want you can set the default Object class to implement the NamedObject interface. Simple, easier and more powerful to query, multiple views of same data, more meaningfull names (doesn't have to be some crazy concocted name), can implement multiple interfaces and therefore it can be indexed more than one way (many more). Also, it forces you to conform to its method of organizing data which is more logical than being able to put multiple file types in a single folder, just make an interface and have everything in the project or whatever extend that interface. And it makes security a breeze by just giving every role and user on the computer their own interface name. I don't know about you, but this seems to me to be a far more powerful method of computing.
This could very well be implemented on top of any existing OS. I am making a prototype of it right now using java and Swing. Where there are different roles granted to different users. There are different tasks and objects which different users can access. It has a very small and simple set of interfaces which you implement to make a task (which is really just like a method on an object).
no technically win3.1 was an ms-dos frontend. win95 was the first partially 32-bit OS, and there is much that could be changed with GUIs.
For starters, get rid of the desktop and just get a big list of tasks. You don't want to have to hunt things down on a computer. You want to do things.
Second of all, we need to get off the file name bandwagon. What we really need is a searchable live indexing service. Such a service would, upon serialization (saving) of the files, store in an index all the properties of the file for later searching. This is far more intuitive than a file name. For instance say you have a powerpoint project which you are serializing, well low and behold thanks to this new OS you can now search on the indexed executive summary, the number of slides, any property of the object you are serializing, and if the system is really nice and extensible, you can supply name properties and values that are also indexed.
There should be a section on the tasks screen with your inbox (not just email but just tasks assigned to you), and multiple outboxes.
Eh, thats pretty much it. Mainly we just need to abandon this unnecessary attachment we have with file names, and our love of the desktop, and we need to embrace object stores, property based indexed search, and task oriented computing. All of these are getting closer and closer to being there, but nobody seems to want to just make this simple but most effective system.
These things will be used for mainly a factory or lab based environment where:
1) workers have to move between stations but still need access to order information, and need to fill out order processing forms
2) workers do not have room for a desktop computer or need mobility (i.e. supervisors running periodic checkups on workers etc.)
3) situations that only require thin clients (web browser) to perform all data handling duties
4) also you do not need to design where individual computers go. Departments just check one out, and go with it (of course this also raises the issue of security but that can be handled quite simply)
As far as the ability to read human input goes. I think that is not quite as big an issue, as I would think with these devices it would primarily be used for checking status or updating status of certain items (which would probably be done with a pull down list). I personally am very excited about these tablet PCs and am writing software to take advantage of them in the lab in which I work. It should make things quite a bit more efficient, and it could potentially eliminate the need for paper (I know we've all heard that before, but this has the actual potential for doing it). And it enables instant transfer of jobs between departments (if the software is designed effectively). Sure a lot of this could be handled by laptops, but you have to be sitting to use those. And in lab based environments, people are not going to be writing prose at their station, they are going to be checking things off and selecting from lists different options. Anyways, I can't wait to get some of these babies in. This is what I've been telling management will be happening for a long time, and now the time has finally come.
Driver Management and configuration
Cross-application integration and interoperation(OLE)
fewer bugs in the window manager
thats all I feel like listing right now
The poster of this article is a fucking moron. It does not "in fact" hold every memory we ever fucking had. This stupid son of a bitch poster made me waste ten minutes of my fucking time reading about a stupid fucking database, which does not even do what the article implies. Mod this fucking piece of shit down -5 (BullShit).
Slashdot Mirror
Yeah but celsius is a scale using water temperatures under 1 atmosphere of pressure. I think the point is to disassociate the earth from the units.
CISC
Thats easy. Set up a SOAP interface in each location and let them adapt to that. No problem.
The only thing I know of Star Control are the ripped mods. I've been listening to those for many years without ever even playing the game. For some weird reason I never thought of even searching for the game. Hmmm, weird.
Why isn't Duke Nukem Forever in there? I mean, come on.
light is a radio source. Also you don't need a CCD to pick it up. You just need a tuned circuit and a dish. I don't see the advantages to this. You can focus microwaves as easily as light waves (and I believe that the higher frequency microwaves actually diffuse less than visible light).
The only reason their data is like this is because its London, where charge/unit time services are still everywhere. In America, where we already have unlimited internet people get it for the broadband and always on.
Why doesn't this guy just realize that you can do just about anything with 'bash' scripts and 'at'. Its fun.
Hey dumb fuck, voxels are volume elements. You know, exactly what these scientists are trying to visualize. These points are voxels. This scientist didn't do anything original. He just discovered what has been around for many years now.
MP3s have an ID3 Tag right?? Thats an interface (although simplistically it would not be called an ID3 tag). You can search on Artist, Title, anything in there. This concerns both programmers and users alike. A user is not oblivious to certain properties associated with the files they use. The interfaces are intrinsic, they require no code they only define a set of properties which can be used to identify an object. That is all in this case.
sorry DOS doesn't win on the prompt issue. In order to get the path to the left you have to enter in the command PROMPT $P$G. I remember doing that back when I was a little one.
OK, I'm not saying objects having names is a bad thing. Essentially I'm saying the current path mechanism can sometimes be quite limited read my above comments on the ability to add names to Objects. Mainly I'm just saying that we should classify documents instead of creating an adhoc folder hierarchy. Again read my above comments. And as far as the task oriented view goes. Different tasks can be done with different programs. Every object that implements the required task interface can be enumerated if need be. And the applicability of the "text editor" in all the areas you mention above just shows the systems lack of common interchangeable effective text editing objects (I've mentioned in another article a while ago that the most ideal computing environment would be to get rid of programs all together and just have a large set of interconnectable objects.). Although, one of the tasks could very easily be query objects. If you just want to do a bunch of "of the moment" operations. Also, this is very data oriented, it essentially turns every file into an object with properties, as in you just deserialize it and go (ideally). Read above, I'm making a prototype client using java and Swing. Rest assured I'll post something on slashdot when its runnable to the point at which people will at least partially understand what I'm getting at.
I understand what you are saying, but I think you misunderstood me slightly. I have nothing against names, and the ability to supply named properties and values would accomplish the same point (Especially if there are predefined views or Collections of objects). Also, I left out of my above posting that, everything is classified to the extreme, and that interface names would take the place of folders. For example: Say you have a set of images that you want to associate with project4. Well instead of making a new folder to store it all in, you define a couple of interfaces (provided with a gui method) such as a Project4 interface (which could extend other interfaces). Then when you save the images, you don't save them in a folder. You define which interfaces it implements besides its standard JPEGImage class or whatever its object classification (along with the other interfaces you associate with JPEGImage). After you define every interface it implements, you set all the values (there can be different frames for each interface, and some interfaces could be filled in automatically by the program). After its saved it would be a simple query to determine all of your Project4 files or just return a single object. And if you want you can set the default Object class to implement the NamedObject interface. Simple, easier and more powerful to query, multiple views of same data, more meaningfull names (doesn't have to be some crazy concocted name), can implement multiple interfaces and therefore it can be indexed more than one way (many more). Also, it forces you to conform to its method of organizing data which is more logical than being able to put multiple file types in a single folder, just make an interface and have everything in the project or whatever extend that interface. And it makes security a breeze by just giving every role and user on the computer their own interface name. I don't know about you, but this seems to me to be a far more powerful method of computing.
This could very well be implemented on top of any existing OS. I am making a prototype of it right now using java and Swing. Where there are different roles granted to different users. There are different tasks and objects which different users can access. It has a very small and simple set of interfaces which you implement to make a task (which is really just like a method on an object).
I meant to say '...you can supply named properties and values that are also indexed...'. Sorry for the confusion.
no technically win3.1 was an ms-dos frontend. win95 was the first partially 32-bit OS, and there is much that could be changed with GUIs.
For starters, get rid of the desktop and just get a big list of tasks. You don't want to have to hunt things down on a computer. You want to do things.
Second of all, we need to get off the file name bandwagon. What we really need is a searchable live indexing service. Such a service would, upon serialization (saving) of the files, store in an index all the properties of the file for later searching. This is far more intuitive than a file name. For instance say you have a powerpoint project which you are serializing, well low and behold thanks to this new OS you can now search on the indexed executive summary, the number of slides, any property of the object you are serializing, and if the system is really nice and extensible, you can supply name properties and values that are also indexed.
There should be a section on the tasks screen with your inbox (not just email but just tasks assigned to you), and multiple outboxes.
Eh, thats pretty much it. Mainly we just need to abandon this unnecessary attachment we have with file names, and our love of the desktop, and we need to embrace object stores, property based indexed search, and task oriented computing. All of these are getting closer and closer to being there, but nobody seems to want to just make this simple but most effective system.
These things will be used for mainly a factory or lab based environment where:
1) workers have to move between stations but still need access to order information, and need to fill out order processing forms
2) workers do not have room for a desktop computer or need mobility (i.e. supervisors running periodic checkups on workers etc.)
3) situations that only require thin clients (web browser) to perform all data handling duties
4) also you do not need to design where individual computers go. Departments just check one out, and go with it (of course this also raises the issue of security but that can be handled quite simply)
As far as the ability to read human input goes. I think that is not quite as big an issue, as I would think with these devices it would primarily be used for checking status or updating status of certain items (which would probably be done with a pull down list). I personally am very excited about these tablet PCs and am writing software to take advantage of them in the lab in which I work. It should make things quite a bit more efficient, and it could potentially eliminate the need for paper (I know we've all heard that before, but this has the actual potential for doing it). And it enables instant transfer of jobs between departments (if the software is designed effectively). Sure a lot of this could be handled by laptops, but you have to be sitting to use those. And in lab based environments, people are not going to be writing prose at their station, they are going to be checking things off and selecting from lists different options. Anyways, I can't wait to get some of these babies in. This is what I've been telling management will be happening for a long time, and now the time has finally come.
Driver Management and configuration
Cross-application integration and interoperation(OLE)
fewer bugs in the window manager
thats all I feel like listing right now
There are far more advantages to businesses than there are for a lone person.
Its about time somebody wrote an audio output device driver for Windows which outputs to the HD. Thank you.
He has a patent on converting sequences into a mathematical model? I hate America. Is this freedom?
The poster of this article is a fucking moron. It does not "in fact" hold every memory we ever fucking had. This stupid son of a bitch poster made me waste ten minutes of my fucking time reading about a stupid fucking database, which does not even do what the article implies. Mod this fucking piece of shit down -5 (BullShit).
No, because while scooters looked stupid (and still do), the segway just looks gay as hell.
Mod this guy troll. Just kidding. He has a point, and the parent of the parent is one serious asshole.
Guess what, it is still a candidate recommendation. It has not been finalized and thus this this article is a completely redundant repost.