Earlier quoted context omitted.
> Circa 1998 I was a teenage Linux zealot who would attend LAN parties carrying a Linux box. Arch, I suppose.
if it were arch you'd know already
MS Teams channels cannot contain MS-DOS device names
251–260 of 364 posts
Re: MS Teams channels cannot contain MS-DOS device names
#252Earlier quoted context omitted.
You need to clean slate the entire world because everything is interconnected. If , for example, you want files to be more than streams of bytes then you basically have to re-invent the Internet as well. The older I get, the more I realize that we don't need a clean slate OS. If you pick any modern OS right now, the most annoying parts are never the parts that were from 30 years ago; it's almost always the newest thi…
The opposite is true. You can convert anything to anything at the boundary. The beauty of looser coupling
Re: MS Teams channels cannot contain MS-DOS device names
#253This is such a Microsoft thing to do. DOS compatibility will haunt us for the rest of this century at least.
Sometimes I wish we had fresh clean slate OS. Not the baggage of DOS or Unix... Something modern and sensible without insanity of either system.
Capability-based microkernels have been exciting research projects for decades, and Google has apparently made one that achieves acceptable performance, which was a significant challenge.
Re: MS Teams channels cannot contain MS-DOS device names
#254I was about to say "Which is essentially leaking the existence of something terrible inside. They should be embarrassed to say something like this in public. Like saying you can't have %s or $PS1. Why the hell not? What are you doing with this user-supplied input?" But maybe it's more about what everyone else might do with a channel name. Ie they might cut & paste it anywhere, and I guess windows users aren't expecte…
Re: MS Teams channels cannot contain MS-DOS device names
#255Earlier quoted context omitted.
I think it was RedHat. I had tried Debian first but switched to RedHat pretty quickly afterwards. (Back then, RedHat had nothing to do with "enterprise", it was just the most polished Linux distro around. Ubuntu didn't exist yet.) (These days FWIW I use boring old Debian, and I'm not a zealot about it. It works for me. Use what works for you, I don't care. I have a separate machine for gaming and it runs Windows. I k…
Back when Redhat was the name of the enterprise releases and the open source releases.
Re: MS Teams channels cannot contain MS-DOS device names
#256Still incredibly sad, but not as insane as if you couldn't use the names inside a chat.
Re: MS Teams channels cannot contain MS-DOS device names
#257Re: MS Teams channels cannot contain MS-DOS device names
#258Re: MS Teams channels cannot contain MS-DOS device names
#259This is most likely due to those names not being allowed for files or folders in the Windows file system. MS Teams channels create a matching folder in SharePoint where file attachments are stored.
Microsoft, when confronted with a problem, think "I know, I'll build it on top of SharePoint."
Re: MS Teams channels cannot contain MS-DOS device names
#260Earlier quoted context omitted.
It's still being played heavily and professionally in Korea and there are many non Korean tournaments too. I watch pro matches everyday!
> heavily Sadly not the case, as much as I love ASL the scene has zero new blood. SC2 really killed the Brood War scene, and League of Legends really killed SC2. The days of packing an aircraft hanger with 30,000+ fans for OSL finals are long gone. I was invited to the Stormgate alpha, and while I can't say anything about it (NDA), I am hopeful it will bring new life into RTS esports.
Is it in it's heyday? No. Is it still fantastic? Yeah.
KESPA killed Brood War primarily because Blizzard forced them to. Then KESPA itself died.
Lots of great BW still being played no question about that