Why would such a transcendent power or consciousness do such a thing?
for Q ❓- why would a transcendent power do such a thing? - why should death and pain be such an intrinsic creation of the transcendent? - pain receptors helo give us feedback to survive - but unfortunately, they are there often when it life is coming to an end
there are people in the Trump administration orbit who actually view the dollar's role as the world's reserve currency, as bad for the U.S. economy, not an exorbitant privilege, but something that undermines our export competitiveness
for - adjacency - US reserve currency - Some in Trump admin see it as a bad thing - question - Does Trump admin want to intentionally devalue US dollar and US reserve currency status?
comment - They want to devalue the US dollar so that US goods are more competitive - lower cost
when you hear something you know your eardrum is vibrating that goes your CIA stuff happens ships off to your brain but it's all happening in here and yet you believe you hear the dog out there and it turns out the same thing happens after about half a year of wearing this
for - sensory substitution - after 6 month - signal on skin - sounds like there is an external source of sound - same thing happens with our ear - David Eagleman
the first thing to understand is human beings are relational beings
for - quote - first thing to understand is that humans are relational beings - John Churchill - adjacency - humans are relational beings John Churchill - Deep Humanity - individual / collective gestalt - self / other gestalt
The seeming luxury of having multiple words to choose from is not sufficient to offset the lingering fear that no matter which word you pick it will be the wrong one, causing people to silently laugh at you and judge both you and your grammar school teachers
what really I was really interested in was the idea that Marx wasn't really Keen or was sort of hostile to the idea of equality which I'm guessing will come as a surprise to many people
for - interesting perspective - Karl Marx - He wasn't principally interested in equality - book - Capitalism: the word and the thing - perspectival knowledge of - Michael Sonenscher - misunderstanding - modern capitalists - misunderstand Karl Marx's work - Michael Sonenscher - Karl Marx and Capitalism - Maximizing each individual's freedom while not trampling on the same aspiration of other individuals within a society
Interesting perspective - Karl Marx wasn't principally interested in equality - Sonenscher offers an interesting interpretation and perspectival knowledge of Karl Marx's motivation in his principal work paraphrase - Marx's thought centered on is interest in individuality and the degree to which in certain respects being somebody who is free and able to make choices about his or her lives and future activities is going to depend on each person's: - qualities - capabilities - capacities - preoccupations - values, etc - For Marx, freedom is in the final analysis something to do with something - particular - specific and - individual w - What matters to me may not matter entirely in the same sort of way to you because ultimately - in an ideal State of Affairs, my kinds of concerns and your kinds of concerns will be simply specific to you and to me respectively - For Marx, the problems begin as is also the case with Rosseau - when these kinds of absolute qualities are displaced by - relative qualities that apply equally to us both - For Marx, things like - markets - prices - commodities and - things that connect people - are the hallmarks of equality because they put people on the same kind of footing prices and productivity - Whereas the things that REALLY SHOULD COUNT are - the things that separate and distinguish people that make each individual fully and and entirely him or herself and - the idea for Marx is that capitalism - which is not a term that Marx used, - puts people on a kind of spurious footing of equality - Getting beyond capitalism means getting beyond equality to a state of effect in which - difference , - particularity, - individuality and - uniqueness - in a certain kind of sense will prevail
comment - This perspective is quite enlightening on Marx's motivations on this part of his work and is likely misconstrued by those mainstream "capitalists" who vilify his work without critical analysis - Of course freedom - within a social context - is never an absolute term. - It is not possible to live in a society in which everyone is able to actualize their full imaginations, something pointed out in the work of two other famous thought leaders of modern history: - Thomas Hobbes observed in his famous work, Leviathan, and - Sigmund Freud also made a primary subject of his ID, Ego and Superego framework. - Total freedom would lead - first to anarchy and then - the emergence within that anarchy of those which possess the most charisma, influence, self-seeking manipulative skills and brutality - surfacing rule by authority - Historically, as democracy attempts to surface from a history of authoritarian, patriarchal governance, - democracy is far from ubiquitous and authoritarian governance is still alive and well in many parts of the world - The battle between - authoritarian governments among themselves and - authoritarian and democratic governments - results in war, violence and trauma that creates the breeding ground for the next generation of authoritarian leaders - Marx's main intent seems to be to enable the individual existing within a society to live the fullest life possible, - by way of enabling and maximizing their unique expression, - while not constraining the same aspiration in other individuals who belong to the same society
for - capitalism - etymology - book Captialism: The Word and the Thing - Michael Sonenscher - from - Princeton University Press
Summary - Michael Sonenscher discusses the modern evolution of the word "capitalism". Adding the suffix "ism" to a word implies a compound term. - Capitalism is a complex, compound concept whose connotations from the use in 18th and 19th century France and England is quite different from today's. - How meaning evolved can give us insight into our use of it today.
from - Princeton University Press - book - Capitalism: the word and the thing - to - https://hyp.is/kVaURoxREe-x7MtVDX2t3Q/press.princeton.edu/ideas/capitalism-the-word-and-the-thing
Michael Sonenscher
for - capitalism - etymology - modern - book Capitalism: The Word and the Thing - Michael Sonenscher - from - Discussion of "spiritual capitalism" on Kansas Missouri Fair Shares Commons chat thread - to - youtube - New Books Network - interniew - Captialism: The word and the thing - Michael Sonenscher
Summary - Michael Sonenscher discusses the modern evolution of the word "capitalism". Adding the suffix "ism" to a word implies a compound term. - Capitalism is a complex, compound concept whose connotations from the use in 18th and 19th century France and England is quite different from today's. - How meaning evolved can give us insight into our use of it today.
to - youtube - New Books Network - interniew - Captialism: The word and the thing - Michael Sonenscher - https://hyp.is/ftWWfoxQEe-FkUuIeSoZCA/www.youtube.com/watch?v=ZpNaxyPpOf0
Let your operating system handle daemons, respawning and logging while you focus on your application features and users.
This makes developing a modern daemon much easier. The init config file is what you use to configure logging, run as a user, and many other things you previous did in code. You tweak a few init config settings; your code focuses less on housekeeping and more on functionality.
Disable all observers in your test suite by default. They should not be complicating your model tests because they should have separate concerns anyway. You don't need to unit test that observers actually fire, because ActiveRecord's test suite does that, and your integration tests will cover it.
hash digest returns an alphanumeric message which is the digest. that is incorrect, this alphanumeric message is a representation of the digest. The digest itself is a string of bits with a fixed length
The worst thing for stone – and for bricks, come to that – is for them to be bedded, jointed or rendered with hard cement mortars.
for - sustainable building - cement mortar is the worst thing for re-using bricks
I'd agree that much of the time 'not prefer' is a perfectly adequate way of conveying the same sense as 'disprefer' (just as 'not agree' will for most purposes convey the same sense as 'disagree', and 'not like' the same sense as 'dislike'). However, they aren't strictly equivalent; I might neither prefer nor disprefer Coke to Pepsi, but rather be neutral between them. Possibly the purpose for which 'disprefer' is most useful is cancelling implications – 'I don't prefer it – though I don't disprefer it either'.
Failure to assemble an appropriate IEP team:
Understanding how you feel in the face of other voices, without second guessing yourself, is probably the single most important thing to practice as an artist.
for - quote - most important thing to practice as an artist - Rick Ruben
quote - single most important thing to practice as a musician - Rick Ruben - (see below)
when you actually have chronic anything usually it's not a good result
for - chronic disease - usually chronic is not a good sign - too much of a good thing turns out to be bad - it means too much of something, like inflammation will cause harm - when inflammation knob is stuck on high, it becomes a problem
metaphor - inflammation and forest fire - If you are camping in the forest, a small fire keeps you warm and you can cook - Inflammation is like that small fire going out of control and burning the whole forest down
// Not recommended: log into the application like a user
// by typing into the form and clicking Submit
// While this works, it is slow and exercises the login form
// and NOT the feature you are trying to test.
One more example of a simple approach to this that might help a lot too is add a PORO generator. It could be incredibly basic - rails g poro MyClass yields class MyClass end But by doing that and landing the file in the app/models directory, it would make it clear that was the intended location instead of lib.
So then they put it into lib only to find that they have to manually require it. Then later realize that this also means they now have to reboot their server any time they change the file (after a painfully long debugging time of "why what aren't my changes working?", because their lib folder classes are now second-class citizens). Then they go down the rabbit hole of adding lib to the autoload paths, which burns them because rake tasks then all get eager loaded in production. Then they inevitably realize anything inside app is autoloaded and make an app/lib per Xavier's advice.
I think the symmetry of the naming between lib and app/lib will lead a fresh Rails developer to seek out the answer to “Why are there two lib directories?", and they will become illuminated. And it will prevent them from seeking the answer to “How do I autoload lib?” which will start them on a rough path that leads to me advising them to undo it.
What interests us far more is that these apprentice writers have interesting ideas to convey, and manage to support their arguments well.
only partial match: the most important thing is the information (more than presentation/formatting)
it should provide one task only and do it well
UNIX philosophy: Do one thing and do it well!
There Ain't No Such Thing as a Free Lunch (TANSTAAFL)
In recent git versions, git restore is supposed to be a "better" way to revert undesired local changes than the overloaded checkout. Great, that sounds reasonable - a nice simple purpose-built tool for a common operation.
We now take an opinionated stance on which second factor you should set up first – you'll no longer be asked to choose between SMS or setting up an authenticator app (known as TOTP), and instead see the TOTP setup screen immediately when first setting up 2FA.
I've worked with and have helped maintain paranoia for a while. I'm convinced it does the wrong thing for most cases. Paranoia and acts_as_paranoid both attempt to emulate deletes by setting a column and adding a default scope on the model. This requires some ActiveRecord hackery, and leads to some surprising and awkward behaviour.
<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>John Mount</span> in Good Stationery as a Tool of Thought | MZLabs (<time class='dt-published'>11/30/2022 13:11:31</time>)</cite></small>
Read 2022-12-31
Let’s say the recipient is considering unsubscribing. He or she may be too busy to search through the email to find the unsubscribe link, so he or she just clicks “Report as SPAM” to stop the emails from coming. This is the last thing any marketer wants to see happen. It negatively impacts sender reputation, requiring extra work to improve email deliverability. With the list-unsubscribe header, you will avoid getting into this kind of trouble in the first place.
You can access Events through a few interfaces: Webhooks (we POST data to your URL). The Events API (you GET data through the API). The Logs tab of the Control Panel (GUI).
In v3, svelte-preprocess was able to type-check Svelte components. However, giving the specifics of the structure of a Svelte component and how the script and markup contents are related, type-checking was sub-optimal. In v4, your TypeScript code will only be transpiled into JavaScript, with no type-checking whatsoever. We're moving the responsibility of type-checking to tools better fit to handle it, such as svelte-check, for CLI and CI usage, and the VS Code extension, for type-checking while developing.
In the guide below, you may see different terms referring to the same thing.
They are 100% identical; just different names. From podman-build: “Builds an image using instructions from one or more Containerfiles or Dockerfiles and a specified build context directory. A Containerfile uses the same syntax as a Dockerfile internally. For this document, a file referred to as a Containerfile can be a file named either ‘Containerfile’ or ‘Dockerfile’.”
Good commit hygiene is considered a best practice. GitLab should encourage and enable these kinds of best practices. This feature currently creates a problem and requires workarounds that remove information, or significant manual work.
highly recommended that the resulting image be just one concern per container; predominantly this means just one process per container, so there is no need for a full init system
container images: whether to use full init process: implied here: don't need to if only using for single process (which doesn't fork, etc.)
Doing everything PID 1 needs to do and nothing else. Things like reading environment files, changing users, process supervision are out of scope for Tini (there are other, better tools for those)
I took along my son, who had never had any fresh water up his nose and who had seen lily pads only from train windows. On the journey over to the lake I began to wonder what it would be like. I wondered how time would have marred this unique, this holy spot--the coves and streams, the hills that the sun set behind, the camps and the paths behind the camps. I was sure that the tarred road would have found it out and I wondered in what other ways it would be desolated. It is strange how much you can remember about places like that once you allow your mind to return into the grooves which lead back. You remember one thing, and that suddenly reminds you of another thing. I guess I remembered clearest of all the early mornings, when the lake was cool and motionless, remembered how the bedroom smelled of the lumber it was made of and of the wet woods whose scent entered through the screen. The partitions in the camp were thin and did not extend clear to the top of the rooms, and as I was always the first up I would dress softly so as not to wake the others, and sneak out into the sweet outdoors and start out in the canoe, keeping close along the shore in the long shadows of the pines. I remembered being very careful never to rub my paddle against the gunwale for fear of disturbing the stillness of the cathedral.
Michael Buckland coined in 1991 the phrase "information as thing" and discussed this concept in relation to evidence.
Protagonist Does a Thing formula
https://slate.com/culture/2022/06/book-titles-eleanor-oliphant-women-fiction.html
This article has a nice number of examples of the naming convention: "Protagonist Does a Thing"
I am a bit shocked to see Hypothes.is indicates that there are 31 (private) annotations on this particular page. What is going on here?!
particular
in particular ?
supports
support or supporting
susbtantial
substantial
This collection of three classes of fields
hanging sentence
researcher
a researcher or researchers
Making MoneySerializer reloadable would be confusing, because reloading an edited version would have no effect on that class object stored in Active Job.
Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.
PPW 四分区坐垫
software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directly opposed to short-term efficiency. Unfortunately, people are fairly good at short-term design, and usually awful at long-term design
So if I just forward the cookie header (which contains the access-token), wouldn't that be just what I am not supposed to do. I mean what's the point of using 'HttpOnly' flag if I return the token to the client-side js on every request.
THE SUNDAY THING
The love of money is the root of all evil
This week, Michael Gungor asked us to discuss money in our breakout groups.
We outsource our power and authority to those who claim to have greater access to capital, because we underestimate and undervalue our own social influence, economic capacity, and political agency. The entreprecariat is designed for learned helplessness (social: individualism), trained incapacities (economic: specialization), and bureaucratic intransigence (political: authoritarianism). https://hypothes.is/a/667dOC0bEeyV6Itx3ySxmw
Indigenous cultures in Canada were disempowered by outlawing the cultural practice of generosity (potlatch) and replacing the practice with centralized power over the medium of exchange: money. Money is a mechanism of disempowerment.
Money is a shared story we tell ourselves about what has value. https://www.npr.org/transcripts/795246685
We translated “ekklesia” as church. It is the deliberative body of the experiment in democracy in Athens, Greece. The people who are figuring out how to live together in the commons. The work of the people. The Liturgists.
In this hour, On the Media looks at the story of money, from its uncertain origins to its digital reinvention in the form of cryptocurrency.
On the Media: Full Faith & Credit
People were also discussing Squid Game.
Squid Game was on my mind today before the call. “The reality of the history of Canada’s mining industry makes #SquidGame look like child’s play.” https://twitter.com/bauhouse/status/1449726452098682881?s=20
The truth is that all of the gold that was mined out of the Klondike was under Indigenous land. There was no treaty with any of Indigenous peoples in the Yukon.
those users apparently can't even be trusted to choose the option to enable it from a pop-up
Now consider we want to handle numbers in our known value set: const KNOWN_VALUES = Object.freeze(['a', 'b', 'c', 1, 2, 3]) function isKnownValue(input?: string | number) { return typeof(input) === 'string' && KNOWN_VALUES.includes(input) } Uh oh! This TypeScript compiles without errors, but it's not correct. Where as our original "naive" approach would have worked just fine. Why is that? Where is the breakdown here? It's because TypeScript's type system got in the way of the developer's initial intent. It caused us to change our code from what we intended to what it allowed. It was never the developer's intention to check that input was a string and a known value; the developer simply wanted to check whether input was a known value - but wasn't permitted to do so.
By looking at the code screenshot, you are either opening your mouth in awe or in appall. I feel there is no in-between here.
Bird sound encoding
I was at the bookstore yesterday and ran into two new useful resources that looked interesting in this space.
Specific to birdsong, there was
Read about and listen to birds from six continents. A beautiful painting illustrates each selection along with concise details about the bird's behavior, environment, and vocalizations. On the built-in digital audio player, hear each bird as it sings or calls in nature with audio of the birds provided by the Macaulay Library at the Cornell Lab of Ornithology.
This could be useful in using the book itself as a memory palace in addition to the fact that the bird calls are built directly into the book for immediate playback while reading/memorizing. There are a few other related books with built in sound in this series as well.
The other broader idea was that of
I saw the book A Bird A Day by Dominic Couzens (Batsford, 2021, ISBN: 978-1849945868) to help guide one towards learning about (or in our context maybe memorizing) a bird a day. It had names, photos, and other useful information which one might use to structure a palace to work at in small chunks. I know there are also many other related calendars which might also help one do something like this to build up a daily practice of memorizing data into a palace/journey/songline.
The broader "Thing-a-day" calendar category might also be useful for other topics one might want to memorize as well as to have a structure set up for encouraging spaced repetition.
Different ways to prepend a line: (echo 'line to prepend';cat file)|sponge file sed -i '1iline to prepend' file # GNU sed -i '' $'1i\\\nline to prepend\n' file # BSD printf %s\\n 0a 'line to prepend' . w|ed -s file perl -pi -e 'print"line to prepend\n"if$.==1' file
The first argument to shared_context (the shared group name) is superfluous. It feels a bit like "what's this argument for again?" (Note that you could still use it with include_context to include the group manually, but it's a bit odd to mix-and-match the approaches).
I'm not sure if there's any cost in terms of contributing either, especially when by design git can have any branch as default, and will not hinder your experience when you use something other than master.
git is neutral/unbiased/agnostic about default branch name by design
And that is a good thing
Once a variable is specified with the use method, access it with EnvSetting.my_var Or you can still use the Hash syntax if you prefer it: EnvSetting["MY_VAR"]
Of course you must not use plain-text passwords and place them directly into scripts. You even must not use telnet protocol at all. And avoid ftp, too. I needn’t say why you should use ssh, instead, need I? And you also must not plug your fingers into 220 voltage AC-output. Telnet was chosen for examples as less harmless alternative, because it’s getting rare in real life, but it can show all basic functions of expect-like tools, even abilities to send passwords. BUT, you can use “Expect and Co” to do other things, I just show the direction.
Too new to comment on the specific answer
So you think it's better to make people post a new "answer" (as if it were actually a distinct, unrelated answer) instead of just letting them comment on the answer that they actually want to comment on? Yuck.
The central decision of the game is when to play your houses. And you didn't even really talk about that.
Scholar@UC: University of Cincinnati's self-submission institutional repository
Focus is better than features.
non-regression testing
That would probably be a better name because you're actually testing/verifying that there hasn't been any regression.
You're testing for the absence of regression. But I guess testing for one also tests for the other, so it probably doesn't matter. (If something is not true you know it is false, etc.)
Write modules that do one thing well. Write a new module rather than complicate an old one.
.
Nee na ndëmm amul.
Il dit que la sorcellerie n'existe pas.
nee -- pr. circ. so, demonstratively distant. Cf. nale.
na -- 1. pr. circ. so, defined distant. How? 'Or' What. 2. function indicator. As.
ndëmm gi -- symbolic anthropophagia. 🧙
Webshim is also more than a polyfill, it has become a UI component and widget library. Webshim enables a developer to also enhance HTML5 capable browsers with more highly customizable, extensible and flexible UI components and widgets.
And now that it's deprecated (presumably due to no longer needing these polyfills), not only do the polyfills go away (no longer maintained), but also these unrelated "extras" that some of us may have been depending on are now going away with no replacement ...
If those were in a separate package, then there would have been some chance of the "extras" package being updated to work without the base webshims polyfills.
In particular, I was using
$.webshims.addCustomValidityRule
which adds something that you can't do in plain HTML5 (that I can tell), so it isn't a polyfill...
the Activity component is the heart of TRB
Hey, that’s is an imaginary complication of our example - please don’t do this with every condition you have in your app.
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 breaks magnetic_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:
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?
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.
Yes, we could and should use Reform or Dry-validation here.
In order to invoke, or run
A task is often called step.
I want to emphasize that Result is just an alternative name for the Either monad.
Examples of different ways of defining forms
Wow, that's a lot of different ways.
The inline_form way in particular seems interesting to me, though it's worth noting that that method is just an example, not actually part of this project's code, so it's not really a first-class option like the other options.
The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false or nil.
Seems like these helper functions could be just as easily used in ActiveRecord models. Therefore, they should be in a separate gem, or at least module, that can be used in both these objects and ActiveRecord objects.
That's the whole point of an abstraction layer—to isolate your business logic from a subsystem's mechanics
DSLs can be problematic for the user since the user has to manage state (e.g. am I supposed to call valid? first or update_attributes?). This is exactly why the #validate is the only method to change state in Reform.
Yes, you do face difficult choices (moral) but you don't care about it. All you care are the reputation bars. So... Let's kill this guy, who cares if he is innocent, but this faction needs it or I'm dead. Sounds great on paper but to be honest... you just sit there and do whatever for these reputation bars. If you won't, then you lose
So the hard and unsolvable problem becomes: how up-to-date do you really need to be?
After considering the value we place, and the tradeoffs we make, when it comes to knowing anything of significance, I think it becomes much easier to understand why cache invalidation is one of the hard problems in computer science
the crux of the problem is: trade-offs
You can write the query in this good old way to avoid error
Also there is always an option to use SQL: @items .joins(:orders) .where("orders.user_id = ? OR items.available = true", current_user.id)
but if .or() throws an error then I'm back to the bad old days of using to_sql
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
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.
Making literal grids. Like X columns with Y gap between them homegrown framework stuff. grid-gap is wonderful, as gutters are the main pain point of grid systems.
Depending on what other component libraries you’ve used, you may be used to handling events by passing callback functions to component properties, or using a special event syntax – Svelte supports both, though one is usually more appropriate than the other depending on your situation. This post explains both ways.
"Headless Tippy" refers to Tippy without any of the default element rendering or CSS. This allows you to create your own element from scratch and use Tippy for its logic only.
It's a generic abstraction for the logic and styling of elements that pop out from the flow of the document and float next to a reference element, overlaid on top of the UI.
Popper has a sole goal: position elements. That's why we call it a "positioning engine" and not a "tooltip library".
Dropped FFmpeg support (focus on primary functions instead)
Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.
I tried leaking session and page data and indeed it's easy. Too easy. So I definitely agree that session data should not be readable from anywhere but the request itself.
it focuses on compiling non-standard language extensions: JSX, TypeScript, and Flow. Because of this smaller scope, Sucrase can get away with an architecture that is much more performant but less extensible
No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.
This could be both good and bad.
potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.
Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.
Ah, good, I see they touched on some of these points in the sections:
I don't think this is what really matters at the end, since whatever is the implementation the goal should be to provide a library that people actually like to use.
delete myObject.regex; // or, delete myObject['regex']; // or, var prop = "regex"; delete myObject[prop];
emphasizing that 'this' and 'global object' are two different things not only in Node.js but in JavaScript in general
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.)
This one gets the SEO, so I hope you're successful @raythurnevoid.
I assume this gets search traffic because people hope/assume that since there's a React "material-ui" that there might already be a "svelte-material-ui" port/adaptation available. So they search for exactly that (like I did). That and being the first to create that something (with that name).
Svelte makes the pit of success larger because it hides all of this from us at compile time.
I'm still calling this v1.00 as this is what will be included in the first print run.
There seems to be an artificial pressure and a false assumption that the version that gets printed and included in the box be the "magic number" 1.00.
But I think there is absolutely nothing bad or to be ashamed of to have the version number printed in the rule book be 1.47 or even 2.0. (Or, of course, you could just not print it at all.) It's just being transparent/honest about how many versions/revisions you've made. 
So handling the interop upfront will avoid users writing invalid ES6 and make sure that they write ES6 that loads CommonJS in the right way.
Never use x && y || z when y can return a non-zero exit status.
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).
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.
can you not also use a .babelrc?
const useEffect = (subscribe) => ({ subscribe })
This is linux. Ouput first, formatting second. systemctl --no-pager -l should be the default.
First of all, we solved our problem! As demonstrated here our app is happily running again.
The crux of this pattern is to introduce an index.js and internal.js file.
Any software that makes HTTP requests to other sites should make it straightforward to enable the use of a cache.
Furthermore, JSX encourages bad non-dry code. Having seen a lot of JSX over the past few months, its encourages copypasta coding.
A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important.
An onevent event handler property serves as a placeholder of sorts, to which a single event handler can be assigned. In order to allow multiple handlers to be installed for the same event on a given object, you can call its addEventListener() method, which manages a list of handlers for the given event on the object.
"The Map is not the territory" —Alfred Korzybski
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 map–territory relation describes the relationship between an object and a representation of that object, as in the relation between a geographical territory and a map of it.
"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.
An alternative (maybe not good) would be to restrict {@const} to certain blocks like {#each} and {#if}. In both cases, it significantly reduces the "multiple ways to do the same thing" problem and avoids ergonomic and performance overhead of our current situation.
it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.
Solid supports templating in 3 forms JSX, Tagged Template Literals, and Solid's HyperScript variant.
focuses way too much on the getter/tracking part of the equation which is really the part you want reduce the mental bandwidth on
React does not attempt to provide a complete "application library". It is designed specifically for building user interfaces[3] and therefore does not include many of the tools some developers might consider necessary to build an application.
Rollup also does something very different compared to the other bundlers. It only tries to achieve one simple goal: Bundle ES modules together and optimise the bundle.
Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
The problem with working around the current limitations of Svelte style (:global, svelte:head, external styles or various wild card selectors) is that the API is uglier, bigger, harder to explain AND it loses one of the best features of Svelte IMO - contextual style encapsulation. I can understand that CSS classes are a bit uncontrollable, but this type of blocking will just push developers to work around it and create worse solutions.
Lets not extend the framework with yet another syntax
Even without going to that extreme, the constraint of having a single <style> can easily force component authors to resort to the kinds of classes-as-namespaces hacks that scoped styles are supposed to obviate.
If your reaction to the video was 'fine, but if we use TypeScript and write plugins for each editor then we can get all the autocomplete and syntax highlighting stuff' — in other words, if you believe that in order to achieve parity with CSS it makes sense to build, document, promote and maintain a fleet of ancillary projects — then, well, you and I may never see eye to eye!
Now of course we know how React handles this conflict: it takes the new nodes in your virtual DOM tree — the waters in your flowing river — and maps them onto existing nodes in the DOM. In other words React is a functional abstraction over a decidedly non-functional substrate.
To me this is a warning sign, because in my experience, the bigger the gap between an abstraction and the thing it abstracts, the more likely you are to suffer what programmers like to call ‘impedance mismatches’, and I think we do experience that in React.
While the modifying version will occasionally be useful, in general, we should gently push people towards using non-modifying code.
OK, so what about regular messages? Turns out they are not encrypted after all. Where Signal implements the security and privacy protocols right from the start, Telegram separates the two and offers an additional option. The problem is that not everyone is aware of the Secret Chat option and first-time users may send sensitive information in the regular chat window unknowingly.
“Make it work” means shipping something that doesn’t break. The code might be ugly and difficult to understand, but we’re delivering value to the customer and we have tests that give us confidence. Without tests, it’s hard to answer “Does this work?”
Pipes are great for taking output of one command and transforming it using other commands like jq. They’re a key part of the Unix philosophy of “small sharp tools”: since commands can be chained together with pipes, each command only needs to do one thing and then hand it off to another command.
Just to make this clear, I'm on the side that adding strict rules doesn't necessarily improve a situation. Especially with something that is subjective like a commit message.
The "'strict-dynamic'" source expression aims to make Content Security Policy simpler to deploy for existing applications who have a high degree of confidence in the scripts they load directly, but low confidence in their ability to provide a reasonable list of resources to load up front.
It even proclaims that "the processing of personal data should be designed to serve mankind."
This is it. I'm done with Page Translator, but you don't have to be. Fork the repo. Distribute the code yourself. This is now a cat-and-mouse game with Mozilla. Users will have to jump from one extension to another until language translation is a standard feature or the extension policy changes.
Mozilla will never publicly ask users to circumvent their own blocklist. But it's their actions that are forcing people to do so.
So to me, it seems like they want to keep their users safer by... making them use Google Chrome or... exposing themselves to even greater danger by disabling the whole blocklist.
If you're wearing the same shoes as I have so many times before where you're trying to make yourself heard and do what you ultimately believe is in the organisation's best interests
Now, do I care which one you use? No. As long as you test your code, I am happy. A professional developer should be able to work in either one of these because they essentially do the same thing: test your code.
The only goal is correctness. Code style is not a consideration. Providing the level of configuration necessary to make everyone happy would be a huge distraction from the main purpose. After conversion, I recommend using rubocop's awesome --auto-correct feature to apply your preferred code style.
it reminds me of IT security best practices. Based on experience and the lessons we have learned in the history of IT security, we have come up with some basic rules that, when followed, go a long way to preventing serious problems later.
The fact is that it doesn’t matter if you can see the threat or not, and it doesn’t matter if the flaw ever leads to a vulnerability. You just always follow the core rules and everything else seems to fall into place.
Falcon tries to do as little as possible while remaining highly effective.
The handler can be a method or a Proc object passed to the :with option. You can also use a block directly instead of an explicit Proc object.
Example of: letting you either pass a proc (as a keyword arg in this case) or as a block.
When submitting new methods for consideration, it is best if each method (or tightly related set of methods) is in it's own pull request. If you have only one method to submit then a simple commit will do the trick. If you have more than one it best to use separate branches. Let me emphasizes this point because it makes it much more likely that your pull request will be merged. If you submit a bunch of methods in a single pull request, it is very likely that it will not be merged even if methods you submitted are accepted!
Earlier this year it began asking Europeans for consent to processing their selfies for facial recognition purposes — a highly controversial technology that regulatory intervention in the region had previously blocked. Yet now, as a consequence of Facebook’s confidence in crafting manipulative consent flows, it’s essentially figured out a way to circumvent EU citizens’ fundamental rights — by socially engineering Europeans to override their own best interests.
All of which means — per EU law — it should be equally easy for website visitors to choose not to be tracked as to agree to their personal data being processed.
The business had a policy that you should report safety incidents when you see them. The process around that was you fill out a form and fax it to a number and someone will take action on it. The safety manager in this company saw that and decided to digitize this workflow and optimize it. Once this process was put into place, the number of safety incidents reported increased 5 times. The speed at which safety incidents were addressed increased by 60%.
For several reasons the Simple backend shipped with Active Support only does the "simplest thing that could possibly work" for Ruby on Rails3 ... which means that it is only guaranteed to work for English and, as a side effect, languages that are very similar to English. Also, the simple backend is only capable of reading translations but cannot dynamically store them to any format.That does not mean you're stuck with these limitations, though. The Ruby I18n gem makes it very easy to exchange the Simple backend implementation with something else that fits better for your needs, by passing a backend instance to the I18n.backend= setter.
We do the smallest thing possible and get it out as quickly as possible.
a private library is not an ego-boosting appendages but a research tool. The library should contain as much of what you do not know as your financial means … allow you to put there. You will accumulate more knowledge and more books as you grow older, and the growing number of unread books on the shelves will look at you menacingly. Indeed, the more you know, the larger the rows of unread books. Let us call this collection of unread books an antilibrary.
You can but it's difficult. I recommend switching to a different tool.
One thing well. rbenv is concerned solely with switching Ruby versions. It's simple and predictable.
It doesn't use a database (unlike Keepass) and thus doesn't open all passwords at once. Just one at a time. Since it's just a directory of encrypted files, you can access your passwords with any PGP-compatible tool.
Using find and cpio is a more unix-y approach in that you let find do the file selection with all the power that it has, and let cpio do the archiving. It is worth learning this simple use of cpio, as you find it easy to solve problems you bang your ahead against when trying tar.
It shouldn't be useful to distinguish between requests made by Ajax and other kinds of request. Pretty much any usecase where you'd want to do that is better served by using the Accept header to ask for data in a specific format.
As Onivim 2 completely handles the rendering layer, this Vim-modelled-as-a-pure-function could focus on just buffer manipulation.
It is responsible for
do something specific and do it well
Epiphany aims to present the simplest interface possible for a browser. Simple does not necessarily mean less-powerful. The commonly-used browsers of today are too big, buggy, and bloated. Epiphany is a small browser designed for the web: not for mail, newsgroups, file management, instant messaging, or coffeemaking. The UNIX philosophy is to design small tools that do one thing and do it well.
Discourse
We will study how a Disc Jockey’s (DJ’s) endorsement of recording on radio, in the 1950s, could boost sales into the millions.
but Salt Lake City’s cost of living is 16 percent lower than in Denver, 37 percent lower than Seattle’s and 48 percent under San Francisco’s, according to PayScale. The state — often led personally by Governor Gary Herbert — pitches its advantages well to firms considering relocation, says Joe Vranich, whose consulting firm helps small businesses looking to move. “They will roll out the carpet for you and treat you like a king.” The approach is working. Utah’s “Silicon Slopes”
Utah's low cost of living attracts tech companies to operate in Utah. This will make more outsiders to relocate to Utah for jobs which can further aggravate the burden of housing shortage and pricing.
excessive reading has a scattering effect: “In reading of many books is distraction.”
I feel personally attacked. ;)
A , word is an event, a happening, not a thing, as letters make it appear to he
Ong's using "thing" in the sense of a material object, but it'd be worth looking at this line in the context of "thing" and "ding"
But these are also reductions that decline to grant the bridge its autonomy, its unique manner of holding sway in the world. Heidegger points out how the banks of a stream emerge as banks only as the bridge joins them; this happens because the banks show forth in a new relation
This is a helpful articulation, and makes me think back to Home; typically we would frame a "home" through the sentimental or material value it provides to the people living in it, but by moving erratically through time, we got to see the home as the thing itself--an assemblage that pulled together different parts of the world at different times. Because we were not able to "get to know" the humans who lived there well enough to really empathize or become engaged in their personal narratives, our attention was focused on the four-fold of the "home" as a thing itself.
Believing there is no God means the suffering I’ve seen in my family, and indeed all the suffering in the world, isn’t caused by an omniscient, omnipresent, omnipotent force that isn’t bothered to help or is just testing us, but rather something we all may be able to help others with in the future. No God means the possibility of less suffering in the future.
Opinions are one thing but when it comes down to this crazy world we live in, I would have to say that God is not the only reason people are suffering. We face our own difficulties and challenges and there is more then one reason to everything. That's just my opinion.
One electron could stay in orbit around one proton to become an atom of hydrogen
“Starting from a place of 'I don’t have biases' is never helpful.” It’s not necessarily the gender of an engineer that matters, it’s that engineer’s ability to consider perspectives outside their own.
When design solutions address the symptoms of a problem (like sleeping outside in public) rather than the cause of the problem (like the myriad societal shortcomings that lead to homelessness), that problem is simply pushed down the street.
Marvel has always been political. Captain America started fighting Hitler and the Nazis before the USA entered the War. Fantastic Four fought the Communists. Captain America fought, then resigned because of Nixon. The Invisible Girl became The Invisible Woman, you had a character actually called The Black Panther from a fictitious, idealised African country.
Matthew S. MacLennan
I am the author of this paragraph. I am also one of the scientists doing the metabolomic studies. I am in collaboration with many others in this project.
Indeed, the object, or res, of intellectual property may be so new that it is unknown to anyone else.
Definition of res: http://legal-dictionary.thefreedictionary.com/res
Res [Latin, A thing.] An object, a subject matter, or a status against which legal proceedings have been instituted. For example, in a suit involving a captured ship, the seized vessel is the res, and proceedings of this nature are said to be in rem. Res, however, does not always refer to tangible Personal Property. In matrimonial actions, for example, the res is the marital status of the parties.
Latin for: a thing
An object, a subject matter, or a status against which legal proceedings have been instituted.
res (rayz) n. Latin, thing. In law lingo res is used in conjunction with other Latin words as "thing that."