we have individual capitalists who try 00:48:45 to make the most profit and this is linked to their capital and productivity so to achieve more in less time and 00:48:57 productivity is linked to energy [Music] the only source of energy to increase profit is carbon oil and gas and this has resulted in a change in our 00:49:15 atmosphere we have to put an entities if we wish to live in our planet can our capitalism do this based on the current data we won't be able to do so 00:49:28 therefore perhaps we should do the following reflection if capitalism is unable to do so either Humanity will die with it or 00:49:42 Humanity will overcome capitalism so that we can live in our planet

个人学习可能取决于他人行为的主张突出了将学习环境视为一个涉及多个互动参与者的系统的重要性

Much of what they do can be done without eliciting the ire of nation-states. Bike shares, pedestrian zones, insulated buildings, renovated port facilities, congestion fees, car emission limits, furnace specifications, fuel upgrades (from oil to gas to alternative energy) and white paint roofs, for example, are only some of the innovations city officials can promote to effect significant reductions in emissions and pollutants.

here states have grown dysfunctional and sovereignty has become an obstacle to global democratic action—as when the United States (or China, France, or Canada) refuses to compromise its sovereignty by permitting the international monitoring of carbon emissions on its soil—cities have increasingly proven themselves capable of deliberative democratic action on behalf of sustainability, as they have actually done in intercity associations like the C-40 or ICLEI. If presidents and prime ministers cannot summon the will to work for a sustainable planet, mayors can. If citizens of the province and nation think ideologically and divisively, neighbors and citizens of the towns and cities think publicly and cooperatively.

Post.in_order_of(:type, %w[Draft Published Archived]).order(:created_at).pluck(:name) which generates SELECT posts.name FROM posts ORDER BY CASE posts.type WHEN 'Draft' THEN 1 WHEN 'Published' THEN 2 WHEN 'Archived' THEN 3 ELSE 4 END ASC, posts.created_at ASC

