Using operations as test factories is a fundamental concept of Trailblazer to remove buggy redundancy in tests and manual factories.

It will be useless work when gvfs-open will solve the bug, but in the meantime...

A simple, yet surprisingly mind-boggling puzzle game. Simplicity may be perceived as a negative connotation when it comes to games for many people, but Neon Warp's simplicity actually works in it's favor in the best way possible and becomes one of it's strength.

There used to be other backends in addition to C: Java, CSharp, and Javascript but those suffered from bitrot and have been removed.

I'd suggest there ought to be config to disable source maps specifically, and specifically for either CSS or JS (not alwasy both), without turning off debug mode. As you note, debug mode does all sorts of different things that you might want with or without source maps.

# This behavior can be disabled with: # # environment.unregister_postprocessor 'application/javascript', Sprockets::SafetyColons

I totally understand that there may be a majority still considering this a bad practice and thus keeping it disabled by default in production seem ok. But there could at least be an option to enable it for people who want to, no?

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.

Yes, but honestly, and no offense intended, but I don't see the harm in these type questions, nor why some people are offended when they are asked. If I owed a website, I wouldn't mind it because it just creates more pages that can be indexed. I see it as helping the website. But, I did look and didn't see a simple answer. Again, no offense is intended. I've just never understood the complaints.

Personally, I'm starting to think that the feature where it automatically adds xray.js to the document is more trouble than it's worth. I propose that we remove that automatic feature and just make it part of the install instructions that you need to add this line to your template/layout: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %>

Now that I've thought more about it, I honestly think the auto-adding the script feature is overrated, over-complicated, and error-prone (#98, #100), and I propose we just remove it (#110).

now that I've thought more about it, I think the auto-adding the script feature is overrated, over-complicated, and error-prone (#100), and ought to just be removed (#110).

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

but if you were previously using regexp or proc values, they won't work at all with Sprockets 4, and if you try you'll get an exception raised that looks like NoMethodError: undefined method 'start_with?'

The gem was inspired by the Kleisli gem.

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.

Scrivener is Bureaucrat's little brother. It draws all the inspiration from it and its features are a subset of Bureaucrat's.

As a result, dry-types, dry-struct and dry-schema were born. These projects should be considered as virtus' successors, with better separation of concerns and better features.

Special thanks to the owners of the great gems that inspired this work: Nick Sutterer - creator of reform Nathan Van der Auwera - creator of cocoon

The Java packages contain a lot of great code. But there are also parts of that code I'm sure the authors are embarrassed to admit they wrote.

The reason Reform does updating attributes and validation in the same step is because I wanna reduce public methods. This is to save users from having to remember state.

‘Programs are meant to be read by humans and only incidentally for computers to execute.’

Emerald

work against the shared objective of a more open and equitable scholarly ecosystem

However, we are unable to support one route to compliance offered by Plan S,

If the full SSN provides an account

If the full SSN does not populate an account

Part of me thinks that open source can be more rewarding to the creators/contributors. But maybe the real contribution is the permanent addition to the tools available to humanity, and if you have the wits, you can make a decent business out of it without tainting open source.

For a sufficiently successful and industry-relevant open source project, it's possible for the main developers to earn a living e.g. by selling related consulting services.

Although it is open-source, Snap on the other hand, only works with the Ubuntu Store. Nobody knows how to make a Snap Store and nobody can. The Snap client is designed to work with only one source, following a protocol which isn’t open, and using only one authentication system. Snapd is nothing on its own, it can only work with the Ubuntu Store.

that's by design:

It appears that Canonical is continuing it's vice grip of unliateral, maybe dictatorial control on the development of Snap to the benefit of Ubuntu, but to the detriment of groups like Linuxmint, and all other non-Ubuntu based Linux distributions - like CentOS/Redhat, Suse/openSuSe, Solus, Arch/Manjaro, PCLinuxOS, etc, that are pushing Flatpak as a truly cross-distro application solution that works equally well and non-problematic for all. .

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

By design, snap apps have no access to /etc. They live in their own little world, but instead of a normal chroot, they are splatted all over the standard Linux filesystem layout. With other bits mounted hither and thither. Its a mess, and subject to change with each release.

