What are some top UX design principles when designing for kids?Some important UX design principles when designing for kids are as follows. Simplicity and clarity Interactive and engaging elements Age-appropriate content Safety and privacy Consistent feedback and rewards

My belief is that societies cannot organize effectively to cope with the impacts of climate change without a shared understanding of the future that awaits.

If you are going to crawl sites you better use Ferrum or Vessel because you crawl, not test.

So when should you use rbspy, and when should you use stackprof? The two tools are actually used in pretty different ways! rbspy is a command line tool (rbspy record --pid YOUR_PID), and StackProf is a library that you can include in your Ruby program and use to profile a given section of code.

Guys, I'm sorry to revive an old discussion, and if there's a new one, point me to it please.

innovation can result in trade-offs that undermine both progress on mitigation and 12 progress towards other sustainable development goals

assistive technology

rguments for a lot of prior instrumentation.

Arguments for little prior instrumentation.

This is the wrong place for this conversation though.

Most issues have been manually labelled as stale rather than automated and closure will be manual too, so we have time to think.

apart from [Websockets], which is unnecessarily complex for non-browser applications

A better place to ask would be on the new (since 2010) coreutils user mailing list.

for cpp_file in *.cpp; do gcc -c $$cpp_file & done; wait This gives much finer control than make -j.

There is one very important reason for enabling job control to be useful inside scripts: the side-effect it has of placing background processes in their own process groups. This makes it much, much easier to send signels to them and their children with one simple command: kill -<signal> -$pgid. All other ways of dealing with signaling entire trees of processes either involve elaborate (sometimes even recursive) functions, which are often bugnests, or risk killing the parent in the process (no pun intended).

Provides a template for future specific classes

The main (IMO) feature of MQTT – quality of service – doesn't make sense in our case: if a WebSocket server is down and doesn't receive broadcast messages (through HTTP/Redis/queue), it's likely not to handle client connections too.

We used testing tools that were in the same ecosystem as our backend technology stack for primrily three reasons: We owned both ends of the stack Team experience Interacting with the database

These tests should only be used when: the functionality/component being tested is small the internal state of the objects/database needs to be tested it cannot be tested at a lower level

Thanks, this was just what I was looking for! This is a perfect appropriate use of instance_eval. I do not understand the nay-sayers. If you already have your array in a variable, then sure, a.reduce(:+) / a.size.to_f is pretty reasonable. But if you want to "in line" find the mean of an array literal or an array that is returned from a function/expression — without duplicating the entire expression ([0,4,8].reduce(:+) / [0,4,8].length.to_f, for example, is abhorrent) or being required to assign to a local, then instance_eval option is a beautiful, elegant, idiomatic solution!!

instance_eval is analogous to using tap, yield_self, … when you are dealing with a chain of method calls: do use it whenever it's appropriate and helpful! And in this case, I absolutely believe that it is.

instance_eval lets you run the code while only specifying a once, so it can be chained with other commands. I.e. random_average = Array.new(10) { rand(10) }.instance_eval { reduce(:+) / size.to_f } instead of random = Array.new(10) { rand(10) }; random_average = random.reduce(:+) / random.size

We think that, although Ruby is a great language for the backend, the view should be written in languages designed for that purpose, HTML and JavaScript.

Our app is mostly about displaying pages of static information. We crunch a lot of data to generate a single error report page.

Honeybadger isn't a single page app, and it probably won't ever be. SPAs just don't make sense for our technical requirements.

Flexbox's strength is in its content-driven model. It doesn't need to know the content up-front. You can distribute items based on their content, allow boxes to wrap which is really handy for responsive design, you can even control the distribution of negative space separately to positive space.

Flexbox is for one dimensional layout (row or column). CSS grid is for two dimensional layout.

There is one situation where iframes are (almost) required: when the contents of the iframe is in a different domain, and you have to perform authentication or check cookies that are bound to that domain. It actually prevents security problems instead of creating them. For example, if you're writing a kind of plugin that can be used on any website, but the plugin has to authenticate on another domain, you could create a seamless iframe that runs and authenticates on the external domain.

I normally try to figure out if that's a good solution for the problem before resorting to iframes. Sometimes, however, an iframe just does the job better. It maintains its own browser history, helps you segregate CSS styles if that's an issue with the content you're loading in.

Usually, if you can do it without an iframe, that is a better option. I'm sure others here may have more information or more specific examples, it all comes down to the problem you are trying to solve.

Ubuntu also supports ‘snap’ packages which are more suited for third-party applications and tools which evolve at their own speed, independently of Ubuntu. If you want to install a high-profile app like Skype or a toolchain like the latest version of Golang, you probably want the snap because it will give you fresher versions and more control of the specific major versions you want to track.

Depending on what other component libraries you’ve used, you may be used to handling events by passing callback functions to component properties, or using a special event syntax – Svelte supports both, though one is usually more appropriate than the other depending on your situation. This post explains both ways.

I wouldn't use Flutter for web, mobile is good though.

It's super promising for web apps, just maybe not for web pages. I went from React to Svelte to Flutter for my current app project, and every step felt like a major upgrade.Flutter provides the best developer experience bar none, and I think it also has the potential to provide the best user experience. But probably only for PWAs, which users are likely to install anyway. Or other self-contained experiences, like Facebook games. It does have some Flash vibes, but is far more suitable for proper app development than Flash ever was while still feeling more like a normal website to the average user. It won't be the right choice for everything, but I believe it will be for a lot of things.

The RFC repo (where the reaction was strongly positive) is the place for discussion about what features to add; the decision has been made.

Discussion is not necessary, but could be useful for critiquing a pattern. This would be useful for people who are proposing a pattern to the community or for people who want to gather feedback on an experiment.

I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.

It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.

Further discussion can take place when this has a PR.

GitHub Issues are preferred for discussion of this specification.

Yarn also has an RFC process which may offer a better discussion platform compared to this GitHub issue.

I suggest you start a thread in the forum as this is a support request.

I would recommend they visit SU because that's a place to get help with commands, like openssl rsa and openssl rsautl

This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic.

You may receive better information if you ask your question in the help forum for that topic

I'm happy to try to reach agreement with you, but this isn't the right place. Feel free to invite me to a more appropriate forum.

I faced similar issues a while ago and created this timestamp9 extension for Postgres.

soon be served in restaurants and appearing at your local fish counter

we need to embrace GM to feed the world

Scottish ban on GM crops.

To express emotion, you will employ the language of anger in speaking of outrage; the language of disgust and discreet reluctance to utter a word when speaking of impiety or foulness; the language of exultation for a tale

Your language will be appropriate if it expresses emotion and character, and if it corresponds to its subject. "Correspondence to subject" means that we must neither speak casually about weighty matters, nor solemnly about trivial ones; nor must we add ornamental epithets to commonplace nouns, or the effect will be comic, as in the works of Cleophon, who can use phrases as absurd as "O queenly fig-tree." To express emotion, you will employ the language of anger in speaking of outrage; the language of disgust and discreet reluctance to utter a word when speaking of impiety or foulness; the language of exultation for a tale of glory, and that of humiliation for a tale of and so in all other cases.

Your language will be appropriate if it expresses emotion and character, and if it corresponds to its subject. "Correspondence to subject" means that we must neither speak casually about weighty matters, nor solemnly about trivial ones;

Appropriateness. An appropriate style will adapt itself to (1) the emotions of the hearers, (2) the character of the speaker, (3) the nature of the subject.