- Feb 2021
-
www.morozov.is www.morozov.is
-
The DSL has a weaker control over the program’s flow — we can’t have conditions unless we add a special step
-
I want to emphasize that Result is just an alternative name for the Either monad.
-
-
jrsinclair.com jrsinclair.com
-
Don’t worry if you get confused at first. Everyone does. I’ve listed some other references at the end that may help. But don’t give up.
-
-
mmhaskell.com mmhaskell.com
-
So every program starts in the IO monad. From here you can get any input you need, call into relatively "pure" code with the inputs, and then output the result in some way. The reverse does not work. You cannot call into IO code from pure code like you can call into a Maybe function from pure code.
-
-
en.wikipedia.org en.wikipedia.org
-
it is inconvenient to write specific implementations for each datatype contained, especially if the code for each datatype is virtually identical. For example, in C++, this duplication of code can be circumvented by defining a class template
-
-
trailblazer.to trailblazer.to
-
An operation has two invocation styles. This is the only difference to an Activity.
-
-
trailblazer.to trailblazer.to
-
Feel free to pick and choose what you need for your applications.
-
-
en.wikipedia.org en.wikipedia.org
-
which entails computer programming (process of writing and maintaining the source code), but also encompasses a planned and structured process from the conception of the desired software to its final manifestation
-
-
en.wikipedia.org en.wikipedia.org
-
"Open access" refers to toll-free or gratis access to content
not necessarily free content
-
-
2019.trailblazer.to 2019.trailblazer.to
-
note that TRB source code modifications are not proprietary
In other words, you can build on this software in your proprietary software but can't change the Trailblazer source unless you're willing to contribute it back.
loophole: I wonder if this will actually just push people to move their code -- which at the core is/would be a direction modification to the source code - out to a separate module. That's so easy to do with Ruby, so this restriction hardly seems like it would have any effect on encouraging contributions.
Tags
- proprietary software
- open-source software: not contributing new code back to project
- wording designed to be more palatable/pleasing/inoffensive
- neutral/dispassionate/impartial/objective wording
- annotation meta: may need new tag
- loophole/escape hatch
- well-written
- software licensing
- reminder
- LGPL
- good point
Annotators
URL
-
-
github.com github.com
-
In Trailblazer, models are completely empty. They solely contain associations and finders. No business logic is allowed in models.
-
The bare bones operation without any Trailblazery is implemented in the trailblazer-operation gem and can be used without our stack.
-
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
Tags
- allowing developer/user to pick and choose which pieces to use (allowing use with competing libraries; not being too opinionated; not forcing recommended way on you)
- focus on what it should do, not on how it should do it (implementation details; software design)
- rails: the Rails way
- abstractions
- trailblazer-operation
- focus on concepts/design/structure instead of specific/concrete technology/implementation
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively
- leaving the details of implementation/integration up to you
- the Trailblazer way
- models: should be thin, dealing with persistence/associations only, not business logic
- freedom of user to override specific decision of an authority/vendor (software)
- Trailblazer
- newer/better ways of doing things
Annotators
URL
-
-
unix.stackexchange.com unix.stackexchange.com
-
Example (in bash, but my question shouldn't be considered bash-specific):
-
-
psychclassics.yorku.ca psychclassics.yorku.ca
-
stolen love from the child and infant and made it the exclusive property of the adolescent and adult
Love is not exclusive to adults and adolescents as there are many types of love. I do not believe it has been stolen but added to love in general.
-
-
github.com github.com
-
Any idea @AaronLasseigne if this is mergeable?
-
-
github.com github.com
-
Since we're using an interaction, we don't need strong parameters. The interaction will ignore any inputs that weren't defined by filters. So you can forget about params.require and params.permit because interactions handle that for you.
-
-
reinteractive.com reinteractive.com
-
The great thing about working with reinteractive is you get to work directly with the developers, which is a huge plus. As a technical founder, I find proxying through a project manager adds unnecessary layers of complexity and creates opportunity for human error.
-
-
www.infoworld.com www.infoworld.com
-
companies want to promote what the technology can do, so they de-emphasize that the way in which you do it is less than ideal
-
-
softwareengineering.stackexchange.com softwareengineering.stackexchange.com
-
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.
-
This is not correct. Or at least, it is not entirely correct.
-
-
www.javaworld.com www.javaworld.com
-
Rather than implement features you might need, you implement only the features you definitely need, but in a way that accommodates change. If you don't have this flexibility, parallel development simply isn't possible.
-
-
-
It makes me happy to see people actually think about things and not just accept a shitty API.
Tags
- intentional/well-considered decisions
- "makes me happy when ..."
- describe the ideal hypothetical solution
- less than ideal / not optimal
- can we do even better?
- don't settle for/accept something that's not as good as it can be
- doing something without knowing why/how it works
- actually consider / think about how it _should_ (ideally) be
Annotators
URL
-
-
github.com github.com
-
By explicitly defining the form layout using ::property there is no more need for protecting from unwanted input. strong_parameter or attr_accessible become obsolete. Reform will simply ignore undefined incoming parameters.
-
-
-
Any attribute in the list will be allowed, and any defined as attr_{accessor,reader,writer} will not be populated when passed in as params. This means we no longer need to use strong_params in the controllers because the form has a clear definition of what it expects and protects us by design.
strong params not needed since form object handles that responsibility.
That's the same opinion Nick took in Reform...
-
-
-
I close the issue but we can continue the discussion.
closing does not necessarily imply end of discussion
-
-
www.medrxiv.org www.medrxiv.org
-
Chen, Y.-H., Glymour, M., Riley, A., Balmes, J., Duchowny, K., Harrison, R., Matthay, E., & Bibbins-Domingo, K. (2021). Excess mortality associated with the COVID-19 pandemic among Californians 18–65 years of age, by occupational sector and occupation: March through October 2020. MedRxiv, 2021.01.21.21250266. https://doi.org/10.1101/2021.01.21.21250266
-
-
emaildesign.beefree.io emaildesign.beefree.io
-
We got this email from Parabo, the print shop app, and smiled. Instead of the very standard “Please confirm subscription” header text, we were greeted with a funny, whimsical hello that’s totally in their brand voice. “We really want you to want us” is a clever way to break up the usual mundane greeting, and, guess what? It totally reaffirmed why we thought we wanted to sign up for their emails in the first place.
-
-
www.metacritic.com www.metacritic.com
-
the gameplay is meaningless and the devs just missed the point.
-
-
hilton.org.uk hilton.org.uk
-
We could of course refactor our code to rename things any time we like, but we don’t do this enough in practice
-
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.
-
-
copyheart.org copyheart.org
-
That ♡copyheart isn’t a legally binding license is not a bug – it’s a feature!
Tags
Annotators
URL
-
-
www.honeybadger.io www.honeybadger.io
-
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.
https://github.com/MoOx/pjax doesn't say it's no longer maintained (though hasn't been updated in 2 years), and does say that it doesn't use jQuery. Oh well.
-
Honeybadger isn't a single page app, and it probably won't ever be. SPAs just don't make sense for our technical requirements.
Tags
- I'm not sure about this
- determining if something is an appropriate application / best tool for the job
- no longer maintained
- depends on use case / application
- not the most appropriate / best tool/application/fit for every use case
- not the most appropriate / best tool/application/fit for this use case
- single-page app
Annotators
URL
-
-
-
Technically, it isn’t a part of the comparison internally but it is a factor that some users care for.
-
-
stackoverflow.com stackoverflow.com
-
I have checked the following close stackoverflow sources : Relation passed to #or must be structurally compatible. Incompatible values: [:references]
referencing similar questions so it won't be marked as duplicate
-
-
10.11.66.200 10.11.66.200
-
provide information for the following call type ONLY: New Enrollment Card Not Received
-
If the full SSN does not populate an account
-
refer to the New Enrollment Card Not Received call type in the DCFC
-
do not put the caller on hold
-
If No
-
DO NOT disclose that City or State where the Direct Express call center is located.
-
-
stackoverflow.com stackoverflow.com
-
never care and try to understand design standards
-
-
stackoverflow.com stackoverflow.com
-
If you teach your users to trust that URL bar is supposed to not change when they click links (e.g. your site uses a big iframe with all the actual content), then the users will not notice anything in the future either in case of actual security vulnerability.
-
And if there's a suitable vulnerability, it might be possible to trigger it even without using <iframe>, <img> or <a> element, so it's not worth considering for this issue.
-
-
medium.com medium.com
-
The point is, just because you don’t see it, doesn’t mean it’s not happening. It’s been more than two years and as far as I know, no one has ever noticed one of my requests. Maybe it’s been in your site this whole time
-
-
www.dekudeals.com www.dekudeals.com
-
This game is not currently available in United States.
-
- Jan 2021
-
www.adventisthealth.org www.adventisthealth.org
-
even if you have already had COVID-19, because you can catch it more than once
-
-
groupkit.com groupkit.com
-
(optional googlesheet & zapier integration for any other email marketing software)
-
-
slackmojis.com slackmojis.com
-
Slackmojis is made by some random dude in Brooklyn. He doesn't work for Slack, isn't paid by Slack, he just thinks Slack is pretty cool. Super Official Lawyer Talk: Slackmojis is not created by, affiliated with, or supported by Slack Technologies, Inc.
-
-
www.zdnet.com www.zdnet.com
-
I think some of the design details are insane (I dislike the binary logs, for example), but those are details, not big issues.
-
Systemd problems might not have mattered that much, except that GNOME has a similar attitude; they only care for a small subset of the Linux desktop users, and they have historically abandoned some ways of interacting the Desktop in the interest of supporting touchscreen devices and to try to attract less technically sophisticated users. If you don't fall in the demographic of what GNOME supports, you're sadly out of luck.
-
Systemd flies in the face of the Unix philosophy: 'do one thing and do it well,' representing a complex collection of dozens of tightly coupled binaries
-
-
blog.linuxmint.com blog.linuxmint.com
-
We don’t do politics, and we certainly don’t do religion. You’re bringing these here by using terms such as “politicians” or “evil”.
Does "evil" refer to religion? Or perhaps they meant "evil" in a more general way, as a more extreme version of "bad".
-
-
sankeymatic.com sankeymatic.com
-
SankeyMATIC unlocks the capabilities of the D3 Sankey tool for anyone to use.
-
SankeyMATIC builds on the open source tool D3.js and its Sankey library, which are very powerful but require a fair amount of work & expertise to use.
-
-
www.emailonacid.com www.emailonacid.com
-
The Gmail Android app that comes pre-installed with most new Android phones contains a feature to access non-Google accounts using POP and IMAP. Unfortunately, emails accessed through this setup lack the embedded style (<style>) support as well as the support for background images.
-
-
isthereanydeal.com isthereanydeal.com
-
We are not allowed to show you historical data for Amazon
Tags
Annotators
URL
-
-
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.
-
-
css-tricks.com css-tricks.com
-
I can’t promise I’m explaining this 100% accurately, but the way I understand it, the minimum width of a grid column is auto.
-
-
forums.theregister.com forums.theregister.com
-
I've already said this, but if you think the average desktop computer user thinks a sentence beginning "I just make a chroot..." makes any kind of sense, you haven't been paying attention to the level of intelligence of the general public.
-
Well, that user can safely stay with Windows. Hiding these things from me makes wish that.
-
Linux on the desktop won't take off until it is equally easy. Snap may be dumbed down, restricted and all the rest of it, but for ordinary users it's easier - and more secure - than the alternative.
-
if it's not broken, fix it until it is.
-
-
christophm.github.io christophm.github.io
-
Normality
?
-
-
svelte.dev svelte.dev
-
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).
-
-
www.digitalocean.com www.digitalocean.com
-
While this tutorial has content that we believe is of great benefit to our community, we have not yet tested or edited it to ensure you have an error-free learning experience. It's on our list, and we're working on it! You can help us out by using the "report an issue" button at the bottom of the tutorial.
-
-
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!
-
-
www.dennisdeacon.com www.dennisdeacon.com
-
However, one of the drawbacks of this property is that the line intersects descenders of the characters.
I think it actually looks great/better because it intersects descenders of the characters.
-
-
material-ui.com material-ui.com
-
👍 Upvote issue #204 if you want to see it land faster.
-
-
stackoverflow.com stackoverflow.com
-
“JSONP is JSON with extra code” would be too easy for the real world. No, you gotta have little discrepancies. What’s the fun in programming if everything just works? Turns out JSON is not a subset of JavaScript. If all you do is take a JSON object and wrap it in a function call, one day you will be bitten by strange syntax errors, like I was today.
-
-
snapcraft.io snapcraft.io
-
On Ubuntu, Chromium is not the default browser, and the package resides in the ‘universe’ section of the archive.
-
-
discourse.ubuntu.com discourse.ubuntu.com
-
Most users frankly don’t care how software is packaged. They don’t understand the difference between deb / rpm / flatpak / snap. They just want a button that installs Spotify so they can listen to their music.
-
In addition, PPAs are awful for software discovery. Average users have no idea what a PPA is, nor how to configure or install software from it. Part of the point of snap is to make software discovery easier. We can put new software in the “Editor’s Picks” in Ubuntu Software then people will discover and install it. Having software in a random PPA somewhere online is only usable by experts. Normal users have no visibility to it.
-
While you may have some objections due to your specific setup, please consider you’re not the usual use case. Most people install Ubuntu on a single drive, not separate /home, and not multiple disks. Most are quite happy with automatic updates - in line with how their phone is likely setup - both for debs (with unattended-upgrades) and snaps (via automatic refresh in snapd). Experts such as yourself are capable of managing your own system and are interested in twiddling knobs and adjusting settings everywhere. There are millions of Ubuntu users who are not like that. We should cater for the widest possible use case by default, and have the option to fiddle switches for experts, which is what we have.
-
The best place to let the developers know, and track those bugs is in the bug tracker. There are hundreds of forums online, all over the place in many languages. We can’t be expected to read all of them. Anyone with a launchpad ID (thus, anyone who has an account on this discourse instance) has the capability to file a bug. I’d strongly recommend doing so, for each specific issue. Taking just a few minutes to do that will help tremendously.
-
We have consistently said that we cannot forsee the deb-based desktop going away. I still can’t see that happening. Debs are an integral part of the way the desktop is built. It’s just not feasible / desirable to make the desktop be “all snap”.
-
When there are imperfections, we rely on users and our active community to tell us how the software is not working correctly, so we can fix it. The way we do that, and have done for 15 years now, is via bug reports. Discussion is great, but detailed bug reports are better for letting developers know what’s wrong.
-
but that doesn’t mean that confining applications is not a benefit also to FOSS applications, security is an issue that needs to be addressed with many layers of measures no mater what licensing approach you use to license the software
-
The benefits for developers do reflect on benefits for users, with more software delivered faster and more securely.
-
But now Chromium is no more available as deb, so what to expect ?
-
What’s the use of ie. snap libreoffice if it can’t access documents on a samba server in my workplace ? Should I really re-organize years of storage and work in my office for being able to use snap ? A too high price to pay, for the moment.
-
Disk space is an issue. Resource usage is an issue. Those new packages nowadays need huge amount of storage to finally do the exact same thing as their older and lighter deb counterpart. Whatever the price of storage, it’s the opposite of a progress, it’s not optimal at all.
Tags
- discoverability
- audience: power users
- security
- Snap
- deb packages
- pull the rug out from under someone
- the benefits of both
- audience: casual users (not power users)
- unfortunate
- opinion about which way is better
- benefiting one party benefits another
- users just want to get work done
- not
- doesn't matter
- discussion
- not adding to discussion
- not delivering on promise
- not necessarily the case
- packaging software
- not worth it
- discoverability: not easily discoverable
- software licensing
- delivering software/changes faster
- the needs of the many outweigh the needs of the few
- be specific
- waste of disk space
- technical details
- discussion without action
- high-cost changes
- discoverability of software
- user experience
- less than ideal / not optimal
- PPAs
- surprising
- helpful
- detailed issue/report
- good point
- not going away
- actionable
- confinement (security)
- don't care
- wasteful/inefficient use of resources
- bug reports
- unhelpful
- better for some but worse for others
- user expectations
- benefit to both developer and to user
- bad user experience
Annotators
URL
-
-
www.alfiekohn.org www.alfiekohn.org
-
They may skim books for what they’ll “need to know.” They’re less likely to wonder, say, “How can we be sure that’s true?” than to ask “Is this going to be on the test?”
This is completely true! As a student we honestly do not care about anything, as long as our grade is an A. I hate that it is true, because sometimes as a student, I just want to really learn for a second. Although it is nearly impossible when pressured is applied based on a letter grade that may or may not affect one's life. This class is really helping realize that it is not me, is that pressure kills the beauty of learning.
-
-
css-tricks.com css-tricks.com
-
One lesser-appreciated user-behaviour is when a user would like to choose an alternative download location. On a download link, your user can right-click -> “save link as…” and place the download directly into a folder of their choice. Handy if you want something to go directly to removable media, for example. On a download button, there’s no such option.
-
- Dec 2020
-
www.npmjs.com www.npmjs.com
-
You can afford to make a proper PR to upstream.
-
-
github.com github.com
-
Can we just forward/bubble all events emitted by the underlying input element?
-
Can this be merged please, this fixes a problem I have
-
-
github.com github.com
-
May I ask what is holding this back?
-
-
github.com github.com
-
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.
Tags
- balance of power
- business interests/needs overriding interests/needs of users
- at odds with
- future of project depending on continued delivery of business value to one company
- more interested in their own interests
- organic
- open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
- conflict of interest
Annotators
URL
-
-
www.bbc.co.uk www.bbc.co.uk
-
Magnetic materials are always made of metal, but not all metals are magnetic
-
-
github.com github.com
-
I personally think that starting from google's components makes easier to keeping update to material specs updates.
-
- Nov 2020
-
acorwin.com acorwin.com
-
Notably, LLVM and JVM are by far the most prominent targets in this scenario: they’re both open-source and well-documented targets that provide a ton of firepower, and there frankly aren’t a ton of other options.
-
-
stackoverflow.com stackoverflow.com
-
If the client JS is disabled, then handleSubmit will never be executed and you have to care that your /api/fakeBackendRoute will handle the data exactly how the client would.
-
-
stackoverflow.com stackoverflow.com
-
emphasizing that 'this' and 'global object' are two different things not only in Node.js but in JavaScript in general
-
-
www.reddit.com www.reddit.com
-
Svelte by itself is great, but doing a complete PWA (with service workers, etc) that runs and scales on multiple devices with high quality app-like UI controls quickly gets complex. Flutter just provides much better tooling for that out of the box IMO. You are not molding a website into an app, you are just building an app. If I was building a relatively simple web app that is only meant to run on the web, then I might still prefer Svelte in some cases.
-
-
developer.mozilla.org developer.mozilla.org
-
Fallback values aren't used to fix the browser compatibility. If the browser doesn't support CSS custom Properties, the fallback value won't help.
-
-
uxdesign.cc uxdesign.cc
-
So if you are designing for an app
If you're designing a web app, you still have hover.
-
-
github.com github.com
-
There is no rerender, when you call listen, then all scroll events will warn on chrome. See this entry from svelte: breaking the web
Even the author of this library forgot this about Svelte?? :) (Or maybe he didn't and this response misunderstood/falsely assumed that he had.)
-
-
github.com github.com
-
After i've stabilized the library i can start to discuss about adding new components and features!
-
-
github.com github.com
-
Many of you will not be able to use this if you depend on custom import types or other fancy loaders. This project is just not for you!
Tags
Annotators
URL
-
-
www.thecodebuzz.com www.thecodebuzz.com
-
GET is the primary mechanism of information retrieval and the focus of almost all performance optimizations.
-
-
stackoverflow.com stackoverflow.com
-
Never use x && y || z when y can return a non-zero exit status.
-
-
unix.stackexchange.com unix.stackexchange.com
-
I think what the author intended to do was check if the second argument was a non-empty string (which is not the same thing as checking whether there are more than 1 argument, as the second argument could be passed but be the empty string).
-
-
mywiki.wooledge.org mywiki.wooledge.org
-
However, this construct is not completely equivalent to if ... fi in the general case.
The caveat/mistake here is if you treat it / think that it is equivalent to if a then b else c. That is not the case if b has any chance of failing.
-
Some people try to use && and || as a shortcut syntax for if ... then ... else ... fi, perhaps because they think they are being clever.
-
-
github.com github.com
-
It is open to the community to help set its direction.
-
-
github.com github.com
-
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)
Tags
- build concensus
- allowing sufficient time for discussion/feedback/debate before a final decision is made
- soliciting feedback
- attracting contributors
- have discussion/feedback/debate in public (transparency)
- change proposal workflow: RFCs
- open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
- welcoming feedback
- feeling blindsided
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
All browers handle 302 incorrectly. Chrome 30, IE10. It became the de facto incorrect implementation; that cannot be changed because so many web-sites issue mistakenly issue 302. In fact ASP.net MVC incorrectly issues 302, depending on the fact that browsers handle it incorrectly.
-
-
github.com github.com
-
Tell you why tree-shaking fails, if it does.
-
What it doesn't do
Tags
Annotators
URL
-
-
stackoverflow.com stackoverflow.com
-
But using internal api's is dangerous as these may change when you update svelte. If you decide to use this, add a line to your project Readme.md mentioning which internal api's you used and why. Try to write it using other methods when you can.
-
-
github.com github.com
-
I see this issue has 2 open PR's is this going to be finalized anytime soon?
-
-
github.com github.com
-
github.com github.com
-
Furthermore, how come there's a PR open since 3 months, at what seems to be the authoritative repo for Svelte?
-
-
github.com github.com
-
github.com github.com
-
This is Sass based, and therefore doesn't require Svelte components
Just because we could make Svelte wrapper components for each Material typography [thing], doesn't mean we should.
Compare:
material-ui [react] did make wrapper components for typography.
- But why did they? Is there a technical reason why they couldn't just do what svelte-material-ui did (as in, something technical that Svelte empowers/allows?), or did they just not consider it?
svelte-material-ui did not.
- And they were probably wise to not do so. Just reuse the existing work from the Material team so that there's less work for you to keep in sync and less chance of divergence.
-
This is not an MDC Web component. It is an addition that SMUI provides.
Tags
- differences
- don't reinvent the wheel
- reuse/leverage existing _ when possible
- not:
- extension of standard format
- keeping core small
- build upon the work of others
- just because you can doesn't mean you should
- wrapper
- additional/extra/bonus feature not present in original/upstream/specification
- added/extra benefit/bonus
- keep things simple
Annotators
URL
-
-
-
Feel free to subscribe to the issue (there's button in the right hand column) but do not comment unless you are adding value to the discussion. "Me too" and "+1" are not valuable, nor are use cases that have already been written in the comments (e.g., we know that you can't put <tr> or <dd> elements with a <div>).
-
-
www.npmjs.com www.npmjs.com
-
Note that when using sass (Dart Sass), synchronous compilation is twice as fast as asynchronous compilation by default, due to the overhead of asynchronous callbacks.
If you consider using asynchronous to be an optimization, then this could be surprising.
-
-
github.com github.com
-
When you do import '../scss/application.scss', you're telling webpack to include application.scss in the build. This does not mean it's going to be compiled into your javascript, only that webpack now compiles and knows how to load this file.
Not necessarily the case that importing something into a JS file means the thing being imported is also JS.
-
-
-
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.
-
- Oct 2020
-
www.scispike.com www.scispike.com
-
I came up with this solution by piecing together man pages and random google result. I was surprised at how many incomplete and inaccurate answers were out there. What may have been more surprising was the complete lack of a full intact solution.
-
-
meta.stackoverflow.com meta.stackoverflow.com
-
I don't think the heading/bearing split is as clear-cut as that.
-
-
-
In summary TLS uses PKI to secure information over the internet. However, it is important to note that TLS supports other encryption standards which are not part of PKI.
-
-
stackoverflow.com stackoverflow.com
-
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?
-
Library author here. I'm always fascinated by new ways people can invalidate my assumptions. I mean that in a sincerely positive way, as it results in learning.
Tags
- they've thought of everything
- can't support everything / all cases
- invalidating one's assumptions
- different way of thinking about something
- official preferred convention / way to do something
- author of software answering questions in community (support)
- sincere
- not:
- kludge
- not considering all use cases
- testing/challenging one's assumptions (either validating or invalidating them)
- not officially supported / you're on your own
- surprising
- learning from others
- assumptions
Annotators
URL
-
-
www.basefactor.com www.basefactor.com
-
Ok, I have seen that there are lot of built-in and third party validations, but sooner or later I will face a validation rule not covered by this buffet. Can I build a custom one? Of course you can!
-
Of course you can start implementing your own thing, but you will waste a lot of precious time reinventing the wheel. Why not take advantage of a validation library that takes care of all this complexity for you?
-
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?
Tags
- reinventing the wheel / not invented here
- don't write your own
- extensibility
- run-time dynamicness/generics vs. having to explicitly list/hard-code all options ahead of time
- can't support everything / all cases
- complexity
- not considering all use cases
- flexibility
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
Annotators
URL
-
-
english.stackexchange.com english.stackexchange.com
-
Logistically speaking, I suppose "depender" and "dependee" would be more accurate, though neither of those are proper english words as far as I know.
-
In the context of software engineering, I've always used "dependent" and "dependee".
-
-
hypothes.is hypothes.is
-
Every pastor is called to be a theologian.
-
-
medium.com medium.com
-
We don’t need to apply refactorings we don’t want.
-
This does solve the problem, but now our project and API is structured differently. In large projects it might be very hard to determine how to pull this trick off, or even impossible!
-
-
-
Especially when rollup is configured with multiple outputs, I find this particular onwarn to be helpful in reducing warning clutter. It just displays each circular reference once and doesn't repeat the warning for each output:
-
I think my personal preference would be to see them all at once. Or maybe limit it to up to 10 messages and then list the count of how many more messages were not displayed. Pick your reaction
-
Another thing we could do to limit output would be to only every show the first circular dependency warning. I think we already do this for other types of warnings. Then you would need to tackle the warnings one-by-one, though.
-
-
medium.com medium.com
-
These are fine and do not cause any issues.
-
-
icla2020b.jonreeve.com icla2020b.jonreeve.com
-
Why will you children insist on giving parties!”
I doubt the children had much to do with this, consider Laura's apathy for the silly boys she dances with, or Laura's desire to end the party on the account of Scott, or how Jose felt it was too late to call it off, rather than feeling like she would be personally upset to call it off. These parties are the adults ideas, but Sheridan likely has trouble accepting such a vapid pass-time as worth while, her ego is a mess, because its such a pointless endeavor, and that's why she must convince herself that it's the children's idea.
-
-
-
Note that these are not hyperlinks; these URIs are used for identification. This is a machine-readable way to say “this is HTML”. In particular, software does not usually need to fetch these resources, and certainly does not need to fetch the same one over and over!
-
-
-
if you’re just the casual web surfer type, learning about Internet terminology might not be of much real use to you
-
-
github.com github.com
-
{#with someExpression as someVariable} <p>{someVariable}</p> {/with}
-
-
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.
-
-
ponyfoo.com ponyfoo.comPony Foo1
-
I’ll try to answer them over email and I may publish them here, with your approval.
-
-
masteringjs.io masteringjs.io
-
However, objects are generally easier to work with than maps, because not all JavaScript functions, frameworks, and libraries support maps. For example, the JSON.stringify() function doesn't serialize maps by default.
-
-
-
Windows: Shift + Delete
On Linux, it's this:
Linux: Shift + Delete
Thanks for listing us, too. It's like we don't even exist.
-
-
github.com github.com
-
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
-
This isn’t to say that multiplying code is good or bad – it’s a characteristic of all code regardless of quality.
-
For years, I’ve shared with friends and clients what I call the bunny theory of code. The theory is that code multiplies when you’re not looking, not unlike bunnies that tend to multiply when you’re not looking.
Tags
- avoid extra/needless work
- when you're not looking
- prolific
- good analogy
- time wasters
- analogy
- applicable
- most efficient way
- duplication of work/effort
- not necessarily good or bad
- funny
- inherent to all
- better/superior solution/way to do something
- characteristic/property/attribute/feature
- inherent
- inevitable
- duplication
- bunny theory of code
- ubiquity
Annotators
URL
-
-
-
just saying that if you're going to try to go with a markup approach, at least go all the way, instead of the frankenstein that is JSX
-
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.
-
Yes, you can embed loops in it and compose lots of small repeated JSX snippets, but that almost never happens in practice because 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 (the syntactical approach taken by virtual-dom).
-
Without elegant ways of expressing loops/iterators (like angular does with directives), the primary way to keep JSX readable thus becomes copying and pasting.
I'm not quite sure I understand this (so until I do, I'm not sure I agree)...
Why does he think copying and pasting is the only way to make it readable? Like he pointed out, you can extract JSX snippets and use loops within JSX. But maybe he means (his previous point), that people often don't do that. Hmm. 
-
The react community has become a big cargo cult. There are some good ideas in the community and many Bad Ideas™. Paving the bad idea cowpaths lends a sense of legitimacy to these bad technical ideas that is not merited.
-
I agree that "it feels gross" is a bad reason. "not paving a bad cowpath" is a much better reason.
-
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.
-
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.
Tags
- subjective
- javascript
- readability
- extracting small reusable snippets of code
- comfortable because familiar
- familiar syntax
- bad combination/mixture/hybrid/frankenstein
- plugins
- JSX
- not a real/actual problem
- not
- unfamiliar
- hard to make it work in _all_ cases
- have a good reason
- can't support everything / all cases
- not enough advantages/merits/pros to make it worthwhile
- not necessarily the case
- reuse existing language constructs
- advantages/merits/pros
- minimal benefits
- it's just _
- can in theory but not commonly done in practice
- hyperscript
- readability: depends on familiarity
- not good enough reason/rationale/explanation
- comparison with:
- bad engineering
- investing time to really understand something
- can't do everything
- elegant
- paving cow paths
- I have a differing opinion
- is it worth the effort?
- extensibility
- expressiveness
- getting stuck in a rut
- not:
- excellent writing
- template language: bad: by not reusing existing language constructs; forced to reinvent equivalents which are inferior and unfamiliar
- legitimize
- making it easy for later refactoring
- do pros outweigh/cover cons?
- adding special cases only for certain popular things but not others
- template language vs. reusing existing language constructs
- favoring/catering to the needs of … over …
- not merited
- special cases
- cargo cult
- commit fully / go all in
Annotators
URL
-
-
github.com github.com
-
Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.
-
-
github.com github.com
-
However, in function components there really isn't much need for this pattern since you can just use JS default arguments
-
-
leiss.ca leiss.ca
-
Good risk management is inherently simple; adding too many complexities increases the likelihood of overlooking the obvious.
-
-
github.com github.com
-
Node doesn't have a DOM available. So in order to render HTML we use string concatenation instead. This has the fun benefit of being quite efficient, which in turn means it's great for server rendering!
-
-
facebook.github.io facebook.github.io
-
Why not just use that instead of inventing a syntax that's not part of ECMAScript?
-
Why not Template Literals?
-
-
medium.com medium.com
-
This is a very dangerous practice as each optimization means making assumptions. If you are compressing an image you make an assumption that some payload can be cut out without seriously affecting the quality, if you are adding a cache to your backend you assume that the API will return same results. A correct assumption allows you to spare resources. A false assumption introduces a bug in your app. That’s why optimizations should be done consciously.
-
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
-
In the vast majority of cases there’s nothing wrong about wasted renders. They take so little resources that it is simply undetectable for a human eye. In fact, comparing each component’s props to its previous props shallowly (I’m not even talking about deeply) can be more resource extensive then simply re-rendering the entire subtree.
Tags
- not adding feature because of the risk it may be abused / shoot self in foot
- rationality
- fast (software performance)
- risky/dangerous assumptions
- premature optimization
- false assumptions
- assumptions
- the optimization costs more than not having the optimization
- time wasters
- risk
- not good enough reason/rationale/explanation
- bugs: less attack surface/possibility for bugs
- good/preferred/recommended behavior
Annotators
URL
-
-
github.com github.com
-
"The Map is not the territory" —Alfred Korzybski
-
-
en.wikipedia.org en.wikipedia.org
-
-
Alfred Korzybski remarked that "the map is not the territory" and that "the word is not the thing", encapsulating his view that an abstraction derived from something, or a reaction to it, is not the thing itself.
-
"The menu is not the meal."
-
A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.
-
-
tech.ebayinc.com tech.ebayinc.com
-
Every new variation to the view requires updating both the view model and the template. This holds true even for simple variations.
-
-
dylanvann.com dylanvann.com
-
Our custom useEffect is not idiomatic Svelte.
-
Beautiful, except that switching albums does not update the PhotoGrid. This is not the automatic reactivity we were promised by Svelte.
-
-
github.com github.com
-
I'm not sure I understand the problem, everything you are describing is already possible.
-
-
dylanvann.com dylanvann.com
-
Disclaimer: I’m new to Svelte so this isn’t so much a recommendation as it is a “I guess this is a way to do it 🤷♂️”
-
-
github.com github.com
-
Why struggle with custom Syntax DSLs when you can use one so widely supported?
-
JSX is an XML-like syntax extension to EcmaScript (https://facebook.github.io/jsx/). It is not a language or runtime.
-
-
-
Unfortunately people lack the the time to invest to really understand those things
-
People constantly suggest that I should have just worked with a different library instead of writing another one.
-
If you are interested in a library that has the discipline of React, transparent implementation that doesn't cut corners for easiness, and all the performance to back it up maybe SolidJS is the library for you.
-
Very few were interested in furthering the platform in the places they just took for granted.
-
-
stackoverflow.com stackoverflow.com
-
Always fascinated to discover a use case I'd never have considered.
-
-
online.mines.edu online.mines.edu
-
Class participation vs. attending class.The quantity andquality of online class participation replaces on-siteattendance
The flexibility is nice!
-
-
-
But maybe this PR should still be merged until he finds time for that?
Tags
- big change/rewrite vs. continuous improvements / smaller refactorings
- pull request stalled
- waiting for maintainers to review / merge pull request / give feedback
- open-source software: progress seems slow
- not a blocker (issue dependency)
- iterative process
- don't let big plans/goals get in the way of integrating/releasing smaller changes/improvements
Annotators
URL
-
-
github.com github.com
-
I created a pull request to have the if (node.parentNode) conditional added to detach. It was not applied due to the desire to find the root cause of the <meta> tag manifestation of this issue.
-
- Sep 2020
-
github.com github.com
-
I don't think we need more tooling here.
-
-
devblogs.microsoft.com devblogs.microsoft.com
-
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:
-
-
final-form.org final-form.org
-
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).
-
-
github.com github.com
-
To be clear, I have a reasonable workaround. I'd only like it to be less difficult to discover. At a minimum, this issue should help others find it...
-
-
final-form.org final-form.org
-
You probably want initialValue! ⚠️ The value of the field upon creation. This value is only needed if you want your field be dirty upon creation (i.e. for its value to be different from its initial value).
-
-
www.javascriptjanuary.com www.javascriptjanuary.com
-
The problem I have with this approach to state and prop variables is that the difference between them is very blurry. In React you can clearly see that a prop is an input to component (because of clear function notation), and that state is something internal. In Svelte they are both just variables, with the exception that props use export keyword.
This is something I've seen before: people noticing that Svelte is missing some kind of naming convention.
React has use___ convention, for example. Without that, it makes it hard to see the difference between and know just from the name that a function is an (mentioned in the other article I read) action and not a event handler or even component, for example.
-
-
svelte.dev svelte.dev
-
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.
-