current system is ‘closed source’, and is carried out by competitive agents that do not share innovations for very long time periods; the competitiveness of these agents requires behaviors that externalize costs

I've encountered several people in the Kagyu and Nyingma traditions who say, "Oh, we, you know 'tukdam,' yeah, people go in 'tukdam,' "but it's like, you know, not that big a deal. It's, we don't care that much." Part of the reason they don't care that much is that the idea that you need to go into this completely, kind of, a state where there's no phenomenal content— that's just a pure clear light mind— actually is something that many of the contemporary practitioners and teachers in those lineages don't agree with.

think about how many of those applications were built by people that you know didn't have the capabilities to just build this massive infrastructure they just wrote some code and deployed it to you and now you have it and now you have a superpower uh this is a a remarkable uh kind of Technology

what we're doing is feeding in real-time data from the stock market he's making buy and sell decisions and we're seeing if he can come to have a better sense of the economic movements of of the planet

development becomes as popular as mindfulness

but people wanting to take projects on that can produce things in the world that get things done.

he English education does notencourage learners to think. They are generally told toreproduce the ideas of others, and, unless the questioncomes straight out of the Text-book, they often findthemselves quite unable to answer it.

A free program allows you to tinker with it to make it do what you want (or cease to do something you dislike). Tinkering with software may sound ridiculous if you are accustomed to proprietary software as a sealed box, but in the Free World it's a common thing to do, and a good way to learn programming. Even the traditional American pastime of tinkering with cars is obstructed because cars now contain nonfree software.

Provide a complete description of the issue. If it works on A but not on B and others have to ask you: "so what is different between A and B" you are wasting everyone's time.

IEP Process: Common Errors

And what I assume you shall assume, For every atom belonging to me as good belongs to you.

Of course, the developer usually does not do this out of malice, but rather to profit more at the users' expense. That does not make it any less nasty or more legitimate.

Yielding to that temptation has become ever more frequent; nowadays it is standard practice. Modern proprietary software is typically an opportunity to be tricked, harmed, bullied or swindled.

Degradation ofecosystem services could be significantly slowed down or even reversed if the role ofbiodiversity and its full contribution to economic production were an integrated part ofdecisions made by governmental entities, companies, and other stakeholders (Paul et al2020)20

“I’m also branching out to develop a typewriting service,” continues Leo. “I am currently typing the best man speech for someone. He’s getting it framed to use as a gift for the groom. I’ve also begun hiring typewriters out for weddings, to be used for guests to type notes for the bride and groom on the day.” What a genius idea.

we are not giving ourselves a deal of trouble merely forthe pleasure thereof

we need to make the transition acceptable and attractive for the vast majority of citizens, and the only way to do that, is to make the changes easy to adopt. This requires strong engagement with society at large, and policies that make sustainable life choices not only easier, but also cheaper and more attractive. Or, put it the other way around, it must be more expensive to destroy the planet or the health of our fellow citizens".

It doesn’t matter if *you* believe in climate change or not… Because Insurance companies believe in climate change. And so you're *already* paying for the costs of climate breakdown

It does provide an answer. The issue is that the Google form validates that the user has input a valid looking URL. So he needs to input an arbitrary, but valid URL, and then add that to /etc/hosts so his browser will resolve it to the address of his devserver. The question and answer are both fine as is and don't require any critique or clarification.

As I’d mentioned, the problem is not with the first printing, when our usual press run ranges from 7,000 to 15,000 copies, but with subsequent printings of a many of our titles. In many cases, a few years after a title’s initial publication, a three- to five-year supply can be as low as 500 copies. The cost to set up the book (called “make-ready” in the industry) is so high that the printing/binding cost per book is far more than most readers would be willing to pay. To “break even” on some of these titles, we’d have to charge $100 or more in bookstores, which would decrease sales even further. As it is, we subsidize those volumes with donations and with sales of other books.

Are protected members/fields really that bad? No. They are way, way worse. As soon as a member is more accessible than private, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it "out in the wild" opens your class and classes that inherit from or interact with your class to higher bug risk. There is no way to know when a field changes, no way to control who or what changes it. If now, or at some point in the future, any of your code ever depends on a field some certain value, you now have to add validity checks and fallback logic in case it's not the expected value - every place you use it. That's a huge amount of wasted effort when you could've just made it a damn property instead ;) The best way to share information with deriving classes is the read-only property: protected object MyProperty { get; } If you absolutely have to make it read/write, don't. If you really, really have to make it read-write, rethink your design. If you still need it to be read-write, apologize to your colleagues and don't do it again :) A lot of developers believe - and will tell you - that this is overly strict. And it's true that you can get by just fine without being this strict. But taking this approach will help you go from just getting by to remarkably robust software. You'll spend far less time fixing bugs.

Another point is that properties are good in that you can place breakpoints in them to capture getting/setting events and find out where they come from.

