Fontforge move background software#
However, the "web" ecosystem is becoming truly amazing, and in particular it is providing tools that support very clean software design and implementation. Given the variety of different frameworks that one can call "web technologies", I am convinced that the complexity of a large "web based" software product can vary a lot depending on design decisions and frameworks adopted (which is of course true also in the C and C++ world). The " current state of web technology" is a very fast moving target, and incredibly diversified.
If, with the current state of web technology, it can be done at all. Posted 6:37 UTC (Fri) by massimiliano (subscriber, #3048) and the subreddit and IRC channel are very helpful.
(Overview of server-side web frameworks) (Very nice command-line argument parser) (Ghe concepts behind Rust and calling Rust from Ruby)
Fontforge move background code#
It's got string handling, package management, segfault-immunity, and GTK bindings that place it in competition with languages like Python and JavaScript but it compiles to GC-less native code with performance comparable to C or C++ and not only does it have a great FFI for calling C code, it makes it really easy to generate libraries that C code can call.) (If you haven't tried the Rust 1.0 beta, I highly recommend trying the 1.0 final release that's coming out tomorrow. Given how much onus JavaScript puts on the developer to ensure the codebase remains maintainable (duck-typed dynamism doesn't help there), my hopes are for Emscripten being updated to a new enough version of LLVM for such apps to be written in Rust. However, it does eliminate a giant portion of the other kind of complexity which definitely matters. The quote contains a measure of truth in that the algorithms and datastructures have to be more or less the same in order to solve a similar problem, so writing in JavaScript does not equate to magically waving a wand that eliminates the core of the problem. If anything, there is less point today than ever to even consider choosing C or C++ for writing web application frontends. JavaScript won over these despite its (subjective) ugliness and steep performance and memory penalty. Secondly, neither C nor C++ can be comfortably used as a development language. For web application server side, C and C++ are basically nonstarters.
Java and the scripting languages of various kind basically own this space. Firstly, there are very few to none who write web backends in either C or C++. I hope it had better context, because it's so clearly not true in practice. CSS and JavaScript user interfaces rely on levels of abstraction to keep things simple, he said the core development underneath is just as complex in a "web stack" as it is in native code. Øyvind "Pippin" Kolås from GIMP then disagreed strongly with the notion that web-development languages could compete with C and C++.
0 kommentar(er)
