It is part of the constitution. What they're referring to is the events of 1975 when Gough Whitlam and the Labor party government failed to pass a budget by the hostile senate, leading to the dissolving of parliament by the Governor General.
Basically the Governor General is the Queen's official representative in Australia and officially our head of state. They have the power in specific circumstances to dissolve parliament and force an election. One of those circumstances is if the government fails to legislate a budget. It's complicated how the scenario occurs, but it happened, the powers of the governor general were exercised and a new election was held.
In this case the scenario is only possible because we recognise a power higher than our own parliament, that of the Queen. The USA doesn't have that but perhaps an alternative system could be worked out (if it's even desired, I think it's a useful thing to have).
The event you describe is related: Whitlam requested that the Kerr dissolve parliament, but instead Kerr chose to dismiss Whitlam and instate the opposition as caretaker.
I know there is probably an actual definition of the 80/20 rule somewhere, but here's my interpretation, which I think gels with the article. 80% of the work is done quickly , which is the absolute core stuff, with 0 polish and full of edge-case data and interface bugs. Then the last 20% of the work takes roughly equal to the first 80%. The percentages have nothing to do with actual work completed or time spent, rather how complete it looks to the client/your boss/someone with no details of the technical implementation.
And that's only to get to 1.0. Some of these features would be unnecessary for launch but should be added post-launch, e.g., the editor imo.
EDIT: Looking it up there is an 80-20 rule that I think is in a similar vein but if applied properly to this situation would say that 80% of the work exists in 20% of the features.
When you say things like "realizing how large the universe is", "how meaningless life is", do you really mean that your mental state is impacted by the answers to these questions/implications of these realisations? How does it affect you?
I ask because while the ideas are interesting to me, they have always seemed fairly irrelevant. Sure, the universe is huge, but I don't think knowing that is going to change me. The way I see it, it has no impact on the way I live my life and I can't see anything I do having an impact on that.
I mean the questions genuinely, I realise that not everyone sees things the same way.
Wow. Because this surprised me so much, I just found out that if you open up a node REPL and type 'hello'.blink() you get '<blink>Hello</blink>' returned. So I guess it's an ES thing and it boggles my mind.
I was trying to find the ES standard where it's specified but I'll settle for this[1] instead. Interestingly enough you have quite a few HTML wrapping functions as part of the spec.
We've done this for a lot of data vis work. Clients have access to a cms which lets them stage and publish their data. Doing so puts JSON files on s3 where we also serve the site. There are some trade offs, sometimes you miss having that rest api, but you also gain a lot too.
If I were to guess, I'd say operation based synchronisation is based on syncing user actions and then executing them on the other side to catch up. E.g., user deleted record 23. User added a record with this data. User changed this field to be this new value.
