HEY! I ride my bike to work all the time, and being small I can park it anywhere: between overly cautious Volvos, behind road barriers/pylons, up a tree, etc. It's also a trail bike, as such there's generally a nice splash of mud on the plate. Imagine that.
Of course, the downside is it's max speed is sub-150km/h, so it's for offroad, inner-city and median strip/footpath use only:)
Did you mean that "yes, making short-cuts programatically is a pain", or "yes, NTFS 5 has symlinks"?
Yes, NTFS supports symlinks. Yes, PIFs (shortcuts) are no substitute for symlinks, and they're not supposed to be.
The text/binary mode is a hassle because you have to be careful when writing or reading files to open them appropriately. That is, everywhere else, you don't need to specify "binary" mode. However, if you write code that might be run on Windows (e.g. in Python)
Well, I write in Python all the time, and I always open text files in binary mode and strip EOLs myself. Python's readlines() is broken in text mode, IMO. In binary mode, read() and readlines() are just fine for handling binary and text files.
1) nice for the user, so they don't wonder why suddenly the first letter is capitalized but none of the rest of their camel-case name is capitalized (think Windows Explorer)
2) important when working with case sensitive apps or moving stuff to case sensitive filesystems.
This is nonsense. Either you the programmer made the file paths, and therefore know the case, or the user entered it.
If the user entered it there's two possibilities: the file system is case sensitive, and they are forced to enter the correct case, OR it's not case sensitive and you display whatever the user enters. Which is more user friendly?
Internally, use lowercase internally for text-comparisons. eg. in the aformentioned Python use normcase()
To create simple shortcuts, she had to dig into COM and/or ActiveX. The case retention problems occurred somewhere in their OS-abstraction libraries.
Uh, THEIR abstraction libraries? Windows works fine with not a care in the world about case, if someone goes and writes some shit on top if it, thats not Windows' problem.
Drawing from Windows' MSDOS roots, which draw from MSDOS' CPM roots, which draw from CPMs' DEC-System 10 roots (CPM was developed by Gary Kildall on a DEC-System 10), the '/' character was already burned in the CLI. '/' is used in DEC Operating Systems, CPM and MSDOS for command parameters.
DOS isn't directly compatible with those no there's no need for strict compliance. I don't know about the others, but DOS programs parse the parameters themselves, so it can be any character(s).
Having drive letters is also borrowed from DEC, but they weren't single letters there, but rather names followed by a colon.
Yeah we use VMS where I work... talk about verbose. its1:[really.fugly] only slightly$improved with $ymbol$.
The Windows filesystems have a hard-wired connection between filesystem names and physical devices (i.e. C:\..., D:\..., etc), which causes software configuration information in the non-human-readable registry to depend on physical device configuration
Uh, that's the namespace not the filesystem. It's getting better - physical drives can be mounted inside others, though with networks you either have to use UNC or stick to letters.
Using \ instead of/, since \ requires a longer reach on standard keyboards (while this is true, I'm not really serious about this)
I think they fucked that one up - since \ is the path separator, / should be a valid filename character (since it's common (English) punctuation). But since / is invalid in filenames, yes it should be the path separator.
The separation between devices and files. It is my opinion that the "everything is a file" philosophy employed in the Unix file systems is arguably superior to Microsoft's half-assed support of this concept ('copy con foo.txt' works, but which file represents the sound card's DSP on NTFS 5?). This philosophy goes a long ways in providing nearly-uniform access to all parts of your computer. This design decision greatly enhances the power of scripts, especially when coupled with pipes, redirection, and fine control over file handles
Backwards compatibility. And it's not a real file either. Actually, I think this "mystery meat" shit comes from VMS.
The lack of symbolic links (does NTFS finally have these?). Windows shortcuts require unnecessary nonsense to create programmatically
Yes.
Windows filesystems, AFAIK, *all* make a distinction between "text" and "binary" files. It is arguable whether this was appropriate in DOS. It is clearly inappropriate now.
Any file can be opened in binary or text mode for reading - I don't know whether this is a function of the APIs or part of the filesystem, though I doubt it's the latter.
I don't know about NTFS, but VFAT is case-random. It is difficult, programatically, to correctly discover the original capitalization of a filename.
It's case retentive. Getting the original case is not difficult (just read it from disk!). Why do you need it anyway?
But while stealing the goods, valued at US$90,000, they took their time. According to police reports, these peculiar robbers smoked some cigarettes, ate a snack, and drank a few cups of joe, taking it easy before leaving the scene of the crime
And my favourite:
After they loaded the computers into a van,
the alarm was also taken
ROFL. 10/10 for style. Someone buy these clowns a beer (before they earn themselves a darwin award).
I bet Kodak, etc. will be onto this WORM shit quicksmart. By now they must have realised their little film/developing gravy train has been sitting in the maintenance shed for a while.
which in turn leads to higher sales of new books Does it? Or does it simply lead to higher sales of used books?
It sounds like a loss leader to me. No guarantees it'll work, but any publicity is good publicity, and that goes tenfold for actually getting the suckers^Wcustomers into your shop (or on your website as the case may be)
As did every failed Windows-centric company, and every failed Oracle-centric company, and every failed Solaris-centric company....
Except the kinds of companies/customers that would buy open source are different from those that buy closed source (or any other restricted license).
Those that make major use of open source have come to the realisation that with closed source, you're eventually going to get fucked over. Therefore, there's no way in hell they're going to buy a product from a dodgy upstart, part based on open source, and part based on closed.
Because everything that's easy about OSX has nothing to do with the standard *nix way of doing this. That level of meddling in the old-school *nix way of things will not be welcome in Linux land. Remember, Linux was written for those who longed for the time where men were men and wrote their own device drivers - NOT for people who lick their hardware.
Those that desire the Win/OSX way can suck it down and buy those platforms. Linux is it's own OS.
without the niggling driver details that plague Intel OS distributions. It amazes me that Linux has been as successful as it has with the agony that users have to endure to successfully install the OS.
What the fuck are you smoking? Installing is the EASIEST way to get the system configured and fully functional. It's the changing shit afterwards that's the problem.
For the most part, we do whatever the hell we like anyway. Fucked up laws like this are made to get the votes of the morals crusaders, and score PR points with parents and oldies. Once they're passed they are forgotten, at least until someone gets busted for something else, then they just add it to the list of charges to thoroughly crusify the guy.
Aren't there limits on who can and can't ask for your SS# ? An ID restricted to govt use only is nowhere near as damaging as one that every schmuck can demand.
Graphical Boot-Up (no confusing Linux kernel messages)
Kept as simple as possible (no GNOME, no KDE, etc, just GNUstep)
I'm cool with all the features except these two. A) I hope it's easy to get rid of the graphical startup. B) what the hell works with GNUstep? Gnome and KDE have been fighting for the "user-friendly" crown for ages, what's GNUstep bring to the party?
Slashdot Mirror
HEY! I ride my bike to work all the time, and being small I can park it anywhere: between overly cautious Volvos, behind road barriers/pylons, up a tree, etc. It's also a trail bike, as such there's generally a nice splash of mud on the plate. Imagine that.
:)
Of course, the downside is it's max speed is sub-150km/h, so it's for offroad, inner-city and median strip/footpath use only
Well, I write in Python all the time, and I always open text files in binary mode and strip EOLs myself. Python's readlines() is broken in text mode, IMO. In binary mode, read() and readlines() are just fine for handling binary and text files.
This is nonsense. Either you the programmer made the file paths, and therefore know the case, or the user entered it.
If the user entered it there's two possibilities: the file system is case sensitive, and they are forced to enter the correct case, OR it's not case sensitive and you display whatever the user enters. Which is more user friendly?
Internally, use lowercase internally for text-comparisons. eg. in the aformentioned Python use normcase()
Uh, THEIR abstraction libraries? Windows works fine with not a care in the world about case, if someone goes and writes some shit on top if it, thats not Windows' problem.
Yeah we use VMS where I work... talk about verbose. its1:[really.fugly] only slightly$improved with $ymbol$.
I think they fucked that one up - since \ is the path separator, / should be a valid filename character (since it's common (English) punctuation). But since / is invalid in filenames, yes it should be the path separator.
Backwards compatibility. And it's not a real file either. Actually, I think this "mystery meat" shit comes from VMS.
Yes.
Any file can be opened in binary or text mode for reading - I don't know whether this is a function of the APIs or part of the filesystem, though I doubt it's the latter.
It's case retentive. Getting the original case is not difficult (just read it from disk!). Why do you need it anyway?
It's funny shit though:
And my favourite:
ROFL. 10/10 for style. Someone buy these clowns a beer (before they earn themselves a darwin award).
I bet Kodak, etc. will be onto this WORM shit quicksmart. By now they must have realised their little film/developing gravy train has been sitting in the maintenance shed for a while.
If only the Linux kernel changelog was so detailed (it'd be bigger than the kernel itself)
Apache: *) connection.c: changed ++i to ++j in honor of myself [Joe Orton]
LinuxKernel: VM tweaks [read: ripped the arse out of the kernel and replaced it with someone else's]
Those that make major use of open source have come to the realisation that with closed source, you're eventually going to get fucked over. Therefore, there's no way in hell they're going to buy a product from a dodgy upstart, part based on open source, and part based on closed.
Ah, so next time I get caught staring at a cow-orker's tits, I can just say "hey, I was just checking my schedule!"
Or even better:
[mind control]computer, record visual
ULTRA CLOSEUUUUPP WOOOOAAAAAHHHHHH.
end recording, save for later.
Hmmmmm..... sounds like a good target for h4x0ring. While people are in it. Muhaha, eeeeexcellent.
I don't care if my private vehicle takes twice as long, because it's clean and DOESN'T SMELL LIKE VOMIT.
you still need a license to drive a car, lest you cause damage (ILOVEYOU, etc) to innocent bystanders (other n00b's)
Because everything that's easy about OSX has nothing to do with the standard *nix way of doing this. That level of meddling in the old-school *nix way of things will not be welcome in Linux land. Remember, Linux was written for those who longed for the time where men were men and wrote their own device drivers - NOT for people who lick their hardware.
Those that desire the Win/OSX way can suck it down and buy those platforms. Linux is it's own OS.
It's not like there's Indiana Jones/Golden Eye style boobytraps/keys guarding the source..
I think you need to get into some rapid detox program - you're obviously having issues coping with the Real World after prolonged exposure to the RDF.
What the fuck are you smoking? Installing is the EASIEST way to get the system configured and fully functional. It's the changing shit afterwards that's the problem.
For the most part, we do whatever the hell we like anyway. Fucked up laws like this are made to get the votes of the morals crusaders, and score PR points with parents and oldies. Once they're passed they are forgotten, at least until someone gets busted for something else, then they just add it to the list of charges to thoroughly crusify the guy.
Aren't there limits on who can and can't ask for your SS# ? An ID restricted to govt use only is nowhere near as damaging as one that every schmuck can demand.
Once everyone has a single ID then it's a lot easier to link every other database to that ID.
Yeah but nothing says "fuck you" like keeping your cash AND pirating the thing anyway.