What produces that text, and what do you want to use it for?

If it's a list of actual pathnames, just replacing spaces by newlines may obviously mangle pathnames that contain embedded spaces, such as /User/myself/VirtualBox VMs/.

It seems inelegant to me to split this into two different modules, one to include, the other to extend.

include adds instance methods, extend adds class methods. This is how it works. I don't see inconsistency, only unmet expectations :)

What's the point of playing a game featuring fjords without also including vikings to pillage the other player's lands...I've actually developed two additional tiles for Fjords: The Dragon and The Marauding Hoard. Both do exactly that.(I've play tested them with a friend well over 40 times and we both agree that with an expanded set of Fjords tiles, these two greatly improve the game for us. I'll write the tiles up and post them to BGG... eventually)

Micromachines always focused on local multiplayer, and the fun their eccentric races of small toy vehicles competing on tracks made with everyday objects; and all that is present.

There's probably a thousand different directions you can go, but there just needs to be some kind of deeper hook to make this a full-fledged game.

Due to player actions not landing on the beat or being relevant to the background music, this 'rhythm' game falls short of it's goals. No feedback for early or late actions also diminishes the game.

Piano Cat is a challenging rhythm-based platformer game where you [...] jump to the beat [...].No, no, no, just no. This game has nothing to do with rhythm or doing something in sync to the music. If you try to do that, you will fail, a lot. In order to beat the stages you have to mute or ignore the music, ignore the obstacles and only look out for the buttons you have to press. When they light up green, you press the button. This means that you have to press them always too early to the action, ahead of time. If you try to time it to the music, it will be too late and not count. If you are good in these kind of games, this will totally throw you off here.The graphic are nice, the music is ok, but it does a terrible job in having rhythm based gameplay.

Ultimately, Shelter Generations relies on your capacity to dig into its subtleties. On that overt level it's an obtuse and obviously indie game, and it's really quite demanding of the player; it asks them to figure their own way through the game, and it asks them to really commit to an emotional connection to these hopeless little cubs.

The good news: everyone had a genuine blast. We knew we had experimented our way into something fun, even if the rules and designs still needed a lot of work.

To improve the usability of text fields and to determine which text field variables to alter, our researchers and designers conducted two studies between November 2016 and February 2017, with actual users.

You might not always notice, but Material Design is constantly evolving and iterating based on research.

To hear technologists describe it, digital memories are all about surfacing those archival smiles. But they’re also designed to increase engagement, the holy grail for ad-based business models.

I still have a photograph of the breakfast I made the morning I ended an eight-year relationship and canceled a wedding. It was an unremarkable breakfast—a fried egg—but it is now digitally fossilized in a floral dish we moved with us when we left New York and headed west. I don’t know why I took the photo, except, well, I do: I had fallen into the reflexive habit of taking photos of everything. Not long ago, the egg popped up as a “memory” in a photo app. The time stamp jolted my actual memory.

The Not So Good: The Dev/s seems to be in hiatus -- still waiting for the "coming soon" additional levels: Laser Land.

This isn't really a downside to React; one of React's strengths is that it lets you control so much and slot React into your environment

The people of the Kanienkéha:ka Nation– known in English as the Mohawk – are now considered the caretakers of the land and water around Montreal. In their language this island bears the name of Tiohtià:ke, which means “broken in two” because of the way the river breaks around it.

At Montréal in Action, we acknowledge that our work in Tiohtià:ke/Montréal takes place on the unceded Indigenous lands of the Kanien’kehá:ka/Mohawk Nation. Kanien’kehá:ka is known as a gathering place for many First Nations, and we recognize the Kanien’kehá:ka as custodians of the lands and waters on which we gather today. Committed to bringing justice to those who face systemic racism and discrimination in Tiohtià:ke/Montréal, Montreal in Action aims to work alongside Indigenous organizers to empower Indigenous and racialized communities. Through volunteer-led initiatives and the generation of accessible educational content, Montréal in Action strives to raise awareness on the consequences of colonialism and the ways in which it can be resisted.  

I/We would like to begin by acknowledging that Concordia University is located on unceded Indigenous lands. The Kanien’kehá:ka Nation is recognized as the custodians of the lands and waters on which we gather today. Tiohtià:ke/Montréal is historically known as a gathering place for many First Nations. Today, it is home to a diverse population of Indigenous and other peoples. We respect the continued connections with the past, present and future in our ongoing relationships with Indigenous and other peoples within the Montreal community.

