Use the right tool for the job. You can use both and it doesn't make the code any more or less readable. Using one only certainly does limit your abilities to write clean code and in the case of this pattern encourages some nasty shit.
Parameter count denotes logical branches like an if statement.
If you're passing in more than two to three Params a parameter object quickly becomes desireable.
Forcing parameter objects for one or two parameter functions seems.. stupid to say the least.
Boolean parameters are extremely rare if you're code is clean. They're essentially a code smell that indicate someone has dropped a hack in the middle of your function and handed in a parameter to toggle the behavior on in their one case against all others.
You're much better off writing a new function that triggers the new behavior and wraps a call to the old one.
Similar story for object returns, if you need to return an object that's fine but to be honest destructuring an object straight away makes code pretty hard to read in a lot of cases (not all).
For returning two parameters I'm pretty confused about the code, it's likely breaking single responsibility and signalling sideeffects.
You're ignoring that science improves and leads to further discovery.
It's perfectly fine if 0.00000001% of the population spends their lives on something that achieves nothing if a few of these lead to further developments.
We have almost 8 billion people on the planet, we absolutely need to "focus" on every possible solution that may work.
There are currently over 100 proposed solutions that do actually add up to more than enough sequestration but the conversation needs to change and the disparaging whataboutism needs to end.
If people get apathetic or nihilism sets in nobody will be able to make the changes required.
Neither the peacful capitol protest or the thousand days of violent riots in Portland lead to significant upticks in corona virus spreading, but some spreading did happen.
They should really label their packages accordingly so I can differentiate between cagefree packaging and free range worker conditions. I don't mind paying a little more for free range if that's what it takes.
It's in the Twitter thread, to do a port pickup you have to wait days at the port because they're so slow, (because of the traffic jam of containers), truckers are choosing to do pickups elsewhere that doesn't involve waiting for two days to get their load on.
They're paid by the load, so sitting idle is a non option.
Intel has a history of big plays, I'll be taking a punt on them, just as soon as this slow growth and missed earnings errode their stock price over the next couple years.
Those real time deadlines that take you away from your work is what they're talking about. You leaving for those deadlines means someone else implicitly needs to pick up the slack.
Or at least that is the argument.. but there are a few assumptions here that aren't true. Namely, someone doesn't need to pick up the slack, the work will be there the next day in most cases. Someone else with kids might be around. If your boss is treating you different it's on you to call it out and move on.
Well I was setting up a desktop machine as a server. The idea of silverblue is great, only it sucks to actually use. Updates are slow, and everything is just needlessly harder.
I get why maintainers want to push flappypacks, I just don't care, it's a shit solution that leaks all over your users. Find a better way to fix your problems.
You might want to look into something less unstable.
I've had arch running unattended upgrades in a Cron for years.
Worst case I have to find my USB stick and do some debugging, not that an update has ever broken anything.
There is some minor maintenance I run maybe once every 6-12 months to clear caches or fix up any configs that need updating but I've never run into anything that prevents booting.