Thomas Jefferson’s aphorism ‘Do well by doing good’ is timely and trendy in a way it hasn’t been for centuries. Because that ethos for technology entrepreneurs is increasingly recognized as the only way many people will expect firms offering technology innovations to approach them: humbly and with a broader social mission and accounting not just as a corporate social responsibility afterthought, but as a core value of the products and companies themselves

The consequences of our current choices bear not juston us. They bear on the continued evolutionary unfoldingof life in the universe. This marks the scale of our currentresponsibility

I think we have a responsibility not only to ourselves, but also to each other, to our community, not to use Ruby only in the ways that are either implicitly or explicitly promoted to us, but to explore the fringes, and wrestle with new and experimental features and techniques, so that as many different perspectives as possible inform on the question of “is this good or not”.

In the layered architecture pattern, each layer fulfills a specific responsibility and role within the application. Some focus on user interface logic, while others handle the execution of business rules. These layers complement each other's unique purposes, but they aren't explicitly reliant on one another to perform their own tasks.

If it's dangerous, note it in the class/method Javadocs, don't just blindly slam the door shut.

When a developer chooses to extend a class and override a method, they are consciously saying "I know what I'm doing." and for the sake of productivity that should be enough. period.

This ensures that GetResponse and our customers comply with Anti-Spam laws.

hese challenges demand an ethos not of technologicalcleverness, but of social prudence, of acting with humility and cautionwhen confronted by risk and uncertainty. The French philosopherHans Jonas calls this the “imperative of responsibility.”

I have yet to see a Snapd or Flatpak build of Audacity that I'm happy with. Those builds are beyond our control as they are made by 3rd parties. I do find it mildly annoying that Flatpak direct users that have problems with their builds to us.

I just can’t stop dreaming about a perfect world where I could go back to any of my old JavaScript projects with an ease of mind and knowing that everything just works. A perfect world where my program is going to stand the test of time.

I agree that these fields should be whitelisted by ActiveAdmin automatically as it generates them via the form helpers. Regardless of if you use :raise or :log you wouldn't usually want these causing unnecessary noise.

The second situation would be zombie reaping. If the process spawns child processes and does not properly reap them it will lead to a full process table

For both of these concerns we recommend tini. It is incredibly small, has minimal external dependencies, fills each of these roles, and does only the necessary parts of reaping and signal forwarding.

The first being signal handling. If the process launched does not handle SIGTERM by exiting, it will not be killed since it is PID 1 in the container

highly recommended that the resulting image be just one concern per container; predominantly this means just one process per container, so there is no need for a full init system

Is whatever process you exec in your entrypoint registering signal handlers? A good way to figure this out might be to check whether your process responds properly to e.g. docker stop (or if it waits for 10 seconds before exiting)

Tini does install explicit signal handlers (to forward them, incidentally), so those signals no longer get dropped. Instead, they're sent to Jenkins, which is not running as PID 1 (Tini is), and therefore has default signal handlers

Tini fixes by "forwarding signals": if you send a signal to Tini, then it sends that same signal to your child process (Jenkins in your case).

A second problem is that once your process has exited, Bash will proceed to exit as well. If you're not being careful, Bash might exit with exit code 0, whereas your process actually crashed (0 means "all fine"; this would cause Docker restart policies to not do what you expect). What you actually want is for Bash to return the same exit code your process had.

When a zombie is created (i.e. which happens when its parent exits, and therefore all chances of it ever being waited by it are gone), it is reparent to init, which is expected to reap it (which means calling wait on it).

In other words, someone has to clean up after "irresponsible" parents that leave their children un-wait'ed, and that's PID 1's job.

Now, unlike other processes, PID 1 has a unique responsibility, which is to reap zombie processes.

Unfortunately most init systems don't do this correctly within Docker since they're built for hardware shutdowns instead. This causes processes to be hard killed with SIGKILL, which doesn't give them a chance to correctly deinitialize things.

According to the Unix process model, the init process -- PID 1 -- inherits all orphaned child processes and must reap them. Most Docker containers do not have an init process that does this correctly. As a result, their containers become filled with zombie processes over time.

When a process loses its parent, init becomes its new parent. init periodically executes the wait system call to reap any zombies with init as parent.

Zombie processes should not be confused with orphan processes: an orphan process is a process that is still executing, but whose parent has died. When the parent dies, the orphaned child process is adopted by init (process ID 1). When orphan processes die, they do not remain as zombie processes; instead, they are waited on by init.

The result is that a process that is both a zombie and an orphan will be reaped automatically.

In a Unix-like operating system any orphaned process will be immediately adopted by an implementation-defined system process: the kernel sets the parent to this process

