Apotheon Trophy Guide

You'll need a standard C compiler as well (unless you plan to rewrite the entire OS from scratch, which seems at odds with your comment about not being up to the task of making changes in existing software), which will need some development work to make it fully capable of compiling a complete system from whatever base you choose to use, which means you'd have to write substantial code anyway. I don't see how you intend to cobble together a pure-copyfree system without writing a lot of code to modify existing software.I'm not entirely sure what's going on with that 'BetterC' thing. Is that a way to use DMD to compile C99 (that allows for linking in D libraries), or something else?. It turns out. See the advertising clause in the Caldera license, identical to the 'Original' BSD License.

It's arguable that the main project license is copyfree, as 'a traditional 2-clause (or less) BSD license', though, so I count it as a copyfree project. I'm undecided about what kind of strictness should be applied to the 'contaminated' tag, though. Does OBSD as a lingering license from old code warrant that tag?It bears community discussion, I think, which will probably only end up happening on IRC, as that's where I know of actual semi-active community members. DISCLAIMER: I am not your lawyer. I am not a lawyer at all. Even if I was a lawyer, I would not be your lawyer just by way of me sharing these ideas. This is not legal advice.

If you require legal advice, you should seek the counsel of an attorney. If you do something stupid and get in legal trouble because of some interpretation of what I say here, that's on you. Don't sue me.In essence, what you quoted seems to mean this:The things that make the Apache License 2.0 non-copyfree don't apply to other people's projects' object code compiled with LLVM, even if compilation adds LLVM code to the object code in question, so the non-copyfree clauses of AL2 are not 'viral' with regard to, e.g., executable binaries produced by LLVM. You may also rest assured that the LLVM license makes exceptions for GPLv2 as well (an extraordinary step, in my experience; most AL2 projects just ignore the fact AL2 is generally considered legally incompatible with GPLv2 - or perhaps they're just wholly unaware of the problem).Regarding recommendations:.The licenses page is not the correct place to make notes about different versions of software using different licenses.Adding old-version entries to the works list might be worthwhile. It's worth considering, at least.There's a very slow process of trying to identify legally 'contaminated' works. Unfortunately, the resources for this largely involve one single busy person trying to find time to get anything at all done, so it's likely to remain very slow (perhaps even get slower) for the foreseeable future unless a million dollars fall from the sky, legal and tax-free, into Copyfree Initiative funding.

(The first place that money would go is likely toward lawyers and a sysadmin.).Thanks for the language mentions. I'll add them to a list of stuff about a mile long that needs attention. They'll probably get addressed sooner than some other stuff on that list just because reading about 'new' languages is interesting.Someone recently told me some things about scc that make it seem like a more serious potential everyday compiler than I had previously thought. I'm considering looking into it for use in my own projects, though I'll still want to test them against other, more popular compilers as well.

Apotheon Trophy List. 1; 4; 18; 8; 0. PS4 Submit Guide. Show Unlocked. Game Help Game Guides. Load Progress Save Progress. Acropolis is the second hub city you will enter after being cast down by Zeus and ascending via Hera. Here there is another market where you can upgrade your combat abilites, and the guards have been upgraded, with a new flying variety and tougher armor.

I'm still sad the TenDRA project died. (I sense a disturbance in the force. Someone mentioned me by way of misspelling.)Some changes were made to the language in early design stages that made me decreasingly interested in the language for my own use. With sufficient interest in the language, though, I would definitely have contributed at least to the available libraries and lightweight applications in the language's package system, as I do for some other languages.I do still wish Nim luck and success. There's a lot to like about it. It's just not to my taste, unless the things that changed in ways I dislike got changed back.

I'd have to revisit to even recall all the specifics of why I walked away, though. There was also the day that the creator of the language did some things that made me no longer want to hang out in the IRC channel, which helped me walk away, though I know that sort of thing isn't always the best reason to turn one's nose up at a piece of technology.edit: I'm also not particularly concerned about the popularity of a language, so long as it's popular enough to acquire sufficient technical benefits to make it worth using (which I believe Nim has).

