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.

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

Disclaimer: I’m new to Svelte so this isn’t so much a recommendation as it is a “I guess this is a way to do it 🤷‍♂️”

They should see comments as part of that process. It’s not the product that matters, it’s the participation.

Golwg360 will feature a rolling news service and will give businesses, public bodies and individuals the chance to set up their own micro-sites.

However, a healthy news ecosystem doesn’t just require a thriving free press, it also needs a diversity of curators, newsletters and content discovery options that enable the weird and wonderful to surface. We want to use Nuzzel as a test kitchen to see what models works for curators as well as content creators. The simple goal is a sustainable open web where the goals of creators, curators and consumers are aligned around the best possible experience.

Republishing guidelines

Grant Potter

The architecture of the platform where I published allowed authorial control of content but could not control context collapse or social interactions.

There is a sense that one can cobble together a common public by overlapping various social media platforms and audiences. Many of my colleagues are doing a fine job of problematizing the intersections of private social media and the university. The larger project from which this essay is drawn is part of that emerging conversation.

When you can assume that all the materials you’re using in and with your class are open educational resources, here’s one way to remix the effective practices listed above with OER in order to provide you and your students with opportunities to spend your time and effort on work that makes the world a better place instead of wasting it on disposable assignments.

Shopify-Ex would offer retailers something they don’t get from Amazon: partnership. Newco would provide merchants a lot of the great taste of Amazon (robust e-commerce tools and fulfillment) without the calories (merchants keep their data, control the customer, branding, no private label launches on backs of merchant data).

Professional blogging; whether that be funded by advertisers, subscribers, fans – is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?

I just wrote a long, considered, friendly, and I hope helpful comment here but -- sorry, I have to see the irony in this once again -- your system wouldn't let me say anything longer tahn 1,500 characters. If you want more intelligent conversations, you might want to expand past soundbite.

But note well, my friend, that all of these people are speaking to you with intelligence, experience, generosity, and civility. You know what’s missing? Two things: First, the sort of nasty comments your own piece decries. And second: You.

The first is when you build businesses on platforms your don’t own; and then they change the rules on you.

It just makes sense that news outlets and libraries collaborate. That’s something we at the News Co/Lab have believed from the beginning, and it’s something we’ve seen work very well in our partnerships

Mr. Duncombe published the results online using CommentPress, open-source software by the Institute for the Future of the Book. Online discussion and commenting is made possible by Social Book, a social-reading platform created by the institute.

What if the best tools for thought have already been discovered? In other words, perhaps the 1960s and 1970s were an unrepeatable golden age, and all we can expect in the future is gradual incremental improvement, and perhaps the occasional major breakthrough, at a decreasing frequency?

Put another way, many tools for thought are public goods. They often cost a lot to develop initially, but it’s easy for others to duplicate and improve on them, free riding on the initial investment. While such duplication and improvement is good for our society as a whole, it’s bad for the companies that make that initial investment. And so such tools for thought suffer the fate of many public goods: our society collectively underinvests in them, relative to the benefits they provide

In the meantime, stay in touch with Crosscut by: Liking us on Facebook  Following us on Twitter  Following us on Instagram Chatting with us on Reddit Signing up for one (or all) of our newsletters 

It's sort of unfortunate that the justification for existence comes from pointing at gaps.

you expect some hyperbole during these presentations and you should of course question and verify the claims being made.

helped me carve a niche for what would become SolidJS. I still see that space today, so I'm glad that I did.

Very few were interested in furthering the platform in the places they just took for granted.

Over time Adam, Surplus' creator, had less and less time to spend on the project and I decided to take my own shot.

It was only pragmatic to use a tool that basically gives you that all for free.

Templates are prone to unnoticed runtime errors, are hard to test, and are not easy to restructure or decompose.

There's one downside to Reacts reactivity model - the hooks (useState and useEffect) have to always be called in the same order and you can't put them inside an if block.

It's designed for Single Page Applications (SPA). If you need Server Side Rendering then consider using Sapper.

For an API used by many third parties with many diverse uses cases, GraphQL is the right tool.

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.

Class participation vs. attending class.The quantity andquality of online class participation replaces on-siteattendance

Those banners should really be reserved for the important stuff. Because they're not, I've developed a reflex to immediately close those banners without paying attention. It's almost the same as blocking it with an ad-blocker; which defies the (original) purpose of banners.

But maybe this PR should still be merged until he finds time for that?

Sorry this sat for so long!

He says that he sees the combination of long form pieces and Q&A as a new level of support. “We used to have level one, which was sending a ticket to the help desk, and it was something we could easily resolve for you. Level two was a more complex problem that maybe required an engineer or specialist from a certain team to figure out. I look at this new system as a level zero.” Before sending us a ticket, folks can search Teams. If they find a question that solves the problem, great. If they need more details, they can follow links to in-depth articles or collections that bring together Q&A and article with the same tags.“

no one wants to feel like their time is wasted

There is this black hole syndrome where you spend hours working on something and get no feedback.

Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.

I took the same approach with _layout.svelte and not just for the svelte-apollo client. Except I put all of that setup into another module (setup.js) and imported from _layout. I just couldn't stomach having all that code actually in my _layout file. It's for layout, supposedly, but it's the only component that is a parent to the whole app.