And it not actually happening will be proof to the contrary. It hasn't happened yet, and it hasn't "not happened" yet, so there's no proof one way or the other, there's just a bunch of loudmouths offering their guesses about the future as solid predictions. (The trouble with predicting "X will happen" is that it's obvious when the prediction is proven true, but, in general, it's not always obvious when the prediction is proven false; unless there's a time limit on the prediction, or something happens that makes it obvious it'll never happen - e.g., Apple getting out of the computing equipment business and switching to running a line of luxury hotels, or something such as that - the predictor can always weasel out of it by saying "well, it hasn't happened yet, but, mark my words...".)
So they are doing it in a stupid way to be different?
No, they're doing it a different way to solve a broader set of problems, as their rationale says. Feel free to debate whether the problems they claim to be solving are worth solving, or whether their solution is the right one for those problems, but don't claim they're just being stupid until you've read the rationale. (I don't have a dog in this fight; the OS I use and develop for/on uses fat binaries for the multi-architecture part of that. I'm just noting that there's a rationale to read before concluding that they're just being different to be different.)
Leave it to Slashdot to bitch about a $60 operating system.
Considering that some of us have had a free OS for a good chunk of the last 20 years?
YOU DAMN BETCHA!
Well, then, you're probably not going to start using OS X any time soon, so the extra $30 for the USB stick won't matter to you, so you have nothing to bitch about in that department.
OS/X is proof that the idea of building on the mach kernel can result in a sound and performant OS.
OS X is proof that by using the Mach kernel as a provider of process/thread management and VM services, and putting a BSD kernel atop that, you can get a sound and performant OS. It's not as if OS X is a true microkernel OS; if that's the goal of the Hurd, as I have the impression it is, that's a different matter.
I really don't care about coordinated universal time or time that has to be regular. I care about the real rotation of the Earth and the Earth's orbit around the sun. So, what we see in the sky is always gonna matter most to me and not what humans create:) It doesn't matter to me if it's irregular.
And you're going to notice a small number of seconds difference?
They did the exact same thing with iMovie a couple of years ago. They built a completely new product, and let it take over the name of a popular and established but long in the tooth product. People screamed bloody murder about the lost features (and to some extent because there were any radical changes, regardless of what they were). And then Apple re-added the lost functionality in the next couple of releases....
I sincerely hope this is what Intuit plans to do with Quicken for Mac. They haven't gotten to the "re-added the lost functionality in the next couple of releases" stage yet, alas....
The GUI is the Quartz window server in both cases (just with different window management policies).
iStat isn't showing an instance of WindowServer running on my (iOS 3) iPhone; ps is showing an instance of WindowServer running on my (OS X 10.6) MacBook Pro. Are you sure that "the GUI is the Quartz window server in both cases"?
So if I want to protect against malware on a mac I need to update its OS every day, potentially?
No. If you want to use Apple's anti-malware protection you need to install the Security Update (which might require updating to the current version of Snow Leopard) and have it potentially update the malware definition files every day, not update the entire system every day.
That user doesn't have admin privileges; that user is in effect, in the sudoers file.
In particular, one of the groups that user is in is the "admin" group (which does, in fact, happen to be in the sudoers file). At least some directories in OS X have permissions rwxrwxr-x and a group owner of admin, so users in the admin group do have, even when not sudoing something or the GUI equivalent, more privileges than users not in the admin group.
and Apple are moving to LLVM so that they don't have to release the source code to their compiler at all.
More correctly stated as "Apple are moving to LLVM, including writing their own non-GPLed front end for C/C++/Objective-C; this means that, whether they choose to do so or not, they are not required to release the source code to their changes to the compiler". Whether that is one of their reasons for doing so (not the reason) is another matter; note that it also means that they could, say, use Clang, LLVM, LLDB, etc. as libraries and link closed-source programs with them, rather than having to keep, say, the GUI bits of Xcode at arm's length to avoid having the GPL require them to provide the source to them.
Currently, the core compiler parts are open-source, under the UIUC license.
I really don't know where you get this. Are you just making it up? DEP (Data Execution Protection) is supported by x86
Well, to be fair, page-level "you can't execute code from here" is only supported by newer x86 processors - although "newer" isn't all that much newer, these days - but if you can shrink the size of the code segment so it excludes as much of the writable region of the address space as possible....
But, yeah, the stuff you're responding to is largely "Windows is just a thin wrapper around DOS" nonsense that's at least 10 years out of date.
Yes, in Windows XP the first user created was unfortunately an administrator by default. But what does that have to do with "assembly calls"? The stupidity of having the user run as admin by default is not something which is defined by the API.
I assume he's referring to some Windows applications that allegedly require admin privileges - but it's not as if the entire Win32 API requires admin privileges (and, as you indicate, that has nothing whatsoever to do with "assembly calls"). And Windows XP isn't the only OS that gives the first account created admin privileges - another one that does so has its name in the title of this article....
I am so sick of morons pretending to know about OS design, OS security, Unix and Windows. You are clueless, and slashdot has you modded as 5 - insightful. Doesn't bode well for the "nerds" site.
And they are when they're wrong. (Hint: "suggesting that something is harmful, and that you remove it, and offering a button to remove it, along with a Cancel button for those who choose not to remove it" != "blocking something".)
The slow, but inevitable slide to Mac OS X being locked down in the exact same way that iOS is.
First they block apps in the name of protecting users from themselves... Then they just slowly increase the definition of "harmful apps."
If by "first they block apps..." you mean "first they warn you that an app might be harmful, suggesting that you drag it to the trash, and providing a one-click option to do that from the warning dialog...", yeah.
I've considered the first idea to be basically a no-brainer for some time and hopes it becomes common in the Linux world.
I hope it becomes common in the UN*X world in general, not just the Linux world; the "commands should produce output that has too little extra columns etc. to be easily human-readable and too little syntactic help to be easily software-parseable" annoyance gets in the way in Solaris and *BSD and Mac OS X and... just as it does on Linux.
For instance, I don't like reading actual text in the terminal, because the default line wrapping sucks and monospace font isn't very good for that task. There's other text formatting you could do as well, like bolds or different sizes or something. So it'd be nice to render that in proportional fonts.
It generally doesn't bother me that much, but I guess if, as long as output that needs to line up vertically can be made to do so, variable-width fonts aren't too bad.
Or, from the link, the fact that we do progress bars with ======== is pretty silly.
The faults of X are grossly overblown and mostly made moot by modern systems that are vastly more powerful than what existed when X was first created.
People like to whine about X but it's by no means the worst thing out there.
Infact, Apple is a great example of a GUI that actually sucks more when put to use rather than just held up as some academic ideal dissasociated from the real world.
X isn't a GUI, it's a framework atop which various GUIs have been implemented. It would be more appropriate to compare the OS X GUI with, for example, GNOME, KDE, XFCE, blackbox+xterm, etc.. (And I've used the OS X GUI, GNOME, and KDE; they all have their good points and bad points - the OS X GUI works pretty well for me, but, then again, one of the apps I use the most on OS X is called "Terminal", just as one of the apps I use most on GNOME is called "gnome-terminal" and one of the apps I use most on KDE is called "Konsole".)
When I cat a PNG I want to see the bytes, not a picture. If I want to see the picture I'll firefox or gimp the PNG, then it will just work.
And fixed-width fonts for data are ideal. Using a variable-width font and trying to od anything is a freaking nightmare.
If by "od" you mean the od command, trying to od anything involves piping it to od. When I cat a PNG I usually type ^C pretty quickly; if I want to see the bytes I'll pipe it to, err, umm, od.
But, yes, there are places where variable-width fonts are suboptimal, even in pure GUI apps; Wireshark would have to do a bit more work to ensure, for example, that the entries for bitfields within a byte/word/etc. line up when using a variable-width font. In a world with variable-width fonts in the terminal emulator, commands such as od might have to explicitly indicate "hey, this is a table with numbers in it, don't fuck it up" (and commands that haven't explicitly adopted any of the Shiny New Stuff might have to be assumed to require that its output be displayed in a fixed-width font).
Slashdot Mirror
No, it actually happening will be proof.
And it not actually happening will be proof to the contrary. It hasn't happened yet, and it hasn't "not happened" yet, so there's no proof one way or the other, there's just a bunch of loudmouths offering their guesses about the future as solid predictions. (The trouble with predicting "X will happen" is that it's obvious when the prediction is proven true, but, in general, it's not always obvious when the prediction is proven false; unless there's a time limit on the prediction, or something happens that makes it obvious it'll never happen - e.g., Apple getting out of the computing equipment business and switching to running a line of luxury hotels, or something such as that - the predictor can always weasel out of it by saying "well, it hasn't happened yet, but, mark my words...".)
So they are doing it in a stupid way to be different?
No, they're doing it a different way to solve a broader set of problems, as their rationale says. Feel free to debate whether the problems they claim to be solving are worth solving, or whether their solution is the right one for those problems, but don't claim they're just being stupid until you've read the rationale. (I don't have a dog in this fight; the OS I use and develop for/on uses fat binaries for the multi-architecture part of that. I'm just noting that there's a rationale to read before concluding that they're just being different to be different.)
This may be due in part to the way github integrates social networking and coding
[ +1 ] <[70]
[w> Follow] @{projectname}
[mnIn Like] [f] 375 people like this commit.
{shudder}
sac longchamp have superior craftsmanship and design ,so that many people like to own them blah blah blah
But do they support any workflow?
This why you NEED battry packs that can be Removed from the systems.
Windows PHONE has this.
An operating system has removable battery packs?
Perhaps what you meant is "some (or all?) mobile phones not from Apple have this"; not all such phones run Windows.
Leave it to Slashdot to bitch about a $60 operating system.
Considering that some of us have had a free OS for a good chunk of the last 20 years?
YOU DAMN BETCHA!
Well, then, you're probably not going to start using OS X any time soon, so the extra $30 for the USB stick won't matter to you, so you have nothing to bitch about in that department.
xdg-open is the command you're looking for.
Unless you're trying to open a Web page's URL on Debian, in which case you're apparently supposed to use sensible-browser instead (and, if your software uses xdg-open on UN*Xes that don't have the string "Mac OS X" in their name, the Debian package for your software patches it to use sensible-browser). It appears that not all Debian derivatives follow that path, however.
It's like complaining the Toyota Prius can't go 0 to 60 in 3 secs and can't carry 8 people.
I think that the only vehicles that'd fit into those specs are called airplanes.
This humble family minivan is claimed to do it in 2.8 seconds, although whether it'd hold 8 people is another matter....
OS/X is proof that the idea of building on the mach kernel can result in a sound and performant OS.
OS X is proof that by using the Mach kernel as a provider of process/thread management and VM services, and putting a BSD kernel atop that, you can get a sound and performant OS. It's not as if OS X is a true microkernel OS; if that's the goal of the Hurd, as I have the impression it is, that's a different matter.
WTF is Thunderbolt?
http://www.intel.com/technology/io/thunderbolt/index.htm.
I really don't care about coordinated universal time or time that has to be regular. I care about the real rotation of the Earth and the Earth's orbit around the sun. So, what we see in the sky is always gonna matter most to me and not what humans create :) It doesn't matter to me if it's irregular.
And you're going to notice a small number of seconds difference?
They did the exact same thing with iMovie a couple of years ago. They built a completely new product, and let it take over the name of a popular and established but long in the tooth product. People screamed bloody murder about the lost features (and to some extent because there were any radical changes, regardless of what they were). And then Apple re-added the lost functionality in the next couple of releases....
I sincerely hope this is what Intuit plans to do with Quicken for Mac. They haven't gotten to the "re-added the lost functionality in the next couple of releases" stage yet, alas....
Call me paranoid but government fiat seems a little untrustworthy to me.
Actually, Fiat aren't state-owned, and I have the impression they've improved reliability a lot since the "Fix It Again, Tony" days.
The GUI is the Quartz window server in both cases (just with different window management policies).
iStat isn't showing an instance of WindowServer running on my (iOS 3) iPhone; ps is showing an instance of WindowServer running on my (OS X 10.6) MacBook Pro. Are you sure that "the GUI is the Quartz window server in both cases"?
So if I want to protect against malware on a mac I need to update its OS every day, potentially?
No. If you want to use Apple's anti-malware protection you need to install the Security Update (which might require updating to the current version of Snow Leopard) and have it potentially update the malware definition files every day, not update the entire system every day.
That user doesn't have admin privileges; that user is in effect, in the sudoers file.
In particular, one of the groups that user is in is the "admin" group (which does, in fact, happen to be in the sudoers file). At least some directories in OS X have permissions rwxrwxr-x and a group owner of admin, so users in the admin group do have, even when not sudoing something or the GUI equivalent, more privileges than users not in the admin group.
and Apple are moving to LLVM so that they don't have to release the source code to their compiler at all.
More correctly stated as "Apple are moving to LLVM, including writing their own non-GPLed front end for C/C++/Objective-C; this means that, whether they choose to do so or not, they are not required to release the source code to their changes to the compiler". Whether that is one of their reasons for doing so (not the reason) is another matter; note that it also means that they could, say, use Clang, LLVM, LLDB, etc. as libraries and link closed-source programs with them, rather than having to keep, say, the GUI bits of Xcode at arm's length to avoid having the GPL require them to provide the source to them.
Currently, the core compiler parts are open-source, under the UIUC license.
I really don't know where you get this. Are you just making it up? DEP (Data Execution Protection) is supported by x86
Well, to be fair, page-level "you can't execute code from here" is only supported by newer x86 processors - although "newer" isn't all that much newer, these days - but if you can shrink the size of the code segment so it excludes as much of the writable region of the address space as possible....
But, yeah, the stuff you're responding to is largely "Windows is just a thin wrapper around DOS" nonsense that's at least 10 years out of date.
Yes, in Windows XP the first user created was unfortunately an administrator by default. But what does that have to do with "assembly calls"? The stupidity of having the user run as admin by default is not something which is defined by the API.
I assume he's referring to some Windows applications that allegedly require admin privileges - but it's not as if the entire Win32 API requires admin privileges (and, as you indicate, that has nothing whatsoever to do with "assembly calls"). And Windows XP isn't the only OS that gives the first account created admin privileges - another one that does so has its name in the title of this article....
I am so sick of morons pretending to know about OS design, OS security, Unix and Windows. You are clueless, and slashdot has you modded as 5 - insightful. Doesn't bode well for the "nerds" site.
You must be new here. :-)
They're not when they're right.
And they are when they're wrong. (Hint: "suggesting that something is harmful, and that you remove it, and offering a button to remove it, along with a Cancel button for those who choose not to remove it" != "blocking something".)
The slow, but inevitable slide to Mac OS X being locked down in the exact same way that iOS is.
First they block apps in the name of protecting users from themselves... Then they just slowly increase the definition of "harmful apps."
If by "first they block apps..." you mean "first they warn you that an app might be harmful, suggesting that you drag it to the trash, and providing a one-click option to do that from the warning dialog...", yeah.
At first read I thought you wrote "I don't need pipe bars looking like big boobs" and started looking for the download link.
I suspect it wouldn't be that hard to customize TermKit to do that.
I've considered the first idea to be basically a no-brainer for some time and hopes it becomes common in the Linux world.
I hope it becomes common in the UN*X world in general, not just the Linux world; the "commands should produce output that has too little extra columns etc. to be easily human-readable and too little syntactic help to be easily software-parseable" annoyance gets in the way in Solaris and *BSD and Mac OS X and... just as it does on Linux.
For instance, I don't like reading actual text in the terminal, because the default line wrapping sucks and monospace font isn't very good for that task. There's other text formatting you could do as well, like bolds or different sizes or something. So it'd be nice to render that in proportional fonts.
It generally doesn't bother me that much, but I guess if, as long as output that needs to line up vertically can be made to do so, variable-width fonts aren't too bad.
Or, from the link, the fact that we do progress bars with ======== is pretty silly.
Again, that's never really bothered me.
on the Mac I never had problem with Copy and Past, and still Linux still struggles and it is a crapshoot if it work across applications or not.
Still? Even with, say, modern GTK+-based or Qt/KDE-based apps?
The faults of X are grossly overblown and mostly made moot by modern systems that are vastly more powerful than what existed when X was first created.
People like to whine about X but it's by no means the worst thing out there.
Infact, Apple is a great example of a GUI that actually sucks more when put to use rather than just held up as some academic ideal dissasociated from the real world.
X isn't a GUI, it's a framework atop which various GUIs have been implemented. It would be more appropriate to compare the OS X GUI with, for example, GNOME, KDE, XFCE, blackbox+xterm, etc.. (And I've used the OS X GUI, GNOME, and KDE; they all have their good points and bad points - the OS X GUI works pretty well for me, but, then again, one of the apps I use the most on OS X is called "Terminal", just as one of the apps I use most on GNOME is called "gnome-terminal" and one of the apps I use most on KDE is called "Konsole".)
When I cat a PNG I want to see the bytes, not a picture. If I want to see the picture I'll firefox or gimp the PNG, then it will just work.
And fixed-width fonts for data are ideal. Using a variable-width font and trying to od anything is a freaking nightmare.
If by "od" you mean the od command, trying to od anything involves piping it to od. When I cat a PNG I usually type ^C pretty quickly; if I want to see the bytes I'll pipe it to, err, umm, od.
But, yes, there are places where variable-width fonts are suboptimal, even in pure GUI apps; Wireshark would have to do a bit more work to ensure, for example, that the entries for bitfields within a byte/word/etc. line up when using a variable-width font. In a world with variable-width fonts in the terminal emulator, commands such as od might have to explicitly indicate "hey, this is a table with numbers in it, don't fuck it up" (and commands that haven't explicitly adopted any of the Shiny New Stuff might have to be assumed to require that its output be displayed in a fixed-width font).