Again, it just didn't seem to be the language for me any longer after some feature/design changes.(By the way, Nim is still in the, of course. There's no reason to remove it, as far as I know; the license appears to still qualify.). So you agree with me now?The argument that it would all be closed source is the GPL doesn't play in Peoria: iOS is based on MacOS, which was built on top of the Darwin core, which is what Apple called its open source project full of code contributed by Apple on top of a bunch of copyfree (not copyleft) code.When Apple's contributions rest atop code whose licenses don't require release of the source code, it becomes clear that the licenses on the 'borrowed' code aren't the reasons they contribute what they contribute. The ultimate result is that 'the only reason Android isn't as locked down as iOS is' not, in fact, the fact 'it's not based on BSD'. The device manufacturers are and they very rarely upstream something they do.Fuck 'em. Nothing they add is worthwhile, other than what gets upstreamed, anyway.

The only devices that would even be too closed are such shoddy crap (often in part because of the software, with code only a masochist would want) that it's not worth it in any case.I don't even run the stock OS on my phone, and the important stuff for the hardware is in Google's upstream.I think the problem is much more avoidable than you believe. In addition to some (perhaps more knowledgeable than mine - definitely in the case of Daniel) answers already given, I'll give my impression:Daniel has done an incredible amount of work, from what I can see; heroic, even. He's overworking himself, and turning out what looks like high quality results. If he could do it forever, at peak speed, it might even be sustainable with current levels of contribution at the current level of utility and quality (and perhaps with slow improvement), even if it falls well short of the ultimate ambitions for the project (which would be a big shame). That's unrealistic, though. One person cannot carry so much load forever.Given that the number of devices supported seems to be very predictable and limited for now, I suspect that more users who are knowledgeable and both willing and able to help out, even by way of there being enough of them available to always have someone around to test updates and so on, and help refine information in the issue tracker, should help ensure that some of the load gets a lot lighter. Just try to avoid adding to the load, rather than helping distribute it and lighten it, and you'd surely be a welcome addition to the user community and, hopefully, eventually a welcome addition to the dev community.I'm already overcommitted on things to do outside of GrapheneOS, but I find my Pixel 3a with GrapheneOS delightful, and want it to thrive.

TempleRating Views 1KTime to say “No” to boring games. Prepare for a super hot bike. Motocross racing videos.

I catch myself thinking about delving into the world of Android development to help, though I'm pretty sure it's unrealistic to expect to find the time at this point. I do expect to occasionally skim issues that might be low-hanging fruit in parts of the project involving C code, though, and I intend to draw more users to GrapheneOS and convey to any who are potential code contributors the importance of the project. If that's you, I urge you to give GrapheneOS a try and eventually become a developer.Is it sustainable? Is it sustainable by just installing it on your phone, treating it like a throw-away consumer device maintained by secret programmer gods you can safely ignore, with everyone else doing the same thing? It's sustainable if the community, including the developer community, grows around it.I, for one, certainly do not intend to go back to stock Android, whether GrapheneOS grows and thrives or not. I also intend to use GrapheneOS as long as it makes any sense to do so, at this point, because it's frankly awesome, and I'm quite happy Daniel put in the work to make it happen. If (fates forbid) the project died out, I'd switch to a (probably less-awesome) alternative system image on whatever phone I would use next.

I would certainly not go back to stock Android, and I suspect that after experiencing GrapheneOS and knowing about its benefits you would probably do the same. That being the case, I don't see a downside to trying it out, and perhaps becoming a contributor to the extent you can help.Someone please correct me if I said anything that doesn't make sense. I've only been using GrapheneOS about a month, and my impressions are basically all from my use, what I've read, and the community on IRC+Matrix (starting some time before I got the Pixel 3a).