Follow

powershell horror 

powershell file redirection writes output in utf-16 D: D: D:

re: powershell horror 

@jookia Really? Seriously?

The move towards UTF-8 for MS is taking way too long.

re: powershell horror 

@loke @jookia They'll never do it. They don't give a fuck about anyone who isn't a Windows fanboi, and to Windows fanbois, Unicode == UTF-16.

Signed, a person who worked with a Microsoft fanboi.

powershell horror 

@jookia Gotta entrench a shitty decision harder. Because Microsoft actually fixing things is less likely than hell freezing over.

re: powershell horror / pretty much totalyl unrelated 

@koz_ross @jookia

/much/ less likely, considering hell sort of /is/ frozen over as per the 9th circle (if we're considering Dante to be canon anyway)

Also I never used UTF-16 /anything/ because all I hear are horror stories about it, and it makes me mad that it exists. Is it even backwards-compatible with UTF-8 in the same sense that UTF-8 is compatible with ASCII?

re: powershell horror / pretty much totalyl unrelated 

re: powershell horror / pretty much totalyl unrelated 

@jookia @SyrupSlushie UTF-16 is worst-of-both-worlds. Unlike UTF-8, it's not backwards-compatible with ASCII or space-efficient as an encoding. However, it's also not fixed-width either. Plus, it's also endianness-dependent (again, unlike UTF-8).

There's a reason nobody but Microsoft uses this piece of garbage. But, true to form, given a range of solutions, Microsoft will pick the worst.

re: powershell horror / pretty much totalyl unrelated 

@jookia @SyrupSlushie OK, I stand corrected. Nobody but Microsoft, or Haskell's 'text' library. But that second thing is a fucking cruise ship of bad decisions and suffering.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!