Beej’s guides are absolute classics. The networking guide is also amazing. Definitely worth the read.
I’m a software engineering developer from Ottawa, Ontario, Canada.
Beej’s guides are absolute classics. The networking guide is also amazing. Definitely worth the read.
Yeah, that’s pretty much what I was thinking too. The combination of a c API and a JVM API (and maybe .NET if you’re in Microsoft land?) Hits most FFI available in languages I’ve seen. I can’t think of any language I’ve used that couldn’t Interop with either a c library (.a or .so) or JVM library (.jar). However I’ve never used any .NET system seriously, so I don’t know about them.
FWIW I regularly remake the same API based game whenever I start a new job working in a new environment to test that my environment is “up to snuff” with my development methodologies. I’ve never needed to port more than API.a and API.jar to play around in any language. I’ve ported that system to at least 100 languages over the years, and while some have more friction than others, and often the c/JVM paradigm doesn’t line up well with the target language, it is always effective.
Except for one issue: it’s an even width, so now we have the inevitable attempt to make it off-centered but pointy leading to a leafageddon. Oh well, can’t have everything.
What are factions, and where do you search them? I don’t see anything in the UI?
EDIT: found them under a link under info. Thanks for setting the faction up!
Yeah, when I was picking a scale I intentionally looked for one with minimal AA cause I was worried about that. The 180-wide version was full of it, as was the 99.
FYI: I’m starting with the outline of the left half of the leaf. I have to go to work soon, but hopefully there’ll be enough outline for the rest to be filled in (just mirror it one pixel over).
If you read the linked document, it outlines how reverse engineering may fall under a certain level of fair use, e.g. for reasearch and/or backup/archival purposes.
It really isn’t as clear-cut as it seems at first.
Great read. Only constructive criticism I have is a pet peeve of mine that is especially prevalent in type theory articles. In particular it may be worth mentioning the more formal names of some of the types discussed. Trying to map Haskell’s types to other languages can be very tricky and can hinder understanding. Mentioning more googleable names like unit, top, bottom, can be helpful in disambiguation which characteristics are intrinsic to the Haskell type, versus which are properties of the type system in general.
All praise our lord and saviour
git rebase -i
!