does your scholarship suggest why so many societies do that rather than 00:20:09 saying maybe we start with a Declaration of Human Rights today maybe we write a new one from scratch based on what we know today um because it's very difficult to reach an agreement between a lot of 00:20:21 people and also you know you need to base a a a a real Society is something something extremely complex which you need to base on empirical experience 00:20:34 every time that people try to create a completely new social order just by inventing some Theory it ends very badly you need on yes you do need the ability 00:20:46 to change things a long time but not too quickly and not everything at once so most of the time you have these founding principles and shr find in this 00:20:58 or that text also orally it doesn't have to be written down and at least good societies also have mechanisms to change it but you have to start from some kind 00:21:12 of of of of social consensus and some kind of of social experience if every year we try to invent everything from scratch then Society will just collapse

Note: Git 2.6+ (Q3 2015) will propose that in command line: see "Why does git log not default to git log --follow?" Note: Git 2.6.0 has been released and includes this feature. Following path changes in the log command can be enabled by setting the log.follow config option to true as in: git config log.follow true

Continue with Quora+Unlock this answer and support creators like Mark Jones by joining Quora+

Quora+ is a subscription to the best of Quora.Access great writing, straight-from-the-source knowledge, and stories you can’t find anywhere else while supporting creators who matter to you.

On existing projects, consider the global effort to change from origin/master to origin/main. The cost of being different than git convention and every book, tutorial, and blog post. Is the cost of change and being different worth it?

In the context of git, the word "master" is not used in the same way as "master/slave". I've never known about branches referred to as "slaves" or anything similar.

I'm not sure why MSFT decided to change these codes in the first place. While it might have been a noble goal to follow the IETF standard (though I'm not really familiar with this), the old codes were already out there, and most developers don't benefit by the new codes, nor care about what these codes are called (a code is a code). Just the opposite occurs in fact, since now everyone including MSFT itself has to deal with two codes that represent the same language (and the resulting problems). My own program needs to be fixed to handle this (after a customer contacted me with an issue), others have cited problems on the web (and far more probably haven't publicised theirs), and MSFT itself had to deal with this in their own code. This includes adding both codes to .NET even though they're actually the same language (in 4.0 they distinguished between the two by adding the name "legacy" to the full language name of the older codes), adding special documentation to highlight this situation in MSDN, making "zh-Hans" the parent culture of "zh-CHS" (not sure if it was always this way but it's a highly questionable relationship), and even adding special automated code to newly created "add-in" projects in Visual Studio 2008 (only to later remove this code in Visual Studio 2010, without explanation and therefore causing confusion for developers - long story). In any case, this is not your doing of course, but I don't see how anyone benefits from this change in practice. Only those developers who really care about following the IETF standard would be impacted, and that number is likely very low. For all others, the new codes are just an expensive headache. Again, not blaming you of cours

I feel the pain. It is a normal thing that standards do evolve over time, though, and our software needs to cope with it.

I'm not sure why MSFT decided to change these codes in the first place. While it might have been a noble goal to follow the IETF standard (though I'm not really familiar with this), the old codes were already out there, and most developers don't benefit by the new codes, nor care about what these codes are called (a code is a code).

With all this “monetization” happening around Trailblazer, we will also make sure that all free and paid parts of the project grow adult and maintan an LTS - or long-term support - status. Those are good news to all you users out there having been scared to use gems of this project, not knowing whether or not they’re being maintained, breaking code in the future or making your developers addicted to and then cutting off the supply chain. Trailblazer 2.1 onwards is LTS, and the last 1 ½ years of collaboration have proven that.

If folks want to get together and create a snap-free remix, you are welcome to do so. Ubuntu thrives on such contribution and leadership by community members. Do be aware that you will be retreading territory that Ubuntu developers trod in 2010-14, and that you will encounter some of the same issues that led them to embrace snap-based solutions. Perhaps your solutions will be different. .debs are not perfect, snaps are not perfect. Each have advantages and disadvantages. Ubuntu tries to use the strengths of both.

The “no-snaps” ship already sailed years ago…you folks missed that boat. It’s too late to wish for a return to the past. Snaps in Ubuntu have been happening for years already, and will continue regardless of any opinions expressed here.

