Just don’t forget to wash your hands after.
Web Developer by day, and aspiring Swift developer at night.
Just don’t forget to wash your hands after.
The way I look at it is this: I want credit for the work I do, I should also be able to fork a repo that I work on, and I sure as hell don’t like giving up my rights if I can help it.
But others may feel different.
They are nuts. Their license means that you give up all of your authorship rights to the code you contribute, and on top of that you’re not allowed to distribute modified source, nor can you fork the source for any purpose.
Edit: lol
Like imagine living years of your life desperately calling out to someone, anyone, and you finally hear someone - you desperately rush over, but there’s there’s nobody there. You’re sure you heard someone, but there’s nothing, except you.
Second worst nightmare unlocked. Imma go cry now.
I really shouldn’t feed the trolls, but eh, I’m learning a lot rebuking you, so maybe somebody else can benefit from your ignorance as well:
GrapheneOS has official production support for the following devices:
- Pixel 9 Pro Fold (comet)
- Pixel 9 Pro XL (komodo)
- Pixel 9 Pro (caiman)
- Pixel 9 (tokay)
- Pixel 8a (akita)
- Pixel 8 Pro (husky)
- Pixel 8 (shiba)
- Pixel Fold (felix)
- Pixel Tablet (tangorpro)
- Pixel 7a (lynx)
- Pixel 7 Pro (cheetah)
- Pixel 7 (panther)
- Pixel 6a (bluejay)
- Pixel 6 Pro (raven)
- Pixel 6 (oriole) Source
😊
I didn’t miss the point. Maybe you’re conflating a distribution with an operating system. But, since you brought it up:
My point is that — at least in my eyes — open source is not synonymous with one single project. Do with that what you will.
Yes, and a few broken down satellites in the ocean is but a mere drop in the bucket. Being irresponsible is irresponsible, no matter how you try to excuse it.
Its like saying MAC is UNIX, technically yes but not really
macOS is UNIX-based. Period. In fact, “[s]tarting with Leopard, macOS has been certified as compatible with the Single UNIX Specification version 3 (SUSv3).” Source
We could learn that we are intergalactic litter bugs. We should stick with fixing polluting our inner space.
Could you mean network radios?
Whatever it is, I’ll bet it’ll be 3 nanometers thinner than last year’s model!
I’ll admit I’m no c/c++ aficionado, but after a little research I see what you mean. Originally, C++ was a superset of C, but C has since diverged to include things that are not in C++. So we are both correct.
In before the pedants: clang is a c compiler, in that it compiles c code—but it also compiles other languages too. The distinction is that c, c++, rust, etc are compiled directly into byte code , whereas typescript is transpiled into another language (JavaScript) before it is executed. I’ll probably catch heat for this, but you can liken TypeScript to C++ because they both are supersets of another language.
I feel you’ve missed my entire point. My comment was not based on any technical merits of a language. It’s about a persons personal (religious) view of a tool they use to do their job.
I proudly use PHP, JavaScript, Java, Bash, and SQL. They have given me the means to make a long and fruitful 18+ year career. If my boss walked up to me tomorrow and said I needed to learn Python, or Rust, or even brainfuck, I’d learn it and be better for it.
Would it be as easy as my tried and true toolset? Not at first. I still remember the struggles I had when I was first learning my current toolset. It was frustrating. I remember cursing how stupid this or that was (especially PHP and JavaScript). But I learned, and now they’re not as frustrating — because I work with it, and not against it.
Look at JavaScript. Yeah it’s weird sometimes; if you don’t understand how it works. So people slap these transpiled languages or frameworks (like CoffeeScript or TypeScript or whatever) on top, trying to fix the things they think are wrong with JavaScript, and end up making a chaotic mess of the entire community. (And yes we could spend months arguing pros and cons of any merits of transpires and frameworks and why and what not, but then you’re still missing the point).
Anyway, the point is: if it works, then it’s good. Rust does not make Linux worse. If anything, it makes it better because it makes it more accessible to programmers who know Rust but not C. And that’s a good thing. It ensures the Linux kernel will be around longer than whomever ends up being the last C developer.
Those C developers bitching about how they don’t like the idea of rust in their kernel are akin to those old fogies yelling about those damned kids and their loud music or fashion sense.
This quote applies to so many situations and so many languages. It’s beautiful. 🧑🍳 💋
Typescript is always compiled down to JavaScript, so it’s kinda the same thing, but with “nicer” clothes.
People need to chill with the language fanaticism. It’s one thing to make jokes and rip on a language for its quirks, but at the end of the day it’s just a language. If you truly don’t like it, don’t use it. I’m going to take a stab and guess that there is enough Linux kernel source to go around to both the c devs and rust devs. Just be glad they’re not trying to rewrite it in JavaScript. 😉
Where’s the flex in that statement? How is suggesting you’d have rolled over and let another country bully you better than the “underdog” country fighting back and giving the bully a hard time? I must’ve missed a memo somewhere along the way.