Land Acknowledgement McGill University (Tiohtiá:ke/Montreal) is situated on the traditional territory of the Kanien’kehà:ka, a place which has long served as a site of meeting and exchange amongst many First Nations including the Kanien’kehá:ka of the Haudenosaunee Confederacy, Huron/Wendat, Abenaki, and Anishinaabeg. We recognize and respect the Kanien’kehà:ka as the traditional custodians of the lands and waters on which we meet today. The Cultural and Indigenous Research in Counselling Psychology (CIRC) lab is committed to supporting the Kanien’kehà:ka and Haudenosaunee Peoples, among other First Nations, Inuit, Métis, and Indigenous Peoples globally. CIRC aims to do all within its power to recruit and support Indigenous students as well as to partner with Indigenous communities in research projects that reflect their priorities.  

How many people die planetwide every year?

That has helped me understand this cycle of adoption, defeat, and detachment, but it's also taught me that the IndieWeb isn't a thing. You don't join the IndieWeb or complete the IndieWeb. Attempting to do so will drive you mad 😂

When I first read about the IndieWeb it felt like a lot. I've written about this before, but the sheer weight of jargon in the space is frankly terrifying.

However, if all of these are hosted in the same repository, you lose a lot of those benefits.

he goes on to talk about third party problems and how you're never guaranteed something is written correctly or that even if it is you don't know if it's the most optimal solution

Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.

I suspect you aren't seeing much discussion because those who have a reasonable process in place, and do not consider this situation to be as bad as everyone would have you believe, tend not to comment on it as much.

Unfortunately, this open nature also causes security risks, asevidenced by recent incidents of single packages that brokeor attacked software running on millions of computers.

As of May 24, 2016, antimicro has moved from https://github.com/Ryochan7/antimicro to https://github.com/AntiMicro/antimicro. Additionally, project management has passed from Travis (Ryochan7) to the AntiMicro organization due to Travis having other interests and priorities.

OpenFaaS is hosted by OpenFaaS Ltd (registration: 11076587), a company which also offers commercial services, homepage sponsorships, and support.

I don't myself understand what's going on, it clearly has something to do with source maps, but may also have to do with other sprockets changes.

I don't really understand what's going on. Clearly source maps have something to do with it -- a source map feature that doesn't handle SCSS very well, apparently.

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

Beykat yi duñu dem tool altine.

Sér bi aju na ci caru garab gi.

Ab paaka la yore.

It can also be included as individual modules, i.e. Hashie::Extensions::MethodReader, Hashie::Extensions::MethodWriter and Hashie::Extensions::MethodQuery.

The fact we’re using ActiveRecord (or something looking like it) doesn’t mean Trailblazer only works with Rails! Most people are familiar with its API, so we chose to use “ActiveRecord” in this tutorial.

So, the sad conclusion is: all problems must be resolved individually depending on a specific usage context. There’s no silver bullet to resolve all ZeroDivisionErrors once and for all. And again, I am not even covering complex IO flows with retry policies and expotential timeouts.

Feel free to pick and choose what you need for your applications.

What this means is: I better refrain from writing a new book and we rather focus on more and better docs.

And yes, at TRB GmbH, we do pay people to work on OSS

The LGPL allows users to use and integrate LGPL software components into their own software without being required to release the source code of their own software components. However, if users modify LGPL software components (“derivative work”), they are required to make the modified software component available under the same LGPL license. To avoid the latter with TRB, users have to comply with para. 5 LGPLv2.1: A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. In other words: if you use the TRB libraries in your commercial applications or Open-Source projects, you’re not creating a derivative work of Trailblazer. Your software can be distributed under any terms.

The bare bones operation without any Trailblazery is implemented in the trailblazer-operation gem and can be used without our stack.

Trailblazer offers you a new, more intuitive file layout in applications.

Instead of grouping by technology, classes and views are structured by concept, and then by technology. A concept can relate to a model, or can be a completely abstract concern such as invoicing.

Concepts over Technology

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

Only use what you like.

you can pick which layers you want. Trailblazer doesn't impose technical implementations

Lambda defaults are evaluated in the context of the interaction, so you can use the values of other inputs in them.

The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false or nil.

I like this idea a lot. I have had problems too with having multi-parameters assignments depending so heavily on active record.

The more important point comes from a program design perspective. Here, "programming to an interface" means focusing your design on what the code is doing, not how it does it. This is a vital distinction that pushes your design towards correctness and flexibility.