I just wanted to tweak Java's BufferedReader to handle custom line delimiters. Thanks to private fields I have to clone the entire class rather than simply extending it and overriding readLine().

I'm not saying never mark methods private. I'm saying the better rule of thumb is to "make methods protected unless there's a good reason not to".

Marking methods protected by default is a mitigation for one of the major issues in modern SW development: failure of imagination.

The old wisdom "mark it private unless you have a good reason not to" made sense in days when it was written, before open source dominated the developer library space and VCS/dependency mgmt. became hyper collaborative thanks to Github, Maven, etc. Back then there was also money to be made by constraining the way(s) in which a library could be utilized. I spent probably the first 8 or 9 years of my career strictly adhering to this "best practice". Today, I believe it to be bad advice. Sometimes there's a reasonable argument to mark a method private, or a class final but it's exceedingly rare, and even then it's probably not improving anything.

Belangrijke stuwdam in Dnjepr verwoest, 'waterstroom onbeheersbaar'

The same day, Menashe licensed 56 pictures through iStockphoto– for about $1 each.

Seeking full energy independence from Russian gas, in response to Russia's energy blackmail in #Europe and the war in #Ukraine 🇺🇦, #Lithuania 🇱🇹 has completely abandoned Russian gas

Voor een kernwapenvrije wereld, te beginnen in Europa Jet van Rijswijk -  02.02.2023

Agreements are subjected to climate agreements and not the other way around that could be 00:53:10 an option

We are living in a time of unprecedented danger, and the Doomsday Clock time reflects that reality. 90 seconds to midnight is the closest the Clock has ever been set to midnight, and it’s a decision our experts do not take lightly

2023 Doomsday Clock Statement

make dev

Judge Domino is a game in which players judge if toppling a line of dominoes will succeed or fail. Players take turns adding to the line, but to score points, you must make others think that the toppling will fail. Can you baffle other players' judgment?

In short, the agency put forth a rule that addresses the problem head-on without prevaricating or kowtowing to corporate America.

I used vim and make for my universal IDE.

Hoe staten de oorlog in Oekraïne gebruiken om een nieuwe wapenwedloop op gang te brengen

Nostalgia, a sentimental longing for one's past, predicts or augments psychological wellbeing (PWB).

3. Is THE BOOK TRUE, IN WHOLE OR PART?

The answer lies in an important and helpful rule of reading that is generally overlooked.That rule is simply this: In tackling a difficult book for the firsttime, read it through without ever stopping to look up orponder the things you do not understand right away.

I'm afraid you missed the joke ;-) While you believe spaces are required on both sides of an em dash, there is no consensus on this point. For example, most (but not all) American authorities say /no/ spaces should be used. That's the joke. In writing a line about "only one way to do it", I used a device (em dash) for which at least two ways to do it (with spaces, without spaces) are commonly used, neither of which is obvious -- and deliberately picked a third way just to rub it in. This will never change ;-)

Note: For keyword parameters, use @param, not @option.

laudator temporis acti

We decided to follow their rules to stay in their affiliate program, because that's how we are able to actually run the site (without any ads).And if you look on the issue from the usability point of view, not having their price history isn't that big of a deal, unless the game is sold only on Amazon - and most games aren't - so you always have other stores to compare the price to.

It is important in your summary that you make connections between the key ideas in the article.

unevaluatedProperties is like additionalProperties, except that it can "see through" $ref and "see inside" allOf, anyOf, oneOf, if, then, else

I'm not sure if there's a reason why additionalProperties only looks at the sibling-level when checking allowed properties but IMHO this should be changed.

It's unfortunate that additionalProperties only takes the immediate, sibling-level properties into account

additionalProperties applies to all properties that are not accounted-for by properties or patternProperties in the immediate schema.

additionalProperties here applies to all properties, because there is no sibling-level properties entry - the one inside allOf does not count.

What I want is to use "additionalProperties: false" to validate a union of schemas, but it seems it isn't possible. I already tried with sevaral different combination, but I didn't make it works.

additionalProperties: false works on it, but not along with allOf, because only validate one schema or another.

Oh, my goodness. It's kind of scary looking, actually.

5.11 Convert your principles into algorithms and have the computer make decisions alongside you.

5.6 Make your decisions as expected value calculations.

5 Learn How to Make Decisions Effectively

There is one more layer we can add, though

test2 being marked async does wrap your return value in a new promise:

Honestly, I don't know. Strictly speaking it's different to a window being opened at a specific size (I can see the difference). I don't know whether that difference is material. Seeing as these are tests, I'd like to remove as many unknowns as possible. If someone can tell me that it makes no difference then I'd be happy.

In this article, we have curated a list of various monetization strategies and how to implement them to generate massive revenue through an app.

Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

I still don't understand the difference between a script and a module

There is always a way to work around that by doing expr as unknown as T, but it stops people making basic errors.

Search Terms:

