ITT: simple things Windows simply can't do.
I'll start: create a file with a dot prefix.
>create a file with a dot prefix
And why?
Retard
but it will soon enough when they port in all of Ubuntu and bash into an already bloated operating system cause a few retards whined about rebooting
Requiring less than 100 MB of RAM to run.
Create a file named con, prn, aux, etc., even if you add an extension like con.txt.
>>53902597
Because anything after the dot is an extension, and your file must have a name. It can't just have an extension and no name. Fortunately you can get around this using the command prompt.
>>53902557
>Have to boot into Arch to upload a screenshot
>Reboot
>Updates
Remembered why wankblows is unreliable these days
>>53902557
i dont think anyone would actually want to do this
>>53902557
?
>>53902673
wew lad
Also,
no tabs
and no embedded terminal
Windows honestly looks like a babbycare OS
>>53902597
.htaccess
.dotfiles generally
also why not. a system shouldn't care at all about stuff like this. you are also not forced to typ an extension, so why not vice versa
>>53902557
actually it's even more retarded why the explorer denies stuff like this when you can still do it in cmd
>>53902673
Yeah, because nobody would ever want to copy a bunch of files over from a Linux or UNIX system where this is a common naming scheme for config files. Some ported Linux software names its config files with dots in Windows too.
>>53902701
Yeah, do it in command prompt. I'll see that and raise you some forbidden filenames.
>>53902790
Better still, it does this if I try to open one of them.
>>53902557
name it .this.
>>53902818
And if I use file->open in Notepad instead of open with Notepad from Explorer
>>53902860
Finally got it to open, put some text in it and saved it
>2016
>/v/ cannot tweak system fonts
>>53902935
>2016
>/g/ still in 2004 with that dope UI design
>>53902888
About enough of this, time to get rid of them
C:\>del /s "fucky fucky filenames"
C:\fucky fucky filenames\*, Are you sure (Y/N)? y
C:\fucky fucky filenames\aux
The system cannot find the file specified.
C:\fucky fucky filenames\com1
The system cannot find the file specified.
C:\fucky fucky filenames\con
Access is denied.
C:\fucky fucky filenames\prn
The system cannot find the file specified.
>>53902557
Be a good OS
>>53902957
At least people can change theme without crashing the explorer
Also >>53902672
>>53902973
wew
Can I hide a file on Linux without changing its name?
>>53903025
Linux kernel has no concept of hidden files.
>>53903025
http://en.wikipedia.org/wiki/Steganography
>>53902557
>I'll start: create a file with a dot prefix.
I think you mean, "create a file with only an extension".
>>53902775
>actually it's even more retarded why the explorer denies stuff like this when you can still do it in cmd
Given that their goal was to remove file extensions from the Explorer UI, no, it's not. The fact that they allow power users to do what they want from the command line is a nice bonus.
>>53902658
>It can't just have an extension and no name.
Yes it can.
And sometimes such file are even required.
Like .gitignore
It's only the interface that's blocking you.
So I end up having to copy a .gitignore file from a different repository, empty it and use it for myself.
Annoying as fuck.
>>53902557
try to delete some japanese porn
>filename too long
Have to move it to a lower directory before I can delete it.
Case-sensitive filenames
>>53902557
Symlinks.
You can only make them with the command line interface.
Is there some shit legacy reason for this?
Consider the following scenario:
You have a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 Service Pack 1 (SP1).
You use Windows Explorer to try to copy files or folders in order to paste them into some other folder.
The files or folders that you copy have paths that exceed the maximum allowable path length.
https://support.microsoft.com/en-us/kb/2891362
>>53903159
>things windows can't do
>you can
?
>>53903096
I remember some fuckery back when Vista added the various symlinked directories in your profile dir to make old software work. If you dragged your profile dir to an external drive trying to back it up, it would recursively create something along the lines of AppData\AppData\AppData\AppData\AppData....... until you got sick of waiting for it and cancelled. The result could not be deleted by any real means because "path too long".
The only real ways to get that shit out were either boot to Linux and delete it from there, or reformat the drive.
>>53902973
That's pretty fucking funny. Thought this thread's argument was pointless, but the fact that Windows can't even delete them makes me kek
>>53903191
You can't create them with UI and you can't delete them with UI.
You can create them in console and you can delete them in console.
>>53903078
try creating a file with the name ".gitignore." with the ending dot
>>53902597
>if I don't need it nobody does
typical wincuck
>>53903260
it applies to applefags too
>why would you need a file explorer on your phone anyway
>>53903221
Only if you know the trick. Otherwise you just get "cannot find the file" error from del.
I remember back on Win98, if you put a bunch of stuff in a folder and used command.com to rename it to an alt+254 character, it would appear in Explorer as _. Trying to open, rename, copy, move or delete it just generated weird errors. The only way to do anything with it was to know that it was an alt+254 and rename it with command. I used this to hide shit on the family computer once, right on the desktop.
>>53902557
Install fonts per user and without admin rights
Mac OS X, Linux, BSD, X11, Fontconfig, Gnome, KDE, XFCE, etc can do it for the last 15 years and Windows font management is the same shit it was in Windows 95
Fuck Windows, fuck this fucking shitty OS that only legacy software and monopolistic shady practices still keep it around
>>53902557
Support UTF-8 across the system
It's 2016, every other OS can handle Unicode gracefully, Windows still uses the retarded outdated UTF-16 internally, 8bit legacy regional encoding in terminal, many desktop applications (bundled and Microsoft's) output 8bit ANSI text files, BOMs in UTF-16, UTF-8 is broken and... it STILL uses CRLF line endings unlike every other OS making interoperability a nightmare
In short Windows can't even handle simple text files consistently. Fuck this shit
>>53903119
>renames "makefile" to "Makefile"
>nothing happens
>rename "makefile" to "makefile_" then "Makefile"
Annoying as fuck.
>>53903667
Works for me.
>>53903667
I remember this being an issue, but now it works in 8.1. I know in XP you needed to change the name, not just the case, or it would ignore your request. I don't know if they fixed it in Vista, 7, or 8.
>>53903667
It works, but you need to refresh explorer to see the change.
>>53904021
Yes. This is how it behaves in my 8.1 as well.
BTW, "rename" is kinda long. Try "ren" instead.
>>53902557
you _can_ do that on windows, on any version, its just explorer that limits yourself
like case insensitiveness, the os is mostly made to avoid normies to fuck up on minor stuff, which isnt bad in itself, use cmd if you want to do "weird stuff"
>>53904081
>the os is mostly made to avoid normies to fuck up on minor stuff
Is that why it allows spaces on file and directory names?
>>53904137
Why wouldn't spaces be allowed? Every real OS in the past 20 years allows spaces.
Werks fine.
>>53904137
The only reason why spaces are discouraged on Looni is because of Bash and so many fucking scripts that rely on it.
And the only reason why Bash has so much trouble with spaces is because they decided it was too much work to always accomodate the possibility.
So they just said let's just discourage using spaces in file names.
>>53904286
Windows software has issues with spaces sometimes too when it doesn't process them nicely. In batch and Powershell scripts you have to quote things that might contain spaces, like in Bash.
On both platforms, the problem isn't people putting spaces in names, it's scripts that break when they hit a space. It's so easy to make a script process them correctly, the only excuse for not doing it is ignorance, laziness and incompetence.
I've used windows for 18 years and never had to deal with prefixed dots or postfixed dots in my filenames
Fucking Linux users are such autists worrying about bullshit like that. Grow the fuck up.
>>53902973
Try the UNC path.
>>53904168
>>53904286
You obviously are newfags who weren't around when this "feature" was first introduced and started fucking up literally everything.
>>53903593
>Windows still uses the retarded outdated UTF-16 internally
It's not UTF-16, though. It's... Uh... UCS-2! I think. IIRC UCS-2 is a 2-byte character with no variable-length characters, unlike UTF-whatever.
>>53904466
It caused trouble at first because nobody was used to coding around it and old software didn't know about it. Windows actually made the transition pretty well. Old programs that didn't know about long filenames just saw shortened names like MYDOCU~1 and worked fine so long as you knew which name to select.
Just because transitioning to something caused issues does not mean we should avoid it 20 years later. The transition from 16 to 32 bits was bumpy as well, as was 32 to 64, but it's not an excuse to demonize 32 and 64 bit systems and continue using Windows 3.11 (without win32s) in 2016.
Similarly with UTF-8. Moving to it caused some hiccups and headaches with things like counting how many characters are in a string, but it fixes tons of character encoding messes.
>>53904563
I'm pretty sure they have had full UTF-16 support since 7. I remember having some issues testing my UI in Windows XP because some characters not supported in UCS-2 weren't being displayed properly on XP but worked fine on 7.
>>53902557
Create a folder named "con".
>>53902557
But can you delete a file starting with a - (hyphen) in Linux?
>>53904564
Except 64-bits is actually useful. Spaces in file names are not a feature, they're a bug. Nobody needs spaces in file names, that's why the underscore character was invented.
>>53904633
rm -- -myfile
Yes I can
>>53904137
>Is that why it allows spaces on file and directory names?
>>53904466
>You obviously are newfags who weren't around when this "feature" was first introduced and started fucking up literally everything.
Not really connected, but I remember in the Windows 3.0 & 3.1 days, there was a tool that would allow you to give "human readable" names to your files. So instead of "1994Q3rp.xls" you could have "1994 Q3 Revenue and Profits.xls". AFAIK, it was only in terms of seeing the files as such on the Desktop and in Explorer (or whatever it was called when you double clicked a folder on the Desktop, was it called Explorer before Win95?).
Ah, the good ol' days of crazy weird add-ons to an OS that provided plenty of ways to extend it (system-wide hooks, DLL injection, etc.).
>>53902557
At least Windows can gather personal informations on billions of users.
>>53904633touch -- -lel
rm -- -lel
>>53904615
>I'm pretty sure they have had full UTF-16 support since 7
That may be since the site that reminded me of the term UCS-2 mentioned that it was used up to Win2k and XP.
However, I have no idea if the system really supports UTF-16 or if it's really just .NET that does, or if it's just a smart conversion layer. Literally all the code I've ever written for Windows (going back to ~1995) used either ASCII or UCS-2 (wchar_t/TCHAR/_T()) using 'dumb' _tcslen or wcslen type functions to manipulate them. This includes software that was internationalized to a few Asian languages.
DESU I have no idea why it wasn't ever a problem.
>>53904649
Underscores are ugly. Spaces are convenient and are no trouble at all unless you're too retarded to put "quotes" around the name. There are so few Windows programs that have trouble with spaces these days it's pretty much a non-issue unless you're looking at certain poorly written, usually expensive specialized packages.
>>53904615
>because some characters not supported in UCS-2 weren't being displayed properly on XP but worked fine on 7.
By the way, what kinds of characters? Were they just very unusual characters, or unusual ways to encode characters that were normally encoded a different way, or something else?
>>53904663
>yfw it took Windows almost 20 years to do something Unix had been doing since the late 70s, and it needed third-party software for that
>>53904763
What trickery did you use?
>>53904739
So basically they broke everything up and wreaked major havoc just because "it was ugly"?
>A good example is Windows' long filename support. In an attempt to allow for long filenames in Windows '9x/ME, Microsoft deliberately broke the FAT file system. They stored the extension information into deliberately cross-linked directory entries, which is probably one of their dirtiest kludges ever. And if that wasn't enough, they made it legal for filenames to contain whitespace. Because this was incompatible with Windows' own command line parsing (Windows still expects the old FAT notation) another kludge was needed, and whitespace had to be enclosed in quotation marks. This confused (and broke) many programs, including many of Microsoft's own that came with Windows.
>>53904081
case insensitiveness is good
>>53904763
Nice Cyrillic, faggot.
>>53904758
> >yfw it took Windows almost 20 years
That's unfair because
>and it needed third-party software for that
Windows didn't do it properly until whenever long filenames were introduced, which was later.
I honestly don't remember the history behind the 8.3 filenames. I think it came from CP/M, but I don't know WHY DOS used it.
Wikipedia says
>The filename convention is limited by the FAT file system. Similar 8.3 file naming schemes have also existed on earlier CP/M, TRS-80, Atari, and some Data General and Digital Equipment Corporation minicomputer operating systems.
Meh. I also don't recall why FAT was created the way it was. I'm sure it made sense on the crazy primitive consumer-grade hardware.
>>53904813
It's part of an effort to make OS and computers the most intuitive and human-friendly as possible.
More normies = more money
>>53904794
con
>>53904833
:^)
>>53904840
muh inodes
>>53904763
That's weird, here is my result :
>>53902557
create a file with a colon in it (NTFS does support it, though)
>>53904732
>I have no idea why it wasn't ever a problem.
The most common Asian characters fit into the first 16 bits just fine; they take up most of the UCS-2 compatible Basic Multilingual Plane of Unicode, but they're there. It's evil, but I guess you can often get away with invalid UTF-16 handling.
UTF-8 on the other hand... let's just say many 'murican devs don't seem to test their code with anything except ASCII. Even when a field is supposed to accept arbitrary Unicode strings.
>>53902557
you can. you have to open it and save as, the put " " around the new name
>>53904813
Yes. It was a kludge when it was implemented, to shoehorn the new thing into the existing system. But we use filesystems now that support it without the kludge. Quotes aren't exactly a kludge, they're the syntax UNIX used for ages.
The reason wasn't so much "it was ugly", it was that people were asking "Why is it that I have to name my file like 'GDMALTR1.DOC' on Windows while a Mac will let me have 'Letter to grandma 1.doc'?"
Also it wasn't the spaces that made the FAT kludge necessary, it was getting past the 8.3 length limitation, which I think you'll agree was very useful.
>>53904946
>let's just say many 'murican devs don't seem to test their code with anything except ASCII
I'd say "the vast majority of devs" regardless of region. I don't blame them. UTF-whatever is way different than the dumb ASCII strings that they dealt with all through college and in the vast majority of most work you're going to get in the Western world. Add in the fact that UTF-8 looks just like ASCII unless you know better and BAM.
Hell, it's only an issue today because the Web has opened up the entire world as a market. But most of the world is still poor. If you can just sell shit to Americans in English, you tapped a ~17 trillion dollar economy.
>>53903260
>linux can do it therefore everything else should to
typical lincuck
>>53905323
Some songs and albums have dots at the start of their names. Also, it's useful if files that are common on other systems are allowed on yours. It makes interoperating a lot easier.
>>53905375
>Some songs and albums have dots at the start of their names. Also, it's useful if files that are common on other systems are allowed on yours. It makes interoperating a lot easier.
It's 2016, why are we even dealing with files this way?
Back in 2001, I was promised a new filesystem based on a relational database model. Filename is just another attribute. There shouldn't even be any rules for filenames, other than, "it has to be a valid string of any kind".
>>53905449
Yes, then it proved too difficult for MS to get out in time for Vista. After that, focus shifted from innovation to eyecandy and reducing resource use to make these new netbook things happy.
Today Windows has lost almost all the cachet it had before, with phones and Macs being the thing to have. So their hope of regaining marketshare isn't to make something innovative like that, but to make Windows a sort of universal OS. They want to add support for iOS and Android apps on Windows phones, and Linux programs on desktop Windows. They want to be the one thing that can run everything, not the weird thing with this new database filesystem feature that's really powerful but that you have to learn.
Most users would run to something else sooner than learn the new system. A major strength of Windows is that it's what most users know already.
>>53902672
>kde
disgusting
>>53903119
NTFS does support it but Win32 do not.
>>53905583
A fair sight prettier than Win10. At least they have a unified color scheme across the DE, not like light here and dark there.
>>53905449
B-but there is one, anon. It's called HAMMER.
>>53905582
>They want to be the one thing that can run everything
In the process becoming more and more like Frankenstein's monster.
>>53902557
>simple things Windows simply can't do.
Run without spyware.
>Bonus round: Windows 10
Run without spyware made by Microsoft.
Protect my freedums
>>53904753
I don't remember exactly now but it was in the mathematical alphanumeric symbol table which is higher than U+10000.
I worked around it by replacing the problematic character with its "ASCII-equivalent".
>>53902673
>set up XAMPP stack or something
>need to create a file name.htaccess
BAD END
>>53906222
Found it, it was U+1D4C1.
Not the end of the world, but it looked nice in the formulas.
>>53904563
>no variable-length characters, unlike UTF-whatever.
UTF-32 is not variable-length is it?
>>53906397
Unicode also includes codepoints for diacritics which can be combined so the number of UTF-32 glyphs does not tell you the length of the string either.
Unicode is complex because our languages are.
>>53906435
>Unicode also includes codepoints for diacritics which can be combined so the number of UTF-32 glyphs does not tell you the length of the string either.
It tells you the length of the string. It just doesn't tell you the number of characters.
>>53904563
It's a legacy thing. There's some pretty nasty things sitting around in windows because less than perfect decisions were made a while ago. Microsoft's primary focus seems to be compatibility, especially after the whole vista fiasco.
>>53904946
UTF-8 is designed the way it is so it can simply be thrown into non-aware programs and not cause problems. If a UTF-8 string doesn't work, it's usually not even the direct fault of the programmer, but the underlying system (ie windows or whatever is used to draw the glyphs).
>>53906641
>Microsoft's primary focus seems to be compatibility, especially after the whole vista fiasco.
This. One of the big reasons to use Windows is that it remains compatible with amazingly old software. You can still use most 32 bit programs from 1995 on a new Windows 10 machine. And if you get 32 bit Windows 10 you can even run a lot of old 16 bit Windows stuff with no trouble.
>>53906007
download it here: ipfs.io
>>53905449
naming rules are mostly so that you don't have to fuck around with escapes in the terminal/cmd and so that the char size is smaller in the file system. Size is not as big a problem with 1TB drives and shit though.
I really do want a tagging file system though
>>53907646
πfs best filesystem!
https://github.com/philipl/pifs
>>53907741
Not a filesystem but great: http://www.tagspaces.org/
>>53907753
top laff
>>53902672
i honestly never figured out how to change the wallpaper in plasma
>>53907885
which one? there is a wallpaper for each space, window, gadget bar, screen, virtual desktop, layer
>>53903260
Funny, I've seen linuxfags with that type of logic more than wincucks.
>>53907762
neat. I'll check it out
>>53902759
Where the fuck is .htaccess located in Linux? Fucks sake I have gone through everything and just need to make a simple fokken change
>>53906778
>you can still use most 32 bit programs from 1995 on a new Windows 10 machine
only if they were well coded and don't exploit undefined behaviors.
>>53902759
Windows uses file paths to identify files. If it doesn't have a name then it can't handle your file.
>>53907885
Which one?
>>53908164
not joking: the internet
>>53908520
Ay fite me tho
>>53908580
Even indians are better photoshoppers than you
>>53908597
what about the odd ones
>>53908580
MODS CHILD PORNOGRAPHY HELP
>>53908580
MOODS MOODS MOODS
>>53902557
>I'll start: create a file with a dot prefix.
My computer is full of these. What are you talking about?
>>53908617
>>53908632
Back to tumblr, faggot
>>53902557
>>53908189
Yes. Or if they exploit undefined behaviors that were preserved in a compatibility mode.
>>53908286
Why is extension even a thing? It's just part of the name. Maybe if I type a name starting with a dot, that could be the name and it has no extension?
>>53908680
This is a valid warning. It's trying to help you. You're making a grave error in deleting Utena.
>>53903078
cmd.exe
move "new document.txt" .gitignore
>>53903025
you can create a .hidden file, then add one file name per line, save and refresh your file explorer
>>53911198
Or echo > .gitignore. Note that this will put stupid text "ECHO is on." in the file, since Windows' echo command doesn't just generate a blank line when run by itself like the *nix one.
>>53911313
Note, this only hides it from explorers that pay attention to this. It won't hide it from ls the way that Windows' attrib +h does. The only *nix equivalent to that is putting a dot at the start of the name.
>>53904444
It's just little things where windows fails, no need to get upset.
>>53908680
Kek
>simple things windows simply can't do
Privacy.
Security.
>>53904794
you can check that with a hex editor.
>>53911359
>Note, this only hides it from explorers that pay attention to this.
what exactly do you need? most of the time i hide files just for not seeing them. You need to hide the files from the ls command or something like that?
>>53911487
It's a GIF... I don't see a comment field and the only comprehensible things I see are GIF89a and NETSCAPE2.0, neither of which say anything about it.
>>53911532
I don't. The .hidden approach sounds good to me. I generally want my ls to do ls -A anyhow.
>>53904763
>>53904794
sop or con in Cyrillic
>>53911631
Yah, you can make them just fine using cmd.exe and then manipulate them in Explorer. It's not as bad as with con where you have to use trickery and then you can't do anything with them in Explorer.
>>53903260
Holy shit the irony is strong.
>>53911575
>It's a GIF
oh i'm referring that he used similar characters but with different hex value.
just in case you need it i think it can be done if it may interest you:
http://superuser.com/questions/359784/hide-files-in-linux-without-using-the-dot
there's a lot of things you can manipulate from the .bashrc
>>53903260
>>53903286
>>53904131
>>53905323
>>53907987
>>53911658
>b-but muh muh OS! muh OS is best OS! muh OS is holy! fuck of mom, I'm fapping off to muh OS!
That's why I come to /g/, thanks.
>>53912313
https://www.youtube.com/watch?v=d85p7JZXNy8
/thread
Funny to see people fight over shit like that on the webs.
>>53902672
theme?
>>53906641
>If a UTF-8 string doesn't work, it's usually not even the direct fault of the programmer, but the underlying system (ie windows or whatever is used to draw the glyphs).
When you bring in enough libraries, middleware and whatever into the mix, at some point stuff will inevitably get translated back and forth between UTF-8 and some other encoding. This is where things break if your test developers were too incompetent to include at least some kind of non-ÄSCイー data in every. fucking. input. that could possibly be expected to handle it.
>>53902741
Granted that Dolphin is a great file manager, I would not use it as argument against Windows.
It's like using Adobe Photoshop as an argument against Linux.
It isn't an OS flaw, it's just soemthing that happens to exist only for one or the other OS.
>>53902672
>>53902557
literally rename it you cuck
>>53914233
>winblows 10
>calls other people cucks
>>53914233
>test.txt.txt
>.txt.txt
>implying
>>53914287
still has a dot prefix freetard
>>53915300
oh wow, you found one goofy instance where it works. Too bad it doesn't related to any software that uses files beginning with a dot
>>53912313
thats a little overkill but true
>>53902658
>Create a file named con, prn, aux, etc., even if you add an extension like con.txt.
Why is that a thing? Just tried con.txt prn.txt and aux.txt and I'm getting error every time. Are those some os-related names or something?
>>53915468
>prn.txt
It's the file-name under which win10 phones home all your pron searches. It's too important to them to have it compromised in any way.
>>53915468
They're CP/M (1973) and DOS (1981) names for peripheral devices. Microsoft's OS business started with shitty little microcomputers running these and Windows still retains some compatibility with them.
It's not entirely unlikely some obscure enterprise or government system depends on that feature, actually.
>No SSH
>2016
Legit WTF!
>>53915956
Windows 10 has native ssh
>>53915956
CMD sucks. There's nothing to do, unlike any *nix which will have a multitude of useful programs with text interfaces.
>>53916049
>Windows 10 has native ssh
yeah, but i'm not using w10
also, change input language globally instead of per application. think w10 does that now. still not gonna use it though.
>>53902557
>using windows
>>53916712
>>Devices
>BIG
>DATA
bash
>>53915642
I used to work with some software that actually used COM that way. It was some old shit that had been ported over and over from DOS.