If you’re not a huge fan of Snap packages, but love using Ubuntu, this guide is for you. In it, we’ll go over how you can remove Snap from your Ubuntu system and make it so that your system will no longer have access to the Snap store or anything like that.

enables passive event listeners by default for some events (see list below). It basically will set { passive: true } automatically every time you declare a new event listener.

After i've stabilized the library i can start to discuss about adding new components and features!

But using internal api's is dangerous as these may change when you update svelte. If you decide to use this, add a line to your project Readme.md mentioning which internal api's you used and why. Try to write it using other methods when you can.

Some of the verbs implemented by systemctl are designed to provide a high-level overview in a human readable format. All that information is available over dbus, and/or journalctl, systemctl show. We could provide that information in json format, but there's a second problem. Information and format of information printed by e.g. systemctl status is not stable. Since the output is not suitable for programmatic consumption anyway, there's no need to provide it in a machine readable format.

One of the primary tasks of engineers is to minimize complexity. JSX changes such a fundamental part (syntax and semantics of the language) that the complexity bubbles up to everything it touches. Pretty much every pipeline tool I've had to work with has become far more complex than necessary because of JSX. It affects AST parsers, it affects linters, it affects code coverage, it affects build systems. That tons and tons of additional code that I now need to wade through and mentally parse and ignore whenever I need to debug or want to contribute to a library that adds JSX support.

This balancing act needs to take into account project complexity (size, distribution, etc.), uncertainty (risk, innovation need, etc.), and the cost of change at the project level and for each major component.

Compounding the problem of iteration disguised as oscillation is the cost of change.

If you're going to change the rules on us, I think it would be helpful to do so by first explaining best practices.

you could imagine my extreme disappointment after i came back after a year and a half to find that the entire exploration map was about 80% smaller, every different island was within clear view of your starting island completely decimating any sense of adventure or exploration you could have had.Almost all materials could be collected and all items built within four and a half hours. Islands are literally numbered one to five to display they're level of danger.not only that but you were practically spoon fed each advancement in the game, it feels like it was taken from a greatly ambitious open world, exploration survival game that would take months to finish and achieve everything in. To now being an arcade style iphone app game catered to ten year olds that would foolishly enter their parents card details in order to buy 10,000 roblox coins.

I have over 689 hours into this game and would like to talk about the changes made to the Exploration. In my opinion the Exploration which made this game amazing now stinks!. You know longer need a ship to hit the islands. The exploration has pretty much been removed. One of the things that made this game so amazing was grinding to make your ship and heading out to Explore and find the other islands. Now all the islands are really close to the spawn point, there are not that many and well they stink. There is no reason or need to make a ship because you can easily reach all the island with a raft.

Recently the HaveIBeenPwned API has moved to a authenticated/paid model , this does not effect the PwnedPasswords API, no payment or authentication is required.

three days

Today’s American youth are entering a labor market strikingly different from earlier generations. Over the last decade, global economic integration and the collapse of the Soviet Union have led to what economist Richard Freeman (2008) has called a “dou-bling” of the global labor market, from a pool of 1.46 to 2.93 billion. This has created a chronic shortage of jobs relative to those who seek them. The economic downturn that resulted from the 2007 financial panic has worsened this shortfall (see Figures 1 and 2).2

I have chosen not to hide behind the cloak of anonymity, orbypass the rigors of peer review by posting a version of thispaper on my Web site;

More to the point, in situations of breakdown, whether epic or mundane, the humble mobile phone has extended the city's interactivity and adaptability in all kinds of ways and may well have been the most significant device to add to a city's overall resilience by adding an extra thread to the urban knot

We conceive this step as devaluation, rather than diffusion, as Schwartz and Merten call it

We left the post at an early hour of the morning, and headed north through the rugged, broken country, which in its peculiar formations is unlike any other portion of the earth. Snow had fallen during the night to the depth of several inches, and as we passed into the hilly country an ever-changing panorama of weird and beautiful scenery was opened before us. The tall buttes of variegated hue rising abruptly from the snow-clad plains presented an endless variety of color and form. Some were smooth and round as if chiseled by the hand of man; others were jagged and rough; while others still took the shape of perfect domes.

The company of Indian scouts which is kept at the post is a splendid body of men, being selected from among the bravest and most intelligent young men of the tribe. They have adopted the regulation army uniform, and are neat and careful in their dress