Let's look at a concrete example. Suppose that your container contains a web server that runs a CGI script that's written in bash. The CGI script calls grep. Then the web server decides that the CGI script is taking too long and kills the script, but grep is not affected and keeps running. When grep finishes, it becomes a zombie and is adopted by the PID 1 (the web server). The web server doesn't know about grep, so it doesn't reap it, and the grep zombie stays in the system.

What responsibility does a writer bear when construing Utopian or dystopian alternatives to our contemporary world? Are writersof fairy tales unethical and irresponsible when they create false happyendings and delude us into believing that harmony is possible in ourrapidly changing postmodern globalized war-torn world? Is it unethicalto publish fairy tales in all their mass-mediated modes to make as muchprofit as one can by playing with our Utopian desires?

authentic responsibility

Those who are born today are not individu-ally responsible for this burdensome heritage, but we are all respon-sible for the way in which we choose or fail to take it into account inanalyzing the world economic system, its injustices, and the needfor change.

the underprivileged are priced out of the dental-treatment system yet perversely held responsible for their dental condition.

Understanding the importance of helping others can also have benefits in your own life, such as reducing your stress. It’s true that you create more responsibility for yourself when you choose to help someone. But this won’t add extra stress to your life. In reality, helping others will allow you to handle stress more easily.

I end up with responsibility (friends complaining to me about this, that, and the other) without control (I can't affect any of those things)

Remember, our wizard controller is responsible for showing and updating steps, but our top-level controller is still responsible for managing our Pet models.

The willingness to trade other peoples' fundamental rights for preferential tax treatment fits neatly into all three of these, as does the delusion that somehow this can be resolved with sufficient "personal responsibility."

It is also why it's implementation in firefox is completely useless, considering that windows/osx/most linux distros plan to add support for DoH/DoT/DNScrypt resolvers in the near future, so firefox doing it itself will provide no additional benefit.

Users think every Webpack tool/config problem is a problem with a specific package and opens an issue asking for support on the package instead of Webpack. In the past year alone, I’ve had to deal with hundreds of Webpack issues on my repos.

All answers here which mention scrollHeight/scrollWidth should be adjusted a bit to take body margins into account. Browsers apply default nonzero margins for documents' body element (and it's also applicable to content loaded into frames). The working solution I found is to add this: parseInt(window.getComputedStyle(this.contentDocument.body).margin.

The shell is responsible for expanding variables.

Mike: Yeah. I didn't go to school, because my dad thought that if something happened... And I remember one time the cops came to my house, because my little brother was playing outside and it was school hours. And they're like, "What is this kid doing outside?" And I remember him crying outside, because the cops got him. And I was like, "Oh my God, what do I do?"Mike: So I opened the door and my little brother rushes in crying. And then, I don't know, by the grace of God, they left us alone, but they told us that we had to be in school, this and that. And from there we moved. A month later, that's when he got caught up with the thing.Anne: So basically he would go to work, and you would be in charge of the kids?Mike: Yeah.Anne: That's a lot of responsibility to put on—

I passed all of them except for my math. My senior year I actually passed it, but I didn't graduate. I just would go to school, literally eat lunch, just get out. It got boring for me and I was really good. I should have never started.

I wanted to do better for myself and for my family, and I felt like that was like a big motivation right there. That push you just need, because you see stuff and you're like, "Dude, I hope that when I have kids, they don't have to go through that." And yeah, that was the push that kind of—

Yes. A lot of them. A lot of things. If we didn't do, they probably would have had to do, because if it wasn't me, it would've been the next one. And they did have to go through that stuff too, in a way, because sometimes I couldn't do it, because I'd be in school doing something really, really important.

So sometimes I would have to miss school, sometimes I wouldn't go to school. So then it was chaos.

I was the only one that talked English, and it was just hard.

I used to cry sometimes, because I would wake up at 5:00 in the morning. I'm like, "Dude, I'm a little kid I don't deserve this." You know what I mean?

I was used to it at least, because growing up my mom didn't have a job so she couldn't provide for us even if she wanted to, because she's illegal. So what we would do is we would make fake CDs, and every morning I would just wake up, go to different little towns and stuff, sell CDs.

His wife or his ex-wife was Mexican. He spoke perfect Spanish, so he and my mother were very—they would joke around. It was extremely funny to watch because when other people were around, this big, big figure would joke around with my mom and everyone would be like, "Oh, my God. What's happening?" But my mom was just that kind of person. His sons, I actually grew up with. I know his sons, extremely handsome, very educated people, very, very, very nice. I visited their home quite a few times in Hyde Park. They were great people.

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