The Simplified Spelling Board of the early 1900s in the United States made gauge one of its targets in the early 1920s, urging the replacing of au with a to yield gage. From Simplified Spelling Board, Handbook of Simplified Spelling (1920): Principles Adopted Its [the Board's] recommendations, accordingly, have been based on the following principles : 1) When current usage offers a choice of spellings, to adopt the shortest and simplest. EXAMPLES : blest, not blessed ; catalog, not catalogue; center, not centre; check, not cheque or checque; gage, not gauge; gram, not gramme; honor, not honour; license, not licence; maneuver, not manoeuvre; mold, not mould; plow, not plough; quartet, not quartette; rime, not rhyme; tho, not though; traveler, not traveller.

How to Make a React Progressive Web Application (PWA)Eugene VolkovFrontend DeveloperKate KikidzhanCloud & SaaS Product ResearcherReactJavaScriptPWAHomeBlogDevelopmentHow to Make a React Progressive Web Application (PWA)Oct 7, 202021 min readThe early bird catches the worm. But the situation was not so favourable back in 2007 when Steve Jobs proposed the idea of web applications to be the model for iPhone Apps. Back then, the tech community was not yet ready to bring a huge interest in web apps. But since 2015, tech giants like Google and Microsoft have been preparing the tech ground for progressive web apps (or simply – PWAs). And now, PWA became a must-have technology for both giant corporations and small startups. Twitter, Starbucks, Google, and Aliexpress use progressive web apps to boost their online presence. At Codica, we have been helping our customers to develop their businesses by building robust PWA for our customers since 2015. That is why we have created this comprehensive guide on how to create a PWA with React. Also, you will see the most prominent progressive web app examples.

@7alhashmi: Yes, e.g. the 100 comes from the feature_values table

In this blog, we will see how one can build a fitness app that can be highly accepted by its users and the revenue model. Let’s have a look!

Because constants in Ruby aren't meant to be changed, Ruby discourages you from assigning to them in parts of code which might get executed more than once, such as inside methods.

The implicit dependencies between different versions of different services were not expressed anywhere, which led to various problems in building, continuous integration, and, notably, repeatable builds.

You may want to try putting the one-liner (everything in the single quotes) in an actual script, with a bash shebang line. I think filter-branch is probably trying to run this in sh, not bash.

I just wanted to point out that the syntax is not supported by the POSIX standard and thus won't universally work in /bin/sh scripts (many people erroneously use bash syntax in /bin/sh scripts)

John Company: Second Edition is a dramatic reimagining of the first edition that took over two years of extensive design and production work. 

@H2CO3 Why did you remove your answer? It was the only one explaining what was happening. Or was it incorrect?

Refactor ruthlessly. Rewrite bravely.

This is a copy of the "AMD" document in the repo, kept here to maintain historical links. If this document differs from the one in the repo, the repo version is the correct one.

There are myriads of platformers around, it's an oversaturated market, and just like industrial designer Karim Rashid said about there being no excuse by this point to make an uncomfortable chair, there's no excuse by this point to make a boring patformer.

Fexeel ba kër gi bañ ñàkk alkol.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Keep in mind that third party code with references to other files also processed by the asset Pipeline (images, stylesheets, etc.), will need to be rewritten to use helpers like asset_path.

But so far everything brought up has just been about the relative advantages of checked exceptions, and that issue is closed. We won't do it.

Enforces better architecture

In other words, once you've used Maybe you cannot hit nil with a missing method. This is remarkable because even &. doesn't save you from omitting || "No state" at the end of the computation. Basically, that's what they call "Type Safety".

The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.

The new call API is much more consistent and takes away another thing we kept explaining to new users - an indicator for a flawed API.

Trust me, I thought a lot about #validate and its semantics, and I am gonna make it even more "SRP" by making Form#errors and #valid? semi-public. All that happens via #validate reducing the possible wrong usage for users.

I've reproduced, in a very simple way, what I would like it to do: https://svelte.dev/repl/2b0b7837e3ba44b5aba8d7e774094bb4?version=3.19.1

The only solution that I can see is to ensure that each user gets their own set of stores for each server-rendered page. We can achieve this with the context API, and expose the stores like so: <script> import { stores } from '@sapper/app'; const { page, preloading, session } = stores(); </script> Calling stores() outside component initialisation would be an error.

This would be cumbersome, and would encourage developers to populate stores from inside components, which makes accidental data leakage significantly more likely.

which makes it much harder to accidentally keep logged-in state visible after a client-side logout

I changed if (value) { to if (typeof value !== "undefined") { as it was skipping some keys

If you want a reference to the global object that works in any context, you can read this from a directly-called function. const global = (function() {return this})();. This evaluates to window in the browser, self in a service worker and global in nodejs.

You already have the reason: to raise distinction

So I assume the main reason is for distinction from regular text.

Svelte Material UI 2.0 (Typescript + MDC 7+)

But seriously, give snowpack a read to understand the benefits of leaning on standard esm imports, allowing you to avoid a bundling process entirely.