I think maybe the terms we're using are a bit confusing.

Like all best practices, I think the way you will resolve a problem will depend of the application you are doing.

Bowline will bind up Ruby and HTML - letting you concentrate on the more interesting things

We also find it hard to agree on what good names and bad names look like, which makes it hard to know when renaming improves a name.

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

As soon as you're displaying content from another domain, you're basically trusting that domain not to serve-up malware. There's nothing wrong with iframes per se. If you control the content of the iframe, they're perfectly safe.

systemd has such huge documentation. systemd.unit Did you try searching for explanation yourself? What did you find?

http://letmegooglethat.com/?q=How+to+change+the+default+search+engine+in+chromium&l=1

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.

This is really cool! Having the content decide on the space it needs is so powerful!

I'm very (VERY!) tempted to use that ppa, but without offense to it's maintainers... it's just some random ppa. If it had more "traction" I'd use it. Right now it has only 3 maintainers.

What's wrong here is Canonical trying to position itself as a powerhouse and ascertain control over Linux users.

Canonical are really taking whole chapters out of the Microsoft 'How To' book. Do it our way or not at all.

What we didn't want it to be was for Canonical to control the distribution of software between distributions and 3rd party editors, to prevent direct distribution from editors, to make it so software worked better in Ubuntu than anywhere else and to make its store a requirement,"

👍 Upvote issue #204 if you want to see it land faster.

Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.

I don’t find the software slow, I find the startup time for snap packages when the start for the first time on a session slow, but that has been improved, and it’s public that the snapcraft team has been working hard to improve that.

« Half solved » because, hey, still it’s proprietary so who knows ? You have to trust the software editor then, it’s just moving the trust cursor.

But now Chromium is no more available as deb, so what to expect ?

Slots can already be pretty confusing to comprehend, I think it is better to stick to what people (may) already know.

With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.

It would help greatly if you provided references for "articles online about what universal javascript is". But I think this is just too dependent on opinion.

For use$ since svelte is never going to support actions for components, i designed something that reminds React hooks that will in some ways replace this feature.

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

I'm still calling this v1.00 as this is what will be included in the first print run.

We won’t go into all the details that make an application a PWA, because it all sort of depends on who you ask.

Man, for some reason, I really like this answer. I recognize it's a bit more complicated, but it seems so useful. And given that I'm no bash expert, it leads me to believe that my logic is faulty, and there's something wrong with this methodology, otherwise, I feel others would have given it more praise. So, what's the problem with this function? Is there anything I should be looking out for here?

obviously it's too late, but it's a good practice to keep the 3rd party dependencies mirrored in your own infrastructure :) There is NO GUARANTEE that even a huge site (like launchpad for downloading DEBs) won't go down over a period of time.

It is open to the community to help set its direction.

We are working to develop better communication within TC39 and with the broader JavaScript community so that this sort of problem can be corrected sooner in the future.

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)

In July 2010, Microsoft let go Jimmy Schementi, one of two remaining members of the IronRuby core team, and stopped funding the project.[19][20] In October 2010 Microsoft announced the Iron projects (IronRuby and IronPython) were being changed to "external" projects and enabling "community members to make contributions without Microsoft's involvement or sponsorship by a Microsoft employee".

There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

is this solution considered a hack or is something that we can use as an approved workaround in scenarios where we need to manually trigger validations?

Vue Final Form A form state management system for Vue that uses Final Form under the hood.

Typically, platform accessibility APIs do not provide a vehicle to notify assistive technologies of a role value change, and consequently, assistive technologies may not update their cache with the new role attribute value.

This implementation is based upon following sources: JavaScript Debounce Function by David Walsh Lodash implementation

Looks like the problem is that debounce defaults to waiting for 0 ms ... which is completely useless!

Type safety. Entire codebase is written in TypeScript.

mixing the turing complete of javascript with the markup of HTML eliminates the readability of JSX so that it is actually harder to parse than a solution like hyperscript

andrewdeandrade commented on Jul 31, 2015

The only "issue" it has is that its unfamiliar. People have been working with HTML for years and are comfortable with it. That's basically the only reason that people find it more readable. If you make an effort to spend sometime with hyperscript, it becomes as familiar and readable as jsx.

Encoding is dependent on the type of output - which means that for example a string, which will be used in a JavaScript variable, should be treated (encoded) differently than a string which will be used in plain HTML.