current system is ‘closed source’, and is carried out by competitive agents that do not share innovations for very long time periods; the competitiveness of these agents requires behaviors that externalize costs

these winds, right— these energies—are already flowing, of course, and they flow in very deep patterns that basically constitute one's own ordinary identity. And so quite literally one's own ordinary identity is, is the patterning of these winds.

I certainly think 00:05:50 it's our symbolic abilities that have gotten us here tremendous capacities

we're going to hit some very very hard limits to growth um and yet it's almost like we can't find the language for it

hat meet not match chapter is 00:50:10 a hard chapter

Confront inappropriate language. If a student makes an inappropriate comment—racist, sexist, or otherwise offensive—letting it go without intervention can seem like a tacit endorsement of those views. And whether the slight is intentional or not, the impact is the same. Letting such comments pass unchallenged can seriously harm students' trust in you and their sense of belonging in the class and the university. Have some responses ready for how you are going to address such comments, including

Avoid questions that seem like there is one right answer. In some cases, it works well to ask not for their own opinions, per se, but a sharing of what opinions they have heard about that topic; such an approach allows you to get the “lay of the land” without anyone feeling too exposed from the start.

sk students to complete an assignment in advance that helps them understand and articulate their own views, as well as others they have heard. Such pre-discussion homework can help them reflect on those views, understand potential reasons behind them, and connect them to disciplinary content in the course. Such activities let them do some more logical thinking in advance, before any emotional barriers get thrown up during a heated discussion.

In situations where you know you will be addressing a controversial topic, you can prepare for the discussion in ways that set the stage for success.

does your scholarship suggest why so many societies do that rather than 00:20:09 saying maybe we start with a Declaration of Human Rights today maybe we write a new one from scratch based on what we know today um because it's very difficult to reach an agreement between a lot of 00:20:21 people and also you know you need to base a a a a real Society is something something extremely complex which you need to base on empirical experience 00:20:34 every time that people try to create a completely new social order just by inventing some Theory it ends very badly you need on yes you do need the ability 00:20:46 to change things a long time but not too quickly and not everything at once so most of the time you have these founding principles and shr find in this 00:20:58 or that text also orally it doesn't have to be written down and at least good societies also have mechanisms to change it but you have to start from some kind 00:21:12 of of of of social consensus and some kind of of social experience if every year we try to invent everything from scratch then Society will just collapse

More welcoming migration policies require borders that are secureLet more people in legally, swiftly exclude those who come illegally

virtually every sentence of the critique 00:04:20 presents difficulties attempts have been made to provide commentaries comprehensively illuminating uh comprehensively illuminating each individual section of the work 00:04:33 and some of these run to several volumes without getting near its end and then one commentator com noting what it's like to read the critique of pure reason says it is quote 00:04:46 a disagreeable task because the work is dry obscure opposed to all ordinary notions and long-winded as well who said that 00:04:59 kant

The long-term consequences of Russia’s war are less clear. But experts are concerned it may also lock in more future fossil fuel dependence as places like Europe search for replacements for Russian fuel.

YAML parsing is normally considered hard (complicated as the syntax is complex). With all due respect, personally I can adhere to that in part, the YAML specification appears to be at (isolated) places hard to read despite me self-imagined being trained over decades into reading publicly available specifications (in not my first language). To be fair, it is one of the very few specs that has graphics and by the nature of its formulation, compilers are hard to read as well.

Since the replacement is the same for all errors this makes it impossible to recover the original character. A better (but harder to implement) design is to preserve the original bytes, including the error, and only convert to the replacement when displaying the text. This will allow the text editor to save the original byte sequence, while still showing the error indicator to the user.

// Native const datePattern = /^(\d{2})-(\d{2})-(\d{4})$/; const [, month, day, year] = datePattern.exec('12-25-1995'); new Date(`${month}, ${day} ${year}`);

Recently, Strong, concerned about press reports suggesting that he was “difficult,” sent me a text message saying, “I don’t particularly think ease or even accord are virtues in creative work, and sometimes there must even be room for necessary roughness, within the boundaries dictated by the work.”

