• 0 Posts
  • 89 Comments
Joined 11 months ago
cake
Cake day: August 2nd, 2023

help-circle




  • One important thing to realize is that different dialects of English have slightly different grammars.

    One place where different dialects differ is around negation. Some dialects, like Appalachian English or West Texas English, exhibit ‘negative concord’, where parts of a sentence must agree in negation. For example, “Nobody ain’t doin’ nothing’ wrong”.

    One of the most important thing to understanding a sentence is to figure out the dialect of its speaker. You’ll also notice that with sentences with ambiguous terminology like “he ate biscuits” - were they cookies, or something that looked like a scone? Rules are always contextual, based on the variety of the language being spoken.



  • No.

    There’s two types of grammar rules. There’s the real grammar rules, which you intuitively learn as a kid and don’t have to be explicitly taught.

    For example, any native English speaker can tell you that there’s something off about “the iron great purple old big ball” and that it should really be “the great big old purple iron ball”, even though many aren’t even aware that English has an adjective precedence rule.

    Then there’s the fake rules like “ain’t ain’t a real word”, ‘don’t split infinitives’ or “no double negatives”. Those ones are trumped up preferences, often with a classist or racist origin.




  • Yeah, projects also exist in the real world and practical considerations matter.

    The legacy C/C++ code base might slowly and strategically have components refactored into rust, or you might leave it.

    The C/C++ team might be interested in trying Rust, but have to code urgent projects in C/C++.

    In the same way that if you have a perfectly good felling axe and someone just invented the chain saw, you’re better off felling that tree with your axe than going into town, buying a chainsaw and figuring out how to use it. The axe isn’t really the right tool for the job anymore, but it still works.


  • Pipoca@lemmy.worldtoProgrammer Humor@lemmy.mlSTOP WRITING C
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    5 months ago

    C is not how a computer truly works.

    If you want to know how computers work, learn assembly and circuit design. You can learn C without ever thinking about registers, register allocation, the program counter, etc.

    Although you can learn assembly without ever learning about e.g. branch prediction. There’s tons of levels of abstraction in computers, and many of the lower level ones try to pretend you’ve still got a computer from the 80s even though CPUs are a lot more complex than they used to be.

    As an aside, I’ve anecdotally heard of some schools teaching Rust instead of C as a systems language in courses. Rust has a different model than C, but will still teach you about static memory vs the stack vs the heap, pointers, etc.

    Honestly, if I had to write some systems software, I’d be way more confident in any Rust code I wrote than C/C++ code. Nasal demons scare me.




  • Pipoca@lemmy.worldtoProgrammer Humor@lemmy.mlSTOP WRITING C
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    5 months ago

    Right tool for the job, sure, but that evolves over time.

    Like, years back carpenters didn’t have access to table saws that didn’t have safety features that prevent you from cutting off your fingers by stopping the blade as soon as it touches them. Now we do. Are old table saws still the “right tool for the job”, or are they just a dangerous version of a modern tool that results in needless accidents?

    Is C still the right tool for the job in places where Rust is a good option?



  • Pipoca@lemmy.worldtotumblr@lemmy.worldLiterally no one knows
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    6 months ago

    Why don’t meters go into light years or parsecs nicely?

    Anyways, an acre is the area people would plow by ox in one day. You measured fields by the acre because in a medieval society that said something really interesting about how many farm workers you needed for a given area.

    Similarly, a mile comes from the Latin for ‘thousand paces’, which is a fairly natural way for people on foot to measure distances.

    Much like how light year says something scientifically interesting about distances to stars so we use it instead of petameters or zettameters in astronomy, people used acres and miles despite them not going into feet well.

    It works because you generally don’t convert between light years and meters, or acres and feet. They mostly just exist at different scales.


  • Nope. The idea in no till is just adding stuff to the top and letting worms and roots handle the tilling.

    I’ve had good luck just dumping a foot or two of finished compost on the ground and growing in it.

    Another solid no-till approach is sheet mulching. You put down a layer of cardboard (to kill weeds), then layers of carbon and nitrogen like straw and kitchen scraps. Wait a few months, then plant. So you could do that in the late summer or fall to prepare a site for spring planting.

    A lot of these things depend on location, though. Something that works great in Pennsylvania might not work as well in Utah.



  • Colloquially, accidents are random events without intention or fault.

    That’s why there’s a push to use neutral terms like “crash” that don’t imply that the “accident” was just a random accidental mistake.

    And fault is often a bit of a misnomer. Many crashes are the result of bad design, but the courts would never say “this pedestrian fatality here is 40% the fault of whichever insane engineer put the library parking lot across a 4-lane road from the library but refused to put a crosswalk there or implement any sort of traffic calming because that would inconvenience drivers”.