What you expecting called natural sorting. Mac employed natural sorting back in 90s. What you get is legitimate Alphabetical sorting which used by Linux and Windows. Natural sorting parses tokens in the string and compares them. Alphabetical sorting compares two strings by comparing individual characters at same index (position). Alphabetical sorting is quite common as it simpler to implement (or rather harder to screw up) and yields predictable results

One of many libraries for Python which implements natural sorting https://github.com/SethMMorton/natsort

Too lazy to read article but title sounds silly. One can fart and it will have sound wave which can be unique. And you don’t need entire power plant and quarter of UK water consumption for that

Emm, yes it is. Watch Putins’ interviews where he says Ukrainians is fake nation. Dude is mental and thinks he is savior of slavs. “Peace” is just giving Russia break which it desperately needs to resume invasion later.

What is crazy is that Mac version is more stable than windows in my experience. Still shit, though

Here we go, even drugs are low quality now

Everyone screaming about democracy just died. In fact it was always dead. Electoral college system basically disregards voter who does not vote for winning party. It’s a system where you have only two choices, thus less competition, thus lower quality of candidates. Then everyone is like “is this best US can do?”. Let alone gerrymandering. People should be rioting, not because Trump won, but because system is not democratic.

No, that means you falling into author’s bait where they misuse term “delete”. Refactoring is not equal to deleting. One can be result of another. But the truth is that extendable code needs to be modular to be extendable. And modular code is easy to refactor. Author couldn’t not name it “Write code that is easy to refactor, not easy to extend” coz it’s even more dumb

No, title only

Right, but my initial comment was about article’s statement being wrong. Refactoring in the way you described will make code harder to delete which is bad according to the article.

I don’t understand too. Are you suggesting me to drop bunch of features in the product?

TLDR;

My current project has mostly easy to delete code and not easy to extend. Why? Coz shit was copy-pasted 50 times. It’s not fun to work in this project.

Post commit hook to push + always squash on merging feature branches

I mean, mom could be right. Maybe there’s a rule on router to block Fortnite servers after 21:00. She just doesn’t tell that she the one turning it off

He just applied Russians’ favorite soviet era saying “those who is not with us is against us”

After closer look I can say this is great idea. Initially I thought this messes with Lit’s lifecycle bringing React’s lifecycle drawbacks but seems like it’s not. I think at some point you should get in touch with Lit devs and see if it can become part of Lit lab or even Lit itself

Is it better than React functional components in any way? I don’t see benefit over React functional components or even Lit’s class components

Library built this way because it supposed to be flexible and provide ground for complex usecases. It can only be flexible if your API works with simple abstractions which you can then compose. It’s not driven by “I need this specific utility for this specific scenario”. That would be zoo you have in JS where you have 10 ways to iterate over array and 9 of them wrong for your scenario.

Java’s OO is great because they design library with SRP in mind making sure there is few but good ways to do things.

BufferedReader cannot accept file name because it makes arbitrary reader… well buffered. It’s not BufferedFileReader, even that would accept something like Path or File, not string, because File can be remote file, should Reader now know all possible local and remote protocols and path formats? What else it must do?

Having it designed the way it is, allows Java to have utilities for various scenarios. Your scenario covered by standard lib too. See Files.readAllLines which, surprise-surprise, built on top of BufferedReader.

Char count is poor complexity metric. Perl is better than Python with your logic as it is more condensed.

Can anyone actually tell what exactly complicated in Java? Verbose, maybe it was at some point but I find it very straightforward and easy.

I don’t know german but it seems to be more logical to have one word for “health insurance card” since it describes one class of objects. Better than spelling 3 nouns where one partially describes what object is and other nouns act like clarification