I am not sure this whole ecosystem currently has much maintainers unfortunately. :( Pick your reaction

I agree about lack of maintenance. It's probably because people use more and more Webpack.

I think that over time the distinction is lost. My math teacher, 35 years ago stated "formulas are used in chemistry, in math we have equations". To this day, the word 'formula' in math seems wrong, but I'd accept it's used commonly.

There are myriads of platformers around, it's an oversaturated market, and just like industrial designer Karim Rashid said about there being no excuse by this point to make an uncomfortable chair, there's no excuse by this point to make a boring patformer.

Nee na ndëmm amul.

Fexeel ba kër gi bañ ñàkk alkol.

Peñe, kenn du ko able.

The guard name defaults to default and can be set via name:. This allows having multiple guards.

# Yes, you can use lambdas as steps, too! step ->(ctx, params:, **) { params.is_a?(Hash) }

A nested activity doesn’t have to have two ends, only.

Patching has no implicit, magical side-effects and is strongly encouraged to customize flows for a specific case in a quick and consise way.

Please note that I/O works for both “simple” tasks as well as nested activities.

Sure, zero-config one-click installs are nice and all, but:

Not all cases can be covered and easily restored. And sometimes when we will reuse this function for different use-cases we will find out that it requires different restore logic.

But why do we return 0? Why not 1? Why not None? And while None in most cases is as bad (or even worse) than the exceptions, turns out we should heavily rely on business logic and use-cases of this function.

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.

They possess an unwavering belief in “one right way.”

There is nothing wrong with building your own “service layer”, and many companies have left the Traiblazer track in the past years due to problems they had and that we think we now fixed.

So which seems likelier: that we're no better off than we were a quarter century ago, or that Shadow Stats is total bunk?

Note that it's perfectly fine to add errors during execution. Not all errors have to come from type checking or validation.

But ActiveModel doesn't support out of the box argument parsing, e.g. having a datetime attribute be a datetime attribute and a boolean attribute be a boolean attribute.

you mean Action Form, right?

Set your models free from the accepts_nested_attributes_for helper. Action Form provides an object-oriented approach to represent your forms by building a form object, rather than relying on Active Record internals for doing this.

rafaelfranca closed this on Feb 27, 2018

many successful projects have proven that you can develop high-quality code more rapidly (and cost effectively) this way than with the traditional pipelined approach

*initialize* also supports passing resources (also attributes if you would # like to) manually

My concern with this approach is still that it's somewhat brittle with the current implementation of valid? because whilst valid? appears to be a predicate and should have no side effects, this is not the case and could remove the errors applied by one of the steps above.

Not fun by yourself and the game is dead. Wouldn't be much fun with others either.

It's difficult because it's a case-by-case basis - there is no one right answer so it falls into subjective arguments.

The only problem is that our PJAX library is no longer maintained and was preventing us from updating jQuery (ugh). So it had to go.

Yeah, this is one of those cases where it's not a "yes or no" type answer.

Multiple answers are great. Check out all of them, not just the accepted one.

As you installed a development release (17.04) that had only a 9-month life span and had an End of Life (EOL) in Jan 2018, there is no way to upgrade it to 17.10 as that went EOL back in July 2018. So as you're stuck with a release without an upgrade path (as you cannot skip versions)

Maintaining open source software requires energy and a "want"/"passion". I've not been using this project myself for years, and I mainly work in other things than Rails at this point. That means I'm far removed from this project and see no personal gain in maintaining the energy to keep this going.

Good for the likes of Mint to say NO.

It must be called during the component's initialisation (but doesn't need to live inside the component; it can be called from an external module).

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.

When enough people make false promises, words stop meaning anything, then there are no answers just better and better lies.

For larger files, the wait time can be especially problematic. A standard download is an all-or-nothing affair—interruptions can corrupt them and render them useless. Worse, it can waste valuable data on a metered data plan, an unfortunately all-too-relevant concern.

I guess it's about "preloading" and not "navigation", if it's the case, then I guess there is still no way to attach to navigation events, and this issue should be kept open.

No JS event is fired, so there currently isn't any clean way to do this that I can see.

Fixes #1037 allow slotted components via making <Component> <Inner slot="foo" /> </Component> as a sugar syntax for <Component> <svelte:fragment slot="foo"> <Inner /> </svelte:fragment> </Component>

It's possible to have multiple event listeners for the same event

There's a huge area of seemingly obvious user-centric products that don't exist simply because there isn't a working business model to support it.

Google Archive Where old projects go to retire.

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.

@monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see

I think a casual look at the game could be quick to take fault that some moves are scripted, and perhaps they are.  If play passes to you and there is a stock to be had for free…why _not_ take it? For me, it’s a distraction. The player before you likely considered the options and found the game state to be worth tempting you with that. Those free, or even cheap, stocks won’t gain you the influence in any companies that can make your personal cache more valuable.

Ultimately, I’m an “are there tough decisions?” kind of gamer, and on that matter I’m torn. There are some turns and some positions and some situations that will play themselves. Sometimes obviously so, and sometimes after you think it out.

But seriously, give snowpack a read to understand the benefits of leaning on standard esm imports, allowing you to avoid a bundling process entirely.

I don't need to support non-esm browsers for most projects and I really like the idea of a super light build process. By removing the complexity of configuration and the overhead of bundling, svelvet makes the development process an optimal experience for myself and hopefully others

It replaces heavier, more complex bundlers like webpack or Parcel in your development workflow.

We do not utilize a formulaic or standard, formalized benchmarking level or element in setting our executive compensation relative to that of other companies. 

GET is the primary mechanism of information retrieval and the focus of almost all performance optimizations.

There's not much we can do there. It's not possible for a Svelte component to inspect another Svelte component and check if it exposes any prop

I understand this is not ideal, but sadly this is not something we can change as it's how Svelte works.

Just coming here to voice my agreement that these warnings are annoying and exist in other libraries as well. For me this happened with svelma. I didn't write the library code, so I don't have complete control over it even though I agree there is an argument to be had around whether I should be notified anyway. In either case, these warnings should be easily disabled since libraries don't always get updated over night.

In Cantrell's view, pharmaceutical companies are the only ones that have the money to do long-term studies on drug's efficacy, "but there's absolutely no financial incentive for them to do it." (When the medicine you need expires, you, or your insurer, pay for more.)

We don’t need to apply refactorings we don’t want.

We don’t have to compromise the architecture, API or semantic structure of our code base.

Intercepting proxies are commonly used in businesses to enforce acceptable use policy, and to ease administrative overheads since no client browser configuration is required.

The false promise of your source code repository is that everything it contains is “good.” To complete your task, just find something that does something similar, copy, modify, and you’re done. Looking inside the same repository seems like a safety mechanism for quality but, in fact, there is no such guarantee.

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!

Most projects and teams need a balance between "big" and "no."

In highlighting the dangers of big-up-front-design (BUFD) and waterfall development, Agilists seem to advocate no-up-front-design (NUFD) or no-up-front-requirements (NUFR) or no-up-front-architecture (NUFA).

It was clear no one was interested in what I was working towards.

React hook for creating a value exactly once. useMemo doesn't give this guarantee unfortunately - https://reactjs.org/docs/hooks-faq.html#how-to-create-expensive-objects-lazily

However, it only serves as a hint, and doesn’t guarantee the computation won’t re-run. But sometimes you need to be sure an object is only created once.

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

But I just want to say npx is lame. It should have been npm run or npm exec or something.

More than one subscriber can subscribe to the same field.

Wow, no answers to this question. That's too bad. Did you ever find the solution?

Luckily, there is absolutely no good reason not to use strict mode for everything — so the solution to this problem is to lobby the authors of those modules to update them.

and one which you don’t need to use and won’t add any code to your app if you choose not to use

And of course, if you don't use them you don't pay for them

The more I think about this, the more I think that maybe React already has the right solution to this particular issue, and we're tying ourselves in knots trying to avoid unnecessary re-rendering. Basically, this JSX... <Foo {...a} b={1} {...c} d={2}/> ...translates to this JS: React.createElement(Foo, _extends({}, a, { b: 1 }, c, { d: 2 })); If we did the same thing (i.e. bail out of the optimisation allowed by knowing the attribute names ahead of time), our lives would get a lot simpler, and the performance characteristics would be pretty similar in all but somewhat contrived scenarios, I think. (It'll still be faster than React, anyway!)

