Well, yes and no... At the risk of introducing shades of grey into a slashdot thread, a bicycle is a vehicle for transporting a person (or people) and cargo from one place to another, so the question is what vehicle belongs where? Ideally, we have bike paths. Yeah, right... Speaking as one who used to ride exclusively for my transportation, I would not go on a sidewalk. On my way to work I once grazed someone with my shoulder when he stepped out into the street and the energy thusly imparted was enough to knock him unconcious! This was not a square hit and I did not crash. What if I had nudged an old lady and not a relatively fit and healthy guy? Should people on the sidewalk signal when changing sides or direction? Has anyone reading this ever been amused by calling "on your left" and watching pedestrians dodge into your path you just warned them you would be taking? While bikes on the road may be annoying to people driving past them, one could argue that they are a major hazard on the sidewalk. If the traffic laws are insufficient to deal with bikes (I think they work just fine) then they should be fixed. Putting bikes somewhere else is not a solution to outdated laws, it just relocates the problem somewhere else.
Ouch! Well maybe it didn't improve your life, but you tried it, and kudos to you for that. Think of it like that strange food in the buffet line with the unpronounceable foreign-ish name where you don't even recognize what it's made out of. You try a little of it and maybe you like it, maybe you don't. If you don't, you don't get seconds. It's not really the game genre's fault it didn't work for you. If you invested a lot of your life in RPGs and are now unhappy, consider it a life lesson on time/resource management. If nothing else you can get that!
The operative phrase here:"most of the time". We are not discussing selective privacy here. We are not talking about something you have voluntarily posted on your blog. We are talking about information you have explicitly not made public and may very well not want others to use against you. This is not information you chose to share. This is information someone else has chosen to collect/use/share without your knowledge or consent. Please bear this in mind when talking about your "open subculture" and the people who you believe are not in it!
--insert reality check--
1) SMB works great, no argument there. Apple's stopgap solution of putting the fork info into another file and hiding it leaves a bit to be desired IRL, such as when an Apple user sends a document to a PC user straight from the file server. Better yet, let them send it via email. It will probably arrive on the other end as half the file with a.dat extension.
2) All modern fonts are OpenType? Be careful about using words with that global a scope when discussing facts. It's dangerous. That being said, I will guarantee you that not just most but ALL fonts from the OS8 days WILL have a file fork. Convert old fonts? I work in the print industry. You don't "convert". It's like driving on the wrong side of the freeway. Even if you get there successfully, it was a really bad idea.
3) Since Appletalk needs to be up for older files anyway, you may as well use it.
Basically, I am working in an environment where the front half of the business uses PCs the back half uses macs and the servers run RH. Samba works great on anything new. Older stuff, you gotta use Appletalk or it'll be mangled when it gets through on the other side, without exception. Appletalk still has its place, weather we like it or not.
The problem is those infuriating mac commercials!
I made a notice I posted in our break room. In bold, 30 pt. type it reads "Web address to watch the commercials Microsoft makes to slam Apple and mock their product:". The rest of the sheet is blank. I think a couple people have gotten it. For the most part, these are straw man arguments they use in those commercials. If they had more legitimate arguments I think they would be less annoying.
Any old apple file you're going to move across a network needs Appletalk. Without it your best case scenario is that it arrives at the other end and the client doesn't know what to do with it, so you force open in the correct app and resave or add an extension. More often, the part of the file fork that got stripped out via a non-appletalk transfer had necessary data. Troubleshooting a document built with a font that's been mangled like this can be a nightmare if you don't know what to look for in the first place. Educating users on when to connect to a server share via smb vs. afp can be an interesting experience as well, as they are often the creative types that don't care about file transfer protocols, they just want it to work.
PS. if you don't know the name or IP address of a printer on a network, Appletalk can be a handy "cheat" if you need to print something from a workstation immediately.
Slashdot Mirror
Well, yes and no... At the risk of introducing shades of grey into a slashdot thread, a bicycle is a vehicle for transporting a person (or people) and cargo from one place to another, so the question is what vehicle belongs where? Ideally, we have bike paths. Yeah, right...
Speaking as one who used to ride exclusively for my transportation, I would not go on a sidewalk. On my way to work I once grazed someone with my shoulder when he stepped out into the street and the energy thusly imparted was enough to knock him unconcious! This was not a square hit and I did not crash. What if I had nudged an old lady and not a relatively fit and healthy guy?
Should people on the sidewalk signal when changing sides or direction? Has anyone reading this ever been amused by calling "on your left" and watching pedestrians dodge into your path you just warned them you would be taking?
While bikes on the road may be annoying to people driving past them, one could argue that they are a major hazard on the sidewalk. If the traffic laws are insufficient to deal with bikes (I think they work just fine) then they should be fixed. Putting bikes somewhere else is not a solution to outdated laws, it just relocates the problem somewhere else.
Ouch!
Well maybe it didn't improve your life, but you tried it, and kudos to you for that. Think of it like that strange food in the buffet line with the unpronounceable foreign-ish name where you don't even recognize what it's made out of. You try a little of it and maybe you like it, maybe you don't. If you don't, you don't get seconds. It's not really the game genre's fault it didn't work for you. If you invested a lot of your life in RPGs and are now unhappy, consider it a life lesson on time/resource management. If nothing else you can get that!
If you just got done reviewing two machines each with a 7" screen, that extra half inch on the third may well seem like a wonderful relief!
The operative phrase here:"most of the time". We are not discussing selective privacy here. We are not talking about something you have voluntarily posted on your blog. We are talking about information you have explicitly not made public and may very well not want others to use against you. This is not information you chose to share. This is information someone else has chosen to collect/use/share without your knowledge or consent. Please bear this in mind when talking about your "open subculture" and the people who you believe are not in it!
--insert reality check-- .dat extension.
1) SMB works great, no argument there. Apple's stopgap solution of putting the fork info into another file and hiding it leaves a bit to be desired IRL, such as when an Apple user sends a document to a PC user straight from the file server. Better yet, let them send it via email. It will probably arrive on the other end as half the file with a
2) All modern fonts are OpenType? Be careful about using words with that global a scope when discussing facts. It's dangerous. That being said, I will guarantee you that not just most but ALL fonts from the OS8 days WILL have a file fork. Convert old fonts? I work in the print industry. You don't "convert". It's like driving on the wrong side of the freeway. Even if you get there successfully, it was a really bad idea.
3) Since Appletalk needs to be up for older files anyway, you may as well use it.
Basically, I am working in an environment where the front half of the business uses PCs the back half uses macs and the servers run RH. Samba works great on anything new. Older stuff, you gotta use Appletalk or it'll be mangled when it gets through on the other side, without exception. Appletalk still has its place, weather we like it or not.
The problem is those infuriating mac commercials!
I made a notice I posted in our break room. In bold, 30 pt. type it reads
"Web address to watch the commercials Microsoft makes to slam Apple and mock their product:".
The rest of the sheet is blank. I think a couple people have gotten it. For the most part, these are straw man arguments they use in those commercials. If they had more legitimate arguments I think they would be less annoying.
Any old apple file you're going to move across a network needs Appletalk. Without it your best case scenario is that it arrives at the other end and the client doesn't know what to do with it, so you force open in the correct app and resave or add an extension. More often, the part of the file fork that got stripped out via a non-appletalk transfer had necessary data. Troubleshooting a document built with a font that's been mangled like this can be a nightmare if you don't know what to look for in the first place. Educating users on when to connect to a server share via smb vs. afp can be an interesting experience as well, as they are often the creative types that don't care about file transfer protocols, they just want it to work. PS. if you don't know the name or IP address of a printer on a network, Appletalk can be a handy "cheat" if you need to print something from a workstation immediately.