"Without the right to tinker and explore, we risk becoming enslaved by technology; and the more we exercise the right to hack, the harder it will be to take that right away" - Andre "Bunnie" Huang
hah, we are already "enslaved by technology". ask Ted Kaczynski
our enemies already have hardware backdoors, compromising emissions (tempest), closed-source firmware/drivers/hardware, ... but sure, "feel free"
Comments may be turned off across YouTube
False. They may not as long as anyone has Hypothes.is installed.
Comments are turned off.
You wish. 🙄
This Be The Verse<br /> by Philip Larkin
They fuck you up, your mum and dad. <br /> They may not mean to, but they do. <br /> They fill you with the faults they had<br /> And add some extra, just for you.
But they were fucked up in their turn<br /> By fools in old-style hats and coats, <br /> Who half the time were soppy-stern<br /> And half at one another’s throats.
Man hands on misery to man.<br /> It deepens like a coastal shelf.<br /> Get out as early as you can,<br /> And don’t have any kids yourself.
Philip Larkin, "This Be the Verse" from Collected Poems. Copyright © Estate of Philip Larkin. Reprinted by permission of Faber and Faber, Ltd. Source: Collected Poems (Farrar Straus and Giroux, 2001)
Reference: Larkin, Philip. Collected Poems. New York: Farrar Straus & Giroux, 1989.
Compare with The Kids Are Alright.
Recited in Ted Lasso, S3 https://www.looper.com/1294687/ted-lasso-season-3-episode-11-maes-poem-sounds-familiar/#:~:text=To%20jog%20your%20memory%2C%20the,extra%2C%20just%20for%20you.%22
https://wiki.openglobalmind.com/what%E2%80%99s_a_neobook_
Conference calls at 10:30 AM on Mondays. Search YouTube for past occurrences.
Relationship to wikis and zettelkasten for accumulating knowledge as a ratchet.
Recent work has revealed several new and significant aspects of the dynamics of theory change. First, statistical information, information about the probabilistic contingencies between events, plays a particularly important role in theory-formation both in science and in childhood. In the last fifteen years we’ve discovered the power of early statistical learning.
The data of the past is congruent with the current psychological trends that face the education system of today. Developmentalists have charted how children construct and revise intuitive theories. In turn, a variety of theories have developed because of the greater use of statistical information that supports probabilistic contingencies that help to better inform us of causal models and their distinctive cognitive functions. These studies investigate the physical, psychological, and social domains. In the case of intuitive psychology, or "theory of mind," developmentalism has traced a progression from an early understanding of emotion and action to an understanding of intentions and simple aspects of perception, to an understanding of knowledge vs. ignorance, and finally to a representational and then an interpretive theory of mind.
The mechanisms by which life evolved—from chemical beginnings to cognizing human beings—are central to understanding the psychological basis of learning. We are the product of an evolutionary process and it is the mechanisms inherent in this process that offer the most probable explanations to how we think and learn.
Bada, & Olusegun, S. (2015). Constructivism Learning Theory : A Paradigm for Teaching and Learning.
Speed is great but if it doesn't conform to the specification, that's not a great case for using it for future development
If we hand most, if not all responsibility for that exploration to the relatively small number of people who talk at conferences, or have popular blogs, or who tweet a lot, or who maintain these very popular projects and frameworks, then that’s only a very limited perspective compared to the enormous size of the Ruby community.
Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.
Although there's an argument for keeping case sensitivity for the local mailbox (as they can be case sensitive, depending on how they're set up, though I haven't come across case sensitivity in university emails), the domain part of the email address is not case sensitive and should not be treated as such. Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.
If you are storing email addresses then you probably should store them in their original case (the recipient at least) to be safe. However, always compare them case-insensitively in order to avoid duplicates.
However, it's difficult to rely on a case-sensitive email address in the real world because many systems (typically ones that have to handle data merging) don't preserve case. Notably systems that use email addresses for user IDs, or any system that has to collate data from multiple sources (CRMs, email broadcast systems, etc) will either normalise case or treat them case-insensitively.
However, for all practical purposes in the modern age, I believe you can consider email addresses to be case insensitive.
a SHOULD is always trumped in RFCs by a MUST. The fact that hosts SHOULD do something means that they might not and I just wanted reassurance that, in reality, the SHOULD is a bit more widely adopted than its definition implies.
While email addresses are only partially case-sensitive, it is generally safe to think of them as case insensitive. All major providers, such as Gmail, Yahoo Mail, Hotmail, and others, treat the local parts of email addresses as case insensitive.
According to RFC 5321, the local part of the email address is case sensitive. This means that, in theory, SoMething@something.com is not the same as something@something.com. However, email providers have the liberty to treat the local parts as both case sensitive and case insensitive.
Are Email Addresses Case Sensitive? Technically, the answer is yes. However, email addresses are typically not case sensitive; if you type your email address into a form and accidentally capitalize one or two letters, it probably won’t prevent the sender from emailing you.
The local part does, in fact, take the case into account, as per RFC 5321. However, Email Service Providers (ESPs) are aware of the potential confusion that could result from allowing upper-case letters.
In short, while it’s technically possible to make the part before @ case sensitive, most popular email servers do not allow that.
Most big email providers like Gmail, Outlook and even company email address hosted on Google Suite are not case sensitive. Just to avoid any unnecessary confusion. However, in extreme cases, some large companies, implement case sensitivity on their server as some people can often have the same first and last name. But in general, this creates more confusion, than the usability, which is why most standard email providers avoid case sensitivity.
Either way, at some point almost everyone started treating addresses as case-insensitive.
Despite it being commonplace to “fix up” email addresses by lowercasing them — or, in financial/government contexts, uppercasing them — email addresses are clearly defined as case-sensitive in the only standard that matters.
Since using case insensitivity is so widespread, take their sign up email address and make it lower case. Whenever they try to log in, convert that to lowercase as well, for comparison purposes, when you go to see if the user exists. As far as sign up and sign in go, do a case insensitive comparison. If the person signs up as Steve@example.com, you'll still want to allow them to sign in later with steve@example.com or sTeVE@example.com.
But you should also keep track of the email address that they signed up with in a case sensitive fashion. Any time you send an email to them, be sure to send it with that original casing. This allows the email server to handle it however it feels like it needs to. So even though the person may always be signing in to your site with steve@example.com, if they signed up as Steve@example.com, you'll always send email to Steve@example.com, just to be safe.
The de facto standard is to treat local mailboxes as case insensitive, but the official standard says case matters (though even the official standard mentions the de facto standard).
So yes, the part before the "@" could be case-sensitive, since it is entirely under the control of the host system. In practice though, no widely used mail systems distinguish different addresses based on case.
In short, you are safe to treat email addresses as case-insensitive.
Since the case sensitivity of email addresses can create confusion and delivery problems, most email providers and clients either fix the case if the email address is entered in the wrong case, or they ignore upper-case entries. Not many email services or ISPs enforce case-sensitive email addresses.
Stop to think about "normal app" as like desktop app. Android isn't a desktop platform, there is no such this. A "normal" mobile app let the system control the lifecycle, not the dev. The system expect that, the users expect that. All you need to do is change your mindset and learn how to build on it. Don't try to clone a desktop app on mobile. Everything is completely different including UI/UX.
depends on how you look at it: "normal"
gaga's third question where are we going is what i want to address in these talks 00:05:26 it may seem unanswerable who can foretell the human course through time but i think we can answer it in broad strokes by answering the other two questions first 00:05:40 if we see clearly what we are and what we've done we can recognize human behaviors that persist through many times and cultures and knowing these can tell us what we 00:05:52 are likely to do and where we are likely to go from here
the artist managed to harness his grief to produce a vast painting more a mural in conception than a canvas in which like the victorian age itself he demanded 00:04:31 new answers to the riddle of existence he wrote the title boldly on the image three childlike questions simple yet profound where do we come from 00:04:46 what are we where are we going the work is a sprawling panorama of enigmatic figures amid scenery
Paul Gauguin's painting: - Where Do We Come From? What Are We? Where Are We Going? - https://en.wikipedia.org/wiki/Where_Do_We_Come_From%3F_What_Are_We%3F_Where_Are_We_Going%3F#:~:text=Que%20sommes%2Dnous%20%3F,the%20themes%20of%20the%20Gospels%22. - Wright uses this painting as a appropriate introduction to his work tracing human progress because to answer the third question - where are we going? - requires answering the first two - where do we come from? - what are we?
When you call 'foo' in Ruby, what you're actually doing is sending a message to its owner: "please call your method 'foo'". You just can't get a direct hold on functions in Ruby in the way you can in Python; they're slippery and elusive. You can only see them as though shadows on a cave wall; you can only reference them through strings/symbols that happen to be their name. Try and think of every method call 'object.foo(args)' you do in Ruby as the equivalent of this in Python: 'object.getattribute('foo')(args)'.
Note though, that this only works when you're already using git for your dependency
I was trying to figure out why it wasn't working for me. This was probably the reason.
So if you just have gem 'rack', it just silently has no effect.
It seems like it should just work either way. Or at least give a warning/error if you try to use this config and it's not going to use that config!
"Personal knowledge management is an aid to your work, not the work itself." —Sam Matla #
This is entirely dependent on what and how you're doing it. If you're actively reading and annotating, and placing it somewhere, then that is the work, just in small progressive steps.
He needs to be more specific about what he means by "personal knowledge management" as a definition of something.
People know it’s bad but not how bad. This gap in understanding remains wide enough for denialists and minimisers to legitimise inadequate action under the camouflage of empty eco-jargon and false optimism. This gap allows nations, corporations and individuals to remain distracted by short-term crises, which, however serious, pale into insignificance compared with the unprecedented threat of climate change.
个人学习可能取决于他人行为的主张突出了将学习环境视为一个涉及多个互动参与者的系统的重要性
ned the art of notetaking for themselves that this pamphletis prepared. It does not seem wise to attempt to lay down any verystringent rules on the subject. We can only suggest the more generalmethods from which every man can work out his own particular system.
Primary keys and foreign keys are the fundamental building blocks of the relational database because these are the components that make the relationships work while allowing tables to be accessed independently. One-to-many relationships between primary keys and foreign keys are thus defined as referential constraints in the physical database
this has a few sections we're going to first talk about snakes and 00:12:58 elephants then about this idea of the atman it's the sanskrit name for itself the self that's the english word and the soul or suitcase we might say in christian theology then i will introduce 00:13:10 you to my favorite illusion because it's fun and it will help us to get a fix on what we're doing and then i will argue that in fact you do really think that you have a self so there is a point to all of this there 00:13:21 would be no point if we didn't think we had self there would be no point in refuting them and then we'll fight try to ask why you think you have a self so that's what we're going to do in the first part of tonight's talk
!- who do you think you are : has sections - snakes and elephants - the atman - favorite illusion - argument: you really do think you have a self - why you think you have a self
This was originally disallowed because #5907 was opened asking for different behavior in this situation that we didn't want to allow, and so we decided to make it a compiler error rather than have confusing behavior in that situation.
The console needs to be readable in development and to provide the best DX I have to design my libraries in ways that prevent these warnings. This results in design decisions that are detrimental to functionality and/or code readability/simplicity.
I just spent a day dismantling a model, trying to find the cause of the silent rollback - taking out every association, every validation, every callback, whittling down all the code in the transaction, only to finally discover that it was return true that was the cause of it all. Or yes, an exception!
Instead of imposing a ‘rational’ order on the fragments,Barthes used the ‘stupid’, arbitrary, obvious order of the alphabet(which he also most often followed when he was classifying his indexcards): this was how he proceeded in ‘Variations on Writing’ and inRoland Barthes par Roland Barthes. This was how he achieved anindividual identity, surrendering to his tastes and to concrete littleidiosyncrasies.
Deutsch’s index, then, did not constitute the systematic and overarching view ofJewish history and contemporaneous Jewish issues that Deutsch had initially hoped tocreate. Instead, it was much more personal. It reflected his singular reading regime, and itworked with a certain shorthand: In later years Deutsch often just cited ‘Yiddish papers’or ‘Daily papers’, and in some instances he referred to ‘private information’. The cards,topics, and sources provide a sense of the specific information that interested Deutsch.
Examining the cards, it becomes clear that the index constitutes not a mythic totalhistory but a specific set of facts and data that piqued Deutsch’s interest and whichreflected his personal research priorities (see Figure 2).
Zettelkasten, if nothing else, are a close reflection of the interests of the author who collected them.
link: Ahrens mentions this
Does this mean that the schema is available now since the bug is closed?
Shouldn't have had to ask. But fortunately, link posted below
There is a connection between the words that is from the setting, background, and image of the words.
Politique documentaire Ensemble des objectifs et processus pilotant la gestion de l’information, incluant la politique d’acquisition, la politique de conservation et la politique de médiation des collections. La politique documentaire est une partie intégrante et essentielle du projet d'établissement, permettant de répondre aux missions de la structure et aux attentes des usagers.
We brought in a metadata librarian, Elizabeth Padilla, from British Columbia Institute of Technology (BCIT), to ensure people can find the materials in the niches they want, using the language they already know.
5.5 Logic, reason, and common sense are your best tools for synthesizing reality and understanding what to do about it.
5.5 Logic, reason, and common sense are your best tools for synthesizing reality and understanding what to do about it.
4.4 Find out what you and others are like.
4.4 Find out what you and others are like.
4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.
4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.
4.1 Understand the power that comes from knowing how you and others are wired.
4.1 Understand the power that comes from knowing how you and others are wired.
4 Understand That People Are Wired Very Differently
4 Understand That People Are Wired Very Differently
3.4 Triangulate your view with believable people who are willing to disagree.
3.4 Triangulate your view with believable people who are willing to disagree.
25:32 - We have no social constraints anymore
Technology has liberated us and there is nothing to constrain us, except our reflective ability. We are wired for accumulation. Americans are, on average shorter than they were two decades ago, and this is a reflection of poorer health.
Gandhi once said, “Anything that exists is possible.
We can also say that any human being is a also a possible reflection of our own intrinsic human nature that each of us posesses..
Each of the currently 7.8 billion people on the planet are a combination of nature and nurture. 7.8 billion different genetic expressions of the human genome and 7.8 billion different and unique environmental conditions operating on that unique expression create 7.8 billion unique forks of the human template. One fork results in a Saint, another in a ruthless warlord. Both are reflections of what is possible when unique environments interact with our basic human nature.
No option is perfect here, but a warning seems like a decent compromise unless there's a whole bunch of other plugins that break
Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.
Hands can be a prompt, a window, a way station—butwhat they ought never have to be is still.
Missing reference in this chapter on encouraging gestures as a tool for thought: "idle hands are the devil's workshop".
Could the Bible have been encouraging the use of one's hands for communication??
https://en.wiktionary.org/wiki/idle_hands_are_the_devil%27s_workshop
Proverbs 16:27 "Scoundrels concoct evil, and their speech is like a scorching fire." (Oxford, NSRV, 5th Edition) is translated in the King James version as "An ungodly man diggeth up evil: and in his lips there is as a burning fire." The Living Bible (1971) translates this section as "Idle hands are the devil’s workshop; idle lips are his mouthpiece."
The verse may have inspired St. Jerome to write "fac et aliquid operis, ut semper te diabolus inveniat occupatum" (translation: "engage in some occupation, so that the devil may always find you busy.”) This was repeated in The Canterbury Tales which may have increased its popularity.
such as installing permanent lighting
Remember, bad guys are vampires. They melt with sufficient lighting.
Plenty of campus crime happens during the day, when there is plenty of lighting.
I just thought that if there was any time to improve the naming it would be now, before rolling it out to thousands of devs/projects. I don't think of that as bikeshedding, personally.
Comments are turned off.
I'd like to ask everyone to watch this 19 second long "public meeting" with comments disabled so you can see what a joke Government is.
If you agree, please re-share. If you disagree, please explain how you think this could possibly be legitimate in the comments.
underscores are better than dashes for representing spaces
today I'm here to describe that everything really is connected, 00:02:02 and not in some abstract, esoteric way but in a very concrete, direct, understandable way. And I am going to do that with three different stories: a story of the heart, a story of the breath, and a story of the mind.
These three are excellent candidates for multimedia Stop Reset Go (SRG) Deep Humanity (DH) BEing Journey.
It is relevant to introduce another concept that provides insights into another aspect required for engaging a non-scientific audience, and that is language.
The audience is important! BEing Journeys must take that into consideration. We can bias the presentation by implicit assumptions. How can we take those implicit assumptions into consideration and thereby expand the audience?
For a non-scientific audience, these arguments may not be so compelling. In this case, it is important to demonstrate how science can lead us to make such astounding predictions of times and space not directly observable to normative human perception.
Okay thank you. I'll need to do some thinking then on how to apply that to things like git config --global core.editor
It is initiated when bargaining is done between the parties, i.e employers and employees
From paper to block and ink we are now learning about the printing press. The best invention at the time because you can create a news paper. And now printers are becoming obsolete and so is the news paper now a news paper is on line.
Employees were ‘free’ to negotiate a work contract to their liking within the context of accepting the ‘prerogatives’ of managers to organised and remunerate their efforts as they saw fit (Fox, 1974).
DIRECTORY (in progress): This post is my directory. This post will be tagged with all tags I ever use (in chronological order). It allows people to see all my tags, not just the top 50. Additionally, this allows me to keep track. I plan on sorting tags in categories in reply to this comment.
External links:
Tags categories will be posted in comments of this post.
hold four hours a week on set days and times; M 11:15AM-12:15PM (in-person & on-line) T 10AM-11AM (on-line)W 2:15PM-3:15PM (in-person & on-line)Th 1PM-2PM (on-line) and by appointment
If you forget to define x in the object you pass as the second argument, or if there's some similar bug or confusion, you won't get an error -- just unexpected results.
Aaron linkt in zijn blogpost aan meer bronnen die ik zeker eens verder wil onderzoeken voor mijn eigen Frankopedia.
I love that Frank calls his personal wiki / digital garden / online commonplace book "Frankopedia".
I should come up with a more clever name for mine.
Sanity check = Does this even make sense? For example, if your application only outputs integers, sqrt(-1) and log(-1) are undefined.
Sending body/payload in a GET request may cause some existing implementations to reject the request — while not prohibited by the specification, the semantics are undefined. It is better to just avoid sending payloads in GET requests.
However, this request-by-request mindset doesn’t map well to GraphQL because there’s only one controller and the requests that come to it may be very different.
Whether you agree or not, to me there's nothing in this world that is entirely apolitical - when there are people there is politics. You don't have to agree with my views, nor do I expect you to. Diversity and disagreement is what drives mankind forward.
We’ve enabled deprecation warnings by default when running specs. Making these warnings more visible to developers helps upgrading to newer Ruby versions.
DigiNotar was a Dutch certificate authority owned by VASCO Data Security International, Inc.[1][2] On September 3, 2011, after it had become clear that a security breach had resulted in the fraudulent issuing of certificates, the Dutch government took over operational management of DigiNotar's systems.[3]
Dutch Certificate Authority gets hacked.
wanted to surface to the user during SSR if the client-side call would likely fail due to cross-origin fetching, credentials, etc.
First of all, I would start off presenting yourself: Dear XYZ support team I am the web developer in charge of example.com website. By presenting you this way, you are establishing the frame to treat you, hinting that you should be presupposed to be somewhat proficient, so they could choose to answer in a more technical detail.
Feel free to hint, brag, or both! The best CS reps should easily take a hint from clear language and a signature like John Appleseed, JavaScript/Ruby Developer, but any will catch on with a simple line like "I know what I'm doing, so I'd appreciate an extra-technical explanation!"
Hey, I'm a PhD in [field] and do [whatever] professionally. Before calling you, I've narrowed down the problem to [something on their end], so that's what needs to be addressed. If I could speak to an engineer about [specific problem], that'd be great; but if we've gotta walk through the script, let's just knock it out quickly. If they end up requiring the script, then the best way to use your expertise is to run through it quickly. Keep the chit-chat to a minimum and just do the stuff efficiently. If they start describing how to perform some step, you might interrupt them with, "Got it, just a sec.", then let them know once you're ready for the next step.
However, what speaks against just straight up telling them that you're working as [Insert title of your position] and you know what you're talking about?
OP is referring to letting people know they can speak like proper adults when talking about technical terms, without going through the usual nanny-like discourse that tech support has to provide to non-techies. For instance, it happened to me with Amazon support. The speaker told me exactly where to touch in order to clear the cache of the Android Amazon App Store. Given that I work as an app developer the guy could have just said "please clear the cache". No need to go through "tap here, then here, now you should see this, tap that"...
I have tried different tactics of showing the tech support that I am proficient in their field of work (I work as a web developer). Specifically: using accurate terms and technologies to show my knowledge of them and telling the support that I am the "administrator" of the website in question.
How to let tech support subtly know that I am proficient without showing off?
I would argue though that crashing is better than quietly providing unexpected behavior.
We’re the ones who code. The people you talk to are the people who work on your project. When you have a question, we know what we are talking about.
Mentioned here:
but I can't find it on my system
The privacy policy — unlocking the door to your profile information, geodata, camera, and in some cases emails — is so disturbing that it has set off alarms even in the tech world.
This Intercept article covers some of the specific privacy policy concerns Barron hints at here. The discussion of one of the core patents underlying the game, which is described as a “System and Method for Transporting Virtual Objects in a Parallel Reality Game" is particularly interesting. Essentially, this system generates revenue for the company (in this case Niantic and Google) through the gamified collection of data on the real world - that selfie you took with squirtle is starting to feel a little bit less innocent in retrospect...
Yelp, like Google, makes money by collecting consumer data and reselling it to advertisers.
This sentence reminded me of our "privacy checkup" activity from week 7 and has made me want to go and review the terms of service for some of the companies featured in this article- I don't use yelp, but Venmo and Lyft are definitely keeping track of some of my data.
The good news: everyone had a genuine blast. We knew we had experimented our way into something fun, even if the rules and designs still needed a lot of work.
Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.
click the images below
why not make this a link too?
Software that is not currently being used gradually becomes unusable as the remainder of the application changes.
Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.
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.
I don't even know how to tell if they're working 100%, I'm getting mixed signals ..
Should it only contain link* calls?
When should I use link, vs dir, vs. tree?
but I still have no idea if I'm writing this new file correctly.
If you plan on using a gamepad with big picture mode I made a config that works perfectly so check it out.
Yes, but honestly, and no offense intended, but I don't see the harm in these type questions, nor why some people are offended when they are asked. If I owed a website, I wouldn't mind it because it just creates more pages that can be indexed. I see it as helping the website. But, I did look and didn't see a simple answer. Again, no offense is intended. I've just never understood the complaints.
Almet ji dafa tooy.
Les allumettes sont mouillées.
almet ji -- (French) matches.
ji -- the (indicates nearness).
dafa -- are (?).
tooy v. -- to be/get wet, humid, to be soaked; be fresh, be green.
Here's the last issue where source maps were discussed before the beta release.
Literally, everything in this example can go wrong. Here’s an incomplete list of all possible errors that might occur: Your network might be down, so request won’t happen at all The server might be down The server might be too busy and you will face a timeout The server might require an authentication API endpoint might not exist The user might not exist You might not have enough permissions to view it The server might fail with an internal error while processing your request The server might return an invalid or corrupted response The server might return invalid json, so the parsing will fail And the list goes on and on! There are so maybe potential problems with these three lines of code, that it is easier to say that it only accidentally works. And normally it fails with the exception.
exceptions are not exceptional, they represent expectable problems
Exceptions are not exceptional
I work with crazy geniuses who share many of my opinions (not all, and that’s good).
There is nothing wrong with building your own “service layer”, and many companies have left the Traiblazer track in the past years due to problems they had and that we think we now fixed.
Can't have a steam library without MMX.
I feel like I should've paid more for this masterpiece.
This article explains why you shouldn't use getters and setters (and when you can use them) and suggests a design methodology that will help you break out of the getter/setter mentality.
Unlike naming children, coding involves naming things on a daily basis. When you write code, naming things isn’t just hard, it’s a relentless demand for creativity. Fortunately, programmers are creative people.
Scalability is the problem you want to have, and sooner rather than later, but maintainability is the problem you’re definitely going to have, sooner or later.
cultural capital
Introduced by Pierre Bourdieu in the 1970s, the concept has been utilized across a wide spectrum of contemporary sociological research. Cultural capital refers to ‘knowledge’ or ‘skills’ in the broadest sense. Thus, on the production side, cultural capital consists of knowledge about comportment (e.g., what are considered to be the right kinds of professional dress and attitude) and knowledge associated with educational achievement (e.g., rhetorical ability). On the consumption side, cultural capital consists of capacities for discernment or ‘taste’, e.g., the ability to appreciate fine art or fine wine—here, in other words, cultural capital refers to ‘social status acquired through the ability to make cultural distinctions,’ to the ability to recognize and discriminate between the often-subtle categories and signifiers of a highly articulated cultural code. I'm quoting here from (and also heavily paraphrasing) Scott Lash, ‘Pierre Bourdieu: Cultural Economy and Social Change’, in this reader.
The code is far simpler and easier to understand/verify
while Fascism died in 1945 with the collapse of the Axis powers
I would (not) like to introduce you to Francisco Franco and Spain until the 1970s.
that first began in the United States
Oh. Hell. No.
Aside from the British example above, the authors seem to have forgotten that "movements to abolish slavery" included movements not run by White abolitionists, such as rebellions by enslaved people. One modest example roughly contemporaneous with the creation of the Bill of Rights: the Haitian Revolution. Or if you're hung up on White people abolitionists, Bartolome de las Casas (late in life). Who the hell even thinks the US invented abolitionism? WTF?
But the people do not directly exercise their sovereignty, for instance, by voting directly in popular assemblies.
False. In New England states, they actually do. And there's this little thing called the referendum...
(Y'know, it's not like they're wrong about representative institutions. It's that they insist on putting in stupid false shit when they didn't even need to.)
The first was the sundering of civil from religious law with the advent and widespread adoption of Christianity.
WHAT THE EVERLOVING FUUUUUCK??
HAHAHAHAHHAHAHAHAHAHA Hang on I gotta roll on the floor for a minute HAHAHAHAHAHAHAHAHAHA
Ahem.
MAY I INTRODUCE TO YOU CHRISTIAN MONASTICISM? THE HOLY ROMAN EMPIRE? EMPEROR CONSTANTINE? THE POPE? ALL THE POPES? INCLUDING THE TIME THERE WERE TWO POPES?
The sundering of--
Children. Sit down and let the adults do history.
Needless to say:
to write the document which we have today.
Incorrect. They came up with what we have today minus twenty-seven important bits of it that comprise most of what the United States has spent the last 240 or whatever years fighting over. The Bill of Rights--the "but mah freedoms" part of the Constitution--didn't come along for four more years.
The second momentous change was the emergence of multiple denominations within Christianity that undid Christian unity and in turn greatly undermined political unity.
OK wait. So...civil law was sundered from religious law because of Christianity in the last sentence, but in this sentence, schisms in Christianity (which, remember, had sundered political and religious law) undermined political unity?
(I mean, there were a lot of wars because of the various reformations and counter-reformations, but
Look, it's like somebody thinks the multi-national, polyglot monastery in The Name of the Rose was representative of pre-Reformation Europe and forgot that The Name of the Rose is a murder mystery.
(They didn't think that. These people wouldn't make it ten pages in anything by Eco. Bear with my nerd analogies.)
👍 Upvote issue #204 if you want to see it land faster.
If you’re not a huge fan of Snap packages, but love using Ubuntu, this guide is for you. In it, we’ll go over how you can remove Snap from your Ubuntu system and make it so that your system will no longer have access to the Snap store or anything like that.
Snap packages are quickly becoming the primary way that Ubuntu users consume software. Despite Snaps dominating Ubuntu, many users still opt to avoid Snap packages in favor of Apt packages that have long been available in Ubuntu.
Get told in big red letters when the dependency changed and you need to check that your fix is still valid.
With some frameworks, you may find your needs at odds with the enterprise-level goals of a megacorp owner, and you may both benefit and sometimes suffer from their web-scale engineering. Svelte’s future does not depend on the continued delivery of business value to one company, and its direction is shaped in public by volunteers.
The Jamstack removes multiple moving parts and systems from the hosting infrastructure resulting in fewer servers and systems to harden against attack.
Better contribution workflow: We will be using GitHub’s contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
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.
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).
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.
It is open to the community to help set its direction.
In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
For both the tailor-customer and doctor-patient examples, personal data is an input used to improve an output (dress, suit, medical treatment) such that the improvement directly serves the interests of the person whose information is being used.
This reminds me of "Products are functions" where your personal data is a variable than enters into the function to determine the output.
Obviously we shouldn't rush into anything. But changes like these are best made earlier on in a project's lifecycle, so I'm eager to hear what people think so that we can start making some progress.
You can determine which openssl.cnf is being used by adding a spurious XXX to the file and see if openssl chokes.
`Module ${a.id} may be unable to evaluate without ${b.id}, but is included first due to a cyclical dependency. Consider swapping the import statements in ${parent} to ensure correct ordering`
Svelte forces you do to do all kinds of things in a very specific way (as does every other framework/library), those constraints generally make for a better experience.
hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.
Svelte doesn't re-render, so you need to respond to component mount/dismount and prop changes separately as they are distinct concepts and never tied together, unlike in React.
Sometimes, you may be tempted to write that wrapper. Because all your (React or Vue or insert your reactive framework here) instincts tell you so.Resist the temptation. There is a better way. A svelter way. Introducing: the use-directive (a.k.a. “actions”).
However, especially when starting out, it’s very easy to fall into the “this is how I did things in my previous framework” trap.
So while Solid's JSX and might resemble React it by no means works like React and there should be no illusions that a JSX library will just work with Solid. Afterall, there are no JSX libraries, as they all work without JSX, only HyperScript or React ones.
Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.
Not an actual fix.
The node-resolve plugin doesn't like failing to resolve module IDs (because it usually indicates a bug, like you forgot to install the package in question), so it will throw an error rather than letting Rollup print a warning.
using modulesOnly behaves exactly as expected when it warns you that the listed npm libraries do not use the ES6 format and are in fact ignored. This option is meant as a way to determine if you still have commonjs libraries in your dependencies that require special treatment via rollup-plugin-commonjs. Your code will probably not work since the listed dependencies will be missing. You should remove modulesOnly and instead add rollup-plugin-commonjs.
User experience above all
balancing developer and user experience
You oftentimes see packages list react as a peer dependency. Since this prevents react from being installed into that package's node_modules, this is another way of preventing Rollup from bundling the module. This is also nice _if_ you want the application to install react from npm, because if an application forgets to install a peer dependency, npm will issue a warning.
But library users are more numerous, and so their needs are more important.
When the message say function was called outside component initialization first will look at my code and last at my configuration.
i feel it should get a runtime warning / error, if it returns something besides function or undefined.
There is a good amount of properties that should mostly be applied from a parent's point of view. We're talking stuff like grid-area in grid layouts, margin and flex in flex layouts. Even properties like position and and the top/right/left/bottom following it in some cases.
The main reason using classes isn't a great solution is that it completely breaks encapsulation in a confusing way, the paren't shouldn't be dictating anything, the component itself should. The parent can pass things and the child can choose to use them or not but that is different: control is still in the hands of the component itself, not an arbitrary parent.
The RFC is more appropriate because it does not allow a parent to abritrarily control anything below it, that responsibility still relies on the component itself. Just because people have been passing classes round and overriding child styles for years doesn't mean it is a good choice and isn't something we wnat to encourage.
Ideally: Only let a parent control those specific CSS properties, and never let a child use them on the root element.
margin, flex, position, left, right, top, bottom, width, height, align-self, justify-self among other is CSS properties that should never be modified by the child itself. The parent should always have control of those properties, which is the whole reason I'm asking for this.
new style RFC
https://github.com/sveltejs/rfcs/blob/style-properties/text/0000-style-properties.md
the notion that any given component should be in charge of its own thing, and not do something outside of itself. I.e., loosely coupled components in a sandbox, not tightly coupled to something outside of its own scope.
when choosing community building activities that ask students to disclose information about themselves, and especially about how they are feeling, it is important to recognise the risk of unintended harm.
Most faculty in a teaching setting chooses to do certain activities that can make a student very uncomfortable. In high school my teachers would do "icebreakers" and I would hate them because that meant I would have to talk in front of people and sometimes the topic would be a little too personal.
In a similar vein to (#33), it is arguably just something that compensates for the lack of power in the template language relative to JavaScript.
The complaint is that by choosing less powerful languages, template-based frameworks are then forced to reintroduce uncanny-valley versions of those constructs in order to add back in missing functionality, thereby increasing the mount of stuff people have to learn.
Personally, I think class is too blunt an instrument — it breaks encapsulation, allowing component consumers to change styles that they probably shouldn't, while also denying them a predictable interface for targeting individual styles, or setting theme properties globally
...but ultimately the component itself has control over what is exposed, and can specify its own fallback values using normal CSS custom property syntax:
A component should be in complete control of itself. Not only should a component's styles not leak out but other component's style should never leak in. Consider this 'Encapsulation part 2' if you will. When writing a component, you have certain guarantees that not only will the styles you write be contained within the component, but nothing from the outside should affect you either. You have a certain confidence that if it works in isolation, then it will continue to work when embedded within a complex application.
By adding constraints, we have managed to create a simple API and a performant output.
Instead, my purpose is to illustrate why an alternative approach — based on Single File Components with real CSS — is so damn delightful.
I think this is such a fantastic viewpoint. Sometimes in order to reach our overall goal, we have to "cast down our bucket" in compromise or be the first to extend the olive branch. I like that he used this same analogy for the white southerners as well. We all have to compromise to some degree to reach progress.
JavaScript for impatient programmers
Designing with constraints. Using inline styles, every value is a magic number. With utilities, you're choosing styles from a predefined design system, which makes it much easier to build visually consistent UIs.
First, let's make it clear that NODE_ENV has no explicit relationship to RAILS_ENV. Setting one of the ENV variables will have no effect on the other.
You must opt in to continue. If you're not paying, you're the product.
It’s an established fact that most people don’t really read the content of a website – they scan it
“The alarming truth,” warned the researcher, “is that the average number of permissions requested by a flashlight app is 25.”
“Asking for too many permissions is dangerous,” ESET malware researcher Lukas Stefanko explains. “These permissions can be misused as an exploit to access more device components, such as call logs, phone numbers, and browsing history.”
At the heart of Google’s challenge has been so-called permission abuse—millions of apps requesting the rights to access device data and functions beyond those needed to deliver their own functionality.
The security feature in Android 11 is a long overdue crackdown on this permission abuse.
Google’s novel response has been to compare each app to its peers, identifying those that seem to be asking for more than they should, and alerting developers when that’s the case. In its update today, Google says “we aim to help developers boost the trust of their users—we surface a message to developers when we think their app is asking for a permission that is likely unnecessary.”
Requested Dormant Username Enter the username you would like to request, without the preceding URL (e.g., "User" instead of "gitlab.com/User")
Problem Type: Dormant Username Requests
The GitLab.com support team does offer support for: Account specific issues (unable to log in, GDPR, etc.) Broken features/states for specific users or repositories Issues with GitLab.com availability
Out of Scope The following details what is outside of the scope of support for self-managed instances with a license.
For general questions, use cases, or anything else that does not fit into one of the above cases, please post in the GitLab Forum or on a third-party help site.
Some conventions reverse the order of priorities, considering lower values to be higher priority
Having said all that, I think this is completely absurd that I have to write an entire article justifying the release of this data out of fear of prosecution or legal harassment. I had wanted to write an article about the data itself but I will have to do that later because I had to write this lame thing trying to convince the FBI not to raid me.
I could have released this data anonymously like everyone else does but why should I have to? I clearly have no criminal intent here. It is beyond all reason that any researcher, student, or journalist have to be afraid of law enforcement agencies that are supposed to be protecting us instead of trying to find ways to use the laws against us.
User subjects and data objects are treated as programmable matter, which is to say extractable matter.
yes.
It doesn’t.What it does do is teach AI to recognize various things and fool you into thinking you’re getting better security.When you get something for free, you are the product.
For mainly two reasons: I pay for things that bring value to my life, and when something's "free", you're usually really just giving away your privacy without being aware.