Perhaps not a good idea, in general, to use a random PPA for such sprawling software as a browser. Auditability near zero even if it is open source.

Sigh why was such a standard feature like resizable columns that have been super simple to do in desktop apps for 15+ years not added to css3/html5

Today, Sass uses complex heuristics to figure out whether a / should be treated as division or a separator. Even then, as a separator it just produces an unquoted string that’s difficult to inspect from within Sass.

But more so, external style cannot be applied to a subsection of a web page unless they force it into an iframe, which has all sorts of issues of it's own which is why external CSS is usually ignored. Inline CSS is often stripped by the tag strippers who don't want you turning things on or off... and media queries shouldn't even play into it since the layout should be controlled by the page it's being shown inside (for webmail) or the client itself, NOT your mail.

Email is Hard: learn how MJML will help you.

Also cross-compatibility with mail clients can be hairy, so you should see what the industry experts are doing.

These are games that make arguments and encourage discussion. They don't shy away from difficult subjects.

When one is searching for it on the internet, there are many many people wondering how one can open .desktop files. It seems trivial, since one usually just has to click an item on the launcher so one thinks there must be some way.

But sometimes not even that helps; the onceability factor can, ultimately, trump the usefulness.

If you think that for every problem there is a simple and easy solution, either you don't understand what is a problem or you don't understand what is a solution.

For the $$$ question, nothing comes to mind. These problems i'm hitting up against are larger than a contractor could solve in a few hours of work (which would be hundreds/thousands of dollars).

Progress is slow though. I want to change how assets are loaded, the current implementation of "pipelines" is challenging to work with.

I'm not sure about all consequences of my change and this is very complex.

Validating forms has notoriously been a painful development experience. Implementing client side validation in a user friendly, developer friendly, and accessible way is hard. Before HTML5 there was no means of implementing validation natively; therefore, developers have resorted to a variety of JavaScript based solutions.

Redesigning the pieces was very difficult work, because traditional pieces have 4 specialties below.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

we also wrap them in Failure to solve the second problem: spotting potential exceptions is hard

It turns out that, given a set of constraints defining a particular problem, deriving an efficient algorithm to solve it is a very difficult problem in itself. This crucial step cannot yet be automated and still requires the insight of a human programmer.

The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.

The new call API is much more consistent and takes away another thing we kept explaining to new users - an indicator for a flawed API.

It is difficult to come up with content that is not extracted from a real application. Manufacturing scenarios to see if ideas have practical application turned out to be an exhasting and time consuming process.

I don't see a way to hook into Devise's route mapping load process to add the action (several monkey patching attempts failed)

violates our expectation that hard things should be technical

Anyone who has ever tried to name a child knows that naming is hard. Naming things in code is harder. It’s bad enough that you have to commit to a name that someone isn’t going to like. You also have to be able to live with it.

It's difficult because it's a case-by-case basis - there is no one right answer so it falls into subjective arguments.

the 2 hardest problems in computer science are essentially the 2 hardest problems of life in general, as far as humans and information are concerned.

If upstream code presumes things will work that dont in snap (e.g. accesses /tmp or /etc) the snap maintainer has to rewrite that code and maintain a fork. Pointless work. Packaging for .deb is a no-brainer.

I think you’re missing the spirit behind the classic “centering is hard” complaint in a couple of places, which, at least for me, always comes back to not knowing the height of the elements.

The CardLayout creates a store in context and the Card creates a standardized div container and registers it to the store so that the CardLayout has access to that DOM element. Then in afterUpdate you can move the DOM elements into columns and Svelte will not try to put them back where they go. It's a bit messy but it works.

They say that there are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors. Caching is what Service Workers do. It’s literally the #1 hard thing! … or maybe the #0 thing? Whatever. It’s hard.

I would love to see this features as well, since it makes component composition and reuse a lot easier.

