How would I allow a PHP front end to communicate with a back end written in Go (or any other combination of languages)?
I like PHP. It’s not overly complex to achieve what you want, you can write straight up HTML inside it, and I suppose I’m just used to it. I also like Go, having just discovered it while looking for something to write the back-end of a web app in that wasn’t Node.js (can’t abide callbacks everywhere).
How would I allow a PHP front end to communicate with a back end written in Go (or any other combination of languages)?
I like PHP. It’s not overly complex to achieve what you want, you can write straight up HTML inside it, and I suppose I’m just used to it. I also like Go, having just discovered it while looking for something to write the back-end of a web app in that wasn’t Node.js (can’t abide callbacks everywhere).
Best way to handle language interoperability
Background In a language like F#, direct interoperability with most other .NET languages is possible. For example, it is possible to use classes written in C# directly in F#, and it is possible to call F# code directly from C#. In F#, modules are compiled to CIL instructions corresponding to static classes, ADTs to a […]
Why the practice of writing unit tests in a different language isn’t that popular?
When Microsoft released Visual Studio 2008, there was a thing they were talking a lot about at the conferences and in their online tutorials: the idea of writing the actual code in one language, and the unit tests in a different language. For instance, unit tests for C# code can be written in Visual Basic.
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…
Better to write your .NET library with COM limitations in mind, or separate your .NET library from Interop?
I came across this interesting article: How I Came to Love COM Interoperability on CodeProject, which got me thinking…