If we're not careful, it could become the new 'systemd' problem It probably already is. I don't want to sound too Stallman, but this is the inevitable "company" influence you'll always have. Companies do have their objectives which they will pursue determinedly, since they are not philanthropic (no judgment, just observation). Systemd and Red Hat. Nvidia and their drivers. Google and Android. Apple and iOS. Manufacturers with MS only support. And Canonical also has a history there: the Amazon links, Unity, Mir, and now snap.

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,"

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).

I figured I could try making my own with modern technologies.

The CSS Zen Garden era was hugely inspirational to many.

§ 2645. Charters; adoption, repeal, or amendment; procedure (a) A municipality may propose to the General Assembly to adopt, repeal, or amend its charter by majority vote of the legal voters of the municipality present and voting at any annual or special meeting warned for that purpose in accordance with the following procedure: (1) A proposal to adopt, repeal, or amend a municipal charter (charter proposal) may be made by the legislative body of the municipality or by petition of five percent of the voters of the municipality. (2) An official copy of the charter proposal shall be filed as a public record in the office of the clerk of the municipality at least 10 days before the first public hearing. The clerk shall certify the date on which he or she received the official copy, and the dated copies thereof shall be made available to members of the public upon request.

This is a by-product of the success of Ubuntu. Whether people like it or not, most software available for Linux will target Ubuntu first. There may be packages available later for other distros / systems, but on the whole, you can be sure a software developer will target Ubuntu if they target Linux.

Treating the web as a compile target has a lot of implications, many negative. For example “view source” is a beloved feature of the web that’s an important part of its history and especially useful for learning, but Svelte’s compiled output is much harder to follow than its source. Source maps, which Svelte uses to map its web language outputs back to its source language, have limitations.

Some of these are absent-by-design

For a long time, the blue flame coming out of a gas burner has evoked cleanliness. That was no accident, but the result of a concerted advertising campaign.

Familiar npm inspired dependency management.

All projects here are completely frozen, though feel free to fork and continue using them on your own.

So far, all the grouping we've done is according to the unique values within a column or set of columns (using PARTITION BY). However, you can do even fancier things by making the group relative to each row. In other words, as SQL runs through each row, it will perform a calculation for the surrounding rows. This allows you to do things like get a sum for only the 5 previous rows. Here is a diagram that demonstrates which rows SQL will consider (in purple) when it reaches a given row (in aqua), if we tell it to look at the 5 previous rows:

I’ve asked Mark about the inspiration and, yes, SNCF/Paris Connection, was in there, but he also cited Knizia’s Spectaculum for parts.

at least in the meantime allow users to bypass the security protections in situations where they are confident of the source of the layers

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.

deprecated – plese see / use caly

Highly inspired by Foreman.

Or even keep as is, the simplicity of this feels right in line with svelte's simplicity :)

Since 'using decorators' has come to mean 'smothering your code in @ symbols' it's probably no longer a great name.

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

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

All validators can be used independently. Inspried by functional programming paradigm, all built in validators are just functions.

