Of course no.

DOOM wasn't fine on Am486DX4 100MHz and Ziggurat Vertigo was like 5fps at best on it.

Ziggurat Vertigo was Quake, not Doom.

>> DOOM wasn't fine on Am486DX4 100MHz and [Quake's] Ziggurat Vertigo was like 5fps at best on it.

Are you happy now?

> there people that use the caps lock key?

Yes, of course. Because I programmed my Keychron for it to be a regular LShift. Works very good for my hands. But when I'm on the regular keyboard I have a real trouble with typing or entering passwords, but it's manageable.

> Cant remember using a function key

I use it for the volume control when I'm in a fullscreen app or with both hands on the keyboard - but only because my Fn is on the right and volume controls on F10-F12.

You need Fn anyway because even 16" now come without a navigation block and even if you have it (asus tm420 though they ditched that too) you have no way to make PrtScr, Break, ScrollLock.

The real atrocity is placing it on the left side when 90% of the most used combos are on the right eg Fn+arrows for paging and home/end.

It could be way better if Fn was on the place of ContextMenu - Thinkpad already used it for the stupid PrtScr and now even more stupid Copilot key.

I wouldn't buy a laptop that requires the use of Fn for any key I commonly use. I don't particularly care about PrtScr, Break or ScrollLock. Can't remember the last time I used either of those. But Home/End/PgUp/PgDown are requirements.

> I don't particularly care about PrtScr, Break or ScrollLock

Glad for you. But the moment you need to hit Ctrl+Break...

> They earned enemies for life. Some of us care about business relationships. Broadcom is dead to me and anyone that will listen to me.

That's the thing: Broadcom don't. Care, bother, whatever. You are not even a blip.

Ah, yes the famous sticks with "AK-74" and "RPG" on them.

It's also amusing how the stupid Soviets took two wars to subdue that tiny, sparsely populated country had that country been armed with nothing but sticks, stones, and Molotov's; while the mighty, eagle screeching top-tech first world economy with a giant student debt took checks notes two decades to accomplish check the notes again replacing Taliban with Taliban in a "country been armed with nothing but sticks, stones, and Molotov's".

you appear to have misread my comment. I didn't say the Chechens were unarmed.

Verbatim:

> tiny, sparsely populated country had that country been armed with nothing but sticks, stones, and Molotov's?

It’s cheaper than landing ten divisions of Marines.

Because the world is actually very small and Ukraine winning helps the US

It is in this position thanks to US in the first place.

Dixie Flatline says hello.

> The Windows ecosystem handles it fine (by using a single standard). Linux doesn't. That's its problem.

It's always funny to see how the fanbois treat their way as the one and only 'True Way'.

I didn't say it was the one and only True Way. My intended meaning - which I admit I may have poorly conveyed - is that tools from the unix ecosystem are intended to work on unix conventions, and do, and that works. Windows has different standards, which is also fine, but it follows that you shouldn't expect unix tools to follow Windows standards even if you make them run on Windows. This is like getting Windows software to run under WINE and then complaining that it doesn't use /n newlines and that it should change to accommodate Linux (or whatever). No, a Windows program will follow Windows standards even when made to run on a unix-like. And in the same way, unix-family software is going to follow unix standards even on Windows.

Your entire framing is wrong imho.

Multi-platform is very easy and a solved problem if you try juuuust a tiny amount.

For example the Rust stdlib iterator for lines() handles both conventions. It just works. Very easy.

I live in a cross-platform world. Line endings in text files should not be a breaking problem because some CLI tool refuses to support both. That’s just plain bad software engineering.

I expect Unix tools that process text files to be capable of supporting text files that have different conventions. This is very easy. Refer to previous comments on stubbornness out of spite.

Even Python has str.splitlines, which accepts a range of line separators (not just LF and CRLF), and the same when iterating over a file handle (which iterates over lines).

You're right, this is a complete nonissue.

UNIX and Windows aren't the only OSes on the planet, even though UNIX folks tend to assume that.

Heck many mistake UNIX with GNU/Linux even, and then complain when given a UNIX that isn't a Linux distro.

I think the point is that line endings are a really, really stupid hill for either Linux or Windows to die on. The day when any programs should have cared about line endings came and went decades ago.

Don't do the absolute paths. Do the environment.

Maybe someone out there mixmashes PowerShell, bash, sh and cmd scripts from different platforms in one session - but usually it's one, quite straightforward 'flow' which requires a quite specific environment.

You forgot the paranoia after it. Along with surrendering anything in the name of anti-terrorist measures. And protecting children.