But more so, external style cannot be applied to a subsection of a web page unless they force it into an iframe, which has all sorts of issues of it's own which is why external CSS is usually ignored. Inline CSS is often stripped by the tag strippers who don't want you turning things on or off... and media queries shouldn't even play into it since the layout should be controlled by the page it's being shown inside (for webmail) or the client itself, NOT your mail.

I don't believe the sprockets and sprockets-rails maintainers (actually it's up to the Rails maintainers, see rails/rails#28430) currently consider it broken. (I am not a committer/maintainer on any of those projects). So there is no point in "waiting for someone else to fix" it; that is not going to happen (unless you can change their minds). You just need to figure out the right way to use sprockets 4 with rails as it is.

The role of the terminal emulator process is:

Example

Then who is responsible for the actual rendering?

Although echo "$@" prints the arguments with spaces in between, that's due to echo: it prints its arguments with spaces as separators.

Wasn't sure if this belonged as an issue in Devise or Rails though.

It sounds like a gnome-open (or the equivalent library call) bug. Reassigning.

I agree that it's bad to have to handle this at the application level

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.

A MicroJS library is a small JavaScript library with a single purpose; you’ve already seen me use a variation of this phrase several times in this article

If a company really wanted to invest, I would prefer they dedicated an employee for X hours a week for Y months than money.

Money could be good if it is spent to provide some of the above things. Money on it's own is hard because then it means I would have to spend time book-keeping and managing instead of programming.

Is there a PR to... something? sassc-rails? That would make the patch not necessary? (I don't know if there's any good way to monkey-patch that in, I think you have to fork? So some change seems required...) Should the defaults be different somehow? This is very difficult to figure out.

Is there a PR to... something? sassc-rails?

Webshim is also more than a polyfill, it has become a UI component and widget library. Webshim enables a developer to also enhance HTML5 capable browsers with more highly customizable, extensible and flexible UI components and widgets.

Using ::delegates works exactly like the Forwardable module in Ruby, with one bonus: It creates the accessors in a module, allowing you to override and call super in a user module or class.

Maintaining the builds of your repositories should be everyone’s job. Instead of relying on that one build person in the team, Travis CI makes infrastructure and configuration a team responsibility.

Those things are someone else’s job, not ours, you know. 

An endpoint links your routing with your business code. The idea is that your controllers are pure HTTP routers, calling the respective endpoint for each action. From there, the endpoint takes over, handles authentication, policies, executing the domain code, interpreting the result, and providing hooks to render a response.

I am a delegation junkie. Whenever possible, I assign tasks and responsibilities originally assigned to me onto others.

In the classroom, I delegate responsibilities to my students at a rate that astounds people. There is almost nothing that I will not allow my students to do, including teaching my lessons whenever possible. My students take full and complete ownership of the classroom, whether they like it or not, and as a result, they possess great ownership of their learning.

They fail to understand the importance of autonomy when delegating responsibilities.

They lack faith in the capacity of others.

I learned to “let go” and simply trust others to maintain certain gem suites.

One of the main reasons to work with components is re-usability and portability, but also a delegation of responsibilities. Adding a component should be as easy as simply adding the component without having to know the inner workings (or markup) of this component. A consumer should only be aware of the properties, methods and events of a component. In order to style a child component one has to be aware of the markup as well, which violates this 'delegation of responsibility'-principle.

Bureaucrat doesn't define save

From my perspective the onus is on you to consider not just the words coming out of your mouth, but how they are received.

with ActiveForm-Rails, validations is the responsability of the form and not of the models. There is no need to synchronize errors from the form to the models and vice versa.

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.

About #validate which fill attributes of the form, I think it's a problem of architecture and clarity. If you respect the Single Responsabilty Principle, you must to have two methods. This is wrong. SRP means your class does exactly one thing, which is reflected in a single public method. The more methods you expose, the less SRP you go.

About #validate which fill attributes of the form, I think it's a problem of architecture and clarity. If you respect the Single Responsabilty Principle, you must to have two methods. The validate method do two thing really different.

Now let me ask you, do you write JS for a single page application differently from a "traditional" web application? I sure hope you do! In a "traditional" application, you can get away with being sloppy because every time the user navigates to a new page, their browser destroys the DOM and the JavaScript context. SPAs, though, require a more thoughtful approach.

where's the code that unloads the table-sorter plugin when the page unloads? There isn't any. There didn't need to be back in the day because the browser handled the cleanup. However, in a single-page application like Turbolinks, the browser doesn't handle it. You, the developer, have to manage initialization and cleanup of your JavaScript behaviors.

When people try to port traditional web apps to Turbolinks, they often run into problems because their JS never cleans up after itself.

All Turbolinks-friendly JavaScript needs to: Initialize itself when a page is displayed Clean up after itself before Turbolinks navigates to a new page.

They can tackle all aspects of a problem, from initial data collection and data conditioning to drawing conclusions. They can think outside the box to come up with new ways to view the problem, or to work with very broadly defined problems: ‘here's a lot of data, what can you make from it?’"

