but I still have no idea if I'm writing this new file correctly.

For the $$$ question, nothing comes to mind. These problems i'm hitting up against are larger than a contractor could solve in a few hours of work (which would be hundreds/thousands of dollars).

I think that's fine, but I also don't particularly care about @mikeycgto's desire to not have the linking comment be present in the minified JS.

we used `backticks` to jump into native Javascript to use moment.js

I went by the reviews and now i am seeing a pattern on STEAM where even good reviews are bought and paid for and not really player revews and that actuallly watching game play from google will be my best option in the future. AGAIN don;t trust bought and paid for reviews from STEAM....I just learned and realised this now

step :direct_debit

This connects the failure output to the previous task, which might create an infinity loop and waste your computing time - it is solely here for demonstrational purposes.

In both filters, you’re able to rename and coerce variables. This gives you a bit more control than the simpler DSL.

Yes, we could and should use Reform or Dry-validation here.

certainly I wouldn't want it to start telling me that I'm not catching these!

Though rarer in computer science, one can use category theory directly, which defines a monad as a functor with two additional natural transformations. So to begin, a structure requires a higher-order function (or "functional") named map to qualify as a functor:

This stuff is intoxicating once you get into it.

note that TRB source code modifications are not proprietary

The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.

No one has requested it before so it's certainly not something we're planning to add.

To give a little more context, structures like this often come up in my work when dealing with NoSQL datastores, especially ones that rely heavily on JSON, like Firebase, where a records unique ID isn't part of the record itself, just a key that points to it. I think most Ruby/Rails projects tend towards use cases where these sort of datastores aren't appropriate/necessary, so it makes sense that this wouldn't come up as quickly as other structures.

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.

I will continue to use form objects and push changes into the repo when I feel they are universally relevant and valuable.

There's no such a thing, more like beautiful interface trying to hide that there's no actual gameplay.

The filthy casuals write positive reviews on steam and it's clear that true gamers won't even try to review such a shallow game.

The syntax itself provides a visualization of the structure of the grid.

Well, a click funnel is basically an online sales funnel, but it’s widely referred to as a click funnel due to the growing popularity of the software called “Clickfunnels”.

Please don't thank me! ;-) If this answer did help, just click the little grey ☑ at the left of this text right now turning it into beautiful green. If you do not like the answer, click on the little grey down-arrow below the number, and if you really like the answer, click on the little grey ☑ and the little up-arrow... If you have any further questions, just ask another one! ;-)

There is a dimension of personal preference to it. I don't like to expose more than strictly necessary to external consumers, because it makes it harder to track usages. If you find a bind:prop in a consumer, you know prop is used (which you already kind of knew since the prop is part of the "public" API of the component). Done. If you find a bind:this, you now need to track all usages of this this.

In fact, even <svelte:slot /> feels a bit confusing because it introduces a new kind of slot, where the concept is already a bit crowded (there the <slot /> in the parent component, and the target slot="name" for the slot content).

Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.

It’s worth mentioning that Svelte limits its scope to being only a UI component framework. Like React, it provides the view layer, but it has more batteries included with its component-scoped CSS and extensible stores for state management. Others like Angular and Vue provide a more all-in-one solution with official routers, opinionated state management, CLIs, and more. Sapper is Svelte’s official app framework that adds routing, server-side rendering, code splitting, and some other essential app features, but it has no opinions about state management and beyond. Some devs prefer Svelte’s minimal approach that defers problems to userland, encouraging more innovation, choice, and fragmentation, and other devs prefer a more fully integrated toolkit with a well-supported happy path.

With the caveat that hero worship can be gross, distorting, and unhelpful to everyone involved, Svelte author Rich Harris (@rich_harris on Twitter) is one of my favorite open source developers. In the JS community he’s well-known among tool authors for spreading interesting ideas. He’s the creator of many open source projects including Rollup, the bundler of choice for many libraries including React and Vue.

Svelte is its own language, not plain HTML+CSS+JS

The compiler architecture moves complexity from the runtime and source code to buildtime and tools. Behind Svelte’s simple APIs sits a beefy compiler. Frontend web development has become very tool heavy in the webapp era, so in practice this adds little cost beyond what developers like myself already pay, but increased build complexity is important to acknowledge.

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.

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.