When you visit location /one and the server redirects you to location /two, you expect the browser’s address bar to display the redirected URL. However, Turbolinks makes requests using XMLHttpRequest, which transparently follows redirects. There’s no way for Turbolinks to tell whether a request resulted in a redirect without additional cooperation from the server. To work around this problem, send the Turbolinks-Location header in the final response to a visit that was redirected, and Turbolinks will replace the browser’s topmost history entry with the value you provide.

Open Science by Design

There's a few other questions on StackOverflow regarding how to structure YAML files for i18n, and I don't think there is a 'right' answer to your question. If it works for you, then great! I would say that any answer you get will be completely subjective, and more about i18n and translation management rather than anything specifically to do with the Rails way.

This repository has been archived by the owner. It is now read-only.

I could not find any way to do this with the standard library.

It’s even worse that there’s no alternative method that does the unsurprising thing IMO.

As of March 2018, Tor Messenger is no longer maintained and you should NOT use it.

Between 2008 and 2010 weren't any updated packages, resulting in the bundled version of Tor becoming obsolete and unable to connect to the Tor network,[2] which was the reason for the appearance of forks that basically just replaced the bundled Tor.exe with a current one.

We have come to a place where thanks to many libraries and frameworks, and overall improving software, what would’ve once used many developers to build from scratch is now more often than not, a bunch of people plumbing different things together. Software is creating software faster than we can use it. This is also why you are seeing so many of these “no-code” or “low-code” solutions pop up all over the place. There are increasingly fewer reasons to write code, and those who are writing code should, and do, increasingly write less of it. This will only be more accelerated by shifting to remote work due to how it’s going to change how we decide what code to write.