"Headless Tippy" refers to Tippy without any of the default element rendering or CSS. This allows you to create your own element from scratch and use Tippy for its logic only.

Think first: why do you want to use it in the browser? Remember, servers must never trust browsers. You can't sanitize HTML for saving on the server anywhere else but on the server.

Or maybe a better standard was in the humanitarian world. “There’s a core ethical principle called the responsibility to protect, which is about organizations having a primary responsibility to protect their own personnel,” said Abramowitz. “What’s very clear is that many teachers are distrustful because they have been in deeply unsafe situations for a very long time.” Teachers are asked to deal with school shootings, violent children, aggressive adults, poverty, online bullying—a host of complex social problems that aren’t part of their job description, she said. “Educators are so abandoned, they no longer trust in their own system to protect them.

it focuses on compiling non-standard language extensions: JSX, TypeScript, and Flow. Because of this smaller scope, Sucrase can get away with an architecture that is much more performant but less extensible

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.

And the App will be responsible for display a list of users adding/removing users of said list

anyone else can challenge those boundaries

in outsourcing is that we’ve placed the outsourced activities outside of our control, but they’re still inside our ‘boundary of identity’ – what others see and experience as ‘us

The great ones have a thought pro-cess, philosophy and habit all rolled into one that overshadows the rest: I am responsible.

Take responsibility for your outgoing network traffic If you install software that interacts with other sites over the network, you should be aware how it works and what kind of traffic it generates. If it has the potential to make thousands of requests to other sites, make sure it uses an HTTP cache to prevent inflicting abuse on other sites.

Identify your user agents When deploying software that makes requests to other sites, you should set a custom User-Agent header to identify the software and provide a means to contact its maintainers. Many of the automated requests we receive have generic user-agent headers such as Java/1.6.0 or Python-urllib/2.1 which provide no information on the actual software responsible for making the requests.

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.

Instead of using classes and local state, Deku just uses functions and pushes the responsibility of all state management and side-effects onto tools like Redux.

A class should only have a single responsibility, that is, only changes to one part of the software's specification should be able to affect the specification of the class.

When using TypeScript, cast the type of file.contents on your side.

But this is only a halfway decent way to clarify that this is an external dependency, because the only way to resolve a peer dependency warning is to install react from npm—there's no way to notify npm that you resolve the dependency to a browser global. So peer dependencies should be avoided in favor of external declarations. Then Rollup will take care of warning about "unresolved dependencies", even if external declarations can't express a particular version range with which your library is compatible like peer dependencies can.

Then, the projects that use these libraries get to process these import statements how they like when they are bundled. For the ones that wish to load jQuery from a global, we again mark 'jquery' as an external—since we still don't want Rollup to bundle jQuery—and as a global.

(Note that you're responsible for handling any race conditions that arise as a result of the component being destroyed before the promise resolves, though assigning state inside a destroyed component is harmless.)

Also Svelte is so great because developer do not need to worry about class names conflict, except of passing (global) classes to component (sic!).

The RFC is more appropriate because it does not allow a parent to abritrarily control anything below it, that responsibility still relies on the component itself. Just because people have been passing classes round and overriding child styles for years doesn't mean it is a good choice and isn't something we wnat to encourage.

margin, flex, position, left, right, top, bottom, width, height, align-self, justify-self among other is CSS properties that should never be modified by the child itself. The parent should always have control of those properties, which is the whole reason I'm asking for this.

You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)

This is where hooks/behaviors are a good idea. They clean up your component code a lot. Also, it helps a ton since you don't get create/destroy events for elements that are inside {{#if}} and {{#each}}. That could become very burdensome to try and add/remove functionality with elements as they are added/removed within a component.

But some sort of official way to do that in the language would make this nicer - and would mean I would have to worry less about destroying components when their parent is destroyed, which I'm certainly not being vigilant about in my code.

I think we could even broadly caveat that by saying “do whatever element you want” but don't expect Svelte to care about following any HTML spec, etc.

I don’t want my source to be human-readable, not for protective reasons, but because I care about web performance more. I want my website to arrive at light speed on a tiny spec of magical network packet dust and blossom into a complete website. Or do whatever computer science deems is the absolute fastest way to send website data between computers. I’m much more worried about the state of web performance than I am about web education. But even if I was very worried about web education, I don’t think it’s the network’s job to deliver teachability

I don't think it should be the individual application's responsibility to add Cache-Control: Vary when that negotiation/routing is done by Rails on behalf of the app, do you?

At a certain point it is up to the application to specify when they're varying.

We don't have an internationalization group. That responsibility is shared across many groups. We might instead have an internationalization tooling group.

We don't have a performance group. Ensuring GitLab is performant is the responsibility of all groups.

Monitor what others are doing on your behalf.Even if you’ve out-sourced your email marketing to another company, the law may hold both you and the other company responsible.

Other sites could absolutely spend time crawling for new lists of breached passwords and then hashing and comparing against their own. However this is an intensive process and I'm sure both Facebook and Google have a team dedicated to account security with functions like this.