(15x) ENJOYMENT: Forgettable Outstanding(10x) DEPTH (IN RELATION TO COMPLEXITY): Lacking Meaty (5x) LUCK FACTOR: All Luck All Skill (3x) REPLAYABILITY: Nil Limitless(10x) MECHANICS: Boring Interesting (4x) PLAYER INTERACTION: Low High (4x) PLAYER COUNT PERFORMANCE: Not Balanced Balanced (2x) GAME LENGTH: Too Short/Long Just Right (2x) CLARITY OF RULES: Mud Crystal (5x) COMPONENT QUALITY: Cheap World ClassINITIAL RATING (sum(Criteria Rating x Criteria Weight)/Total Weight) = 7.7

I realise this is old, but as it isn’t a forum i see no problem in replying

Did you look at it and decide not, or not look at it?

This isn't written to hype a battle in the holy war.

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

Obviously we shouldn't rush into anything. But changes like these are best made earlier on in a project's lifecycle, so I'm eager to hear what people think so that we can start making some progress.

http://jonudell.info/h/tag-rename-02.mp4

He highlights the Memex’s killer feature of associative linking and how trails of links have never been implemented in the way the Memex envisioned: It is associative indexing though, that is the essential feature of the memex, “the process of tying two items together is the important thing.” Bush describes a hypertext like mechanism at this point, but most interesting from my perspective is his emphasis on a trail as a fundamental unit — something we largely seem to have lost today. […] Documents and links we have aplenty. But where are our trails?

We could broadcast a warning if we find the variable to be set in the environment, but that is more likely than not to annoy people who intentionally set it.

Paths are traversed in the order they occur in the search path. By default, this means the files in app/assets take precedence, and will mask corresponding paths in lib and vendor.

Doing so also means adding empty import statements to guarantee correct order of evaluation of modules (in ES modules, evaluation order is determined statically by the order of import declarations, whereas in CommonJS – and environments that simulate CommonJS by shipping a module loader, i.e. Browserify and Webpack – evaluation order is determined at runtime by the order in which require statements are encountered).

In a browser, deep-diff defines a global variable DeepDiff. If there is a conflict in the global namespace you can restore the conflicting definition and assign deep-diff to another variable like this: var deep = DeepDiff.noConflict();.

// Use `noConflict` to restore the pre-fp variant. var fp = _.noConflict();

It is important to note here that the flow does not need to begin with a user interaction. With the rise of asynchronous middleware like redux-saga and redux-observable, the ability to trigger any code on a component anywhere is very useful.

The primary motivation behind virtual-dom is to allow us to write code independent of previous state. So when our application state changes we will generate a new VTree. The diff function creates a set of DOM patches that, based on the difference between the previous VTree and the current VTree, will update the previous DOM tree to match the new VTree.

Moreover, React team even removed the “highlight updates” feature from dev tools because people used to obsessively haunt wasted renders with no reasoning behind it

Unfortunately, this only worked because of a feature called import elision. When TypeScript outputs JavaScript files, it sees that Options is only used as a type, and it automatically drops its import. The resulting output looks kind of like this:

The onBlur function can take a SyntheticFocusEvent like it would if you had given it directly to an <input/> component, but you can also just call it: props.input.onBlur() to mark the field as blurred (inactive).

We don't want to rely on there being a single root element - or prevent ourselves from ever implementing named slots without a single root node - and so there's not anything to apply the class to or the transition to.

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.

This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.

The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.

Your LazyLoad image is now inextensible. What if you want to add a class? Perhaps the author of LazyLoad thought of that and sets className onto the <img>. But will the author consider everything? Perhaps if we get {...state} attributes.

The feature is highly likely to be implemented, the API and implementation are the only real topics of discussion right now.

6to5 attempted to ship a quick and dirty TDZ static checking feature but had to retract it immediately afterwards due to various bugs in the algorithm.

But this is a case where it feels like we're papering over a deficiency in our language, and is the sort of thing detractors might well point to and say 'ha! see?'.

It relies on something that is inherently global. Different components might 'claim' a given property name. While it's possible to differentiate them at the subtree level, it's not possible to do so globally.

Global selectors, even when scoped to a subtree, cascade just like regular CSS would. This might be fine for a leaf component, but anywhere else in your app, this is the CSS equivalent of crossing your fingers and hoping that bad things won't happen.

