I'm not saying it was OK because it was incredibly goddamn rare. What I'm saying is that to allow students to arm themselves for the 1 in 1 million chance of a school shooting, or attack on campus is insane.
Also, if you go from having one student armed to having all students armed, then the rarity of such events drops as a result.
Here's a better idea: why not go from one student armed to no students armed. It's absurd to solve a gun problem by throwing more guns at it.
But that's my preference. Yours obviously differs on the remote.
I may have been stating preference but I'm quite certain that objective analysis of usability testing would show that the Apple remote is more intuitive and requires less learning curve than remotes that have many more buttons.
The single button on my Macbook Pro is also by far my largest complaint about it, even if I can do the multi-finger tap thing.
What're you trying to do that requires right click? I do almost nothing that requires it. On my iMac I have a wireless Mighty Mouse, but on my MacBook Pro I never use an external mouse and have no problems at all.
I think the biggest and almost sole problem that people have with single button mice is that they've been trained to use a right button for so many years. The problem isn't intrinsic to the interface, it's in the training.
The most important thing when adapting to new interfaces, I think, is having an open mind and positively accepting changes in the way you work rather than either negatively accepting or not accepting them at all. Then once you've learnt the new interface you can objectively compare it to the interface that you used previously. If you haven't gone in with an open mind and positive acceptance then it's much more difficult to a) become comfortable in it, and b) objectively compare.
Yeah I've noticed the same on every machine I've tried Front Row on. Which is a real shame because it's one of those apps that you use to show off.
Me: "Hey, check this out." Me: *presses menu on the remote and watches the Front Row startup effect*
Friend: "Oooooh. Cooooool."
Me: *accidentally selects a mislabeled menu option, that should have been labelled "Stop. Do nothing. Show a spinner for one minute."* Me: "Uuhh, yeeaah, my network must be down. Hey, look over there!"
But other than Front Row sucking, I really think the remote is genius. Oh, and the DVD playing app in Front Row is actually really smooth and intuitive to use. I sometimes watch DVDs on my iMac 24", when the DVD player under my TV decides to throw a spaz, and every time it's a real joy to use. So intuitive.
Now if only the Apple TV had a DVD drive. It seems absurd to me that they didn't put one in.
While I agree that the Apple TV is severely limited in functionality, your attack on the remote I think is misguided. Personally I've found the Apple remote to be one of the best things to happen to media viewing since TV remotes went wireless. Navigating through Front Row with the remote is elegant and simple and a far superior experience to using any traditional media remote. Everything can be achieved with far less buttons, in a much smaller and neater remote than any other TV/media device offers. It's more intuitive and has almost zero learning curve. That's the sort of innovation that Apple are famous for, and the Apple remote is not an exception.
My take on DHTML widget toolkits is this: It's too soon.
Even the low level toolkits are still in their early stages, shaking out the initial design concepts and best approaches. So the situation in the higher level/GUI toolkits is going to be much worse. There's a very high risk of investing considerable code and project time into a toolkit only to discover that either it just doesn't fit with the project, or that the toolkit is still too quickly evolving to be a stable target.
That rapid evolution is a symptom of something that's going to bite you in the arse: they haven't got them right yet! If they'd got it right, then the evolution would slow down.
I've personally made a degree of use of the Prototype library, and become increasingly disillusioned with it when compared to the competing jQuery library. jQuery appears to be a much more elegant and future proof take on the problem.
I've also put a fair amount of code into making use of the event:Selectors library which I have subsequently completely thrown out.
My policy now is to only make use of the very minimum from the available libraries, while keeping a close eye on their development. AJAX/DHTML is reasonably light on lines of code anyway, so it's not as if you really *need* toolkits to get you through the projects. Eventually the best of breed toolkits will shake out and it'll be obvious what to use, when, and where. But that time hasn't come yet.
Mithraism dates back 4000 years, obviously predating Christianity. Here's a few little details that Christianity borrowed from Mithraism:
1. Mithra was born of a virgin on December 25th in a cave, and his birth was attended by shepherds. 2. He was considered a great traveling teacher and master. 3. He had 12 companions or disciples. 4. Mithra's followers were promised immortality. 5. He performed miracles. 6. As the "great bull of the Sun," Mithra sacrificed himself for world peace. 7. He was buried in a tomb and after three days rose again. 8. His resurrection was celebrated every year.
Heck, there isn't even one single scrap of evidence that Jesus ever lived as a man, let alone a god.
And also plenty of direct evidence that the Jesus story and Christian beliefs were fictional rip offs of the back story of a competing religion.
Actual genuine belief in the factual accuracy of the story of Jesus, let alone belief in Christian spirituality requires either ignorance and stupidity or outright denial and rejection of known facts.
"PHP just doesn't cut the mustard for anything other that a web guestbook."
That this comment has been moderated anything other than troll is a sad indictment of Slashdot's current breed of moderators. Someone who is obviously a failing developer (ie they can't build a web application in one of the web's most heavily used languages) gets to +4 Interesting? That's really sad.
Huh? This is a post about an application made for the motion sensor, not a post about the motion sensor itself.
If you think that IBM's motion sensors should be getting as much attention, then perhaps you should write some cool toys for them? So far it looks like all the cool toys exploiting motion sensors have been written for Macs. Which is why we see posts about these toys on Macs. It kind of follows, you know?
This has been fixed. So long as you're running the latest patch level, that problem will be gone.
I have a 1GHz Powerbook with 768MB RAM, and I was initially having trouble running more than one or two widgets -- they were slowing my system down something awful. But with the latest Tiger patch level, I have five widgets running all the time, and the system is exceptionally snappy.
I was initially going to buy more memory to compensate, but the bug fixes that they rolled out saved me money and hassle:)
No, but the construction dino's having feathers is a gerund
The phrase in question is "fossil evidence of dino's resembling "giant chicks" more then reptiles as formerly accepted". There is no gerund in that phrase. If there were, then sure, you should throw an apostrophe in, but there isn't.
Agreed that the use of a trailing 's' in certain circumstances is open for discussion, but this isn't one of them, and misses the point entirely.
I'm afraid it's you who is missing the point, as you appear to have rephrased the fragment in question in order to support your argument, rather than working off the actual fragment.
a) "dino's" isn't a gerund. b) Shortened words and acronyms can optionally have apostrophes before the 's', but many people frown on the use and thus it's not a universally accepted usage. So no, there's no "require", just an "optional, but not widely approved".
I also used to run a local apache+postgresql dev environment, under Panther. 768MB RAM was still ample for this workload. But yes, Tiger has higher memory requirements and my usage is perhaps heavier than that of an average user:(
I've got 768MB RAM in my 1GHz Powerbook and I'm still suffering memory issues.
I've been forced to slim down to only one widget left running (although I have several more that I'd really like to keep open constantly), and to keep an eye on the number of apps I have resident at any particular time.
I had no such memory concerns under Panther. I would have thought 768MB would be ample, but it appears not. I'm looking to move to 1GB RAM, and hoping that Apple continue to clean up Tiger.
The 10.4.2 update considerably improved the situation, but it has a lot further to go before I'll be completely happy with Tiger.
The idea of sovereign posture (absolute full screen) apps is a hangover from smaller screens and should be on the way out. Its relevancy is something tied to past generations of computing, not our current generations.
When you've got screen dimensions past a certain point there are very few tasks that benefit from using the whole screen space. Your example of wanting to maximise your browser window is a perfect example of where there's absolutely no need for the use of the whole screen space. Web pages are like newspapers in that the readability of the text degrades as the width increases. The less width (to a point) the more readable.
The only cases where web browsing benefits from a browser window wider than say 800px is when either the designer has fucked up their job and made the site too wide or when you're viewing an image or diagram or some such, in which case pressing the zoom button will resize the browser window to exactly the necessary dimensions.
Eventually even Microsoft will have to admit that absolute maximising of windows has become irrelevant due to increased screen dimensions and will have to implement an intelligent zoom feature exactly like Apple's. Apple are ahead of the game on this one, not behind.
I cringe at saying it, but I *actually am* finding this one snappier. Or to be more precise, I'm finding it less memory hungry.
Widgets seem to be using up considerably less memory and running more smoothly than previously, which in turn frees up more memory for other tasks and has reduced general swapping.
It's the word processing documents that are the killer.
Somewhat off-topic: When it comes to word processor apps, nothing I've seen or used has ever come near the vast superiority of WordPerfect (even up to or even especially the latest versions). It's a sad thing indeed to see WordPerfect die a slow death in the market.
Spotlight's indexing processes are also a *major* culprit in Tiger's slowdowns and lockups. I'm at the end of my tether with those, which is really sad as I love Spotlight and use it all the time.
Tiger's also more of a memory hog than Panther, sadly, so performance is going to suffer more often in Tiger simply due to memory exhaustion.
If 10.4.2 doesn't fix at least the Spotlight issues I'm going to start losing my good feelings towards Apple. Bah humbug.
Re:the code of conduct for free software distribut
on
Drafting GPL3
·
· Score: 1
And things things exactly are you restricted from doing with GPLed code? The only things you are restricted from doing are making it less free for anyone else. Other than that, you can do anything.
You're manufacturing imaginary restrictions.
Re:the code of conduct for free software distribut
on
Drafting GPL3
·
· Score: 1
You seem to be talking yourself in self contradictory circles. Either you think it's acceptable for people to take away your freedom (BSD) or you don't (GPL).
Re:the code of conduct for free software distribut
on
Drafting GPL3
·
· Score: 1
There is no need to limit (restrict) freedom in order to promote freedom.
Utter bollocks. It's fundamentally important to restrict people from taking away others' freedoms in order to maintain freedom.
The freedom to take away freedom is not a defensible freedom. You follow?
Why is this interglacial anthropogenic when it's on the same cycle as the previous 9 interglacials?
That's easy: the rate of change. It may be the same or similar cycle but it's not the same rate of change. It's accelerated change (I believe without precedent) that directly correlates with the CO2 build up in the atmosphere.
nobody knows "absolutely and definitely" whether there is global warming or, if it exists, whether it is due to human activity.
Actually I think it's not at all in dispute as to whether we're experiencing any global warming. I believe that's been conclusively established. What some still heavily debate are the causes of said warming.
There's a strong correlation between atmospheric CO2 and warming and well understood atmospheric interactions of CO2, but some try to point the finger elsewhere or back to natural patterns.
What's truly astounding is the massively increasing level of outright propaganda on the subject. The scientists appear to be being left behind and the propagandists (sponsored by private industry) are taking over the show. Do a google for "CO2" -- it's a real eye opener.
Slashdot Mirror
Also, if you go from having one student armed to having all students armed, then the rarity of such events drops as a result.
Here's a better idea: why not go from one student armed to no students armed. It's absurd to solve a gun problem by throwing more guns at it.
I may have been stating preference but I'm quite certain that objective analysis of usability testing would show that the Apple remote is more intuitive and requires less learning curve than remotes that have many more buttons.
What're you trying to do that requires right click? I do almost nothing that requires it. On my iMac I have a wireless Mighty Mouse, but on my MacBook Pro I never use an external mouse and have no problems at all.
I think the biggest and almost sole problem that people have with single button mice is that they've been trained to use a right button for so many years. The problem isn't intrinsic to the interface, it's in the training.
The most important thing when adapting to new interfaces, I think, is having an open mind and positively accepting changes in the way you work rather than either negatively accepting or not accepting them at all. Then once you've learnt the new interface you can objectively compare it to the interface that you used previously. If you haven't gone in with an open mind and positive acceptance then it's much more difficult to a) become comfortable in it, and b) objectively compare.
But other than Front Row sucking, I really think the remote is genius. Oh, and the DVD playing app in Front Row is actually really smooth and intuitive to use. I sometimes watch DVDs on my iMac 24", when the DVD player under my TV decides to throw a spaz, and every time it's a real joy to use. So intuitive.
Now if only the Apple TV had a DVD drive. It seems absurd to me that they didn't put one in.
While I agree that the Apple TV is severely limited in functionality, your attack on the remote I think is misguided. Personally I've found the Apple remote to be one of the best things to happen to media viewing since TV remotes went wireless. Navigating through Front Row with the remote is elegant and simple and a far superior experience to using any traditional media remote. Everything can be achieved with far less buttons, in a much smaller and neater remote than any other TV/media device offers. It's more intuitive and has almost zero learning curve. That's the sort of innovation that Apple are famous for, and the Apple remote is not an exception.
Less buttons == better.
Perhaps you haven't actually tried using it?
My take on DHTML widget toolkits is this: It's too soon.
Even the low level toolkits are still in their early stages, shaking out the initial design concepts and best approaches. So the situation in the higher level/GUI toolkits is going to be much worse. There's a very high risk of investing considerable code and project time into a toolkit only to discover that either it just doesn't fit with the project, or that the toolkit is still too quickly evolving to be a stable target.
That rapid evolution is a symptom of something that's going to bite you in the arse: they haven't got them right yet! If they'd got it right, then the evolution would slow down.
I've personally made a degree of use of the Prototype library, and become increasingly disillusioned with it when compared to the competing jQuery library. jQuery appears to be a much more elegant and future proof take on the problem.
I've also put a fair amount of code into making use of the event:Selectors library which I have subsequently completely thrown out.
My policy now is to only make use of the very minimum from the available libraries, while keeping a close eye on their development. AJAX/DHTML is reasonably light on lines of code anyway, so it's not as if you really *need* toolkits to get you through the projects. Eventually the best of breed toolkits will shake out and it'll be obvious what to use, when, and where. But that time hasn't come yet.
Just type "php.net/[keywords]" and it'll search PHP's function library.
More Mithra/Jesus comparisons:
t mls tianity.html
http://jdstone.org/cr/files/mithraschristianity.h
http://www.venusproject.com/ecs/true_origins_chri
http://tektonics.org/copycat/mithra.html
Mithraism dates back 4000 years, obviously predating Christianity. Here's a few little details that Christianity borrowed from Mithraism:
1. Mithra was born of a virgin on December 25th in a cave, and his birth was attended by shepherds.
2. He was considered a great traveling teacher and master.
3. He had 12 companions or disciples.
4. Mithra's followers were promised immortality.
5. He performed miracles.
6. As the "great bull of the Sun," Mithra sacrificed himself for world peace.
7. He was buried in a tomb and after three days rose again.
8. His resurrection was celebrated every year.
Heck, there isn't even one single scrap of evidence that Jesus ever lived as a man, let alone a god.
And also plenty of direct evidence that the Jesus story and Christian beliefs were fictional rip offs of the back story of a competing religion.
Actual genuine belief in the factual accuracy of the story of Jesus, let alone belief in Christian spirituality requires either ignorance and stupidity or outright denial and rejection of known facts.
"PHP just doesn't cut the mustard for anything other that a web guestbook."
That this comment has been moderated anything other than troll is a sad indictment of Slashdot's current breed of moderators. Someone who is obviously a failing developer (ie they can't build a web application in one of the web's most heavily used languages) gets to +4 Interesting? That's really sad.
Huh? This is a post about an application made for the motion sensor, not a post about the motion sensor itself.
If you think that IBM's motion sensors should be getting as much attention, then perhaps you should write some cool toys for them? So far it looks like all the cool toys exploiting motion sensors have been written for Macs. Which is why we see posts about these toys on Macs. It kind of follows, you know?
This has been fixed. So long as you're running the latest patch level, that problem will be gone.
:)
I have a 1GHz Powerbook with 768MB RAM, and I was initially having trouble running more than one or two widgets -- they were slowing my system down something awful. But with the latest Tiger patch level, I have five widgets running all the time, and the system is exceptionally snappy.
I was initially going to buy more memory to compensate, but the bug fixes that they rolled out saved me money and hassle
And even if it were to take the possessive, it would be dinos' not dino's, as it's dinosaurs plural not dinosaur singular that's being discussed.
No, but the construction dino's having feathers is a gerund
The phrase in question is "fossil evidence of dino's resembling "giant chicks" more then reptiles as formerly accepted". There is no gerund in that phrase. If there were, then sure, you should throw an apostrophe in, but there isn't.
Agreed that the use of a trailing 's' in certain circumstances is open for discussion, but this isn't one of them, and misses the point entirely.
I'm afraid it's you who is missing the point, as you appear to have rephrased the fragment in question in order to support your argument, rather than working off the actual fragment.
a) "dino's" isn't a gerund.
b) Shortened words and acronyms can optionally have apostrophes before the 's', but many people frown on the use and thus it's not a universally accepted usage. So no, there's no "require", just an "optional, but not widely approved".
I initially went for 768MB RAM because I run a lot of concurrent applications. Right now (normal use) I have these applications resident:
:(
Safari, NewsFire, Sciral Consistency, iCal, Mail, Adium, Colloquy, iTunes, Activity Monitor, XCode.
I also used to run a local apache+postgresql dev environment, under Panther. 768MB RAM was still ample for this workload. But yes, Tiger has higher memory requirements and my usage is perhaps heavier than that of an average user
I've got 768MB RAM in my 1GHz Powerbook and I'm still suffering memory issues.
I've been forced to slim down to only one widget left running (although I have several more that I'd really like to keep open constantly), and to keep an eye on the number of apps I have resident at any particular time.
I had no such memory concerns under Panther. I would have thought 768MB would be ample, but it appears not. I'm looking to move to 1GB RAM, and hoping that Apple continue to clean up Tiger.
The 10.4.2 update considerably improved the situation, but it has a lot further to go before I'll be completely happy with Tiger.
The idea of sovereign posture (absolute full screen) apps is a hangover from smaller screens and should be on the way out. Its relevancy is something tied to past generations of computing, not our current generations.
When you've got screen dimensions past a certain point there are very few tasks that benefit from using the whole screen space. Your example of wanting to maximise your browser window is a perfect example of where there's absolutely no need for the use of the whole screen space. Web pages are like newspapers in that the readability of the text degrades as the width increases. The less width (to a point) the more readable.
The only cases where web browsing benefits from a browser window wider than say 800px is when either the designer has fucked up their job and made the site too wide or when you're viewing an image or diagram or some such, in which case pressing the zoom button will resize the browser window to exactly the necessary dimensions.
Eventually even Microsoft will have to admit that absolute maximising of windows has become irrelevant due to increased screen dimensions and will have to implement an intelligent zoom feature exactly like Apple's. Apple are ahead of the game on this one, not behind.
I cringe at saying it, but I *actually am* finding this one snappier. Or to be more precise, I'm finding it less memory hungry.
Widgets seem to be using up considerably less memory and running more smoothly than previously, which in turn frees up more memory for other tasks and has reduced general swapping.
It's the word processing documents that are the killer.
Somewhat off-topic: When it comes to word processor apps, nothing I've seen or used has ever come near the vast superiority of WordPerfect (even up to or even especially the latest versions). It's a sad thing indeed to see WordPerfect die a slow death in the market.
Spotlight's indexing processes are also a *major* culprit in Tiger's slowdowns and lockups. I'm at the end of my tether with those, which is really sad as I love Spotlight and use it all the time.
Tiger's also more of a memory hog than Panther, sadly, so performance is going to suffer more often in Tiger simply due to memory exhaustion.
If 10.4.2 doesn't fix at least the Spotlight issues I'm going to start losing my good feelings towards Apple. Bah humbug.
And things things exactly are you restricted from doing with GPLed code? The only things you are restricted from doing are making it less free for anyone else. Other than that, you can do anything.
You're manufacturing imaginary restrictions.
You seem to be talking yourself in self contradictory circles. Either you think it's acceptable for people to take away your freedom (BSD) or you don't (GPL).
There is no need to limit (restrict) freedom in order to promote freedom.
Utter bollocks. It's fundamentally important to restrict people from taking away others' freedoms in order to maintain freedom.
The freedom to take away freedom is not a defensible freedom. You follow?
Why is this interglacial anthropogenic when it's on the same cycle as the previous 9 interglacials?
That's easy: the rate of change. It may be the same or similar cycle but it's not the same rate of change. It's accelerated change (I believe without precedent) that directly correlates with the CO2 build up in the atmosphere.
nobody knows "absolutely and definitely" whether there is global warming or, if it exists, whether it is due to human activity.
Actually I think it's not at all in dispute as to whether we're experiencing any global warming. I believe that's been conclusively established. What some still heavily debate are the causes of said warming.
There's a strong correlation between atmospheric CO2 and warming and well understood atmospheric interactions of CO2, but some try to point the finger elsewhere or back to natural patterns.
What's truly astounding is the massively increasing level of outright propaganda on the subject. The scientists appear to be being left behind and the propagandists (sponsored by private industry) are taking over the show. Do a google for "CO2" -- it's a real eye opener.