You seem very defensive of the workers. That’s cool, I’m one of them.
Good workers will do better with the right tool. Bad workers, those who are resistant to change and are unwilling to learn, will never do better. So why cater to the bad workers? Now catering to the bad workers makes sense if the job is so basic that virtually no training is required, and bad workers need to eat, too. But saying we should all crawl because they don’t want to run is absurd.
Just because someone got used to walking around on their knuckles doesn’t mean walking upright isn’t easier and better overall. Sure, it will be difficult, it will be uncomfortable, and they’ll have to get used to it before they see any improvement, but once they get past those hurdles even they will be amazed at how fast walking upright can be. And in the meantime, no one else who already has a tendency to walk upright will have to go through the pain and inefficiency of walking on their knuckles.
Yeah, primarily hypergolics are the fun ones. I didn’t hear about the booster that fell near a village recently, but there was one that I think had an emergency dump over some village or town a few years ago.
And rocket fuel, which isn’t great for pretty much anything alive.
A cogent argument. I’m convinced!
You specifically said you chose the MIT license because you wanted to use it in commercial projects. That’s business, no matter how small. As the owner of the property, you could have used any and all licenses available to you. Also, if you wanted to require users of your code to attribute or notify you, you could have. If you want to be disappointed in their behavior that’s perfectly fine, too. Corporations usually disappoint if you have any altruistic expectations of them.
Here’s the core issue. The developer didn’t know his rights, and made a mistake. I’m not criticizing, people make a career dealing with crap like this. But if you want to make a business out of something, it’s worth it to do some research or talk to a lawyer. I believe the MIT license has its place but, from what the OP said, this isn’t it.
I’m perfectly aware of how it works. My whole comment was a proposed way to manage it that doesn’t assume that everyone who uses outlook wants to use MS’s cloud service just because they also happen to use Outlook. I’m not sure how you missed that.
As for emphasis, “Press fucking backspace!” has a whole lot of it. I certainly would consider that, and not your hypothetical, as actively aggressive.
If you wish to talk about critical thinking, look at your own statements with respect to mine. Not once did I say cancel thenlink attachment, but this thing I didn’t say sure got you upset. Moreover, I wasn’t writing a formal specification. I’m sorry your assuming the worst and least likely meaning of what I thought was a pretty simple statement triggered you so badly.
Yeah, it sure does sound like it would be hard to have a notification if the attachment is going to fail due to size policies, and then have an option to use the link or cancel the attachment (and have you choose another way). It would also be unheard of for there to be a setting in that dialog to say to always do whatever action you take so it only inconveniences those who go with the default once.
User-hostile software is never a “you” problem. This applies to a number of FOSS products, as well.
It’s okay buddy, your definition of exodus was wrong. Just let it go.
As for the rest, I made a sarcastic comment based entirely on fact, they asked for proof of my statement, I gave them everything they needed to verify it. I’m sorry if my comment was too harsh for your sensibilities, but if that’s the worst you’ve heard on Lemmy, them I’m glad for you.
No definition I’ve ever heard requires an exodus to be initiated by the people leaving. Also, if you read the comment that started all this, I was explicit that I didn’t mean employee-led. So thanks for stopping by weeks later to display your ignorance and/or lack of reading comprehension.
A cotton t-shirt has a SPF of about 6. It will help, but we can do better, even without melanin-infused clothing.
There are also UV transparent bikinis, for tanning without tan lines or nudity.
The reason we haven’t seen a lot of results in fusion research is mostly because we haven’t spent a lot on it. Here’s A Slashdot article from a long time ago. The spending chart hasn’t changed much until about the last decade, where we’ve finally seen some advances.
I hope you aren’t a pilot, or at least not my pilot.
You can just talk to one of your more inept coworkers.
I had a theoretical math professor. He said something along the lines of, “Being a theoretical math professor is the best job in the world. You can lean back in your chair, put your feet on your desk and close your eyes, and no one can tell if you’re working or having a nap.”
People have been sending NSFW pictures one way or another probably since people started making pictures. We have images scratched into the walls in Pompeii. There are certainly issues of consent, abuse, and advertising that need to be addressed, but demonizing pictures of naked people is also a problem.
As for all those alternatives you mention, the vast majority of fediverse applications/instances seem to be "like [insert commercial entity], but hosted by individuals/the community? How many people would be on Lemmy if Reddit was offering them what they wanted? When you have control or alternatives the odds of finding what you like improve. And some of those things people will want to share will be images, videos, and yes, even porn. But even without porn, if the service isn’t meeting people’s needs, which I agree includes no or fewer ads, then it simply won’t survive.
Something tells me there would be agreements between the instance provider and a media hosting provider and as such the media hosting provider would probably have some disclaimers about what they’re willing to host (war porn, regular porn, what have you). The two host providers would have to make sure everything they want to provide and everything they don’t want to host agree. I mean, there’s already lemmynsfw, so free porn hosting is already happening.
I honestly think the whole media hosting aspect of federation is dangerously flawed as long as instance hosts are still paying for storage and bandwidth, and I’m not sure how to fix it. It will cripple small instances with popular media if they host directly, but not hosting directly has a possibly lesser impact on all instance providers, with a higher aggregate impact. Tough choice. I don’t know enough about CDNs to say if that can solve the problem, depending on how media is federated.
This is going to need to be resolved if federation is going to grow to the next level. I hope someone finds an answer that works well enough for everybody, even the porn users and providers.
The other response said it well enough, but I’ll go a step further.
MS made a tradition of moving functionality around in their OS for no other reason that I could glean than grouping things in an at least superficially comparable group and absolutely not where it was in the last version, merely so that certification from the previous version wouldn’t apply to the current one. They would do similar things with their Office application menus, in one version moving them around based on how often you used them (try doing phone support with that!), in another replacing them with little pictures that pretended they were related to their functionality, and again moving them around every version apparently for the sake of requiring recertification.
To top it all off, they would also not give you access to the old menuing systems. You could argue bloat, but that would be ignoring the massive piles of it they added for the sake of animating their new menus alone (which has value, to a degree).
I’m aware of some of the interesting bits of woodworking, as well. I can imagine the response if you told woodworkers that the only hammer/mallet they could use was a 16 oz claw hammer. And the reason we made all those different hammers is because they are the best option for the task they were designed for. You can get away with using a smaller set, especially if your workflow would require using some rarely enough that it isn’t worth adding in their storage and cost to be worth it, but a good woodworker will still be aware of those tools and be assessing their processes to determine if it’s time to expand their toolset.
And the difference between the physical world and the world of computer interfaces is you aren’t limited to just one. The open source world is particularly fond of including deprecated functionality because there are a lot of pieces working together and it will often take years to get everything updated, and you will never know when the last dependency is removed. Likewise with UIs. A lot of the time, a deprecated one can be kept around for those who can’t be bothered to learn the new one, but the cost of keeping the old version around for a few years is usually relatively low (and the developer can determine how much they are willing to have that cost be and do things to help make it stay within that limit). That’s no reason to leave the old version as the default, though.