if business logic assumes a set of preconditions before a particular piece of code that the language/runtime/os satisfies.. then it's an immediate assert. Any kind of IO, memory creation and OS operations fall into this carefory.
However if the business logic assumes something in its own domain and that assumption does not hold then its better to handle that instead of crashing. Ex. being you expect a queue to have at least one element in some pipeline and if it is empty then return saying nothing to be done.
Edit: don't assert/crash if your application is single process multithreaded unless you want your friend from accounting asking you why their stock ticker crashed just when they clicked a button in the coffee shop module of your app. Use some thread exit mechanism.
statistically, who make up the majority of computer users? Software nerds? No its people using a web browser. So really you're annoyed that "everyone" in "linux is for everyone" doesn't include you?
B.) The whole point of Open Source is there is no single tech support. People learn through exchange of knowledge. How else would you troubleshoot hardware issues? Its the most difficult class of issues linux users face as hardware vendors don't seem to want to support linux.
Besides I find it quite hilarious to get worked up over reddit posts for random issues. Why don't you just ignore it and move on? Or you contribute instead?
And you hang out here and do what exactly? Either you're happy with win11 or you're not. Replying to random people's comment by raging against linux in a linux memes community while supposedly running windows and liking it is a bit weird isn't it?
And you sound like you havent touched a proper linux OS in the past 5 years. Things have genuinely gotten better. But I see you seem quite fixated on coming here to argue instead (again.. quite weird to do so when you have no horse in the race)
I hope you understand being different is not frowned upon.. but rather the constant irritation of people wanting to prove something all the time. Like I get it, people want to be different.. but when you want to communicate ideas you gotta find a common ground so talking is at least pleasant.
I don't want to go through hoops to understand what you're trying to say! having a good conversation is already hard with all the mindless rage bait.
Then why are you expecting me to be any better if you don't want to stop yourself here and begin the introspection?
Somehow you want people to read your arguments and change their opinion but when people ask you to do the same you just declare you are stupid and refuse to do the very thing that you expect others to do?
being kind is actually not political. By definition if someone hates people for anything other than what they do or say.. then its the person who creates the political cloud.
My understanding so far is:
if business logic assumes a set of preconditions before a particular piece of code that the language/runtime/os satisfies.. then it's an immediate assert. Any kind of IO, memory creation and OS operations fall into this carefory.
However if the business logic assumes something in its own domain and that assumption does not hold then its better to handle that instead of crashing. Ex. being you expect a queue to have at least one element in some pipeline and if it is empty then return saying nothing to be done.
Edit: don't assert/crash if your application is single process multithreaded unless you want your friend from accounting asking you why their stock ticker crashed just when they clicked a button in the coffee shop module of your app. Use some thread exit mechanism.