I apologize for any inconvenience this may cause you; however, your PIN must be verified in the automated system before I am able to share account specific information for your security.

But all of these attempts misunderstand why the Open Source ecosystem is successful as a whole. The ecosystem of fairly standard licenses provides a level playing field that allows collaboration with low friction, and produces massive value for everyone involved – both to those that contribute and to those that don't. It is not without problems (there are many essential but unsexy projects that are struggling with funding), but introducing more friction won't improve the success of this ecosystem – it will just lead to some parts of the ecosystem to break off.

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.

(optional googlesheet & zapier integration for any other email marketing software)

best-available evidence—ie, in formal evidence synthesis.

The courses span a suite of synthesis methods, including systematic review and systematic mapping, stakeholder engagement in evidence synthesis, and evidence synthesis technology.

Because there is no time left for trial and error and since resources for organising a transformation into a carbon‐neutral world are inherently limited, decision‐making on climate solutions needs to be based on the best available evidence.

Evidence synthesis, which collates, appraises, and summarises results from individual studies across an evidence base and makes them available for policy advice, is particularly well organised in the health sciences; a key role is played here by the global knowledge network Cochrane, founded in 1993 and seated in London. T

Try systemctl stop docker.service. That did it for me.

Ok, fixed it by upgrading docker

Systemd problems might not have mattered that much, except that GNOME has a similar attitude; they only care for a small subset of the Linux desktop users, and they have historically abandoned some ways of interacting the Desktop in the interest of supporting touchscreen devices and to try to attract less technically sophisticated users. If you don't fall in the demographic of what GNOME supports, you're sadly out of luck.

We took a stance on an issue.

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.

At work, I cannot maintain this project. At home, I'd rather spend time with my children and on projects that I'm currently passionate about.

The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.

Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.

I wanted to use GitHub Gists which are a wonderfully low friction way of sharing code

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.

We believe good tools lead to excellent creations.

Would you work for free? It is a simple but loaded question that requires additional context. Is it working to help a friend do something? Is it work that you would enjoy? Does the act of working for free give you some level of satisfaction? Your gut reaction to the question may have been a hearty, “No,” but many people volunteer for a variety of things all the time, so people will work for free when there is something in it they enjoy.

Open source is fundamentally good with the transparency and flexibility it brings; however, as our reliance on it goes up, the overall investment back into the ecosystem has not. It can be easy to take for granted the time and effort many developers put into open source projects. Yet it is with their time and effort that we often save our own.

These developers are not greedy or selfish for wanting funding for their projects. To the contrary, they want funding to keep the project alive. A person has to eat, after all. Funding the project is a means of changing the maintainer’s timeshare—allowing themselves to put time into the project that otherwise would be used for other employment. There is only so much time in a day that a person can otherwise give.

Funding should not be a struggle for open source projects. We embrace open source into our codebases frequently but have yet to fully embrace the idea that funding it actually helps us too. The bug fixes and feature requests need to be implemented, tested, and reviewed by someone who themselves can only put so much time into the project.

The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.

What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.

I - we all - totally agree about the benefits of snap for developers. But the loss of comfort and flexibility for end user is eventually a no-go option.

I clearly understand why snap is a safety progress on server and IoT but in my « human » usage snap is just restricting how I use my data and computer.

Hi, I Need some help regarding my Ubuntu, is there any way to reach out to you personally ? Vote: 0 0 Share Facebook Twitter Copy link to comment Reply to SAK Copy link to comment Abhishek Prakash People's Favorite with 100+ Upvotes 30 Replies 3 weeks ago This comment is awaiting moderation Use our community forum, please.

I can hardly fault your English. It is actually very good. I take your statement as invitation for corrections. This (being corrected by others) was the most helpful when I came to live in this my country and had to learn English very quickly. Swim or Sink, I was told.

This is crazy but I don't know how to do this, and because of how common the words are, it's hard to find what I need on search engines.

Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.

Get told in big red letters when the dependency changed and you need to check that your fix is still valid.

No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.

Can this be merged please, this fixes a problem I have

Our team is building open source community tools and Svelte fits our identity as an independent labor of love with an organic community.

Regardless of measurable impact, Svelte resonates with our emotions and it makes for a good story.

locked and limited conversation to collaborators

Got a bit sidetracked into refactoring the Element visitor code, so haven't actually started on the event handler stuff per se, but that'll come soon. Element stuff is starting to feel a bit more logical and easier to follow.

If you'd prefer, you can use a third-party library like Modernizr or Detect It to do this test for you.

Serving pages and assets as pre-generated files allows read-only hosting reducing attack vectors even further. Meanwhile dynamic tools and services can be provided by vendors with teams dedicated to securing their specific systems and providing high levels of service.

Because Jamstack projects don’t rely on server-side code, they can be distributed instead of living on a single server. Serving directly from a CDN unlocks speeds and performance that can’t be beat. The more of your app you can push to the edge, the better the user experience.

Because Jamstack markup is prebuilt, content changes won’t go live until you run another build.

Better PerformanceWhy wait for pages to build on the fly when you can generate them at deploy time? When it comes to minimizing the time to first byte, nothing beats pre-built files served over a CDN.

Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.

I don't think this is what really matters at the end, since whatever is the implementation the goal should be to provide a library that people actually like to use.

For safety reasons, certain pumps and sprayers cannot be returned to the store if opened.

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.

I also find that a lot of the complexity of Flutter can be avoided, and I mostly use it to define the UI as a more app-centric alternative to HTML/CSS.

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.

When writing copy for buttons, make sure that you keep consistency.

You can also see this repo: default-passive-events.

This one gets the SEO, so I hope you're successful @raythurnevoid.

