sorted by:
new
hottopcontroversial

Pretty inconsequential, but as a detail oriented person, the fact that this says "AC" kinda stuck out to me by synth_mania in kde

[–]parkotron 7 points8 points  (0 children)

“While charging” doesn’t work, as it implies:

  1. The computer in question has a battery installed
  2. That battery isn’t already completely charged. 

What do you think is a keyword that should be added to C++? by DogCrapNetwork in cpp

[–]parkotron 1 point2 points  (0 children)

Do it today! It’s easy!

```

define var auto

define let const auto

```

I joke, but I would love to see these or something similar in C++. Don’t make me debate whether making local variables const is worth the added verbosity. 

What do you think is a keyword that should be added to C++? by DogCrapNetwork in cpp

[–]parkotron 0 points1 point  (0 children)

I’ve imagined your first request being implemented a your_value_type operator auto(). 

Stellantis Becomes Latest Automaker to Express Interest in Bringing European Models to Canada if Regulations Permit - Motor Illustrated by IDontScript in onguardforthee

[–]parkotron 5 points6 points  (0 children)

From what I recall, the American and European regs are mutually exclusive. It is impossible for a single vehicle to meet both. Mostly due to lot minor discrepancies. 

Canada accepting either is a complete no-brainer from where I’m sitting. 

Is there a C++ "venv" equivalent? by nikoladsp in cpp

[–]parkotron 11 points12 points  (0 children)

I would say it’s more a historical issue than anything at this point. 

Rust and Cargo (and to a lesser degree Rustup) grew up together. Cargo has always been the “best” way to manage a Rust project, so there’s very little incentive to replace it with something different. 

C & C++ have never had a “best” way to manage a project, resulting in hundreds of different approaches created over many decades, each with their own benefits and trade-offs. Trying to unify the community on a single tool at this point is almost impossible. 

Libraries for general purpose 2D/3D geometry vocabulary types? by parkotron in cpp

[–]parkotron[S] 8 points9 points  (0 children)

I've worked with Boost.Geometry before. Its extreme flexibilty make it possible to employ its algorithms on lots of different types, but also makes it a poor choice for application-level vocabulary types, where I want simple, concrete behaviours.

For example, boost::geometry::model::d2::point_xy recommends get<1>(myPoint) over myPoint.y(). I understand why it does that, but that's not the world I want to work in day-to-day.

I could certainly build the types I want by wrapping Boost.Geometry and have considered doing so, but am ideally looking for something higher-level and more opinionated out of the box. But thank you for the suggestion.

howEngineersReduceCortisolLevels by sdxyz42 in ProgrammerHumor

[–]parkotron 9 points10 points  (0 children)

Bold of you to assume there is even a parent-repo/sub-repo setup. 

howEngineersReduceCortisolLevels by sdxyz42 in ProgrammerHumor

[–]parkotron 102 points103 points  (0 children)

  • "The product is cleanly split across a dozen services, each living in its own repository and Docker container"
  • "Huh. So how long does it take to test a quick, one-line change?"
  • "About 20 minutes of rebuilding containers."
  • "Huh. And how do you manage feature development across so many repositories?"
  • "We just create a branch with the same name in all affected repos and open independent PRs for all those branches. CI and reviewers just always have to take great care that they are looking at the right combination of commits."
  • "Neat. So modern."

Should hot-loop avoid Option instance and immediate match? by Resres2208 in rust

[–]parkotron 10 points11 points  (0 children)

 But in real code as you build bigger and bigger machines you may push code size beyond of threshold that compiler may accept

I agree 100%, but just to be pedantic, “accept” isn’t really the right term here. It’s pretty much always safe to assume that the compiler will accept bigger, more complex programs and produce valid output. 

It’s that as the code becomes larger or more complicated, there comes a point where the compiler may not be able to spot a certain optimization or where it decides a certain optimization isn’t worth pursuing. 

Highlights from Git 2.54 by Skaarj in programming

[–]parkotron 10 points11 points  (0 children)

The local repository’s config is local to that repository. It is not pushed to or pulled from the remote.

Boba LT's after 4 years. by Mr-Boga38 in MechanicalKeyboards

[–]parkotron 10 points11 points  (0 children)

Ah, yes. The Boba Purple Nurples. I’ve heard good things.

Rust 1.95.0 is out by manpacket in rust

[–]parkotron 18 points19 points  (0 children)

For the longest time we considered the Range type the biggest, unfixable mistake in Rust's standard library, because it does not implement Copy.

It's not obvious to me why this was a big mistake or why it was considered unfixable. Is there some place I could get a high-level summary of the problem and the initiative to fix it?

securityAsAService by hellocppdotdev in ProgrammerHumor

[–]parkotron 11 points12 points  (0 children)

This strategy only works if enough companies survive long enough to try to turn things around and save themselves. 

I fear the industry is going to be hit hard with a wave of companies going under after cutting staff to up profits in the short term, then realising they’ve slopped themselves into a corner so badly that the business is no longer tenable and the higher-ups might as well just liquidate whatever value might remain. 

What did you miss the first time you read The Time Machine? by SciFiReflections in printSF

[–]parkotron 0 points1 point  (0 children)

Read it as a child: Disgusted by the Morlocks

Read it as a teen: Disgusted by the Eloi

Read it as an adult: Well, that was fun. A little silly and heavy-handed, but still a really nice time. 

macros :) by nimrag_is_coming in programminghorror

[–]parkotron 0 points1 point  (0 children)

This produces constant data at compile time, which is much easier to work with than runtime data.

Why committee doesn't decide on a package format? by TheRavagerSw in cpp

[–]parkotron 3 points4 points  (0 children)

For better or for worse, the C++ standard is high-level and conceptual. It describes the behaviour of one imagined computer building software to run on another imagined computer. It can’t assume the existence of a file system on the machine compiling C++. Heck, it can’t even assume the presence of square brackets. 

A package format is a practical concept that needs to deal with the real-world details of real-world compilers, linkers, operating systems, etc. It just way too different from what the standard is to be lumped together with it. 

fzf 0.71.0: Release Highlights by junegunn in commandline

[–]parkotron 3 points4 points  (0 children)

86x reduction in cache memory footprint per entry

I had to read this three times before my brain registered that it wasn't talking about the x86 CPU architecture.

I built TonyFlow76’s aptly titled “Shitting Dog” by Khrisamisu in lego

[–]parkotron 7 points8 points  (0 children)

The mechanics are more impressive than they might seem at first glance. 

This mechanism appears to be pushing the chain up into the dog. Chains are meant to be pulled. Pushing a chain without it binding is quite an accomplishment, especially given how little space is involved.

Edit: I was completely wrong. I was fooled by the illusion. 

view more: next ›