It took us a long time for everyone to get on the same page about the requirements spanning frameworks, tooling and native implementations. Only after pushing in various concrete directions did we get a full understanding of the requirements which this proposal aims to meet.

// replace css-loader with typings-for-css-modules-loader environment.loaders.get('moduleSass').use = environment.loaders.get('moduleSass').use.map((u) => { if(u.loader == 'css-loader') { return { ...u, loader: 'typings-for-css-modules-loader' }; } else { return u; } });

In principle, this information is already available through other means, but it is actually a fair amount of work to gather it in this form, and I think it could be useful to open it up to programmatic consumption.

Focus on your application: forget about forms details like I'm dirty, field touched...

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

If you want to implement a form with a superb User Experience, you have to take care of many variables:

Form validation can get complex (synchronous validations, asynchronous validations, record validations, field validations, internationalization, schemas definitions...). To cope with these challenges we will leverage this into Fonk and Fonk Final Form adaptor for a React Final Form seamless integration.

Managing Form State (holding field information, check if a control has been touched, if the user has clicked the submit button, who owns the current focus...) can be tedious and prone to errors. We can get help from React Final Form to handle these challenges for us.

This does solve the problem, but now our project and API is structured differently. In large projects it might be very hard to determine how to pull this trick off, or even impossible!

One of Svelte's advantages, for me, is that I can test out ideas with relatively few lines of code. the #with feature could save me from adding a separate component for the content of an #each loop. I get frustrated when I have to create a new file, move the content of the #each clause, import it as a component, and add attributes and create exports for that, and implement events to send messages back, and event handlers, when I just wanted to test a small feature.

This is the problem with baking in support for frameworks with special cases in the codebase. You can never support all the frameworks. :-(

It adds a few constructs to the language to solve one of the most complex problems in UI development — state management.

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.

Very few were interested in furthering the platform in the places they just took for granted.

Svelte had painted this picturesque world for us all to live in but made it difficult to talk about the hard topics.

There are work arounds, but nothing clean. I just feel like this should be functionality that should be part of the slot feature.

I totally get not wanting to extend the syntax. I tried doing these things and in practice it was not easy or pretty. Actions provide a much cleaner and easier way to accomplish a certain set of functionality that would be much more difficult without it.

If this was tied into Svelte's flow with hooks this would not be necessary since it would know when it was being removed from the DOM.

You must: reference each element you are extending using refs or an id add code in your oncreate and ondestroy for each element you are extending, which could become quite a lot if you have a lot of elements needing extension (anchors, form inputs, etc.)

There are very few built-in UI controls in the browser, and those that do exist are very hard to style.

Modern view libraries like React allow teams to build and maintain these components more easily than ever before, but it is still extraordinarily difficult to do so in a fully accessible way with interactions that work across many types of devices.

6to5 attempted to ship a quick and dirty TDZ static checking feature but had to retract it immediately afterwards due to various bugs in the algorithm.

JSON parsing is always pain in ass. If the input is not as expected it throws an error and crashes what you are doing. You can use the following tiny function to safely parse your input. It always turns an object even if the input is not valid or is already an object which is better for most cases.

I agree in general splitting an array, according to some property using the order of the elements (no take_drop_while) or to some other array (this request) is more difficult than it could be.

When evaluating whether or not a legal basis can apply, please be sure to go through them with your lawyer as determining the correct legal basis is very important and can be difficult.

"You can try to make your own captcha. It is not so complicate." I hadn't read anything so wrong in a long time.

Testing is hard. For most developers, testing is a sad story.

During the recession everyone was trying to grab onto anything that would get them more business. Even small trucking companies were trying to get in on the action by saying they offered 3PL and 4PL services, but most were well out of their element.”

but they are not really in a neutral position.” For example, the consulting arm of such an organization would be hard pressed when making recommendations not to include their 3PL services as an option.

4PLs by definition must be non-asset based. She argues that many “wannabe” companies are hiding transportation assets somewhere under false advertising

Dialogue and Difference: Facilitating Difficult Dialogues in the Adult Learning Environment