I understand what you're getting at, but we shouldn't miss out on useful features just because a few developers will abuse it...

It's fashionable to dislike CSS. There are lots of reasons why that's the case, but it boils down to this: CSS is unpredictable. If you've never had the experience of tweaking a style rule and accidentally breaking some layout that you thought was completely unrelated — usually when you're trying to ship — then you're either new at this or you're a much better programmer than the rest of us.

In mapbox.js you'll see this line: const key = {};We can use anything as a key — we could do setContext('mapbox', ...) for example. The downside of using a string is that different component libraries might accidentally use the same one; using an object literal means the keys are guaranteed not to conflict in any circumstance (since an object only has referential equality to itself, i.e. {} !== {} whereas "x" === "x"), even when you have multiple different contexts operating across many component layers.

Some large tech behemoths could hypothetically shoulder the enormous financial burden of handling hundreds of new lawsuits if they suddenly became responsible for the random things their users say, but it would not be possible for a small nonprofit like Signal to continue to operate within the United States. Tech companies and organizations may be forced to relocate, and new startups may choose to begin in other countries instead.

there’s 3 steps to building software: Make it work Make it right Make it fast

The element dem in epidemic, endemic, and pandemic comes from the ancient Greek word demos, which meant people or district:

If we can encourage people to create clean commits as they go, the example as you showed above should be far less common, because cleaning up such history as an after-math is most of the time almost impossible.

Taxonomy, in a broad sense the science of classification, but more strictly the classification of living and extinct organisms—i.e., biological classification.

By bundling AddThis with other Experience enhancement cookies, it makes it impossible to opt in to other Experience enhancement cookies without also opting in to these (what could also be categorized as) Targeting/Advertising cookies (id 5).

Sure, anti-spam measures such as a CAPTCHA would certainly fall under "legitimate interests". But would targeting cookies? The gotcha with reCAPTCHA is that this legitimate-interest, quite-necessary-in-today's-world feature is inextricably bundled with unwanted and unrelated Google targeting (cookiepedia.co.uk/cookies/NID) cookies (_ga, _gid for v2; NID for v3).

In cases where you want to send more than one type of email to your users, you’re required to get additional consent specific to those uses as you must have multiple consents for multiple purposes.

In the case of DEM communications, you must obtain additional consent if also sending emails about third-party products/services in addition to your own.

the French CNIL has reminded that consent has to be given at the time of data collection, has to be specific, and cannot be passed to another controller through a contractual relationship; it could not be bundled.

Amazon has got a neat Requestor Pays Feature but as soon as there's a cost - any cost - there's a barrier to entry.

How do you leverage browser cache when Google’s very own Analytics.js has it’s expiry time set to 2 hours? How do you minimize DNS requests when Google advices you to copy their tracking code, linking to an externally hosted Javascript file?If that isn’t bad enough already, Google’s advice is to avoid hosting the JavaScript file locally. And why? To ensure you get access to new features and product updates.

People cannot see exhaustive documentation and code examples on their own file system. They would have to visit the repository (which also requires an internet connection).