Anyone who’s spent a few months at a sizable tech company can tell you that a lot of software seems to exist primarily because companies have hired people to write and maintain them. In some ways, the software serves not the business, but the people who have written it, and then those who need to maintain it. This is stupid, but also very, very true.

Gifts have ribbons, not strings.

If we find that GitLab doesn't work as people expect, the documentation should be updated so this is no longer a surprise. This applies whether we classify it as a feature request or a bug.

A complete snapshot of the user’s browser window at that moment in time will be captured, pixel by pixel (!)

The mix of a fingerprint and first-party cookies is pervasive as Google can give a very high level of entropy when it comes to distinguishing an individual person.

Google encouraging site admins to put reCaptcha all over their sites, and then sharing the resulting risk scores with those admins is great for security, Perona thinks, because he says it “gives site owners more control and visibility over what’s going on” with potential scammer and bot attacks, and the system will give admins more accurate scores than if reCaptcha is only using data from a single webpage to analyze user behavior. But there’s the trade-off. “It makes sense and makes it more user-friendly, but it also gives Google more data,”

For instance, Google’s reCaptcha cookie follows the same logic of the Facebook “like” button when it’s embedded in other websites—it gives that site some social media functionality, but it also lets Facebook know that you’re there.

You have the right to withdraw from this contract within 14 days without giving any reason.

a person can withdraw from research at any point of time and it is no binding of participant to reveal the reason of discontinuation

Add-ons must function only as described, and should provide an appealing user experience. Based on the description of the add-on, a user must be able to understand and use the add-on’s features without requiring expert knowledge.

But, I was no longer using the gem, the issue activity was overwhelming, and the codebase in serious need of reworking.

Becouse of CanCan, StateMachine and others I deside to create OpenSource organization to maintain gems. People disappear, lose their passion about coding, get new interests, families, children. But if us many we can support gems much longer. I dont pretend to be an expierenced ruby developer, but I can do administarative work: managing teams, members, approve simple pool-requests. If you think it good idea and want to support some inactive gems, not life time, maybe just a little - welcome to organization.

There's actually discussion among the rubygems team about a process for putting gems "up for adoption" that you might be interested in: http://www.benjaminfleischer.com/2014/08/17/rubygems-adoption-center/

you can use my fork. It has all fixes and many people are using it. Pick your reaction