Or the pg tips approach: ‘d’ya know what? No more tag or thread for ya now you’ve got to fish and pinch the baggy out of your scolding tea ya wanker’.
Or the pg tips approach: ‘d’ya know what? No more tag or thread for ya now you’ve got to fish and pinch the baggy out of your scolding tea ya wanker’.
Yeah maybe not even non-standard as much as non-formal in this case.
I wanted to mean ‘different from what you learn in English class in school as a kid’ so non-formal, non -standard, dialectal, slang, misspellings, same-sounding words…
More or less my point, languages are weird with lots of arbitrary idiomatic things—‘would rather’ but ‘had better’.
After posting the comment I’ve thought ‘wait, it makes more sense for it to be should’ so my guesses are a bit off today.
That’d be a contraction of ‘would’ in this case, wouldn’t it? As an ESL speaker I used to find these grammar ‘mistakes’ (for lack of a better word) made more difficult for me to parse the sentences. As with code ‘written once but read many times’ would apply here.
I had an iPhone (4, don’t remember if it had usb tethering) but I didn’t even think of it. I think it was Debian 6 the one I was installing and there was one or two people with android phones…but whatever! Walking is healthy, isn’t it?
In the case of Debian I think it is philosophical. It’s been years since I’ve had to install proprietary things on Debian, but they used to be all in the non-free repository that you had to add manually. Honestly I like it, it reminds me I’m putting proprietary crap in the machine. Can be a pain in the ass when the wifi doesn’t work because some proprietary firmware is missing, and the laptop doesn’t have an Ethernet port so off you go to buy a usb-eth adaptor.
PNG is a good format for graphics, lettering, logos… not photography so unless your video is some cartoons you’re using png compression for something is not meant for.
They still have to provide fair upstream financial kickback imo
Then it’s not FOSS. I don’t see how it’s very different from Unity (for example) licensing model. So maybe a license like that can have a place, but not in the FOSS space and it will be definitely not compatible with any gpl.
I want to say that all this backdoor incident (s, not the first and certainly not the last) only shows how well the FOSS model works. Not only for catching it promptly before it even was released, but these attacks which require a good amount of skill and time, and therefore probably money, demonstrate that some bad actors are fearful of FOSS. Also I want to point that voluntary FOSS contributors are not exploited even if some big corp uses their software without paying anything, as long as they respect the freedoms they have to give to their users. Also many (maybe most idrk) contributions to FOSS aren’t made by volunteers, but through foundations/donations models paid professionals or companies putting developer time to them (I suspect this could be the case here with the guy from Microsoft that caught it).
Another user, toothbrush, has already posted a link to the 4 freedoms, I’d recommend reading that entire page for a most thorough explanation.
But basically your plan goes against three of them (assuming you’re going to release the source code, if you don’t your not granting any of them). Freedom 0 says you can use the software however you like, for any reason including for profit. You can charge the users but once you give them the (Free) software it’s completely theirs. Freedoms 2 and 3 state they can redistribute copies or distribute their modified version in any way they want provided that the give their users the same freedoms they were given.
No, there isn’t and there won’t be any since what your saying is absolutely against FOSS values. You are in non-commercial/commercial license territory, give a look at winrar’s/unity’s and the like, gpl is not for you.
Take this with a pinch of salt, I’m not a programmer just a nerd that likes those kind of things. I tried them years ago first swift (I think it was in version 2) and a couple years later rust, and while both are great I found swift makes it easier to write clear code you’re gonna understand and like when you come back to it. Rust was better I think with concurrency (at the time), you’ll catch everything at compile time, but they talk about interoperability with c++, so this safety will be lost since most code interfacing with c++ will be unsafe.