- Last 7 days
-
css-tricks.com css-tricks.com
-
overflow-wrap: break-word; makes sure the long string will wrap and not bust out of the container. You might as well use word-wrap as well because as the spec says, they are literally just alternate names for each other. Some browsers support one and not the other.
-
-
forums.theregister.com forums.theregister.com
-
Flatpak as a truly cross-distro application solution that works equally well and non-problematic for all
-
- Jan 2021
-
www.americanpressinstitute.org www.americanpressinstitute.org
-
The purpose of news is to inform, educate, and give us understanding and knowledge of what is going on in the world. It helps us to keep up to date with issues so we are in the know and fully aware of events taking place.
-
-
-
Moving DOM elements around made me anxious and I wanted to preserve natural tab order without resorting to setting tabindex, so I also made a flexbox version that never moves DOM elements around. I think it's the superior solution, at least for the layouts I was going for. https://github.com/wickning1/svelte-components/blob/master/src/FlexCardLayout.svelte
-
-
marketplace.visualstudio.com marketplace.visualstudio.com
-
-
www.donielsmith.com www.donielsmith.com
-
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.
-
-
github.com github.com
-
You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops
(lazy checking)
-
-
atomiks.github.io atomiks.github.io
-
"Headless Tippy" refers to Tippy without any of the default element rendering or CSS. This allows you to create your own element from scratch and use Tippy for its logic only.
-
-
github.com github.com
-
A cleaner approach could be the use:action API.
-
-
github.com github.com
-
Popper for Svelte with actions, no wrapper components or component bindings required! Other Popper libraries for Svelte (including the official @popperjs/svelte library) use a wrapper component that takes the required DOM elements as props. Not only does this require multiple bind:this, you also have to pollute your script tag with multiple DOM references. We can do better with Svelte actions!
-
-
docs.docker.com docs.docker.com
-
I'd like to spin up a couple of these, both for my personal box (
localhost
-only) and for the development network.
-
- Dec 2020
-
-
Add this to my toolchain (in particular, configure Lighthouse to run in our CI/CD pipeline).
Tags
Annotators
URL
-
-
docs.microsoft.com docs.microsoft.com
-
I really want to wire this up to our heavy-duty internal apps, like CI, Disputes, and NoteRequest.
-
-
docs.microsoft.com docs.microsoft.com
-
you can set up notifications to alert you to new recommendations
-
-
github.com github.com
-
Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.
-
-
developer.mozilla.org developer.mozilla.org
-
The Web Storage API provides mechanisms by which browsers can store key/value pairs, in a much more intuitive fashion than using cookies.
-
-
github.com github.com
-
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.
-
-
github.com github.com
-
I tried leaking session and page data and indeed it's easy. Too easy. So I definitely agree that session data should not be readable from anywhere but the request itself.
-
-
github.com github.com
-
Like JSON.stringify, but handles
-
-
github.com github.com
Tags
Annotators
URL
-
-
github.com github.com
Tags
Annotators
URL
-
-
www.npmjs.com www.npmjs.com
-
You can afford to make a proper PR to upstream.
-
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.
This could be both good and bad.
potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.
Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.
Ah, good, I see they touched on some of these points in the sections:
- Benefits of patching over forking
- When to fork instead
Tags
- making it easy to do the wrong thing
- forking to add a desired missing feature/change
- when to _
- maintaining a fork while waiting for upstream to merge
- forking (patching vs. forking)
- taking the time to do it right/properly
- irony
- pull request
- doing it right/properly
- pull request stalled
- proper
- limited time: not right now (maybe later)
Annotators
URL
-
-
github.com github.com
-
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.
tag?: what scope of provided features / recommended happy path is needed?
-
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.
tag?: what scope of provided features / recommended happy path is needed?
-
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.
-
-
developer.mozilla.org developer.mozilla.org
-
If you'd prefer, you can use a third-party library like Modernizr or Detect It to do this test for you.
-
-
github.com github.com
-
I think the main difference between the two are the way API are served. Some smelte components need you to input big chunk of json as props, while i prefer keep props as primitive types and in the other hand give you different components tags to compose.
-
-
implicit.harvard.edu implicit.harvard.edu
-
I'd really like to take this.
Tags
Annotators
URL
-
-
yalebooks.yale.edu yalebooks.yale.edu
-
p. 198:
Given any five points on a sphere, show that some four of them lie on a hemisphere that includes its boundary.
I'll admit, I already looked at the hint for this problem, and yes, my initial approach did indeed consist of trying to find the 'worst' configuration.
I can think of two ways to determine whether or not two points on a sphere lie within the same hemisphere:
- First off, since any two points on a sphere may be connected by a great circle, they're in the same hemisphere if they're separated by no more than \(\frac{\tau}{2}\) radians along this shortest path.
- Equivalently, the length of the line segment connecting them must be less than or equal to \(2r\), where \(r\) is the radius of the sphere.
One other note:
- It's always possible to divide the sphere in half in such a way that any two points lie within the same hemisphere. (This is a corollary of the first point, above. Note that two antipodal points must necessarily fall on the boundary of such a division.)
So, I have a picture in my mind of the sphere divided into eight regions of equal area by way of three great circles which intersect one another at right angles. (Think the Equator, the Prime Meridian, and a third great circle drawn through the poles at 90 degrees longitude.) My thinking now tends more toward combinatorics and the pigeonhole principle than geometry proper.
-
-
register.gotowebinar.com register.gotowebinar.com
-
www.joshwcomeau.com www.joshwcomeau.com
-
- Nov 2020
-
stackoverflow.com stackoverflow.com
-
delete myObject.regex; // or, delete myObject['regex']; // or, var prop = "regex"; delete myObject[prop];
-
-
www.686.com www.686.com
Tags
Annotators
URL
-
-
timdeschryver.dev timdeschryver.dev
-
Svelte makes the pit of success larger because it hides all of this from us at compile time.
-
-
github.com github.com
-
-
Another difference is that context in Svelte does not insert anything into the visual component tree. There is no <Context.Provider> element like in React
Tags
- better/superior solution/way to do something
- +0.9
- Svelte
- component tree
- react hooks
- examples
- port (adaptation/translation)
- equivalent/analogous/alternative ways to do something between 2 libraries/languages/etc.
- port from another language
- React
- comparison
- Svelte: context
- react: context
Annotators
URL
-
-
nbdev.fast.ai nbdev.fast.ai
-
I'd love to take this for a spin. Maybe I could rewrite Demeter or
micdrop
using it.
-
-
-
So handling the interop upfront will avoid users writing invalid ES6 and make sure that they write ES6 that loads CommonJS in the right way.
-
-
www.youtube.com www.youtube.com
-
If everyone did this, the repair shops would be out of business.
-
-
github.com github.com
-
-
button.dev button.dev
-
i like working on application frameworks, compilers, interpreters, and emulators.
-
-
jimmy.schementi.com jimmy.schementi.com
-
but know I know what I don't want to do. I definitely know I want to be an Engineer now, and it makes it more clear that I should start my own business.
-
-
imfeld.dev imfeld.dev
-
Converting Angular components into Svelte is largely a mechanical process. For the most part, each Angular template feature has a direct corollary in Svelte. Some things are simpler and some are more complex but overall it's pretty easy to do.
-
-
docs.microsoft.com docs.microsoft.com
-
stackoverflow.com stackoverflow.com
-
can you not also use a .babelrc?
-
-
github.com github.com
Tags
Annotators
URL
-
-
github.com github.com
-
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.
-
-
-
Some of the verbs implemented by systemctl are designed to provide a high-level overview in a human readable format. All that information is available over dbus, and/or journalctl, systemctl show. We could provide that information in json format, but there's a second problem. Information and format of information printed by e.g. systemctl status is not stable. Since the output is not suitable for programmatic consumption anyway, there's no need to provide it in a machine readable format.
-
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.
-
Although I agree that -o json should return proper JSON, believe the proper way for external tools like SaltStack etc. to talk to systemd is DBus. See also saltstack/salt#20392 - everything else is more or less just hack-ish and prone to break easily.
-
- Oct 2020
-
docs.microsoft.com docs.microsoft.com
-
I'll want to generate, upload, and store a certificate for publishing NuGet packages.
-
-
www.typelit.io www.typelit.io
-
-
stackoverflow.com stackoverflow.com
-
If you have a better/simpler/"more official" solution, I'd still love to see it!
The "official" solution is to use submitErrors (see Erik's answer).
-
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?
-
The more official way to do this would be to run the check (you could even reuse this.validate) in onSubmit.
-
-
www.basefactor.com www.basefactor.com
-
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.
Tags
- form validation library
- react-final-form
- tedious
- form validation
- user experience
- form design
- a lot of things to consider
- reinventing the wheel / not invented here
- don't write your own
- integration
- adapter
- easy to get wrong
- fonk (form validation library)
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- complexity
- can't keep entire system in your mind at once (software development) (scope too large)
- difficult/hard problem
Annotators
URL
-
-
-
But it sounds like the library could use some way to setTouched()
-
-
graphql-dotnet.github.io graphql-dotnet.github.io
-
I highly recommend setting a higher bound on the number of returned entities by each resolve function in your code.
-
-
github.com github.com
-
-
-
Any software that makes HTTP requests to other sites should make it straightforward to enable the use of a cache.
-
-
final-form.org final-form.org
-
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.
-
-
github.com github.com
-
Use ponyfill.com for linking here.
Tags
Annotators
URL
-
-
humanwhocodes.com humanwhocodes.com
-
Once again, this isn’t good or bad, it’s just the most efficient way to create something that is similar to something else
-
-
-
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.
-
Of all the compile-to-languages, the one that strikes me as having the least merit is JSX. It's basically a ton of added complexity for the sake of what boils down to syntax. There are no real gains in terms of language semantics in JSX.
-
Furthermore, JSX encourages bad non-dry code. Having seen a lot of JSX over the past few months, its encourages copypasta coding.
Tags
- extensibility
- hard to make it work in _all_ cases
- JSX
- do pros outweigh/cover cons?
- not enough advantages/merits/pros to make it worthwhile
- making it easy to do the right thing
- favoring/catering to the needs of … over …
- is it worth the effort?
- have a good reason
- can't do everything
- advantages/merits/pros
- not merited
- duplication
- special cases
- bad engineering
- making it easy to do the wrong thing
- copy and paste programming
- adding special cases only for certain popular things but not others
- minimal benefits
- encourages the wrong thing
- copy and paste
- making it too easy to do the wrong thing
- can't support everything / all cases
- plugins
Annotators
URL
-
-
github.com github.com
-
For event listeners we support the standard jsx naming convention onEventname (this is converted to on:eventname in svelte) as well.
-
-
developer.mozilla.org developer.mozilla.org
-
An onevent event handler property serves as a placeholder of sorts, to which a single event handler can be assigned. In order to allow multiple handlers to be installed for the same event on a given object, you can call its addEventListener() method, which manages a list of handlers for the given event on the object.
-
-
-
An alternative (maybe not good) would be to restrict {@const} to certain blocks like {#each} and {#if}. In both cases, it significantly reduces the "multiple ways to do the same thing" problem and avoids ergonomic and performance overhead of our current situation.
-
it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.
Tags
- programming: multiple ways to do the same thing
- consistency
- software development: code organization: where does this code belong?
- idiomatic code style (programming languages)
- uniformity
- idiomatic pattern (in library/framework)
- convention
- strong conventions resulting in code from different code bases/developers looking very similar
Annotators
URL
-
-
svelte.dev svelte.dev
-
This is the Svelte version of this example: https://codesandbox.io/s/reactivity-react-responds-to-changing-props-forked-d2j44?file=/src/Label.js
-
-
nginx.org nginx.org
-
Hannah Stepanek annotated the hell out of this reference. I would do well to read what she had to say.
Tags
Annotators
URL
-
-
github.com github.com
-
They even named the main file
react.js
so when converting/migrating components from React you could (at least some of the time, perhaps) simply leave some of the imports as-is:import {createHooks, useRef} from './react';
-
-
github.com github.com
-
It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
-
-
recoiljs.org recoiljs.org
-
For reasons of compatibility and simplicity, it's best to use React's built-in state management capabilities rather than external global state.
-
-
dylanvann.com dylanvann.com
-
I’d still be interested in Svelte making things easier so I’ve opened a feature request for Reactive statement cleanup functions.
-
-
github.com github.com
-
I'm not sure I understand the problem, everything you are describing is already possible.
-
-
rjlipton.wordpress.com rjlipton.wordpress.com
-
A “solution” to GR is more like a model in logic: it may satisfy a theory’s axioms but have other properties that are contingent (unless the theory is categorical, meaning that all of its models are isomorphic).
-
-
github.com github.com
-
Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.
-
-
github.com github.com
-
Might have to cut my own version of the extension if its maintainers won't add support.
Tags
Annotators
URL
-
-
-
It was clear no one was interested in what I was working towards.
-
but everything they were doing started to make sense
Tags
- better/superior solution/way to do something
- finally / at last
- needs to feel right
- having a clear vision in mind / goal you're working towards even if no one else seems to understand/be interested
- build your own ideas
- can we do even better?
- feels natural
- finally got it right
- constant evolution/improvement of software/practices/solutions
- common/shared goal
Annotators
URL
-
-
-
The $: can also be used to trigger effects.
-
We can run effects when some data changes using watchEffect - it takes a function that runs whenever a reactive value used inside changes.
-
MobX - for me personally MobX is a far better way to manage state than React Hooks. It doesn't care about the UI layer so it can be used outside the React ecosystem, and it's simple to mutate data.
-
-
www.thingiverse.com www.thingiverse.com
-
-
neilkakkar.com neilkakkar.com
-
Confidence to express ignorance is a super power. One good way I hone this skill is by saying “Nothing to add” when I have nothing to add, instead of repeating what other people said.
-
-
github.com github.com
-
This library exports a single React Hook, useMethods, which has all the power of useReducer but none of the ceremony that comes with actions and dispatchers.
-
-
-
r self-r
This paragraph discuses the use of the word "bullshit" as it is used in every day life. Decide whether this is arguement, structure or both.
-
A Kind Word for Bullshit: The Problem of Academic Writin
Add MLA citation
-
-
leanprover.github.io leanprover.github.ioLean1
-
I'm so tempted to toy around with this.
-
- Sep 2020
-
stackoverflow.com stackoverflow.com
-
do I really have to do something like that in order to have my local modules working? it's quite impracticable to explain it to a team! there's nothing a little bit more straightforward?
-
-
sapper.svelte.dev sapper.svelte.dev
-
page components can have an optional preload function that will load some data that the page depends on. This is similar to getInitialProps in Next.js or asyncData in Nuxt.js.
-
-
gruyerevjbccnszf.onion.pet gruyerevjbccnszf.onion.pet
-
The AOL helpline number would is the best option "How do I talk to a Live Person at AOL". Usually after dialing the number, stay on the line and move as prompted. It may take a while but you will get proper assistance. The process is quite long, if you think that the process is taking more time than expected it’s better to use chat help option.
-
There might be an issue that you buy a new phone and wish to set up AT&T email in Outlook on your phone, but you are facing some serious technical glitch. If your AT&T is not working, you might want to connect to a live person to get the issue fixed. There are three common ways, How do I talk to a live person at AT&T.
-
-
shipshape.io shipshape.io
-
medium.com medium.com
-
The benefit of this approach is that rather than having these defaults and fighting against them, it’s fully up to you to decide how to handle everything.
-
Unfortunately, many third party libraries, even though they are written in ESM, are published to npm as CJS modules, so we still need to concatenate them.
Tags
- holdover
- better/superior solution/way to do something
- under my control
- feeling in control
- having more control/certainty when you do something manually
- configurable
- control (programming)
- fighting against your tools
- unfortunate
- slow to upgrade/switch to latest version/current best practice/way of doing things
- CommonJS modules
- it's up to you to decide
Annotators
URL
-
-
engineering.mixmax.com engineering.mixmax.com
-
There are two ways of handling this with Rollup, as described by the troubleshooting link from the warning. Unfortunately, both Rollup and React recommend the wrong one.
-
-
github.com github.com
-
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.
-
-
github.com github.com
-
DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
-
When the message say function was called outside component initialization first will look at my code and last at my configuration.
Tags
- web search for something brings me here
- error messages: should reveal/point to why/how error was caused and how to fix/prevent it
- can we do even better?
- dev experience
- frustrating
- reasonable expectation
- expectations
- useless/unhelpful/generic error messages that don't reveal why/how error was caused
- what a reasonable person would do
- errors
- good point
- errors are helpful for development (better than silently failing)
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
The recommended solution for onMount is the same as for useEffect — place an async function inside the handler
-
-
-
There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.
-
-
github.com github.com
-
If you want this control then wrap them in a DOM node that the parent controls. If you want to pass in values then use props and if you want to pass in values from higher up the tree, the new style RFC may be able to help.
-
-
github.com github.com
-
I think Svelte's approach where it replaces component instances with the component markup is vastly superior to Angular and the other frameworks. It gives the developer more control over what the DOM structure looks like at runtime—which means better performance and fewer CSS headaches, and also allows the developer to create very powerful recursive components.
-
-
github.com github.com
-
Lets not extend the framework with yet another syntax
-
I totally get not wanting to extend the syntax. I tried doing these things and in practice it was not easy or pretty. Actions provide a much cleaner and easier way to accomplish a certain set of functionality that would be much more difficult without it.
Tags
- clean
- programming: multiple ways to do the same thing
- library/framework could make this easier
- you aren't going to need it
- avoid complexity
- feature not needed; better to use a different approach/feature instead
- clean solution
- could be easier / more difficult than it needs to be
- just use/do...
- keep things simple
Annotators
URL
-
-
-
Why not just do something like this?
-
You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)
-
This can and should be done with other components, IMHO.
Tags
- scalability
- difficult/hard
- feature not needed; better to use a different approach/feature instead
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- could be easier / more difficult than it needs to be
- why this feature is needed
- just use/do...
- framework taking care of responsibility so users can leverage it and not have to worry about that responsibility themselves
Annotators
URL
-
-
github.com github.com
-
The feature is highly likely to be implemented, the API and implementation are the only real topics of discussion right now.
-
-
github.com github.com
-
You should install the packages individually. Alternatively, you can install all of them at once with the svelte-material-ui package.
-
-
jsrocks.org jsrocks.orgJS Rocks1
-
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.
-
-
github.com github.com
-
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.
-
Most of the linked issues, as well as this RFC, attempt to solve this problem by relaxing Svelte's CSS scoping rules, providing a better API with which to use global, or by manually passing down classes. We have never found this to be an acceptable solution which is why those issues have been closed. That position has not changed.
-
-
github.com github.com
-
Or if we formally took a stance that the class prop is THE ordained way to pass class attributes, though I don't think this functionality warrants this restriction.
-
-
daveceddia.com daveceddia.com
-