Nothing wrong with it, it’s just boring. Fish shell has some new features that make it nice to use. So does zsh. Tab completions, history navigation, plugins and such.
Haven’t been much of a cook in a while, but for some reason the part of my brain that recalls these things really wants me to suggest using a pressure cooker for beans. I honestly don’t know if that’s a good idea. I apologize for this information.
I’d rather have an explicit time zone any time a datetime is being passed around code as a string. Communicating it to a human is relatively safe since even if there’s a mistake, it’s directly visible. Before that last step, incorrect time zone parsing or implicit time zone assumptions in code that was written by “who knows” in the year “who knows” can be really annoying.
Thanks for the link. Reading it gave me a headache. Not because of the proposal, but because of the very clear explanation it includes of just how annoying time zones are. I never even thought about the fact that a time relative to a UTC timestamp isn’t uniquely associated with another UTC timestamp because the local UTC offset can change. It’s obvious when you say it, but now I’m wondering if I have more time zone bugs somewhere.
It’s not ambiguous, it’s just that correctly parsing the expression requires more precise application of the order of operations than is typical. It’s unclear, sure. Implicit multiplication having higher precedence is intuitive, sure, but not part of the standard as-written order of operations.
My opinion hasn’t changed. The standard order of operations is as well defined as a notational convention can be. It’s not necessarily followed strictly in practice, but it’s easier to view such examples as normal deviation from the rules instead of an implicit disagreement about the rules themselves. For example, I know how to “properly” capitalize my sentences too, and I intentionally do it “wrong” all the time. To an outsider claiming my capitalization is incorrect, I don’t say “I am using a different standard,” I just say “Yes, I know, I don’t care.” This is simpler because it accepts the common knowledge of the “normal” rules and communicates a specific intent to deviate. The alternative is to try to invent a new set of ad hoc rules that justify my side, and explain why these rules are equally valid to the ones we both know and understand.
There aren’t two different sets of rules. There’s the simple model that’s commonly understood and taught to kids, and there’s the real world where you have context and the dynamics of a conversation and years of experience with communication. One is well defined, the other isn’t.
Them asking me to solve the arithmetic problem is condescending, yes.
My response didn’t say “anyone who disagrees with the convention is stupid.” Here’s condescension for you: please don’t make your reading level my problem. What I said was, there’s an unambiguous way to parse the expression according to the commonly understood order of operations, but it is atypical to pay that much attention to the order of operations in practice. If you think that’s a value judgment, that’s on you-- I was very clear in my example about capitalization, “strictly adhering to the conventional order of operations” is something reasonable people often just don’t care about.
Hi, expert here, calculators have nothing to do with it. There’s an agreed upon “Order of Operations” that we teach to kids, and there’s a mutual agreement that it’s only approximately correct. Calculators have to pick an explicit parsing algorithm, humans don’t have to and so they don’t. I don’t look to a dictionary to tell me what I mean when I speak to another human.
Calculators do not implement “what conventions are typically used in practice.” Entering symbols one by one into a calculator is a fundamentally different process from writing them in a sentence. A basic traditional calculator will evaluate each step as you enter it, so e.g. writing 1 + 2 * 3 will print 1, then 3, then 6. It only gets one digit at a time, so it has no choice. But also, this lends itself to iterative calculation, which is inherently ordered. People using calculators get used to this order of operations specifically while using calculators, and now even some of the fancy ones that evaluate expressions use it. Others switched to the conventional order of operations.
“Which ruleset do you consider correct” presupposes, as the comment said, that there are 2 rulesets. There aren’t. There’s the standard, well known, and simplified model which is taught to kids, and there’s the real world, where adults communicate by using context and shared understanding. Picking a side here makes no sense.
And that simple model, well-defined model didn’t properly account for juxtaposition, which is how different fields have ended up with two different ways of interpreting it, i.e. strong vs. weak juxtaposition.
No, that’s just not what happened. “Strong juxtaposition,” while well-defined, is a post-hoc rationalization. Meaning in particular that people who believe that this expression is best interpreted with “strong juxtaposition” don’t really believe in “strong juxtaposition” as a rule. What they really believe is that communication is subtle and context dependent, and the traditional order of operations is not comprehensive enough to describe how people really communicate. And that’s correct.
Considering your degree specialisation is in solving arithmetic problems
My degree specialization is in algebraic topology.
I don’t see the issue with them asking you to put your money where your mouth is and spit out a number if it’s so easy
The issue is that this question disregards and undermines my point and asks me to pick a side, arbitrarily, that (as I’ve already explained) I don’t actually believe in.
Ironic that you tell me to check my reading comprehension right after you misquote me, but nonetheless that is the impression your responses have given off - and you haven’t done anything so far to dispel that impression.
I didn’t misread, you’re in denial.
Yes, and the question everyone is asking you is what is that unambiguous way? Which side of weak or strong juxtaposition do you come out on?
Hopefully by this point in the comment you understand that I don’t believe the question makes sense.
The value judgement was actually more to do with your choice of example, and how you applied that example to this debate. It gave me the distinct impression that you view this debate as not worth having, as anybody who does juxtaposition differently from you is wrong out the gate - and again, your further responses only reinforce my impression of you.
Again, that’s your fault-- you’ve clearly misinterpreted what I said. If I didn’t think this conversation was worth having I wouldn’t be responding to you.
People ITT hating on null coalescing operators need to touch grass. Null coalescing and null conditional (string?.Trim()) are immensely useful and quite readable. One only has to be remotely conscious of edge cases where they can impair readability, which is true of every syntax feature
What is a computer but bits of metal, stone, and plastic upon which electrical impulses flip individual bits? What is a human brain but a bunch of goop doing the same thing? That’s the thing about emergent properties, they kind of emerge.
You don’t have to crack the philosophical nature of intelligence to create intelligence (assuming “create intelligence” is a thing, I guess). The inner workings of even the simplest current models are incomprehensible, but the process of creating them is not. Presupposing that there is a difference between “faking” intelligence and “true” intelligence, I think you’re right, but I dunno if that distinction is right.
I am personally unaware of any serious reason to believe that Firefox’s numbers will improve soon.
Either the author doesn’t know about the Manifest v2 deprecation or is saying it’s “unserious” to believe this might improve Firefox’s market share. Either way, goofy.
I don’t get what you mean. You can define class Pie and instantiate it with the type argument Pie.
Huh, maybe I don’t get it because Lemmy is literally erasing angle brackets from our messages. Not just “not rendering.” It’s removing them entirely. There should be four angle brackets in the first line of this comment…
Modern .NET is reducing dependence on reflection. System.Text.JSON and other core libraries have leveraged source generation to produce AOT + trim friendly, reflection free code. But yeah, it’s not a taboo like say dynamic, it’s perfectly normal to use reflection in idiomatic C# code.
Any old schmuck can make a structure with a 10x safety factor. The thing is making the safety factor as low as reasonably possible to minimize costs. If there’s a regulation that says 3x minimum, you’re probably aiming for 3x. Which is why those regulations are important, I guess.
Source: I write code for a living, don’t listen to anything I say
Careful analysis of the stress tensor of a simple geometric model with parameters given by empirical testing of simple materials can give you a reasonable ballpark estimate. I wouldn’t be the first one to drive on a ballpark estimate though.
502 Bad Gateway (jlai.lu)
What is your favourite Hex colour code? (kbin.social)
For example #bf00ff is a nice colour code. Also known as electric purple.
This thread is gold (mander.xyz)
Christine is an epic troll...
Bored With Bash? Change the Default Shell in Linux (itsfoss.com)
There's a difference (startrek.website)
Standards shouldn't be behind a paywall (lemmy.world)
ISO 8601 is paywalled...
6÷2(1+2) (programming.dev)
zeta.one/viral-math/...
don't. blink (lemmy.world)
Just get a bigger fence (startrek.website)
Developers blast the celeb-laden Game Awards as 'an embarrassing indictment of a segment of the industry desperate for validation… with little respect for the devs' (www.pcgamer.com)
know the features of your language (lemmy.world)
Whats your such opinion (discuss.tchncs.de)
Firefox is close to not beeing supported by US government's websites (www.brycewray.com)
Madoka Rule (i.imgur.com)
The cost of maintaining Xorg (mastodon.social)
With PieMixin (lemmy.world)
load limit rule (lemmy.blahaj.zone)
Google says you shouldn't worry about those bumps on your Pixel 8 Pro screen (www.androidauthority.com)
"Last Word" by J.L Westover (telegra.ph)
Source: Tapas(Secret Panel) - RSS
Rule (lemmy.blahaj.zone)
Every time (media.wetdry.world)
alt textwayward vagabond from homestuck: we should improve technology somewhat. well dweller: xkcd 927 “standards”