If you continue to have trouble though, feel free to open a new issue so we can keep this one focused on the theme color palette documentation problem. 1 Pick your reaction

Many of you will not be able to use this if you depend on custom import types or other fancy loaders. This project is just not for you!

The main reason to use these lower-level components is if you need to customize your form input in some way that isn't supported using TextField.

It is important to notice that if you are planning on making your application a PWA, you don’t have to rewrite all the logic.

Scenario

Scenario 1

However, this construct is not completely equivalent to if ... fi in the general case.

When you email me, please include a minimal bash script that demonstrates the problem in the body of the email (not as an attachment). Also very clearly state what the desired output or effect should be, and what error or failure you are getting instead. You are much more likely to get a response if your script isn't some giant monster with obtuse identifiers that I would have to spend all afternoon parsing.

If the document is uncontroversial and agreement is reached quickly it might be committed directly with the "accepted" status. Likewise, if the proposal is rejected the status shall be "rejected". When a document is rejected a member of the core team should append a section describing the reasons for rejection.

In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.

I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)

Express - 19 $ 🏃‍♀️ Skip the Review Queue 🕒 Published in 3 days 💌 Full Customer Support 💚 Support the team

Some of these values are suited for development and some for production. For development you typically want fast Source Maps at the cost of bundle size, but for production you want separate Source Maps that are accurate and support minimizing.

Dart Sass has replaced Ruby Sass as the canonical implementation of the Sass language.

In brief, @import is being replaced with more explicit @use and @forward rules. Over the next few years Sass @import will be deprecated, and then removed.

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

In principle, this information is already available through other means, but it is actually a fair amount of work to gather it in this form, and I think it could be useful to open it up to programmatic consumption.

The make install task installs the following files:

You can determine which openssl.cnf is being used by adding a spurious XXX to the file and see if openssl chokes.

If you have a better/simpler/"more official" solution, I'd still love to see it!

Many individuals are sentenced without any due process of the law. 

Focus on your application: forget about forms details like I'm dirty, field touched...

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

If you want to implement a form with a superb User Experience, you have to take care of many variables:

Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.

Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.

Unfortunately, it is an expression mired with a negative context because of how Rumsfeld used it to lie.

But it sounds like the library could use some way to setTouched()

When using a method in a top-level object to modify its state, such object isn't updated either.

There have been a number of issues opened about this, and a good deal of confusion. The docs indicate that if you mutate an object without there being a = involved, this doesn't trigger an update. But there's no mention that only assignments to certain variables trigger updates.

When you apply this pattern for the first time, it might feel very contrived.

How to fix nasty circular dependency issues once and for all

In the many projects I have maintained so far, sooner or later I always run into the same issue: circular module dependencies. Although there are many strategies and best practices on how to avoid circular dependencies. There is very little on how to fix them in a consistent and predictable way.

`Module ${a.id} may be unable to evaluate without ${b.id}, but is included first due to a cyclical dependency. Consider swapping the import statements in ${parent} to ensure correct ordering`

You might think something like “don’t request the same resource thousands of times a day, especially when it explicitly tells you it should be considered fresh for 90 days” would be obvious, but unfortunately it seems not.

1. The Omniscience Flaw:Reflection in practice requires teachers to effectively address whatever provokes them in the moment, yet sometimes the challenges that require action are not the ones teachers see or hear. For example, while working with a small group or helping an individual student, teachers may miss off-task students in other corners of the classroom. To maximize reflection in practice, teachers need extraordinary, all-knowing powers. While many teachers have superhero-like qualities, omniscience is not one of them.2. The Symptom-Treatment Flaw:Another inadequacy of situational thinking is that it does not provide time for the consideration of root causes. Because teachers must react in the moment, the critical pause required to conduct an “act of search or investigation” is not possible (Dewey, 1910).3. The Recollection Flaw:Reflection on practice relies on the accuracy of memory. Educators must recall the details of prior lessons to maximize their diagnosis, but those details often fade in memory. Reflection is best when specific, yet memory can only deliver an adumbrated version of what happened in any given hour.

Adding an API for something is an endorsement of that approach.

Wondering how to get field state from multiple fields at once? People coming from Redux-Form might be wondering where the equivalent of Redux Form's Fields component is, as a way to get state from several fields at once. The answer is that it's not included in the library because it's so easy to write one recursively composing Field components together.

Avid Bookshop in Athens, Ga., sends personalized URLs to customers with a list of handpicked recommendations.

Sometimes we can’t implement a solution that’s fully spec-compliant, and in those cases using a polyfill might be the wrong answer. A polyfill would translate into telling the rest of the codebase that it’s okay to use the feature, that it’ll work just like in modern browsers, but it might not in edge cases.

Maintainable code is code that you don’t need to modify when the browser changes.

I'm okay with an overall design that allows people to plugin the parts they need in order to be able to generically support a compile-to-javascript language, but to bake in support for one singular solution because its popular is simply bad engineering.

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.

hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.

@subfuzion That error looks unrelated to the existing discussion.

if you think this project can help you or anyone else, you may star it on GitHub

This proposal simplifies how React.createElement works and ultimately lets us remove the need for forwardRef.

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!

If you're targeting these platforms, there's no need to use a transpiler!

using EventTarget.addEventListener(), and this generally replaces using the old HTML event handler attributes.

This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.

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.

but the advantage is the "functional style" with its strict separation of scopes = less attack surface for bugs

It could be nothing more than my mind coming up with ways to justify the absence of variable declarations, because the thought of implementing them scares me.

It's certainly something I've wanted to reach for prior

To fix our Svelte version you might think we could use beforeUpdate or afterUpdate, but these lifecycle functions are related to the DOM being updated, not to prop updates. We only want to rerun our fetching when the album prop is changed.

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.