BOOK 12 THE ARGUMENT The Angel Michael continues from the Flood to relate what shall succeed; then, in the mention of Abraham, comes by degrees to explain, who that Seed of the Woman shall be, which was promised Adam and Eve in the Fall; his Incarnation, Death, Resurrection, and Ascention; the state of the Church till his second Coming. Adam greatly satisfied and recomforted by these Relations and Promises descends the Hill with Michael; wakens Eve, who all this while had slept, but with gentle dreams compos'd to quietness of mind and submission. Michael in either hand leads them out of Paradise, the fiery Sword waving behind them, and the Cherubim taking thir Stations to guard the Place. AS one who in his journey bates at Noone, Though bent on speed, so heer the Archangel paus'd Betwixt the world destroy'd and world restor'd, If Adam aught perhaps might interpose; Then with transition sweet new Speech resumes. [ 5 ] Thus thou hast seen one World begin and end; And Man as from a second stock proceed. Much thou hast yet to see, but I perceave Thy mortal sight to faile; objects divine Must needs impaire and wearie human sense: [ 10 ] Henceforth what is to com I will relate, Thou therefore give due audience, and attend. This second sours of Men, while yet but few; And while the dread of judgement past remains Fresh in thir mindes, fearing the Deitie, [ 15 ] With some regard to what is just and right Shall lead thir lives and multiplie apace, Labouring the soile, and reaping plenteous crop, Corn wine and oyle; and from the herd or flock, Oft sacrificing Bullock, Lamb, or Kid, [ 20 ] With large Wine-offerings pour'd, and sacred Feast, Shal spend thir dayes in joy unblam'd, and dwell Long time in peace by Families and Tribes Under paternal rule; till one shall rise Of proud ambitious heart, who not content [ 25 ] With fair equalitie, fraternal state, Will arrogate Dominion undeserv'd Over his brethren, and quite dispossess Concord and law of Nature from the Earth, Hunting (and Men not Beasts shall be his game) [ 30 ] With Warr and hostile snare such as refuse Subjection to his Empire tyrannous: A mightie Hunter thence he shall be styl'd Before the Lord, as in despite of Heav'n, Or from Heav'n claming second Sovrantie; [ 35 ] And from Rebellion shall derive his name, Though of Rebellion others he accuse. Hee with a crew, whom like Ambition joyns With him or under him to tyrannize, Marching from Eden towards the West, shall finde [ 40 ] The Plain, wherein a black bituminous gurge Boiles out from under ground, the mouth of Hell; Of Brick, and of that stuff they cast to build A Citie and Towre, whose top may reach to Heav'n; And get themselves a name, least far disperst [ 45 ] In foraign Lands thir memorie be lost, Regardless whether good or evil fame. But God who oft descends to visit men Unseen, and through thir habitations walks To mark thir doings, them beholding soon, [ 50 ] Comes down to see thir Citie, ere the Tower Obstruct Heav'n Towrs, and in derision sets Upon thir Tongues a various Spirit to rase Quite out thir Native Language, and instead To sow a jangling noise of words unknown: [ 55 ] Forthwith a hideous gabble rises loud Among the Builders; each to other calls Not understood, till hoarse, and all in rage, As mockt they storm; great laughter was in Heav'n And looking down, to see the hubbub strange [ 60 ] And hear the din; thus was the building left Ridiculous, and the work Confusion nam'd. Whereto thus Adam fatherly displeas'd. O execrable Son so to aspire Above his Brethren, to himself assuming [ 65 ] Authoritie usurpt, from God not giv'n: He gave us onely over Beast, Fish, Fowl Dominion absolute; that right we hold By his donation; but Man over men He made not Lord; such title to himself [ 70 ] Reserving, human left from human free. But this Usurper his encroachment proud Stayes not on Man; to God his Tower intends Siege and defiance: Wretched man! what food Will he convey up thither to sustain [ 75 ] Himself and his rash Armie, where thin Aire Above the Clouds will pine his entrails gross, And famish him of Breath, if not of Bread? To whom thus Michael. Justly thou abhorr'st That Son, who on the quiet state of men [ 80 ] Such trouble brought, affecting to subdue Rational Libertie; yet know withall, Since thy original lapse, true Libertie Is lost, which alwayes with right Reason dwells Twinn'd, and from her hath no dividual being: [ 85 ] Reason in man obscur'd, or not obeyd, Immediately inordinate desires And upstart Passions catch the Government From Reason, and to servitude reduce Man till then free. Therefore since hee permits [ 90 ] Within himself unworthie Powers to reign Over free Reason, God in Judgement just Subjects him from without to violent Lords; Who oft as undeservedly enthrall

I’m going to assume most people in the room here have read Vannevar Bush’s 1945 essay As We May Think. If you haven’t read it yet, you need to.

“I and other so-called ‘deniers’ are members of the 97 percent consensus, which refers to the following: Yes, the earth’s climate has been warming overall for more than a century. Yes, humans emit CO2, and CO2 has an overall warming effect on the climate,” Curry said. Where the consensus ends, Curry added, is “whether the dominant cause of the recent warming is humans versus natural causes, how the 21st century climate will evolve, and whether warming is dangerous.”

VISITS

...one of the most highly regarded and expertly designed C++ library projects in the world.

When you see other get trailed its like the justice system goes easy on them like if they were kids

Appearance Models

Visual Recognition with Text

VLFeat: Mature and well-documented vision library, includes MATLAB bindings.