Ultimately it comes down to how much time and money you can dedicate to keeping your users' accounts secure versus how important it is to do so. Google and Facebook accounts sit at the centre of many users' internet lives and would be devastating to use. Same for most email accounts.

Without passing any judgement on any third party developers, we have to advise people to never enter their 1Password Master Passwords into anything other than 1Password. I have no reason to doubt the integrity or competence of these third party developers, and RogueLazer’s project is even open-source. But it would be irresponsible for us to do anything other than advise you never to give your 1Password Master Password to anyone or any other application.

Covid-19 is an emergency on such a huge scale that, if anonymity is managed appropriately, internet giants and social media platforms could play a responsible part in helping to build collective crowd intelligence for social good, rather than profit

Data has become a “natural resource” for advertising technology. “And, just as with every other precious resource, we all bear responsibility for its consumption,”

this website claims the cookie stuff will be a responsibility of the browser, not the website, which would make live easier for web devs.

Furthermore, one should also consider that **publishers – a category including natural persons and SMEs – are often the “weaker” party in this context.** Conversely, third parties are usually large companies of substantial economic import that work as a rule with several publishers, so that one publisher may often have to do with a considerable number of third parties.

Our solution goes a bit further than this by pointing to the browser options, third-party tools and by linking to the third party providers, who are ultimately responsible for managing the opt-out for their own tracking tools.

You are also not required to manage consent for third-party cookies directly on your site/app as this responsibility falls to the individual third-parties. You are, however, required to at least facilitate the process by linking to the relevant policies of these third-parties.

Arel’s responsibility is SQL query construction and optimization, and it knows very little about ActiveRecord’s Models and nothing about the database. Arel provides the basic building blocks for ActiveRecord.

No annotations matched your search.

https://www.9news.com.au/national/60...b-32168ef9b440 A 60 Minutes investigation has revealed that Australia’s attempts to ethically recycle are falling short, causing harm offshore for our international “dumping ground.” Australia has earned the unfortunate title of one of the world’s most wasteful nations, and as our waste crisis worsened the importance of recycling was drilled into the nation. We were encouraged to reduce, reuse, recycle, in a desperate bid to clean up the country. But as 60 Minutes reporter Liam Bartlett revealed, the reality is that much of the public’s efforts to recycle the huge amounts of plastic we consume are often a waste of time. 60 Minutes has tracked mixed plastic waste - the material assumed easiest to salvage and re-use - from the recycling bins of Australian suburbs to dozens of illegal processing sites in Malaysia, where our discarded plastics often end up being dumped, buried or even burned. It’s turned Malaysia into Australia’s dumping ground, with dire consequences including contamination of drinking water and air pollution. Despite so many Australians diligently separating plastics from their general waste and placing it in their recycling bins, very little reprocessing of mixed plastic is happening on home soil - with the exception of milk bottles and soft drink bottles which have a discrete market. Haydn Breheny, who runs a recycling business for industry waste in south-east Melbourne, revealed to 60 Minutes that when plastic arrives at his warehouse, if it can’t be sold to Asian markets then it can’t actually be recycled here in Australia and just ends up in the tip. “Morally, you want to do something for it,” he told Bartlett. “But if I can't get rid of it, what am I meant to do? Eat it myself?” For the last two decades, Australia’s recycling industry has been dependent on China – which had been taking a staggering 125,000 tonnes of our plastic waste every year, sorting it by hand with low labour costs and melting it down into new plastic products to be sold back to us and the rest of the world. But in January 2018 China effectively closed its doors, citing environmental concerns. The decision threw the world’s recycling industry into a tailspin as nations, including Australia, scoured the globe for new buyers. They found them in Southeast Asia, Malaysia in particular, where hundreds of Chinese operators quickly relocated to set up factories, often illegally. These dodgy businessmen then proceeded to buy as much foreign trash as they could get their hands on. Almost overnight Malaysia overtook China as the world’s largest importer of plastic rubbish. Australia alone has dumped more than 71,000 tonnes of it in just 12 months and it’s helping fuel a criminal underworld in plastic recycling, harming the environment and the people of Malaysia. Malaysia’s Environment Minister Yeo Bee Yin has shut down no less than 150 illegal factories since July last year, but admits her country doesn’t have the resources to properly police the unlawful trade in plastic waste. “I want to send [plastic waste] all back to the counties of origin,” the Minister said. “And have to really ask you to solve your own problem.” Because of this, Malaysia has imposed harsher restrictions on imports and new permits. The Minister warned 60 Minutes it’s only the beginning – Malaysia’s doors will soon close on Australian rubbish for good. “I do not blame ordinary Australians,” she told Bartlett. “I think most of the people do not know this is happening. But, now we know that this is happening, we need the solution.”

Two concepts that I’ve been thinking about a lot lately are guilt and responsibility. When it comes to racism in America, I think that guilt and responsibility tend to be seen as more or less the same thing. But I’m beginning to understand how there’s a real difference. As white people, are we guilty for the sins of our forefathers? No, I don’t think so. But are we responsible for them? Yes, I believe we are.