FormValidation.validators.creditCard().validate({

FormValidation.formValidation(formElement

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.

It causes some implementation complexity just by existing.

Deku is a library for rendering interfaces using pure functions and virtual DOM.

bringing Vue-style reactive stores with data and computed properties into Svelte

This library takes inspiration from Tailwind and utilizes Otion to provide means of efficiently generating atomic styles from shorthand syntax and appending them to the DOM at runtime.

I'm suggesting there should be a way to write lifecycle related code that also responds to changing props, like how useEffect works. I think how React handles this could be a good source of inspiration.

Most of the tech news we get barraged with is about algorithms, AI, robots, and self-driving cars, all of which fit this pattern. I am not saying that such developments are not efficient and convenient; this is not a judgment. I am simply noticing a pattern and wondering if, in recognizing that pattern, we might realize that it is only one trajectory of many. There are other possible roads we could be going down, and the one we’re on is not inevitable or the only one; it has been (possibly unconsciously) chosen.

duty of care

But Vue’s simplicity runs more deeply in its design.

transport en commun

However, if you want to create a backend API that is meant to be consumed only by your frontend, then you don't need REST nor GraphQL — RPC, such as Wildcard, is enough.

inspired by the Express router

The $ contract for auto-sub­scrib­ing is lovely in its sim­plic­ity and flex­i­bil­ity. You can adapt your own preferred state-man­age­ment pattern or library, with or without Svelte stores as helpers. Svelte does not fuss about how you want to manage your state.

“Simplicity in all we do” is one of the core values at DigitalOcean. This includes all aspects of our product portfolio: UX, API, CLI, docs, billing, and pricing.

Because Svelte is a compiler, we're not bound to the peculiarities of JavaScript: we can design a component authoring experience, rather than having to fit it around the semantics of the language.

Rollup also does something very different compared to the other bundlers. It only tries to achieve one simple goal: Bundle ES modules together and optimise the bundle.

Did you know that you can create a Svelte component and with almost no extra steps distribute- and use it like any classic old Javascript library through a global constructor (let myComponent = new MyComponent())?

Svelta was greatly inspired by Vuexy.

Svelta was inspired by them.

“You are free to eat from any tree in the garden;(W) 17 but you must not eat from the tree of the knowledge of good and evil,(X) for when you eat from it you will certainly die.”

In a similar vein to (#33), it is arguably just something that compensates for the lack of power in the template language relative to JavaScript.

The complaint is that by choosing less powerful languages, template-based frameworks are then forced to reintroduce uncanny-valley versions of those constructs in order to add back in missing functionality, thereby increasing the mount of stuff people have to learn.

There are tools in Svelte that break this expectation to a degree, but they are a bit annoying to use, which makes it an active decision on the part of the developer. The API hints at the way we want you to do things because we feel that this will give the better experience.

It’s become increasingly common to divide code into components, rather than by file type. React, for example, allows for the collocation of a components markup and JavaScript. In Svelte, this is taken one logical step further: the Javascript, markup and styling for a component can all exist together in a single `.svelte`​ file

By enforcing this practice, Svelte can make some assumptions that simplify your code.

For the editor level, we took inspiration from Pine's work in the Vue ecosystem via Vetur.

This is what I love about React, it's JavaScript basically, not a DSL

Extend ActionConfig interface in rfc-extended.d.ts file with new params: import * as RFC from 'react-fetching-library'; declare module 'react-fetching-library' { export interface ActionConfig { // Only new params skipAuth: boolean; params: any; }; }

But it's easy to imagine that the caption was incorrect for too long because those who know the language, know where the mistake is, and those who don't, think that it's the correct way to spell it.

+1 for taking the language back.

Can't upvote this enough. It is highly irritating to see language destroyed (and we wonder why kids bastardize the language..).

It reused many ideas and classes from Doug Lea's Collections package, which was deprecated as a result.

In addition to the schema.org structured data format, there are other formats supported by search engines and social media networks. See the supported documentation: Twitter Cards meta tags Facebook Open Graph meta tags

A growing number of platforms, vendors, and partners support the AMP Project by providing custom components or offering integration with AMP pages within their platforms.

A growing number of email platforms, clients and providers support AMP for Email within their platforms.

If you have worked with emails before, the idea of placing a script into an email may set off alarm bells in your head! Rest assured, email providers who support AMP emails enforce fierce security checks that only allow vetted AMP scripts to run in their clients. This enables dynamic and interactive features to run directly in the recipients mailboxes with no security vulnerabilities! Read more about the required markup for AMP Emails here.

All activities are best-effort (keep in mind that most of us are volunteer developers).

The date, time and place are scheduled according to when/where we can reserve Matz's time.

Data that is sent over the network is compressed (optionally) and encrypted (always). When receiving data it must be decrypted and then (if compressed) decompressed.

In a rare show of solidarity, both British English and American English spell advertise with an s in all forms.

As an act of defiance, I will only use advertize. I’ve added the word to my spell check. As an American, it makes sense for me to use this spelling since other -ise words use the more phonetic -ize suffix.

Specify a GanttStart and a GanttDue, GanttLab will give you the higher overview.

Where we got our inspiration The awesome Travis CI had the great idea to use a .yml file for builds and was followed by the popular CircleCI. We're happy to follow this approach, which we believe is superior than any other.

A United States government application

We believe in the power of open source software. That’s why we participate in, contribute to, and support the open source community so strongly.