An attitude (or opinion) is a specific preference on a particular issue. An individual may have an attitude toward American policy in the Middle East or an opinion about economic inequality in America. The attitude or opinion may have emerged from a broad belief about the purpose of military intervention or about the role of government in the economy, but the opinion itself is very specific. Some attitudes may be short-lived, and can change based on changing circumstances or new information.

One federal judge in the Northern District of Texas issued a standing order in late May after Schwartz’s situation was in headlines that anyone appearing before the court must either attest that “no portion of any filing will be drafted by generative artificial intelligence” or flag any language that was drafted by AI to be checked for accuracy. He wrote that while these “platforms are incredibly powerful and have many uses in the law,” briefings are not one of them as the platforms are “prone to hallucinations and bias” in their current states.

the AST version of the code is vastly superior IMHO. The knowledge about what constitutes an access modifier is already encoded in the system so it makes more sense to just call the method to test the type of node. The regexp solution may be expedient, but it's not as resilient to change -- if new access modifiers are added in the future it's very likely this code won't be updated, which will be the source of a bug.

The justices held their final arguments of the current term on Wednesday. The court has set a series of sessions over the next two months to release rulings in its still-unresolved cases, including the Mississippi abortion case.

This proposal is deeply flawed and would have far-reaching consequences if implemented. In #31148 I proposed a strategy to address the same pain points in a correct, more generic way. Regardless of whether my approach is taken or not, async handling of promises is a core feature that simply cannot be deprecated, and we should remove the erroneous deprecation accordingly.

igarett

Someone could mean to say different thing by each of them, but there's hardly any common agreement.

[gripe]Email is supposed to be a text-only medium. I can concede a need for rich text - the occasional bold or italic - but background pictures are just needless bloat.[/gripe]

Why are there so many programming languages and frameworks? Everyone has their own opinion on how something should be done. Some of these systems, like AOL, Yahoo, etc... have been around for a decade, and probably not updated much.

I don't believe the sprockets and sprockets-rails maintainers (actually it's up to the Rails maintainers, see rails/rails#28430) currently consider it broken. (I am not a committer/maintainer on any of those projects). So there is no point in "waiting for someone else to fix" it; that is not going to happen (unless you can change their minds). You just need to figure out the right way to use sprockets 4 with rails as it is.

I strongly prefer this over Carcassonne. It plays faster (I don't want a tile laying game to go for more than 30 mins or so) and I happen to like the limited options. Carcassonne just gets on my nerves because I just don't view selecting between so many placement options to be that interesting. Obviously, YMMV. Ditto the previous statement, it's different than Carcassonne. And that's why I like it.

I would be really proud to show it off it was "my baby", but as a player, it's incredibly boring.

I must say I am quite surprised by so many negative reviews. To me this little game is pure genius. There's something about it you just can't put your finger on... something strange, hard to define. The premise is utterly simple - roll left or right - but the game keeps adding new possibilities every level. And it doesn't make a fuzz about it. "Here's something completely new, it's there, who cares". The mechanics and physics are spot on and the game explores them brilliantly. Visually it's beautiful and the characters you interact with are strange and fascinating. A feeling of novelty and discovery permeates the game from start to finish.Here's my suggestion: watch some videos of the gameplay and see if it bothers you. If not, go for it, for you've barely seen the tip of the iceberg.

This is gonna be an uphill slog and I'm really excited for it. If you know that's what you're getting into (a long slow grind on puzzles that may not fit well together), this could be great - especially if you're invested in both the work and the community (posting on here helps loads with games like this!) Your mileage may vary!

As to why both is_a? and kind_of? exist: I suppose it's part of Ruby's design philosophy. Python would say there should only be one way to do something; Ruby often has synonymous methods so you can use the one that sounds better. It's a matter of preference.

Of course how each developer interprets and applies these very generalized guidelines is subjective and will vary from person to person.

Again, this is all opinion-based, and due to the sheer number of developers who rely on this technology as their bread and butter, sub-communities and religiousness forms around patterns, anti-patterns, practices, de-facto standards, micro-packages, polyfills, frameworks, build-tools, etc.

For instance, those who prefer classical inheritance may enjoy the addition of the class keyword, while others may reject it as conflicting with the idea of a prototypical inheritance model.

JavaScript, as a language, has some fundamental shortcomings — I think the majority of us agree on that much. But everyone has a different opinion on what precisely the shortcomings are.

When Sprockets was introduced, one of the opinions that it held strongly, is that assets such as CSS and JS should be bundled together and served in one file.

About auto-close bots... I can appreciate the need for issue grooming, but surely there must a better way about it than letting an issue or PR's fate be semi-permanently decided and auto-closed by an unknowing bot. Should I be periodically pushing up no-op commits or adding useless "bump" comments in order to keep that from happening? I know the maintainers are busy people, and that it can take a long time to work through and review 100s of open issues and PRs, so out of respect to them, I was just taking a "be patient; they'll get to it when they get to it" approach. Sometimes an issue is not so much "stale" as it is unnoticed, forgotten about, or consciously deferred for later. So if anything, after a certain length of time, if a maintainer still hasn't reviewed/merged/accepted/rejected a pull request, then perhaps it should instead be auto-bumped, put on top of the queue, to remind them that they (preferably a human) still need to review it and make a decision about its fate... :)

arranging his opinion

bad

I have a few colleagues that converted to hyperscript, and while they were adverse at first, they were satisfied with having switched once they had become comfortable with the way it looks/reads.

However, especially when starting out, it’s very easy to fall into the “this is how I did things in my previous framework” trap.

It's hard to fight against a tide of "experts" and preset assumptions. Sometimes it does take tearing things down a little bit.

The pattern was amazing but realistically I felt no one would really get over their preconceptions here.

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

I found that many people have bad experience when it comes to styling in Material-UI, so I want to help them overcome that point and see the beauty of it.

Pro tip: Just use standard and move on. There are actual real problems that you could spend your time solving!

Don't use it! Writing simple assertions (and Minitest way of transforming them to expectations) is almost always a better idea anyway. Work with your favourite library authors to start with assertions and add matchers for convenience and not the other way around. Keep it simple.

Q. Why does Rubinius not support frozen and tainted? A. Rubinius has better features; frozen and tainted are considered harmful. To elaborate... Both frozen and tainted depend on strewing checks throughout the source code. As a classic weak-link system, only one of those checks needs to be misplaced for the guarantees offered by either to fail. Since the number of checks is high, and as new code is written new checks need to be considered, the features inherently constitute unbounded complexity and unbounded risk.

A president with credibility

Such verbose. Much code. Very bloat. Wow. We've lost all the awesome association introspection that ActiveRecord would otherwise have given us.

Flatpak is the best application distribution mechanism for Linux.

World Health Organization Officially Declares Bacon is as Harmful as Cigarettes

When he read the Web address, http://pubweb.northwestern.edu/~abutz/di/intro.html, he assumed that the domain name “northwestern.edu” automatically meant it was a credible source. He did not understand that the “~” character, inserted after the domain name, should be read as a personal Web page and not an official document of the university.

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.