1,958 karma · joined April 19, 2011
All that matters in nature is whether something works or does not work, not whether it's good or evil.
When subclassing, what is the advantage of [Symbol.toStringTag] getter over the toString() method override? Is it just another way to do the same thing?
If poverty was causing reduced birth rate, we should have gone extinct long time ago. I suspect though that increased competition for non-essential resources and territory (like a new car or a house) might somehow turn off our reproductive instincts because in the past this was usually a prelude to self-destructive competition for essential goods.
I'm not encouraging or discouraging anything, I just don't see the problem. Everything seems to work according to the nature. The only thing that needs adjusting is the social security system which is based on the flawed assumption of infinite population growth.
From the biological perspective, excessive population growth can be dangerous to the species [1].
How that area will be fit into the viewport is determined by the "preserveAspectRatio" attribute.
If you don't define any viewBox then there will be no scaling - 1px in the viewport coordinate system will be mapped to 1 user unit in the abstract initial user coordinate system.
[1] http://www.happybootstrapper.com/2014/im-us-whatll-happen-ju...
The second AI created by humans is unlikely to have same goals or to be predictable by the first AI (or whatever evolves from it), thus I guess it's something that the first AI would want to prevent, either by eliminating humans or by fully controlling them (for their own good).
It's extremely important that the first AI we create is well thought out as we won't have the second chance to fix things up, once it's here it will have god-like powers over us.
To be more specific, such structure would not be illegal, but you would have to deal with double the amount of bureaucracy and you would pay the same taxes.
If you want to avoid double taxation while maintaining limited liability, you have to get into some complex and obscure legal structures - like a limited partnership where one partner is a limited company (with at least two directors) and the another partner is you.
Even then, the limited liability is very limited and it's easy to make a mistake that will make you fully liable.
Not sure if this is what you meant, but some tiny rounding errors might occur during conversion if there are many transforms involved between the user space and the viewport space, but this can be avoided if user space values are stored with high enough precision.
In order to convert user units to viewport (physical) units and vice versa you only need the current transformation matrix, viewBox rect and viewport size. I have created a demo which shows how I can determine the line length in physical units: http://jsfiddle.net/9n5hf2jw/1/
The way how real world units are interpreted inside the SVG document is so messed up that even the SVG spec itself discourages their use:
Defining the size of a document in mm and then using mm units for shapes within it is going to give counterintuitive results, since they'll be converted to user units to resolve against the view box. (https://svgwg.org/svg2-draft/coords.html#Units)
It makes sense to use high level languages to manipulate the document model or to implement widgets, but when it comes to the renderer you want to be as close to the metal as possible.
This is because everything inside SVG document lives in an imaginary infinite world where dimensions and distances are expressed in abstract "user units".
You use "viewBox" attribute on the outermost <svg> element to specify a rectangular fragment of that world for the purpose of rendering. You use "width" and "height" properties to specify the real-world size of that fragment.
Authoring tools might show you dimensions of SVG objects such as rectangles or paths in real-world units computed from "viewBox", "width" and "height" of the outermost SVG element, but under the hood the size of those objects should be stored in user units.
The migration from C to C++ was slowly progressing since Inkscape was forked from Sodipodi over 10 years ago, but there are still some C files remaining and SP* prefixes are used all over the place.
Besides, Sodipodi was already using simple GObject-based architecture.
Ideally I would prefer to have an option to draw paths with either quadratic or cubic Bezier segments, but edit paths normalised to cubic Bezier segments.
In the near future (in evolutionary timeline) in order to survive we might be forced to colonise other planets or cooperate with machines that are orders of magnitude more intelligent than we are today. We either learn how to adapt rapidly or we will be out of the evolutionary game.
I would change the title to "A Guide to Declarative Animation in SVG".
Whether a company is considered to be CFC depends on many factors such as double taxation treaties between the two countries, the amount of shares you own and the level of taxation in the offshore country.
In the following code, assuming that there are no read errors, is the load callback guaranteed to be always executed? I.e. are DOM events dispatched only after the call stack is cleared?
let main = () => {
let reader = new FileReader();
reader.readAsText(file);
reader.addEventListener("load", callback = (event) => console.log(event.target.result));
};[1] http://www.youtube.com/watch?v=ZC_rNie61IQ
[2] https://developer.android.com/guide/webapps/migrating.html