License terms when porting free software to another language
I’m exploring in the idea of porting an existing software package to another language. It’s released under the Apache License 2.0, and is distributed for free; but there’s a big different between using a library versus creating a copy of it. I would of course give full credit and be honest about where it came from, and I certainly don’t plan to make any money from the port, just use it in other projects.
License terms when porting free software to another language
I’m exploring in the idea of porting an existing software package to another language. It’s released under the Apache License 2.0, and is distributed for free; but there’s a big different between using a library versus creating a copy of it. I would of course give full credit and be honest about where it came from, and I certainly don’t plan to make any money from the port, just use it in other projects.
Web developer sending port in web service from server to client
I’m working on a project where I have two websites (client and a server).
I’ve opened web service and I’m trying to “send” a picture from my server to the client
Web developer sending port in web service from server to client
I’m working on a project where I have two websites (client and a server).
I’ve opened web service and I’m trying to “send” a picture from my server to the client
Web developer sending port in web service from server to client
I’m working on a project where I have two websites (client and a server).
I’ve opened web service and I’m trying to “send” a picture from my server to the client
Web developer sending port in web service from server to client
I’m working on a project where I have two websites (client and a server).
I’ve opened web service and I’m trying to “send” a picture from my server to the client
Porting Silverligtht application to web application with Asp.net and HTML 5
I work as internal software developer. We used Silverlight to build our application, but we have been asked to start considering their replacement.
Maintain API vs. using idioms in a port
I’m working on a port from Python to Rust and ran into some code that can’t be expressed as naturally in Rust as they can in Python.