The problems that we solved are applicable to a lot of people. Most people are not even aware of these problems, so things can break in unexpected ways (Murphy's law). It's inefficient if everybody has to solve these problems over and over.

Clinical characteristics and diagnostic clues in inborn errors of creatine metabolism

Benefits and drawbacks of guanidinoacetic acid as a possible treatment to replenish cerebral creatine in AGAT deficiency

Cuộc sống xô bồ và hối hả hiện nay khiến chúng ta lười vận động hơn và cũng sử dụng nhiều sản phẩm đồ ăn nhanh hơn. Đó là những nguyên nhân khiến cho cơ thể chúng ta dẫn thừa cân, béo phì, không kiểm soát được cân nặng. Chính vì vậy thì thạch giảm cân Jelly Slim đã ra đời để có thể giải quyết các vấn đề về cân nặng. Vậy thì thạch giảm cân Jelly Slim có thực sự là sản phẩm giảm cân an toàn và giảm cân nhanh chóng hay không? Bài viết dưới đây chúng tôi sẽ có những giải đáp về những vấn đề đó.

Cân nặng chính là một trong những khiến cho chúng ta thiếu đi sự tự tin, mặc cảm. Không chỉ vậy mà béo phì còn gây ra rất nhiều bệnh ảnh hưởng tới sức khỏe. Chính vì vậy bạn nên thường xuyên tập thể dục và ăn uống. Ngoài ra có thể kết hợp thêm sản phẩm hỗ trợ giảm cân. Webdanhgia.net sẽ cung cấp cho bạn các thông tin về sản phẩm viên uống giảm cân Diet Smart để bạn có thêm những cái nhìn rõ nét về sản phẩm.

Do yourself and your peers a favor, write code with them in mind.

Writing Code for Humans — A Language-Agnostic Guide…because code which people can’t read and understand is easy to break and hard to maintain.

Write code for human, not for God

Any fool can write code that a computer can understand. Good programmers write code that humans can understand.

To see if you are writing good code, you can question yourself. how long it will take to fully transfer this project to another person? If the answer is uff, I don’t know… a few months… your code is like a magic scroll. most people can run it, but no body understand how it works. Strangely, I’ve seen several places where the IT department consist in dark wizards that craft scrolls to magically do things. The less people that understand your scroll, the more powerfully it is. Just like if life were a video game.

This is so clear that you don’t even need comments to explain it.

Another type of comments are the ones trying to explain a spell.

people usually forgets about one of the greatest advantages of Open Source. YOU can fix the issue. You can download the source code and dig deep into the code allow you to keep moving. Also, you can merge this changes back to the original repository so others doesn’t have to fix it again. win-win relationship.

The rule of thumbs is, never use code that you do not understand.

Filter gives me the impression of inclusion... so if I filter by fruits, I expect to see apples, oranges, and bananas. Instead, this is more like filter out fruits... remove all the fruits, and you're left with the rest. Filter in/out are both viable. One means to include everything that matches a condition, and the other is to exclude everything that does not match a condition. And I don't think we can have just one.

Earlier this week, during a seminar at Schumacher College that included an exploration into what a Citizens Action Network might entail, a student wondered if we’d ever heard of South Africa’s CANs movement. No, we answered, we had not…

If anyone can completely refactor the JSON Schema description for OpenAPI v3.0 to accurately describe the schema in all its glory, without using this new keyword, then please do so, but I would kindly ask you to test the theory first.

This is a distillation of the results of 230+ comments on #515, not to mention the 300+ comments spread across several other older issues that fed into that one. I know it's long. Please don't complain unless you can offer a shorter write-up. :-)

Booleans and nil can be compared by identity and therefore the `be` matcher is preferable as it is a more strict test.

Just because you can create a plugin for any tool and manage its versions with asdf, does not mean that is the best course of action for that specific tool.

Can nhựa 25 lít làm từ HDPE nguyên sinh bằng quy trình đúc thổi làm cho chúng an toàn và đáng tin cậy cho việc đóng gói và vận chuyển các chất lỏng.

Can nhựa 20 lít hay còn gọi là can 20 lít là một thùng nhựa kín nắp nhỏ chống tràn làm từ nhựa HDPE được sử dụng đựng nước hoặc đựng hóa chất xăng dầu.

Can nhựa 10 lít còn được gọi là can 10 lít là một vật lưu trữ chứa đựng chất lỏng được tạo ra từ những hạt nhựa HDPE nguyên sinh không rỉ ăn mòn.

Can nhựa 15 lít còn được gọi là can 15 lít làm từ HDPE không phản ứng với hóa chất sử dụng đựng hóa chất và đựng nước đựng rượu an toàn chống tràn.

Can nhựa 30 lít là một vật chứa kín có nắp nhỏ làm từ nhựa HDPE có khả năng chống chất ăn mòn được sử dụng chất lỏng như đựng nước hoặc đựng hóa chất.

Can nhựa còn được gọi là bình nhựa là một thùng chứa nhẹ kín có nắp nhỏ vặn được làm bằng vật liệu polyme tổng hợp, thuận tiện cho việc đựng chất lỏng.

Can nhựa 5 lít còn được gọi là bình nhựa 5l là một thùng chứa kín nắp vặn nhỏ chống tràn làm từ nhựa HDPE có khả năng chống ăn mòn có thể đựng hóa chất.

3.6 Understand how you can become radically open-minded.

08:58 - Migrant gene DRD4-7R* Allele and correlation with the pursuit of novelty

A patent is defined as a right granted to an individual or company to protect their invention. It is also known as government-granted exclusive rights over a product or idea. Once your idea is patented no one copies, steals or sells it. Patents give you full control over your product or idea as it comes under the law now.

There is something nice about aligning with the platform. But it risks being a straitjacket, and I think we can provide better ergonomics when it comes to streaming.

There is nothing stopping you from creating store objects which scrapes XE for the current rates or just returns rand(2):

Why can you remove it? The loader will first try to resolve @import as a relative path. If it cannot be resolved, then the loader will try to resolve @import inside node_modules.

Node Sass does not yet support your current environment indicates that the version of node-sass you are trying to run is not compatible with the version of node installed.

What happens when you look it up in a dictionary rather than as a phrase in Google? Google just catalogues other people's [mis-]uses

The automatic conversion not only confuses people but also makes the method less extensible. See [Feature #14183] for more details about the reasons for the change in behavior, and why certain implementation choices were made.

____

When mocking is deemed profitable:

Is there a way to select from multiple custom tables using ActiveRecord QueryMethods? I'm trying to replicate this SQL query using Ruby's ActiveRecord Query Methods. select employee.emplid, address.location from (....) employee, (....) address where employee.emplid = address.emplid

SQL is all about nested subqueries. It's hard to escape without creating views, but who has time to lookup that syntax and get their DBA's permission to run the DDL?!?

Worth noting that in the case where you're proxying /api/ requests to an external server in nginx you can easily do this in handle today:

If you would like to make a code change, go ahead. Fork the repository, open a pull request. Do this early, and talk about the change you want to make. Maybe we can work together on it.

A good heuristic is to not trust the libraries you did not write either.

“Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).

I actually think this is Not Constructive, since there's no absolute rule about which pairings can be joined into a single word or hyhenated, and it's pointless having "votes" here about each specific case. Follow a style guide if you have one, or search Google Books and copy whatever the majority do. Or just make your own decision.

Of course, there is no reason why you can't use <aside> for all sidenotes, if it makes your code simpler. Think of it as civil disobedience. :)

# authenticated :user, lambda {|u| u.role == "admin"} do # root to: "admin/dashboard#show", as: :user_root # end

You can also specify constraints as a lambda:

Would it be desirable to specify the new object in a block? That would make it somewhat symmetrical to how Hash.new takes a block as a default value.

This could be an operation, a workflow, or hand-baked Ruby code completely unrelated to Trailblazer.

Or if you need to change the way the string is assembled, you can provide a proc, for example: if defined?(BetterErrors) BetterErrors.editor = proc { |file, line| "vscode://file/%{file}:%{line}" % { file: URI.encode_www_form_component(file), line: line } } end

If you want to compile youself you can pass the --with-features=huge to the configure script. Note, however, this does not enable the different language bindings because those are mostly optional and also the various GUIs need to enabled specifically, because you can have only one gui.

he goes on to talk about third party problems and how you're never guaranteed something is written correctly or that even if it is you don't know if it's the most optimal solution

he goes on to say that simple functions should not be packages because they are too small.

By treating even small functions like a black box it promotes separation of concerns and allows said black box to evolve independently.

Clearly JS and NPM have done a lot RIGHT, judging by success and programmer satisfaction. How do we keep that right and fix the wrong?

The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.

Another important MicroJS attribute is independence. Ember, Backbone—even Bootstrap to a degree–have hard dependencies on other libraries. For example, all three rely on jQuery. A good MicroJS library stands by itself with no dependencies. There are exceptions to the rule, but in general, any dependency is another small MicrojJS library.

I totally understand that there may be a majority still considering this a bad practice and thus keeping it disabled by default in production seem ok. But there could at least be an option to enable it for people who want to, no?

Better yet, send them a link to this page to help them understand why and how to make an example app:

Rails still encourages you to dump all validation errors at the top of a form, which is lulzy in this age of touchy UX

signal.to_h[:semantic]

In combination with [Track()], the :magnetic_to option allows for a neat way to spawn custom tracks outside of the conventional Railway or FastTrack schema.

  DefTrack do :paypal do
    step :charge_paypal
  end

  paypal_track = RailwayTrack do :paypal do
    step :charge_paypal
  end

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

That such minimalism is possible does not mean that it is necessarily desirable

Operations don't know about HTTP or the environment. You could use an operation in Rails, Hanami, or Roda, it wouldn't know.

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.

account.first_name = first_name if first_name.present? account.last_name = last_name if last_name.present?

It makes me happy to see people actually think about things and not just accept a shitty API.

I do think it's a common pattern that should be solved, and I am probably going to try and solve it as a Gem as opposed to simply writing code that we use in our code base

We could of course refactor our code to rename things any time we like, but we don’t do this enough in practice

considering PopOS is trying to tackle Ubuntu they really need their dual-boot setup to be a lot less tedious

if PopOS! really wants to be what Ubuntu was 10 years ago they need to step up and make dual booting easier.

that's a point, but I would say the opposite, when entering credit card data I would rathre prefer to be entirely in the Verified By Visa (Paypal) webpage (with the url easily visible in the address bar) rather that entring my credit card data in an iframe of someone's website.

This is open-source. You can always fork and maintain that fork yourself if you feel that's warranted. That's how this project started in the first place, so I know the feeling.

I'm very (VERY!) tempted to use that ppa, but without offense to it's maintainers... it's just some random ppa. If it had more "traction" I'd use it. Right now it has only 3 maintainers.

Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.

I’m not a dev either, so no Ubuntu fork, but I will perhaps be forced to look at Debian testing, without some advantages of Ubuntu - but now that Unity is gone (and I deeply regret it), gap would not be so huge anymore…

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 answer should be: you write a language that compiles to Go’s IR.

Svelte by itself is great, but doing a complete PWA (with service workers, etc) that runs and scales on multiple devices with high quality app-like UI controls quickly gets complex. Flutter just provides much better tooling for that out of the box IMO. You are not molding a website into an app, you are just building an app. If I was building a relatively simple web app that is only meant to run on the web, then I might still prefer Svelte in some cases.

All projects here are completely frozen, though feel free to fork and continue using them on your own.

Because of those similarities, it's possible to automate some of the changes.

This seems to be #31189 . It should be fixed when you update to v17.03.0-ce

It took us a long time for everyone to get on the same page about the requirements spanning frameworks, tooling and native implementations. Only after pushing in various concrete directions did we get a full understanding of the requirements which this proposal aims to meet.

We are working to develop better communication within TC39 and with the broader JavaScript community so that this sort of problem can be corrected sooner in the future.

This nested if blocks seems a bit untidy and confusing to me but I've also failed to come up with a clearer way.

I encounter this problem in all of my Svelte projects- feels like I'm missing something. Fighting it with absolute positioning usually forces me to re-write a lot of CSS multiple times. Is there is a better way to solve this that I've overlooked?

This is Sass based, and therefore doesn't require Svelte components

Ignore the warning, given that it's just a warning anyways. It's annoying, but it won't break your app

This is very annoying and I think there must be a better solution.

Just coming here to voice my agreement that these warnings are annoying and exist in other libraries as well. For me this happened with svelma. I didn't write the library code, so I don't have complete control over it even though I agree there is an argument to be had around whether I should be notified anyway. In either case, these warnings should be easily disabled since libraries don't always get updated over night.

Maybe it's also a bug because every warning should be ignorable? Not sure.

I would like the compiler to add a property like canIgnore: false to the warning, if the warning cannot be disabled.

However, that really doesn't mean we should expose everything else in JSON too...

In the software industry we use "dependency" to refer to the relationship between two objects. We say "looking for dependents" for relationships to dependent things and "looking for dependencies" for relationships to prerequisite things, so it gets that connotation, but the literal meaning is the relationship itself, not the object. Finding a better word is exactly the point of the question

There are other features you *could* actually polyfill, such as Array.of, Number.isNaN or Object.assign, because those don’t introduce syntax changes to the language – except that you shouldn’t.

All validators can be used independently. Inspried by functional programming paradigm, all built in validators are just functions.

FormValidation.validators.creditCard().validate({

FormValidation.formValidation(formElement

Yes, you can embed loops in it and compose lots of small repeated JSX snippets, but that almost never happens in practice because mixing the turing complete of javascript with the markup of HTML eliminates the readability of JSX so that it is actually harder to parse than a solution like hyperscript (the syntactical approach taken by virtual-dom).

Doesn't require the use of transpiler or modifications to all JS tooling ever invented.

I recommend folks use https://github.com/shama/bel instead of this package; we've been working hard on it for the past two years to make sure it has all the features you could want to write inline HTML. Hope it's good; closing for now!

However, this would lead to further divergence. Tooling that is built around the assumptions imposed by template literals wouldn't work. It would undermine the meaning of template literals. It would be necessary to define how JSX behaves within the rest of the ECMAScript grammar within the template literal anyway.

This is valid javascript! Or harmony or es6 or whatever, but importantly, it's not happening outside the js environment. This also allows us to use our standard tooling: the traceur compiler knows how to turn jsx`<div>Hello</div>`; into the equivalent browser compatible es3, and hence we can use anything the traceur compile accepts!