834 karma · joined October 10, 2013
A number of their campaigns have direct policy/political goals: Public Money Public Code, Device Neutrality, etc.
Back in the '80s, before AI could quickly produce such things, I had created a "Greek" version of the C language -- obviously named "Γ".
A lot of preprocessor definitions were involved for keyword translation, as one can imagine. Translating the C standard library was a much more difficult process: it involved patching the compiler/linker on a BSD system, since you could not have non-ASCII symbols (function entry points).
All's well with using FOSS libraries, but the licenses have to be respected. So you have to collect license information and comply with the license terms. For GPL and LGPL licensed components, one had to make the complete corresponding source code available. For permissively licensed components, one usually has to provide the copyright notices.
Including the whole Chromium (as in the case of Electron) does not make this easy. Creating a Tauri-based legally compliant distribution is much less effort.
I spent a serious amount of time on this when I discovered it, a couple of years after it was published.
Firmly believing that "variations on a theme is the crux of creativity", I studied what happens to the same construct in other numbering bases. Well, not many: based on the first theorem, only unary, binary and ternary were interesting.
I should unearth the report I wrote back then -- although I have no idea where a digital copy might be stored.
Back in the day, with different technologies, most of it would have been "strange compilers and environments" that had to be supported.
It was more like "the whole CUDA stuff is by a single company".
It should probably also add that everything CUDA is owned by NVIDIA, and "CUDA" itself is a registered trademark. The official way to refer to it is that the first time you spell it out as "NVIDIA® CUDA®" and then subsequently refer to just CUDA.
Personally, I tried SDD, consciously trying to like it, but gave up. I find writing specs much harder than writing code, especially when trying to express the finer points of a project. And of course, there is also that personal preference: I like writing code, much more than text. Yes, there are times where I shout "Do What I Mean, not what I say!", but these are mostly learning opportunities.
This is exactly what they have done. You can call "dot" and it runs the dot layout engine, but you can also run "neato", "sfdp" or any other -- with the same input.
The "graphviz" package installs all these executables.
Graphviz is a visualization framework and it includes many layout engines, implementing different algorithms: dot, neato, fdp, sfdp, circo, twopi, ...
It would be great if this new custom algorithm were to be contributed to Graphviz.
A basic question, before searching these: are they "input compatible"? I mean, can a problem be formulated once and then be solved by a variety of solvers? Or does each one of them use its own input language?
All dates are possible and most (all?) have multiple solutions.
I always used a capital i (I) for one (1); I don't remember ever encountering a "lowercase L".
So your position is that there is no economically feasible way in Europe to open an new restaurant, bakery, hair or nail salon, or any other new enterprise. Yet reality shows that somehow such activities exist and keep happening.