> It’s really sad to see how quickly Hacker News, of all places, is jumping head first into welcoming age restrictions and bans with barely a passing thought to what it means.
I'd avoid such generalizations. It's a divisive topic, but from what I've seen here, there's always lots of criticism (regarding implementation at the minimum) in the comments and it definitely isn't clear that most would be jumping head first into anything.
1. The pipeline is simple to split or cut entirely, though. No reason to grow it into a monstrosity, but many reasons to not do it. This problem sounds similar to growing a function too much.
2. I agree in general when talking about more complex operations. Simple transformation and filtering rarely needs intermediate variables for readability or debugging. And the naming of result variable already describes the final collection.
3. Never had to deal with this kind of code but I haven't used Kotlin.
1. Yes, you hit the nail on the head. It basically requires people to be more cognisant of this. However, I think telling people to break stuff out into intermediary variables is much easier to argue for than whether the function is getting a bit too long.
2. Yes, easy filterings usually don't need to be broken down/named, but it really depends. At the very least, if the culture is to name intermediary values, you might accidentally get useful information from the variable names even if people weren't diligently writing explanatory why comments.
3. This isn't Kotlin related, it is just that if you do not have a language/codebase with branded types (or some type system property I don't know the name of), the type system might only infer the base primitives of the result, ending up with stuff like the type I mentioned.
> Yeah, it’s more lines. But each step is just sitting there. No decoding required.
I actually think the first code block is easier to read. It's a familiar (to me) and simple pattern that is quick to read. I don't get how it would require more "decoding" than the second example which is more disjointed and needs more "parsing" for such a trivial case. Maybe it's about what you're used to?
I agree there are downsides to chaining. With more complex operations it can complicate debugging, and readability can suffer, so chaining is not a good fit there.
> Especially small and independent artists should absolutely avoid any software that introduces additional risk of project failure as one such crash scenario at an advanced project state has a high potential of total destruction.
I can't really comment on kdenlive, but this sounds kind of overly dramatic to me. I mean, I hope you save and take regular snapshots/backups in case your disk, RAM or just human error destroys anything substantial.
> Desktop Linux is not useless, but it is really just sub-par compared to Windows.
Each to their own. My experience is the opposite (I use KDE). I have to use Windows at work and it's always such a pain. At least Windows 10/11 finally has multiple workspaces natively and some keyboard shortcuts for managing windows (ironic), but I would have preferred to stay in Windows 10.
Now Windows doesn't even support proper suspend anymore and it won't stay in the "modern standby" either. Constantly waking up and doing god knows what with fans screaming. When I take a look what it's doing, task manager claims that nothing resource intensive is going on. I'm guessing it's hiding some internal processes. It calms down when I put it to sleep again. Sorry for the rant, I better stop before I start.
yes the flaky sleep is what did it for me - laptop would randomly boot up at 2am, bright lights and whirring fans. Thought it was a virus! Seems like Fedora has cracked the hibernate/sleep issue, possibly due to good intel driver support for my Dell and finally Linux has better hibernate, sleep and wake than Windows 11 (ymmv!)
I actually have been lucky since even my laptop from 15 years ago already worked well with Linux and suspend while Windows didn't (wasn't OEM Windows anymore). I have also had multiple desktops that have _mostly_ had no issues with suspend either: only nvidia has given me grief on some setups when sometimes the screen would be blank when waking up, but I figured out workarounds for that.
You'll have to be more specific what kind of "privacy claims" you're talking about. Proton is definitely a lot more private than, say, Google. But, as always, you'll have to trust the party delivering the binaries you run. Also, any company operating legally, have to co-operate with court orders etc., but afaik they try to push back
Hey, me too! I do touch typing with home row and tried using mechanical keyboard with Cherry MX Brown switches, but eventually switched to scissor switches. I like them for the same reasons as you.
I get your point that plastics are relatively inert and may not cause noticeable harm (depending on quantity?), but I think it'd be wise to be cautious. See for example https://en.wikipedia.org/wiki/Plastic#Bisphenol_A_(BPA) .
I'd also consider plastic, and their additives, to be a lot bigger and longer lasting unknown than GMOs.
I'd avoid such generalizations. It's a divisive topic, but from what I've seen here, there's always lots of criticism (regarding implementation at the minimum) in the comments and it definitely isn't clear that most would be jumping head first into anything.
reply