Oh my goodness, did they really write it in assembler? I always imagined they already used high-level languages at that time.
And nevertheless, the non-availability of multiplication or division is honestly the smallest problem when programming the 6502 in assembler. Using a decent macro assembler it does not take a lot of effort to implement these two instructions. What i personally collided more with where the awkward addressing techniques of the 6502, and, of course, the quite um... limited stack, and of course, having only 3 registers sucked. I liked the Z80 much more form a low-level viewpoint. But in never though about the absence of multiplication instructions as a bad thing, just a little training....
My laptop is rated at max. Power 45W, when i measured it it was approx 20W in normal operation (although i am not sure about the power adapter efficiency....) .
Yes, you are not alone - sadly. I dont like people intentionally meddling around with my computer without giving them my permission, in the same way as I do not appreciate that somebody breaks into my flat to fix damage that somebody else has done when breaking in.
The only way to handle this correctly is that a law is passwd which allows such things under well-defined circumstances (however i have no idea to to set the boundaries).
it is especially annoying that nowadays there are a lot of "circular icons, where some kind of arrow or direction indicator hides a letter or a circular sign which carries a letter". These take a lot of space, and force you to remember the color which is which if you wan to click fast.
is that all the idiotic designers think GUIs are a playground. From 1988 to 1995 Icons changed only marginally with time, but since the web-culture has spoiled the idea of consistent, clean UIs, i prefer to turn on the icon name whereever possible.
I am a big friend of strictly moderated e-mail lists. There is no reason everybody in an institution talks to everybody..... i would more say it is enough if everybody can talk to anybody. If a date of something if misspelled (like, last year, weekday vs. date, etc.), then it is better if only the original sender send updated information. I hate these idiots who point such a thing out onto the mailing list. This may be ok for groups up to 10persons, but not for more.
a) Maintaining large list by copying all recipients into the hrader is a fucked up idea at best (because there is no way this list will be kept updated), and a informaiton leak at worst (because somebody eralier on a non-updated list may get information which he should not get - e.g. former employees). Why do governmental institutions still us it?
b) Why in the world do modern e-mail clients still allow reply all to hundreds of recipients without an additional safety question. I would expect my program would warn me before sending an emails to thousand people.
In *every* Job work can be endless. In my experience (as a scientist) good management can break the endless task into sub-tasks which are doable in a reasonable time, while bad management will do the opposite. That is, shifting the responsibility for the schedule of the whole project to the lower levels. This is *extremely* stupid. If you manage a project, it is your responsibility to stay within costs, time, and promised goals. Over-hours count as costs. If not directly, then indirectly because it may drive your best workers away. Or the person who worked 40hours overtime/week the last year (good luck with replacing him/her).
Other reasons i have seen for stress and frustration: bad information system infrastructure. For example everybody handle backups himself. That is plainly stupid. I have worked as sysadmin for a long time. And there are few things i very willingly leave to be done by experts, and one of them is backup/archiving (the other one is the mailserver...). Distributing these functions makes sese fro mthe viewpoint of your boss (since assuming you may go doe not leave them woth their pants down. They at least can sent you a mail, and from your viewpoint (you dont take additional stress if things go wrong just wo restore your capability to retrieve backups needed for recovery or e-mail to communicate). I figured that accepting certain troubles is sometimes worth it if you reduce the responsibility of a single person/admin/programmer. This includes bad code.
Last but not least: If you are responsible you have to live with the coworkers/programmers you are given. If you have a person writing not so fancy code, let him/her work in a productive way (e.g. i had a coworker who wrote code i would call uninspired at best, and a if-then-else hell at worst, but well documented - but there where tasks when exactly that was needed - e.g. for writing instrument drivers). It is not good to force newbies in OOP to design a base class and the interfaces in a framework. This will cause additional night-shifts (and headache to everybody).
On the other hand, i remind whhat i love about my palm m105
-ran on 2AAA batteries for several weeks (if uses at phone book/clock/calendar). The baterries were available at the end of the world and it ran on rechargeable. -monochrome display was readable in sunlight and had soft eye-friendly illumination -the clock/calendar worked and did not crash (i had a z31 after that and found crashes in very basic functions) -synchronization was easy -memory was enough to have one or two dictionaries installed
I wonder how why palm wants to compete in the market where they are trying to compete now. would they produce a m105 with an e-paper display and in a more flat case and with flash, i would buy it without thinking twice. Would they integrate on of the power-saving an somple models with a few basic funcion (implemented decently) like email, simple web (no, youtube is not needed-and neither is flash) and UMTS (i need that since i live in Japan), i also would buy it.
I left to be a physicist before the UIDs hit the 65000..... (:-)
I was kidding (about the UID beeing below 65000). There where some troubles with that, but the head of the administrators was extremely competent about first testing things for a year or two on a few boxes in his room before rolling them out, so he spotted the problems beforehand and handled them appropriately - so i did not see any of these problems, but i was told how to handle it (i was only co-responsible for the web-server, which also served user homes, deeply buried in my memory i remember there was something....).
And about the config files well i think the usual solaris customers dont want to touch anything without need, which means that 'superior' for them means that their specialised tcl script they used the last 10years stops working (or worse: behaves strange).
Yes, more and more scientists will support this because from the crumbles which fall off the plate in such projects you can live very well scientifically.
b) its not only political. it's real. If you cant hire ad fire for some reason, but haxe a fixed staff, you dont have the choice but to reeducate them (e.g. 15 Persons, 5000 Euro/Person Reeduaction costs). I worked in the computing center of my university, and there i think they i would recommend to buy sun machines als long as they can, because their not so simple network is running without trouble (only the part of it settling on solaris, the novell/nt/linux group is such a mess its incredible), which the personal and infrastructure and under the funding/infrastructure boundaries they have. Causing out-times for services which are used by 20000 students and a few thousand employes, some hospitals and associated research centers sound like a thing to avoid. And no, there failing drives need to be replaced (some Admin has to go there and touch it) in this case.
a) i said "consider" solaris. this somehow matches your "most industrial use". Usually i would end up with linux
b) "is enough" makes it sound like linux is inferior or cheap. Nothing in my posts suggested this. To put it in clearer words: the only application for a newly installed solaris i could imagine is file serving/server for SUNs thin clients. For certain applications in certain environments the *overall* (including administration and education) cost will be lower for solaris. I am thinking right now about the consistency of the documentation and overall platform stability. In both of these SUN has done a good job. Not needing to re-educate you admin may easily bridge some minor difference in price!
c) "cheap disk" is maybe not what you want in some not "most industrial applications"
I was referring to solaris as an OS. I am aware that the quality of hardware which SUN delivers in certain segments of the market offers - contradicting nostalic memories - no advantage over your approach. I am also aware that SUNs hardware was not as good as the lore of the bearded guys sometimes says (e.g. we had a lot of pizza-boxes which died strange hardware deaths and the monitors where crap). I would agree to say that if you want good hardware for and good price, you will have an easier time with not buying SUN and buying two times as much. If the purpos of this machine would be *only* file-serving, i would consider solaris as os.
Sun going out of business? I have heard that before, regularly. One difference to SGI however is that SGI had a single market which borke away. Sun quite diverse products, which fit together. And lets face it: If i want a trouble-free file server, i probably would buy Solaris. So i would guess that they will find some investor in case they run out of cash.
Slashdot Mirror
Oh my goodness, did they really write it in assembler? I always imagined they already used high-level languages at that time.
And nevertheless, the non-availability of multiplication or division is honestly the smallest problem when programming the 6502 in assembler. Using a decent macro assembler it does not take a lot of effort to implement these two instructions. What i personally collided more with where the awkward addressing techniques of the 6502, and, of course, the quite um... limited stack, and of course, having only 3 registers sucked. I liked the Z80 much more form a low-level viewpoint. But in never though about the absence of multiplication instructions as a bad thing, just a little training....
is having a way to handle error systematically and appreciate customer reports about errors.
Sometimes when errors are reported, they are not fixed until 4 program versions later.
My laptop is rated at max. Power 45W, when i measured it it was approx 20W in normal operation (although i am not sure about the power adapter efficiency....) .
Yes, you are not alone - sadly. I dont like people intentionally meddling around with my computer without giving them my permission, in the same way as I do not appreciate that somebody breaks into my flat to fix damage that somebody else has done when breaking in.
The only way to handle this correctly is that a law is passwd which allows such things under well-defined circumstances (however i have no idea to to set the boundaries).
E.g. click on the preinstalled dearch bar in firefox.
creative commons, amazon, ask, google have a dominant circle-like feature
It allows the parts of th companies actually producing something to be decoupled of the last attempts to somehow win some trial somewhere.
a small additional note:
it is especially annoying that nowadays there are a lot of "circular icons, where some kind of arrow or direction indicator hides a letter or a circular sign which carries a letter". These take a lot of space, and force you to remember the color which is which if you wan to click fast.
is that all the idiotic designers think GUIs are a playground. From 1988 to 1995 Icons changed only marginally with time, but since the web-culture has spoiled the idea of consistent, clean UIs, i prefer to turn on the icon name whereever possible.
Combine this with a force feedback in the mouse button, 1g pressure/10recipients....
Realy?
I am a big friend of strictly moderated e-mail lists. There is no reason everybody in an institution talks to everybody..... i would more say it is enough if everybody can talk to anybody. If a date of something if misspelled (like, last year, weekday vs. date, etc.), then it is better if only the original sender send updated information. I hate these idiots who point such a thing out onto the mailing list. This may be ok for groups up to 10persons, but not for more.
a) Maintaining large list by copying all recipients into the hrader is a fucked up idea at best (because there is no way this list will be kept updated), and a informaiton leak at worst (because somebody eralier on a non-updated list may get information which he should not get - e.g. former employees). Why do governmental institutions still us it?
b) Why in the world do modern e-mail clients still allow reply all to hundreds of recipients without an additional safety question. I would expect my program would warn me before sending an emails to thousand people.
In *every* Job work can be endless. In my experience (as a scientist) good management can break the endless task into sub-tasks which are doable in a reasonable time, while bad management will do the opposite. That is, shifting the responsibility for the schedule of the whole project to the lower levels. This is *extremely* stupid. If you manage a project, it is your responsibility to stay within costs, time, and promised goals. Over-hours count as costs. If not directly, then indirectly because it may drive your best workers away. Or the person who worked 40hours overtime/week the last year (good luck with replacing him/her).
Other reasons i have seen for stress and frustration: bad information system infrastructure. For example everybody handle backups himself. That is plainly stupid. I have worked as sysadmin for a long time. And there are few things i very willingly leave to be done by experts, and one of them is backup/archiving (the other one is the mailserver...). Distributing these functions makes sese fro mthe viewpoint of your boss (since assuming you may go doe not leave them woth their pants down. They at least can sent you a mail, and from your viewpoint (you dont take additional stress if things go wrong just wo restore your capability to retrieve backups needed for recovery or e-mail to communicate). I figured that accepting certain troubles is sometimes worth it if you reduce the responsibility of a single person/admin/programmer. This includes bad code.
Last but not least: If you are responsible you have to live with the coworkers/programmers you are given. If you have a person writing not so fancy code, let him/her work in a productive way (e.g. i had a coworker who wrote code i would call uninspired at best, and a if-then-else hell at worst, but well documented - but there where tasks when exactly that was needed - e.g. for writing instrument drivers). It is not good to force newbies in OOP to design a base class and the interfaces in a framework. This will cause additional night-shifts (and headache to everybody).
Symbian os still outsells ihpones grossly.
On the other hand, i remind whhat i love about my palm m105
-ran on 2AAA batteries for several weeks (if uses at phone book/clock/calendar). The baterries were available at the end of the world and it ran on rechargeable.
-monochrome display was readable in sunlight and had soft eye-friendly illumination
-the clock/calendar worked and did not crash (i had a z31 after that and found crashes in very basic functions)
-synchronization was easy
-memory was enough to have one or two dictionaries installed
I wonder how why palm wants to compete in the market where they are trying to compete now. would they produce a m105 with an e-paper display and in a more flat case and with flash, i would buy it without thinking twice. Would they integrate on of the power-saving an somple models with a few basic funcion (implemented decently) like email, simple web (no, youtube is not needed-and neither is flash) and UMTS (i need that since i live in Japan), i also would buy it.
and how far our security in accessing remote system actually is *today*, i become pessimistic about software development.
The point is S is popular, but expensive. R gets some popularity from that. One could hope also S is made free at some point.
And i also dont know why it is called R.... maybe because sounds starting with a vowel sound better.....
I always believed the color of lights in the photo labs has something to do with the insensitivity of the photo paper.
I left to be a physicist before the UIDs hit the 65000..... (:-)
I was kidding (about the UID beeing below 65000). There where some troubles with that, but the head of the administrators was extremely competent about first testing things for a year or two on a few boxes in his room before rolling them out, so he spotted the problems beforehand and handled them appropriately - so i did not see any of these problems, but i was told how to handle it (i was only co-responsible for the web-server, which also served user homes, deeply buried in my memory i remember there was something....).
And about the config files well i think the usual solaris customers dont want to touch anything without need, which means that 'superior' for them means that their specialised tcl script they used the last 10years stops working (or worse: behaves strange).
Yes, more and more scientists will support this because from the crumbles which fall off the plate in such projects you can live very well scientifically.
In my opinion, the biggest victory is the availability of notebooks from larger manufacturers with linux preinstalled, for a low price (netbooks).
To boil the essesce of your commen: RTFTOS when you sign up for something free, not just click ok.
b) its not only political. it's real. If you cant hire ad fire for some reason, but haxe a fixed staff, you dont have the choice but to reeducate them (e.g. 15 Persons, 5000 Euro/Person Reeduaction costs). I worked in the computing center of my university, and there i think they i would recommend to buy sun machines als long as they can, because their not so simple network is running without trouble (only the part of it settling on solaris, the novell/nt/linux group is such a mess its incredible), which the personal and infrastructure and under the funding/infrastructure boundaries they have. Causing out-times for services which are used by 20000 students and a few thousand employes, some hospitals and associated research centers sound like a thing to avoid. And no, there failing drives need to be replaced (some Admin has to go there and touch it) in this case.
a) i said "consider" solaris. this somehow matches your "most industrial use". Usually i would end up with linux
b) "is enough" makes it sound like linux is inferior or cheap. Nothing in my posts suggested this. To put it in clearer words: the only application for a newly installed solaris i could imagine is file serving/server for SUNs thin clients. For certain applications in certain environments the *overall* (including administration and education) cost will be lower for solaris. I am thinking right now about the consistency of the documentation and overall platform stability. In both of these SUN has done a good job. Not needing to re-educate you admin may easily bridge some minor difference in price!
c) "cheap disk" is maybe not what you want in some not "most industrial applications"
I was referring to solaris as an OS. I am aware that the quality of hardware which SUN delivers in certain segments of the market offers - contradicting nostalic memories - no advantage over your approach. I am also aware that SUNs hardware was not as good as the lore of the bearded guys sometimes says (e.g. we had a lot of pizza-boxes which died strange hardware deaths and the monitors where crap). I would agree to say that if you want good hardware for and good price, you will have an easier time with not buying SUN and buying two times as much. If the purpos of this machine would be *only* file-serving, i would consider solaris as os.
Sun going out of business? I have heard that before, regularly. One difference to SGI however is that SGI had a single market which borke away. Sun quite diverse products, which fit together. And lets face it: If i want a trouble-free file server, i probably would buy Solaris. So i would guess that they will find some investor in case they run out of cash.