5,231 karma · joined June 16, 2011
That's not quite right. Method call data is passed in the local variable fields of the method's frame, not on the stack.
No, OSS developers retain authorship (with the exception of public domain). Only the authors can change the license and terms. Users get a license to do various things with the software/code, but they do not get ownership.
It's not completely free. [0] A set of features are available free. The complete set of features runs > $4/month, depending on whether you pay monthly or yearly.
However, I'm not sure that even with greater knowledge of Word's features, whether developers in general would come to like it.
I doubt it's cheap at this level of traffic.
Nim's home page acknowledges borrowing from Python, Ada, and Modula, as well as C/C++. I don't think D is part of the mix.
RIM viewed the BB as a business tool. Apple viewed the iPhone as a consumer device and promoted it heavily that way. In short order, Apple had shipped more devices than RIM.
> I've always thought of the JVM as magical technlogy--I'm certainly not alone in that view. But in trying to learn more about it, I was greatly frustrated by the difficulty of reading the code base. As you likely know, the Hotspot JVM is open source. But reading the code is very difficult, in part because it grew organically and in part because of its unusual design, in which many actions are buried deep at the end of a long series of function calls involving unexpected classes and unusual methods, etc.
> This led me to thinking there would be value in a JVM written as a single cohesive codebase. And given that there is a 300+ page JVM specification and a reference implementation, I thought to myself, how long could this take? Two years later, and with help from two major contributors, we're still finding out! ;-)
> Eventually, we hope, it will be a fun/interesting experience for users to pop open their Go IDE and watch a Java program execute--which is why we're intent on making sure it's written in 100% go.
> In a larger context, Jacobin might eventually be useful as an embeddable JVM.
What I take from that is that in 1980, while there was some awareness of global warming, few scientists thought it would so quickly accelerate and become the central issue regarding the environment.
[0] Summary of the report: https://www.cartercenter.org/resources/pdfs/pdf-archive/glob...
Traditional employment contracts, which were common years ago but are now used principally for C-suite positions, typically have terms employees can sue to enforce such as WFH.
For most positions in tech, nothing in the paperwork will give you a way of enforcing WFH if the company changes its policies.
That's what I meant by my comment above, which I can no longer edit. (I should have been clearer.)