- Mar 2021
-
press.rebus.community press.rebus.community
-
burk.io burk.io
Tags
Annotators
URL
-
-
www.breitbart.com www.breitbart.com
-
after many online called for her firing over a social media post that likened the experience of Jews during the Holocaust to the U.S. political climate
-
-
medium.com medium.com
-
Very often in these monorepos, packages are so incredibly specific in functionality, the question then becomes why even have a separate package at all if it’s tightly coupled? Can you use these packages independently or are they tied to specific versions of other packages in the monorepo? It’ll probably be easier to remove the mask and just work as a monolith.
-
-
www.chevtek.io www.chevtek.io
-
But I believe the core philosophy of tiny modules is actually sound and easier to maintain than giant frameworks.
-
I would much rather have a "cosine" module than a "trigonometry" module because chances are good I only need a small fraction of the utilities provided by the larger trig module.
-
Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.
-
Second, I don't agree that there are too many small modules. In fact, I wish every common function existed as its own module. Even the maintainers of utility libraries like Underscore and Lodash have realized the benefits of modularity and allowed you to install individual utilities from their library as separate modules. From where I sit that seems like a smart move. Why should I import the entirety of Underscore just to use one function? Instead I'd rather see more "function suites" where a bunch of utilities are all published separately but under a namespace or some kind of common name prefix to make them easier to find. The way Underscore and Lodash have approached this issue is perfect. It gives consumers of their packages options and flexibility while still letting people like Dave import the whole entire library if that's what they really want to do.
Tags
- granularity of control
- core/guiding beliefs/values/principles/philosophy/ideology
- composition
- flexibility to use the tool that you prefer
- microlibraries
- all or nothing (granularity of control)
- small units/components/modules/libraries/packages/projects
- sound/reasonable/wise/defensible
- 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)
- monolithic/giant modules/libraries/packages/projects
- composability
- allowing developer/user to pick and choose which pieces to use (a la carte, not all or nothing)
- easy to maintain
- micropackages
- modularity
Annotators
URL
-
-
blog.izs.me blog.izs.me
-
All too often, people get hung up on the wrong aspects of the Unix Philosophy, and miss the forest for the trees
-
-
news.ycombinator.com news.ycombinator.com
-
-
this only applies to end products which are actually deployed. For my modules, I try to keep dependency version ranges at defaults, and recommend others do the same. All this pinning and packing is really the responsibility of the last user in the chain, and from experience, you will make their life significantly more difficult if you pin your own module dependencies.
-
I suspect you aren't seeing much discussion because those who have a reasonable process in place, and do not consider this situation to be as bad as everyone would have you believe, tend not to comment on it as much.
Tags
- distinction
- silent majority
- dependencies: locking to specific version
- tendency of people to only speak up when something is wrong/broken and be silent so long as everything is fine/working/tolerable
- to read
- micropackages
- app vs. library
- trust/reliance/dependence on open-source libraries
Annotators
URL
-
-
www.sitepoint.com www.sitepoint.com
-
The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.
-
JavaScript needs to fly from its comfy nest, and learn to survive on its own, on equal terms with other languages and run-times. It’s time to grow up, kid.
-
If JavaScript were detached from the client and server platforms, the pressure of being a monoculture would be lifted — the next iteration of the JavaScript language or run-time would no longer have to please every developer in the world, but instead could focus on pleasing a much smaller audience of developers who love JavaScript and thrive with it, while enabling others to move to alternative languages or run-times.
-
While various shortcomings of the standard run-time library are the obvious, immediate reason for the creation of micro-packages
-
As to opinions about the shortcomings of the language itself, or the standard run-times, it’s important to realize that every developer has a different background, different experience, different needs, temperament, values, and a slew of other cultural motivations and concerns — individual opinions will always be largely personal and, to some degree, non-technical in nature.
Tags
- avoid giving partiality/advantage/bias to any specific option
- non-technical reasons
- level playing field
- JavaScript: as a process VM
- +0.9
- competition in open-source software
- runtime environment
- separation of concerns
- programming languages
- what is important/necessary for one person may not be for another
- micropackages
- software preferences are personal
- related but independent projects that can be developed independently
- independent release cycles among peer dependencies
- programming languages: choosing the best language for the job
- microlibraries
- everyone has different preferences
- JavaScript
- everyone has different background/culture/experience
- single responsibility
- neutral/unbiased/agnostic
- annotation meta: may need new tag
- reaction / reacting to
- good idea
- software freedom
- software project created to address shortcomings in another project
- good point
- neutral ground
- one size fits all mentality
Annotators
URL
-
-
en.wikipedia.org en.wikipedia.orgPyPy1
-
There used to be other backends in addition to C: Java, CSharp, and Javascript but those suffered from bitrot and have been removed.
-
-
www.inuse.se www.inuse.se
-
A product’s onceability is, to a certain extent, linked to its usefulness. If it is really useful, we will certainly go to considerable lengths to repair it.
-
Even if the damned thing would be really helpful in the long run, I can't give it the time and attention needed to make it work again ... Not right now. And ultimately never.
-
Onceability can be the result of the exaggerated demand for un-memorable passwords.
-
I searched for a replacement, but the list of plug-ins had 5000 items and the search function couldn't find anything of the same kind...
Tags
- onceability
- useful
- hard to search for
- relationship
- limited time: not right now (maybe later)
- passwords: too hard to remember them all
- the more useful/important something is, the greater the lengths to which we will go to preserve/fix/repair it
- good observation
- deferring until a more opportune/convenient time
- supposed to be temporary / things have a way of sticking/becoming permanent
Annotators
URL
-
-
publicinfrastructure.org publicinfrastructure.org
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Jeremy Cherfas</span> in IndieWeb chat (<time class='dt-published'>03/11/2021 14:46:39</time>)</cite></small>
-
-
github.com github.com
-
As of May 24, 2016, antimicro has moved from https://github.com/Ryochan7/antimicro to https://github.com/AntiMicro/antimicro. Additionally, project management has passed from Travis (Ryochan7) to the AntiMicro organization due to Travis having other interests and priorities.
-
-
github.com github.comd3/d32
-
To the consternation of some users, 3.x employed Unicode variable names such as λ, φ, τ and π for a concise representation of mathematical operations. A downside of this approach was that a SyntaxError would occur if you loaded the non-minified D3 using ISO-8859-1 instead of UTF-8. 3.x also used Unicode string literals, such as the SI-prefix µ for 1e-6. 4.0 uses only ASCII variable names and ASCII string literals (see rollup-plugin-ascii), avoiding encoding problems.
-
Microlibraries are easier to understand, develop and test. They make it easier for new people to get involved and contribute. They reduce the distinction between a “core module” and a “plugin”, and increase the pace of development in D3 features.
-
-
github.com github.com
-
It is unrelated to the technology company AMD and the processors it makes.
-
This is a copy of the "AMD" document in the repo, kept here to maintain historical links. If this document differs from the one in the repo, the repo version is the correct one.
Why not just make this document empty (besides a link) and link/redirect to the canonical version?
That way it is impossible for them to disagree.
Tags
- make it impossible to get wrong/incorrect
- maintaining redirect/copy at old URL in order to maintain historical links (broken links)
- canonical version
- avoid duplication
- not to be confused with
- avoid duplication: impossible for them to disagree/diverge if there's only one version/copy
- I have a question about this
Annotators
URL
-
-
github.com github.com
-
Normally you should not register a named module, but instead register as an anonymous module: define(function () {}); This allows users of your code to rename your library to a name suitable for their project layout. It also allows them to map your module to a dependency name that is used by other libraries.
-
-
results.vote.wa.gov results.vote.wa.gov
-
results.vote.wa.gov results.vote.wa.gov
-
- Get out the city shapefile and overlay these values.
- Get the most current version of the voter registration database.
- Determine the number of voters who, according to the Spokane Journal of Business, took part in the 2018 school bond vote, but not the stadium advisory vote. (Geographically, these would be folks who live within SD81, but outside of the city limits.)
-
-
en.wikipedia.org en.wikipedia.org
-
ECMAScript is a programming language itself, specified in the document ECMA-262. In other words, ECMA-262 is the specification of the programming language ECMAScript. JavaScript is an implementation of ECMAScript which conforms to the ECMAScript specification. JavaScript implementations can also provide additional features not described in the specification.
-
-
forum.paradoxplaza.com forum.paradoxplaza.com
-
This thread is more than 5 months old. It is very likely that it does not need any further discussion and thus bumping it serves no purpose. If you feel it is necessary to make a new reply, you can still do so though. I am aware that this thread is rather old but I still want to make a reply.
-
-
github.com github.com
-
I'd suggest there ought to be config to disable source maps specifically, and specifically for either CSS or JS (not alwasy both), without turning off debug mode. As you note, debug mode does all sorts of different things that you might want with or without source maps.
-
Meh... as I said earlier, I think using Webpack is the recommended way now. Another issue is there is no way to generate source maps in production.
-
I don't myself understand what's going on, it clearly has something to do with source maps, but may also have to do with other sprockets changes.
-
But yeah, I'm not sure how you would determine which was the "recommended way" really. I don't see anything in Rails docs saying either way.
-
But last I have seen comments from DHH, he considered webpack(er) recommended for JS, but Sprockets still the preferred solution for (S)CSS.
-
I don't really understand what's going on. Clearly source maps have something to do with it -- a source map feature that doesn't handle SCSS very well, apparently.
-
Is there a PR to... something? sassc-rails? That would make the patch not necessary? (I don't know if there's any good way to monkey-patch that in, I think you have to fork? So some change seems required...) Should the defaults be different somehow? This is very difficult to figure out.
-
I agree about lack of maintenance. It's probably because people use more and more Webpack.
Tags
- official preferred convention / way to do something
- where (which project) do I even report this problem/bug? (whose responsibility is it?)
- unfortunate that this is no longer maintained
- don't understand even what's going on, let alone how to go about finding/identifying/fixing the problem
- possible response/reaction to lack of maintainance / maintainer absence/silence
- hard to figure out where the problem lies / how to solve the problem / where to even begin
- shift in preference
- enabled by default but provides a way to opt out if needed
- all or nothing (granularity of control)
- switching/migrating from Sprockets to Webpack (Rails)
- falling out of favor
- switching/migrating to something different
- webpack
- abandoning/migrating away from
- sprockets
- is anyone even still using it anymore?
Annotators
URL
-
-
github.com github.com
-
# This behavior can be disabled with: # # environment.unregister_postprocessor 'application/javascript', Sprockets::SafetyColons
but it appears to no longer be possible in latest version...
-
-
github.com github.com
-
Essentially after any edit of any js file if we reload /qunit it takes us about 10 seconds for the page to render.
-
I was debugging our painfully slow reload times in Discourse when running qunit.
-
-
github.com github.com
-
but I still have no idea if I'm writing this new file correctly.
-
-
github.com github.com
-
we want source maps in production (like DHH)
-
I totally understand that there may be a majority still considering this a bad practice and thus keeping it disabled by default in production seem ok. But there could at least be an option to enable it for people who want to, no?
-
After waiting years for sprockets to support this we were very happy to see that sprockets 4 officially added support (thanks ), but then when trying to upgrade we noticed there's actually no way to use it in production... (without brittle hacks mentioned above).
-
I'd be happy to open a PR for this, but I'm not sure exactly what code needs to change. default_source_map.rb and source_map_utils.rb seem like candidates, but I'd appreciate guidance
Tags
- official preferred convention / way to do something
- unfortunate
- irony
- contributing: offering to help
- reasonable defaults
- missing configuration option or way to customize this behavior
- rails: the Rails way
- the needs/wishes of a minority
- can be disabled by default but at least provide a way to opt in if needed
- sad/unfortunate conclusion
- best practices
Annotators
URL
-
-
-
If the bug is still there I think that it is better if it is open so others can find it if they run into the same issue.
-
-
github.com github.com
-
The way we do it currently is by calling load from inside of load, via different "pipelines" and processors which is quite elegant and completely impossible to work with.
-
If I can find some time, maybe I can help pitch in somehow.
-
I'm kinda stuck at the moment, going around in circles. Everything is really heavily coupled. I would like to get to the point where no load is called from within processors, but i'm not sure if that's possible. Currently the API and the caching strategies are fighting me at every step of the way. I have a branch where i'm hacking through some refactoring, no light at the end of the tunnel yet though :(
-
Money could be good if it is spent to provide some of the above things. Money on it's own is hard because then it means I would have to spend time book-keeping and managing instead of programming.
Tags
- elegant solution
- requires a big/non-trivial refactoring/rewrite
- requires a non-trivial change
- hard to figure out where the problem lies / how to solve the problem / where to even begin
- pipeline
- contributing: offering to help
- unfun
- doing what you love: leaving what's boring to you for others
- seemingly contradictory
- fun wording
- work: doing what you love
- bookkeeping
- hard to follow/read/understand
- boring
- hard to understand
- hard/costly to change later
- contributing
- too coupled/dependent
- good point
- receiving money: is it worth the hassle/responsibility of bookkeeping?
Annotators
URL
-
-
theanarchistlibrary.org theanarchistlibrary.org
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>nastroika</span> in Natalia: Liberation Through Automation! - The Meta Course / meta-course-8 - Hyperlink Forum (<time class='dt-published'>03/10/2021 14:43:34</time>)</cite></small>
-
-
github.com github.com
-
Reopening #162
https://github.com/rails/sprockets/issues/162 was already closed as duplicated (so this just creates another duplicate).
Technically this could be added there.
Oh, I see, it was from so long ago (2015), that it would probably be frowned upon to reopen such an old issue.
-
-
-
it's super hard to test master because i have no idea which gems need to be updated. is there a guide on how to take a rails 4.2 project to master sprockets without everything mysteriously exploding? ill try to make a repro case but its hard to tell where to even start
-
-
opalrb.com opalrb.com
-
Opal is a Ruby to JavaScript source-to-source compiler. It comes packed with the Ruby corelib you know and love. It is both fast as a runtime and small in its footprint.
-
-
docs.openfaas.com docs.openfaas.com
-
OpenFaaS® makes it easy for developers to deploy event-driven functions and microservices to Kubernetes without repetitive, boiler-plate coding.
-
-
hyperstack.org hyperstack.org
-
Hyperstack gives you full access to the entire universe of JavaScript libraries and components directly within your Ruby code.Everything you can do in JavaScript is simple to do in Ruby; this includes passing parameters between Ruby and JavaScript and even passing Ruby methods as JavaScript callbacks.There is no need to learn JavaScript, all you need to understand is how to bridge between JS and Ruby.
-
-
www.codetriage.com www.codetriage.com
-
Better yet, send them a link to this page to help them understand why and how to make an example app:
-
If you end up finding and fixing a bug in your code, consider re-reading the documentation and seeing if that behavior of the library is unclear. Consider sending a documentation PR.
-
Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?
Tags
- wasteful/inefficient use of resources
- a dedicated page for an issue/convention/recommendation that you can easily link to / share with others
- providing an example app (minimal reproducible example)
- good explanation
- opportunity to improve/fix something
- minimal reproducible example
- avoid wasting maintainers' time so they have more time to work on important things
Annotators
URL
-
-
math.stackexchange.com math.stackexchange.com
-
I think that over time the distinction is lost. My math teacher, 35 years ago stated "formulas are used in chemistry, in math we have equations". To this day, the word 'formula' in math seems wrong, but I'd accept it's used commonly.
-
An equation is any expression with an equals sign, so your example is by definition an equation. Equations appear frequently in mathematics because mathematicians love to use equal signs. A formula is a set of instructions for creating a desired result. Non-mathematical examples include such things as chemical formulas (two H and one O make H2O), or the formula for Coca-Cola (which is just a list of ingredients). You can argue that these examples are not equations, in the sense that hydrogen and oxygen are not "equal" to water, yet you can use them to make water.
-
-
-
We don’t want to invalidate the input if the user removes all text. They may need a moment to think, but the invalidated state sets off an unnecessary alarm.
-
-
stackoverflow.com stackoverflow.com
-
You can use the :placeholder-shown pseudo class. Technically a placeholder is required, but you can use a space instead.
-
There is (currently) no CSS selector for detecting directly whether an input control has a nonempty value, so we need to do it indirectly, as described above.
-
-
store.steampowered.com store.steampowered.com
-
If you plan on using a gamepad with big picture mode I made a config that works perfectly so check it out.
-
There are myriads of platformers around, it's an oversaturated market, and just like industrial designer Karim Rashid said about there being no excuse by this point to make an uncomfortable chair, there's no excuse by this point to make a boring patformer.
-
-
css-tricks.com css-tricks.com
-
Assuming wonderful support, this is how the logic would play out…
-
:placeholder-shown is super useful for us here! It’s basically the secret selector for testing if an input currently has a value or not.
-
You’d think :empty would be it, but it’s not. That’s for matching things like <p></p>… container elements with nothing inside them. Inputs are no-content elements already.
-
always use real <label for="correct_input"> elements. Just that alone is a UX consideration all too many forms fail on
-
-
tylergaw.com tylergaw.com
-
My collection (this isn’t all of it) grows at a comical pace.
-
Having them in a physical form is good for my soul.
-
This is a non-exhaustive list of other things I love;
-
-
stackoverflow.com stackoverflow.com
-
This question was asked over a year ago, but it's a good question that I recently encountered as well...
-
-
jangawolof.org jangawolof.orgPhrases6
-
Alxemes jiy ñów la lekkool di ubbi.
C'est jeudi prochain la rentrée des classes.
alxemes -- (Arabic) Thursday.
jiy -- (?).
ñów v. -- to come, to arrive.
la -- can mean a lot of different things depending on context.
lekkool bi -- (French: l'école) school. 🏫
di v. -- be; mark of the imperfective affirmative not inactual.
ubbi v. -- open, to start, begin, inaugurate.
-
Beykat yi duñu dem tool altine.
-
Fibar bi jàngal na taawan bu góor ni ñuy dagge reeni aloom.
Le guérisseur a appris à son fils aîné comment on coupe les racines du Diospyros.
fibar -- (fibar bi? the healer? as in feebar / fièvre / fever? -- used as a general term for sickness).
bi -- the (indicates nearness).
jàngal v. -- to teach (something to someone), to learn (something from someone) -- compare with jàng (as in janga wolof) and jàngale.
na -- pr. circ. way, defined, distant. How? 'Or' What. function indicator. As.
taaw+an (taaw) bi -- first child, eldest. (taawan -- his eldest).
bu -- the (indicates relativeness).
góor gi -- man; male.
ni -- pr. circ. way, defined, distant. How? 'Or' What. function indicator. As.
ñuy -- they (?).
dagg+e (dagg) v. -- cut; to cut.
reen+i (reen) bi -- root, taproot, support.
aloom gi -- Diospyros mespiliformis, EBENACEA (tree).
-
Dafa ànd ak moroom yi àll ba, fori aloom.
Il est allé dans la brousse ramasser des fruits de Diospyros avec ses camarades.
dafa -- he/she.
ànd v. / ànd bi -- to be together, to go together; copulate; going together, fellowship; placenta.
ak -- and, with, etc.
moroom mi -- comrade of the same age group, equal, companion, neighbor.
yi -- the (plural).
àll bi -- large expanse of uninhabited land, bush; distant, as opposed to home.
ba -- the (indicates distance).
for+i (for) v. -- to pick up.
aloom bi -- edible fruit of Diospyros mespiliformis (aloom gi for the tree).
-
Séentuwul woon ni dinañu ko alamaan.
Il ne s'attendait pas à ce qu'on lui inflige une amende.
"We didn't expect that we would be fined."
séentu+wul (séentu) v. -- to seek to see from afar 👀, to scrutinize 🧐, to expect.
woon -- he didn't (?).
ni -- formats a verb (?)
dinañu -- we will.
ko -- her, him, it.
alamaan v. -- (French: l'amende) give a fine.
-
Sama nijaay aj na ñaari yoon.
Mon oncle a effectué deux fois le pèlerinage à La Mecque.
sama -- my.
nijaay ji n. -- maternal uncle; term of reference and address to designate the husband, in conservative circles.
aj (Arabic) v. -- make the pilgrimage to Mecca. 🕋; deceased ☠️ (for a religious personality).
na -- he (?).
ñaar+i (ñaar) -- twice; two. 2️⃣
yoon wi n. -- lane, path, track 🛤; law, regulation, legislation; times.
Tags
- tool
- aloom
- as
- companion
- sickness
- ñuy
- cut
- the
- tree
- dafa
- she
- of
- neighbor
- lekkool
- expect
- àll
- moroom
- jàngale
- ak
- together
- taught
- learn
- jàng
- janga
- bush
- woon
- aj
- back
- fruit
- fibar
- yi
- -e
- ebenacea
- next
- dagg
- duñu
- placenta
- séentuwul
- -i
- healer
- uninhabited
- roots
- di
- ni
- -an
- ñów
- son
- comrades
- góor
- yoon
- be
- made
- twice
- farmers
- ubbi
- to
- monday
- and
- la
- into
- field
- feebar
- fièvre
- ko
- what
- thursday
- school
- bi
- with
- jiy
- na
- uncle
- dem
- wolof
- ànd
- child
- mespiliformis
- mi
- went
- copulate
- man
- go
- nijaay
- my
- first
- not
- comrade
- fever
- distant
- taaw
- he
- diospyros
- ñaari
- they
- didn't
- dagge
- fined
- reen
- taawan
- land
- gi
- equal
- bu
- fori
- alxemes
- for
- taproot
- how
- alamaan
- support
- ba
- beykat
- jàngal
- his
- eldest
- pick up
- sama
- male
- on
- pilgrimage
- collect
- dinañu
- mecca
- teach
- altine
- reeni
- do
- fellowship
Annotators
URL
-
-
-
Dave Rupert has a good solution that uses an input's invalid event. Instead of using the :invalid pseudo selector, he adds a CSS class to the input when it becomes invalid. We will extend this approach by removing the CSS class when the element becomes valid again.
-
-
www.html5rocks.com www.html5rocks.com
-
Validating forms has notoriously been a painful development experience. Implementing client side validation in a user friendly, developer friendly, and accessible way is hard. Before HTML5 there was no means of implementing validation natively; therefore, developers have resorted to a variety of JavaScript based solutions.
-
-
stackoverflow.com stackoverflow.com
-
I know this is old, but I got the same error and I came here from Google, so in case someone does too, this was my solution:
-
-
github.com github.com
-
markdown-it is the result of the decision of the authors who contributed to 99% of the Remarkable code to move to a project with the same authorship but new leadership (Vitaly and Alex). It's not a fork.
-
-
www.kickstarter.com www.kickstarter.com
-
Try before you buy Here's a link to the game on Tabletopia: Judean Hammer on Tabletopia
-
-
stackoverflow.com stackoverflow.com
-
I realize the question was asked 9 years ago, but this question is (still) ranked highly in search results and I came across it today
-
-
distributed.press distributed.press
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>petermolnar</span> in #indieweb 2021-03-08 (<time class='dt-published'>03/08/2021 10:06:29</time>)</cite></small>
-
-
www.kickstarter.com www.kickstarter.com
-
If you want to try playing to see how these pieces work in the game, you can playtest it on the Iishogi.org site (https://lishogi.org/). Last year the Iishogi designer asked me to register the Design SHOGI pieces on their site. This Iishogi.org is a free to play Shogi website. I was willing to give them permission to use them. You are free to play and switch pieces design from the piece variation section. If you register your ID, then you can play vs the A.I. easily. You can learn how the Design SHOGI pieces work there.
-
-
www.digitalocean.com www.digitalocean.com
-
Wire this up for Brennan's website, so that I can protect the upload portal.
-
-
www.youtube.com www.youtube.com
-
-
openwindows.ace.fordham.edu openwindows.ace.fordham.edu
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>AG Wilsonn</span> in hungry bread elevator {αἱματόϊδρις} on Twitter: "In undergrad graded classrooms 95% of the unprompted questions are about assignments/exams (grades) so the trick is to design your assignments in such a way that when students ask about them they are actually asking about the course material too. anybody know how to do this?" / Twitter (<time class='dt-published'>03/04/2021 20:50:53</time>)</cite></small>
-
-
www.nytimes.com www.nytimes.com
-
This is the story of how a bill to save the vote and preserve a semblance of democracy for millions of Americans died at the hands of an intransigent, reactionary minority in the Senate, which used the filibuster to do its dirty work
The author starts off by personifying "the bill" as something that was supposed to save millions of Americans, but rather was killed by Senators. He immediately provides a brief overview of the claim of his essay before developing his narrative. This way, the audience gets a glimpse of the issue that the author will tackle. Also, by using words such as "intransigent and reactionary", the audience already understands that the author is going to be criticizing the senators for their action.
-
-
twitter.com twitter.com
-
ReconfigBehSci on Twitter. (n.d.). Twitter. Retrieved 5 March 2021, from https://twitter.com/SciBeh/status/1326159560835555328
-
-
github.com github.com
-
It can also be included as individual modules, i.e. Hashie::Extensions::MethodReader, Hashie::Extensions::MethodWriter and Hashie::Extensions::MethodQuery.
-
-
eprint.iacr.org eprint.iacr.org
-
Not that I have any hope of understanding it, but . . .
-
-
www.lavenderandlovage.com www.lavenderandlovage.com
-
trailblazer.to trailblazer.to
-
It is much easier to track what is going on within the activity. Instead of transporting additional state via ctx, you expose the outcome via an additional end event.
Note: It's only super easy to see what's going on if you have the benefit of a diagram.
-
This is my absolute favorite feature ever and the official reason for (re-)writing Trailblazer 2.1. It makes me happy every time I use it.
-
So why the over-complication? What we got now is replicating a chain of && in the former version. This time, however, you will know which condition failed and what went in by using tracing. Look at the trace above - it’s impossible to not understand what was going on.
-
Hey, that’s is an imaginary complication of our example - please don’t do this with every condition you have in your app.
Tags
- favorite
- extremes
- example: not how you would actually do it (does something wrong/bad/nonideal illustrating but we should overlook it because that's not the one thing the example is trying to illustrate/show us)
- artificial example
- easy to see/notice
- coming up with hypothetical examples
- answer the "why?"
- debugging tools
- easy to follow/read/understand
- funny
- why?
- state management
- pleasant/enjoyable to use
- easy to understand
Annotators
URL
-
-
Local file Local file
-
.The firstparadigm centres on institutional power: ‘Our schools, our government, our businessesand corporations are permeated with the view that neither individual nor group aretrustworthy. There must be power over, power to control. This hierarchal system isinherent in our whole culture’. The second paradigm takes the opposite view: ‘Givena suitable climate, humankind is trustworthy, creative, self-motivated, powerful andconstructive – capable of releasing undreamed-of-potentialities’
there is an ongoing struggle in many areas of society, in schools, workplaces, religious organisations. the second paradigm doesn't seem to win over the first on a large scale, since significant change in any domain is a frustrating and never-ending process.
-
importedfrom the business and commercial world.
who decided this? who decides which measures of success are appropriate?
-
target driven climate which has the potential to undermine theimportance of ‘relationship
taking away from the very purpose of the practice
-
-
psyarxiv.com psyarxiv.com
-
Oljača, M., Sadiković, S., Branovacki, B., Pajić, D., Smederevac, S., & Mitrović, D. (2020). Unrealistic optimism and HEXACO traits as predictors of risk perception and compliance with COVID-19 preventive measures during the first wave of pandemic. PsyArXiv. https://doi.org/10.31234/osf.io/rt64j
-
-
seirdy.one seirdy.one
-
en.wikipedia.org en.wikipedia.org
Tags
Annotators
URL
-
-
trailblazer.to trailblazer.to
-
patch: -> { step Destroy.method(:tidy_storage), before: :delete_model }
-
- Feb 2021
-
www.theguardian.com www.theguardian.com
-
Hern, Alex. ‘“Eat out to Help out” May Have Caused Sixth of Covid Clusters over Summer’. The Guardian, 30 October 2020, sec. Business. https://www.theguardian.com/business/2020/oct/30/treasury-rejects-theory-eat-out-to-help-out-caused-rise-in-covid.
-
-
github.com github.com
-
URI::MailTo::EMAIL_REGEXP
First time I've seen someone create a validator by simply matching against
URI::MailTo::EMAIL_REGEXP
from std lib. More often you see people copying and pasting some really long regex that they don't understand and is probably not loose enough. It's much better, though, to simply reuse a standard one from a library — by reference, rather than copying and pasting!!
-
-
netflixtechblog.com netflixtechblog.com
Tags
Annotators
URL
-
-
github.com github.com
-
Since we're not passing any inputs to ListAccounts, it makes sense to use .run! instead of .run. If it failed, that would mean we probably messed up writing the interaction.
-
-
trailblazer.to trailblazer.to
-
For branching out a separate path in an activity, use the Path() macro. It’s a convenient, simple way to declare alternative routes
Seems like this would be a very common need: once you switch to a custom failure track, you want it to stay on that track until the end!!!
The problem is that in a Railway, everything automatically has 2 outputs. But we really only need one (which is exactly what Path gives us). And you end up fighting the defaults when there are the automatic 2 outputs, because you have to remember to explicitly/verbosely redirect all of those outputs or they may end up going somewhere you don't want them to go.
The default behavior of everything going to the next defined step is not helpful for doing that, and in fact is quite frustrating because you don't want unrelated steps to accidentally end up on one of the tasks in your custom failure track.
And you can't use
fail
for custom-track steps becase that breaksmagnetic_to
for some reason.I was finding myself very in need of something like this, and was about to write my own DSL, but then I discovered this. I still think it needs a better DSL than this, but at least they provided a way to do this. Much needed.
For this example, I might write something like this:
step :decide_type, Output(Activity::Left, :credit_card) => Track(:with_credit_card) # Create the track, which would automatically create an implicit End with the same id. Track(:with_credit_card) do step :authorize step :charge end
I guess that's not much different than theirs. Main improvement is it avoids ugly need to specify end_id/end_task.
But that wouldn't actually be enough either in this example, because you would actually want to have a failure track there and a path doesn't have one ... so it sounds like Subprocess and a new self-contained ProcessCreditCard Railway would be the best solution for this particular example... Subprocess is the ultimate in flexibility and gives us all the flexibility we need)
But what if you had a path that you needed to direct to from 2 different tasks' outputs?
Example: I came up with this, but it takes a lot of effort to keep my custom path/track hidden/"isolated" and prevent other tasks from automatically/implicitly going into those steps:
class Example::ValidationErrorTrack < Trailblazer::Activity::Railway step :validate_model, Output(:failure) => Track(:validation_error) step :save, Output(:failure) => Track(:validation_error) # Can't use fail here or the magnetic_to won't work and Track(:validation_error) won't work step :log_validation_error, magnetic_to: :validation_error, Output(:success) => End(:validation_error), Output(:failure) => End(:validation_error) end
puts Trailblazer::Developer.render o Reloading... #<Start/:default> {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model> #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model> {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save> #<Trailblazer::Activity::TaskBuilder::Task user_proc=save> {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Right} => #<End/:success> #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Left} => #<End/:validation_error> {Trailblazer::Activity::Right} => #<End/:validation_error> #<End/:success> #<End/:validation_error> #<End/:failure>
Now attempt to do it with Path... Does the Path() have an ID we can reference? Or maybe we just keep a reference to the object and use it directly in 2 different places?
class Example::ValidationErrorTrack::VPathHelper1 < Trailblazer::Activity::Railway validation_error_path = Path(end_id: "End.validation_error", end_task: End(:validation_error)) do step :log_validation_error end step :validate_model, Output(:failure) => validation_error_path step :save, Output(:failure) => validation_error_path end
o=Example::ValidationErrorTrack::VPathHelper1; puts Trailblazer::Developer.render o Reloading... #<Start/:default> {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model> #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model> {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save> #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Right} => #<End/:validation_error> #<Trailblazer::Activity::TaskBuilder::Task user_proc=save> {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error> {Trailblazer::Activity::Right} => #<End/:success> #<End/:success> #<End/:validation_error> #<End/:failure>
It's just too bad that:
- there's not a Railway helper in case you want multiple outputs, though we could probably create one pretty easily using Path as our template
- we can't "inline" a separate Railway acitivity (Subprocess "nests" it rather than "inlines")
-
Subprocess will try to match the nested ends’ semantics to the tracks it knows. You may wire custom ends using Output.
-
step :direct_debit
I don't think we would/should really want to make this the "success" (Right) path and :credit_card be the "failure" (Left) track.
Maybe it's okay to repurpose Left and Right for something other than failure/success ... but only if we can actually change the default semantic of those signals/outputs. Is that possible? Maybe there's a way to override or delete the default outputs?
-
Patching has no implicit, magical side-effects and is strongly encouraged to customize flows for a specific case in a quick and consise way.
-
However, it can be a PITA if you want to customize one of those deeply nested components and add or remove a certain step, for example.
-
While you could nest an activity into another manually, the Subprocess macro will come in handy.
-
The macro automatically wires all of Validate’s ends to the known counter-part tracks.
-
Since notify sits on the “failure” track and hence is “magnetic to” :failure, find_provider will be connected to it.
-
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.
Tags
- verbose / noisy / too much boilerplate
- official preferred convention / way to do something
- example: not how you would actually do it (does something wrong/bad/nonideal illustrating but we should overlook it because that's not the one thing the example is trying to illustrate/show us)
- concise
- useful
- good abstraction
- powerful
- no magic
- trailblazer-activity
- customizable
- extension API: ability to override/customize nested objects
- macro
- automatic
- example: in order to keep example concise/focused, may not implement all best practices (illustrates one thing only)
- leverage library/tool to do something for you
- helper functions
- flexibility
- nice API
- makes sense to me
- tip
- extension API: patching
- monkey patching
- side effects
- semantics
- feels wrong
- I have a question about this
Annotators
URL
-
-
eprints.lse.ac.uk eprints.lse.ac.uk
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Christopher Ingraham</span> in ‘Trickle-down’ economics doesn’t work, according to comprehensive new research - The Washington Post (<time class='dt-published'>02/25/2021 12:36:59</time>)</cite></small>
-
-
science.thewire.in science.thewire.in
-
onezero.medium.com onezero.medium.com
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Cory Doctorow</span> in Pluralistic: 16 Feb 2021 – Pluralistic: Daily links (<time class='dt-published'>02/25/2021 12:20:24</time>)</cite></small>
It's interesting to note that there are already two other people who have used Hypothes and their page note functionality to tag this article as to read, one with
(to read)
and another with(TODO-read)
.
-
-
www.youtube.com www.youtube.com
-
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Cory Doctorow</span> in Pluralistic: 16 Feb 2021 – Pluralistic: Daily links from Cory Doctorow (<time class='dt-published'>02/25/2021 12:20:24</time>)</cite></small>
-
-
chicinacademia.com chicinacademia.com
-
Chic in Academia. ‘Science Says Sunday – How to Spot Misinformation’, 20 December 2020. https://chicinacademia.com/2020/12/20/science-says-sunday-how-to-spot-misinformation/.
-
-
psyarxiv.com psyarxiv.com
-
Długosz, Piotr. ‘PREDICTORS OF PSYCHOLOGICAL STRESS OCCURRING AFTER THE FIRST WAVE OF THE COVID-19 PANDEMIC IN POLAND’. PsyArXiv, 24 February 2021. https://doi.org/10.31234/osf.io/2k8px.
-
-
queue.acm.org queue.acm.org
-
how to track on-call coverage
-
-
github.com github.com
-
Personally, I'm starting to think that the feature where it automatically adds xray.js to the document is more trouble than it's worth. I propose that we remove that automatic feature and just make it part of the install instructions that you need to add this line to your template/layout: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %>
-
-
github.com github.com
-
Now that I've thought more about it, I honestly think the auto-adding the script feature is overrated, over-complicated, and error-prone (#98, #100), and I propose we just remove it (#110).
-
-
github.com github.com
-
now that I've thought more about it, I think the auto-adding the script feature is overrated, over-complicated, and error-prone (#100), and ought to just be removed (#110).
-
-
github.com github.com
-
now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script
Tags
- removing features to simplify implementation
- removing feature that is more trouble than it's worth (not worth the effort to continue to maintain / fix bugs caused by keeping it)
- removing legacy/deprecated things
- regret
- wasted effort
- fix design/API mistakes as early as you can (since it will be more difficult to correct it and make a breaking change later)
Annotators
URL
-
-
misinforeview.hks.harvard.edu misinforeview.hks.harvard.edu
Tags
Annotators
URL
-
-
psyarxiv.com psyarxiv.com
-
Schwartz, K. D., Cortens, D. E., McMorris, C., Makarenko, E., Arnold, P., Van Bavel, M., … Canfield, R. (2020, December 15). COVID-19 and Student Well-being: Stress and Mental Health during Return-to-School. https://doi.org/10.31234/osf.io/mqpvn
-
-
sass-lang.com sass-lang.com
-
Sass variables, like all Sass identifiers, treat hyphens and underscores as identical. This means that $font-size and $font_size both refer to the same variable. This is a historical holdover from the very early days of Sass, when it only allowed underscores in identifier names. Once Sass added support for hyphens to match CSS’s syntax, the two were made equivalent to make migration easier.
-
-
github.com github.com
-
As a workaround, I guess I'll have to disable my strict CSP in development, but I'd prefer to keep it strict in development as well so that I ran into any CSP issues sooner...
-
-
github.com github.com
-
Keeping bootstrap-sass in sync with upstream changes from Bootstrap used to be an error prone and time consuming manual process. With Bootstrap 3 we have introduced a converter that automates this.
-
-
github.com github.com
-
It's recommended to configure this library by setting environment variables.
-
-
guides.rubyonrails.org guides.rubyonrails.org
-
Keep in mind that third party code with references to other files also processed by the asset Pipeline (images, stylesheets, etc.), will need to be rewritten to use helpers like asset_path.
-
-
github.com github.com
-
Here's the last issue where source maps were discussed before the beta release.
-
How do you know if source maps are working correctly? Try adding a syntax error to one of your assets and use the console to debug. Does it show the correct file and source location? Or does it reference the top level application.js file?
-
Your Rails app Gemfile may have a line requiring sass-rails 5.0: gem 'sass-rails', '~> 5.0' # or gem 'sass-rails', '~> 5' These will prevent upgrade to sprockets 4, if you'd like to upgrade to sprockets 4 change to: gem 'sass-rails', '>= 5'
Tags
- have discussion/feedback/debate in public (transparency)
- Gemfile: version constraints
- test plan / how to test (software development)
- how to check/verify/test whether something is working
- link to what you are referring to
- dependencies: locking to specific version
- allowing sufficient time for discussion/feedback/debate before a final decision is made
Annotators
URL
-
-
www.schneems.com www.schneems.com
-
That’s it. If you have a previous “precompile” array, in your app config, it will continue to work. For continuity sake I recommend moving over those declarations to your manifest.js file so that it will be consistent.
-
That’s pretty gnarly. While the name of the constant LOOSE_APP_ASSETS gives me some idea of what it does, it still takes a second to wrap your mind around. If you were trying to figure out what assets are being precompiled and you did a puts config.assets.precompile that lambda object would be utterly baffling.
-
-
cherrycreekschools.instructure.com cherrycreekschools.instructure.com
-
Did the district just not see the problem with taking away some schools busing?
-
I thought that these numbers where really interesting, especially when the Hispanic enrollments increased
Tags
- Without waiting for judicial approval, the board pulled nineelementary schools out of the busing program this summer, reducing to 10 percent thenumber of students being bused.
- In 1968, the year before busing began, 63,398 white students attended Denver publicschools. Last year, there were 18,000. Black enrollments have remained about 13,000, whileHispanic enrollments have increased to 28,283 from 18,611.
Annotators
URL
-
-
trailblazer.to trailblazer.to
-
Yes, we could and should use Reform or Dry-validation here.
-
provide interfaces so you don’t have to think about them
Question to myself: Is not having to think about it actually a good goal to have? Is it at odds with making intentional/well-considered decisions?  Obviously there are still many of interesting decisions to make even when using a framework that provides conventions and standardization and makes some decisions for you...
Tags
- software design patterns
- example: in order to keep example concise/focused, may not implement all best practices (illustrates one thing only)
- intentional/well-considered decisions
- so you don’t have to think about it
- interfaces (programming)
- standardization
- I have a question about this
- framework
Annotators
URL
-
-
en.wikipedia.org en.wikipedia.org
-
found that using only the Pascal-provided control structures, the correct solution was given by only 20% of the subjects, while no subject wrote incorrect code for this problem if allowed to write a return from the middle of a loop.
-
computers theoretically need only one machine instruction (subtract one number from another and branch if the result is negative)
-
-
sobolevn.me sobolevn.me
-
Now you can easily spot them! The rule is: if you see a Result it means that this function can throw an exception. And you even know its type in advance.
-
we also wrap them in Failure to solve the second problem: spotting potential exceptions is hard
-
Not all cases can be covered and easily restored. And sometimes when we will reuse this function for different use-cases we will find out that it requires different restore logic.
-
But why do we return 0? Why not 1? Why not None? And while None in most cases is as bad (or even worse) than the exceptions, turns out we should heavily rely on business logic and use-cases of this function.
-
Almost everything in python can fail with different types of exceptions: division, function calls, int, str, generators, iterables in for loops, attribute access, key access, even raise something() itself may fail. I am not even covering IO operations here. And checked exceptions won’t be supported in the nearest future.
-
You still need to have a solid experience to spot these potential problems in a perfectly readable and typed code.
-
print will never be actually executed. Because 1 / 0 is an impossible operation and ZeroDivisionError will be raised.
-
So, the sad conclusion is: all problems must be resolved individually depending on a specific usage context. There’s no silver bullet to resolve all ZeroDivisionErrors once and for all. And again, I am not even covering complex IO flows with retry policies and expotential timeouts.
Tags
- depends on use case / application
- type checking
- rule of thumb
- difficult/hard problem
- the specific context is important
- error/exception handling: spotting potential exceptions is hard
- sad/unfortunate conclusion
- why?
- the benefit of experience
- anticipating what could go wrong / error/exception cases
- actually consider / think about how it _should_ (ideally) be
- monad: Either
- type annotations
- error/exception handling
- railway-oriented programming
- easy to miss / not notice (attention)
- easy to see/notice
- can't think of everything
- need to solve specific case/problems individually (there is no general solution)
Annotators
URL
-
-
en.wikipedia.org en.wikipedia.org
-
despite initially appearing to be an appropriate and effective response to a problem, has more bad consequences than good ones
-
-
-
I'm not a fan of listing exceptions functions can throw, especially here in Python, where it's easier to ask forgiveness than permission.
-
certainly I wouldn't want it to start telling me that I'm not catching these!
Tags
- easier to ask forgiveness than permission
- checked exceptions
- programming languages: requires verbosity / extra paperwork to explicitly list types/exceptions/...
- Python: the Python way
- errors/warnings that may not apply to your case and be noisy/annoying to be warned about
- error/exception handling
Annotators
URL
-
-
github.com github.com
-
Enforces better architecture
-
-
www.kickstarter.com www.kickstarter.comDEFCON 11
-
The author will offer presentation/game sessions on Tabletopia, in French and English. In addition, the game will be freely available for players on Tabletopia as soon as the written rules are available.
-
-
www.metacritic.com www.metacritic.com
-
This tedium would be unacceptable in an action game, but Windbound is a survival game. In survival games, death is supposed to mean something. Loss of progress represents the stakes; repetition is the barrier of entry.
-
-
www.morozov.is www.morozov.is
-
Do notation provides an alternative to bind, which also flattens the code.
-
However, you don’t need to have an extensive knowledge of monads to use ROP in your code.
-
-
en.wikipedia.org en.wikipedia.org
-
For historical reasons, this map is instead called fmap in Haskell.
-
-
dry-rb.org dry-rb.org
-
In other words, once you've used Maybe you cannot hit nil with a missing method. This is remarkable because even &. doesn't save you from omitting || "No state" at the end of the computation. Basically, that's what they call "Type Safety".
-
It's hard to say why people think so because you certainly don't need to know category theory for using them, just like you don't need it for, say, using functions.
-
-
jrsinclair.com jrsinclair.com
-
As you can see, we end up with a lot of boilerplate if-statements. The code is more verbose. And it’s difficult to follow the main logic.
-
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 if you don't yet understand functors or applicative functors, check out part 1 and part 2 of this series!
-
-
-
fsharpforfunandprofit.com fsharpforfunandprofit.com
-
This is a useful approach to error handling, but please don’t take it to extremes! See my post on “Against Railway-Oriented Programming”.
-
-
fsharp.org fsharp.org
Tags
Annotators
URL
-
-
trailblazer.to trailblazer.to
-
Feel free to pick and choose what you need for your applications.
-
-
en.wikipedia.org en.wikipedia.org
-
Software architecture is about making fundamental structural choices that are costly to change once implemented.
-
-
www.huffpost.com www.huffpost.com
-
They do not maintain a to-do list (mentally or physically).
-
If you ask my former students, they will tell you that as a teacher, my goal is to do nothing. I dream of the day when I can sit at my desk, feet propped up, reading a book, while the classroom bursts with activity and learning around me.
-
-
-
en.wikipedia.org en.wikipedia.org
-
-
-
In the short term you may have the stamina to get up earlier, stay later, and out-work the demands you face. But the inverse equation of shrinking resources and increasing demands will eventually catch up to you, and at that point how you involve others sets the ceiling of your leadership impact.
-
-
trailblazer.to trailblazer.to
-
The legendary cfp-app will become a Rails-to-TRB refactoring tutorial.
-
And yes, at TRB GmbH, we do pay people to work on OSS
-
-
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
- wording designed to be more palatable/pleasing/inoffensive
- open-source software: not contributing new code back to project
- well-written
- neutral/dispassionate/impartial/objective wording
- software licensing
- annotation meta: may need new tag
- loophole/escape hatch
- good point
- reminder
- LGPL
Annotators
URL
-
-
github.com github.com
-
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.
Tags
- newer/better ways of doing things
- focus on concepts/design/structure instead of specific/concrete technology/implementation
- abstractions
- trailblazer-operation
- focus on what it should do, not on how it should do it (implementation details; software design)
- 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)
- leaving the details of implementation/integration up to you
- rails: the Rails way
- freedom of user to override specific decision of an authority/vendor (software)
- Trailblazer
- making changes / switching/migrating gradually/incrementally/step-wise/iteratively
Annotators
URL
-