It doesn’t have to be the default to be built in, tho. It could be an overloaded function, having the “default” be the typical convert-to-string sorting, and an overloaded function that allows to specify a type.

It’s just such a common thing, wanting to sort a list by different types, that I’m surprised there hasn’t been an official implementation added like this. I get that it a simple “fix” to make, but I just think that if it’s that simple yet kind of obscure (enough that people are still constantly asking about it) there should be an official implementation, rather than something you have build yourself.

Right, but you have to make that comparator yourself, it’s not a built-in part of the language. The only built-in comparator converts values to strings and compares them in code units orders.

Also, that technically isnt type-safe, is it? If you threw a string or a NaN at that it would fail. As far as I knew, type safe means that a function can handle type errors itself, rather than throwing an exception. So in this case the function would automatically convert types if it was type-safe to prevent an unhandled exception.

I think the main shortcoming here is that there isnt a way to specify the type to sort as, instead you have to write the function to compare them as numbers yourself. If it’s such a simple implementation, why isn’t it officially implemented? Why isn’t there a sortAs() that takes two args, the input list, and a Type value? Check every element matches the type and then sort, otherwise return a Type Error.

Well, clocks are just mechanical sundials. Before clockwise, there was sunwise (or deosil), and clocks’ movements are based off of the movement of a shadow across a sundial.

2K is supposed to refer to a 2048x2048 square 1:1 aspect image, same with 4K being a 4096x4096 image. This term is correctly used a lot when referring to texture sizes. A 4K texture is 4096x4096 texels.

I think the term started getting mixed up with people discussing what resolutions benefit from texture size increases. Generally, if you are running, say, 4K textures, you would really only always benefit from that if you have a 2160p screen, just because lower resolutions dont have the definition to actually display those texels. So, people start inter changing “4K screen” and “4K-benefitting screen” and we end up where we are now.

Lmao Ubisoft of all folks should shut the fuck up about UI, they are literally the source of the meme about cluttered and overly complicated UI. If Ubisoft is complaining about a UI I have to automatically assume it is a good UI.

Also, if AAA developers have been paying attention for the last decade, they would know that consumers have valued quality and shown disdain for MTX since MTX started becoming pervasive. MTX overall can generate a lot of revenue, but it isnt sustainable, hence why there is always some sort of FOMO characteristic included with the MTX system, making things limited time and constantly shovelling low effort “new content” to fill out the MTX system.

I feel like a solution similar to m.2 could work, holding the module in place with a screw. I dont think the m.2 connector would suffice as it only has 67 pins and DIMMs have I think 288 pins, so that’s quite a difference. I do think SODIMM has less pins, but not much less, definitely not to the tune of less than a quarter as many.

Having recently looked inside my steam deck to upgrade the storage, I honestly think they would have had room for at least one SODIMM slot, but the tradeoff is increased thermals, more power draw, and probably some design constraints around the pcb leads possibly leading to increased overhead or latency. I agree that a new form factor would be best to address these issues. It would be cool if something similar to the SXM socket came out, having a pad of pins so you can increase the amount of pins while taking up the same space.