https://opendatastructures.org/ods-cpp/10_1_Implicit_Binary_...

I dare say that no tree data structure beats Eytzinger's method in cache locality.

A command line interface (CLI), as the name implies, is a user interface pattern consisting of an application that you pass arguments to it through the command line to form a request/command to be executed by the application.

This type of user interface also covers features such as exit code and text input/output through standard streams as to allow programs to be compostable through pipes.

For example, '$ cp origin rest', '$ grep -Ri foo /opt | sort', etc.

A terminal user interface (TUI) is a type of user interface which uses a terminal's limited features to provide a windowed user interface that supports interactivity.

For example, see apps like vim, fdisk, etc.

https://en.wikipedia.org/wiki/Linear_multistep_method

Thanks for the suggestion. I'll definitely consider that trick with my upcoming setups.

That's not how reality works.

First, you magically turn "could" into "would".

Also, you also ignore the fact that "self-censoring" does not mean "I want to speak out but I can't". It means something as innocuous as not speaking out regarding topics that aren't related to their field of expertise and thus, as smart people do, they don't just blabber on about things that they don't have a solid and well-formed opinion and don't concern them.

Moreover, your percentages don't really add up, nor do you spend any moment considering why 98% (virtually all) claim to self-censor but a far lower number feels they need to put a focus on Israel. I mean what other topics do they consider worthy of self censoring? That would be helpful to gain insight on the phenomena, but it seems the goal was to shoehorn a prejudiced point.

Don't you agree that your comment sounds like a conspiracy theory to justify why your pet scapegoat isn't being attacked enough?

I'm not sure which article you read, but the one linked to in this discussion mentions:

* VMWare laying off 577 employees in Austin,

* startup founders, like Techstars Managing Director Amos Schwartzfarb, announcing their decisions to leave Austin,

* Meta dropping plans to move to Austin,

* Google freezing plans to move to Austin, in spite of already paying rent.

* TikTok not establishing plans to move to Austin in spite of already leasing office space,

* Don Ward, the CEO of Laundris, announced he would be relocating his company to Tulsa,

* Cart announced it was moving its headquarters out of Austin back to Houston, after spending little over 2 years.

The article is solid journalism. It's a summary of individual news pieces which is tied together by observations from leaders of established companies over their decisions and economic forecasts.

You don't know what was being done. All you know is that the manager took a peek at the PR and told the developer to revert the commit.

It's ok if you just call them Hamas.

Oppressing others is really not about options. It's one thing to live your life according to your own beliefs and principles, but it's an entirely different thing to feel entitled to selectively impose them onto everyone around you.

> U.S. deputy ambassador Robert Wood called the resolution “imbalanced” and criticized the council after the vote for its failure to condemn Hamas’ Oct. 7 attack on Israel in which the militants killed about 1,200 people, mostly civilians, or to acknowledge Israel’s right to defend itself. He declared that halting military action would allow Hamas to continue to rule Gaza and “only plant the seeds for the next war.”

It boggles the mind how these declarations pin the issue as Israel capriciously killing civilians for fun, making absolutely no reference to Hamas, it's role in killing civilians on both sides of the border, the role of Hamas oppressing Palestinians to force them to exist as human shields, and more importantly how this resolution was not a cease fire but a demand that Israel stopped neutralizing Hamas without adding any requirement for Hamas to meet.

I don't think your take makes sense. The example in the blogpost states multiple methods have 10 lines of math, but even the author mentions they were similar, not the same. The use of the weasel word "similar" already tells you that it wasn't the math that was shaved off. In fact, the supposedly brilliant refactoring that the blogger did was change the whole interface without any good reason, and with bad object-oriented inheritance chains and mixins to boot. What a mess.

Still, the blogger tries to claim this is clean?

There's a good reason why the blogger was pulled into a meeting and gently forced to revert that mess back to its old state, and why the blogger decided to depict a hero journey in a blog post where any sort of counterpoint is left out.

I think the problem is the rule itself. A rule of thumb is fundamentally broken if it does more harm than good. The heuristics to drive a decision need to lead the developer to a good outcome if they apply it without overthinking things or have meetings, because that's what rules of thumb are for.

Time and again developers tie codebases into contrived knots by mindlessly repeating the mantra "duplicate code is bad code" because they fail to realize that code that looks the same is not the same code at all, and sometimes should not be the same code at all for a number of reasons. Developers need to think hard about whether a refactorization helps simplify a project, and shoving code sections into multiple unrelated code paths is surely a way to do the exact opposite. Moreso when a mastermind developer opts to add conditionals to force similar code blocks to fit other code paths.

That's specious reasoning at best.

A class basically means a way to specify types that track specific states and behavior. Afterwards this materializes in other traits like interfaces and information-hiding.

Don't tell me Rust does not support those.

Also, C++ precedes Rust and it supports free functions and objects without member functions from day one. Rust is hardly relevant or unique in this regard. What Rust supports or not is not progress, nor is the definition of progress whatever Rust supports.

> And objects are a concept to manage state over the lifetime of what the object represents, so that might be a worthy concept, but a class?

You're showing some ignorance here. Classes and objects are entirely different concepts. An object is an instance of a class. A class is a blueprint of an object. This is programming 101.

That's besides the point, isn't it? Just because you can in theory extract functions that doesn't mean you should, or that your codebase will be in a better shape if you do. There's the issue of coupling, and there's the issue of introducing dependencies, and there's the issue of whether the apparent duplication holds the same semantics and behavior across the project. I'm talking about things like does it make sense to change the behavior on all 10 code paths if you need to change it in only two or three? Having a surface-level similarity between code blocks doesn't make them the same behavior, does it?

There is zero cost associated with piracy. Zero.

At best, there's an expectation of profit that's not met. To argue that, you need to show how copying a file translates to a potential sale being converted to a no-sale, and there are plenty of evidence that unauthorized distribution of copyrighted work drives demand up.

> Pretending piracy doesn't hurt revenue is a shaky ground to stand on

Go ahead and show exactly where copying a file hurts anyone. You're trying to pass off your personal assertions as axioms, but it's on you to prove that copying a file without the consent of someone hurts anyone.

Go ahead.

> now whatever it hurts the artists revenue is a different question

If anything, artists are the least impacted counterpart as they literally get paid a small fraction of the whole income.

>

It don't think there is any doubt that it was a bald-faced lie. The comment reads like a puerile feign of ignorance.

> However, Musk has recently addressed his distaste for unions, saying in New York last week: “I disagree with the idea of unions. I just don’t like anything which creates a lords and peasants sort of thing. I think the unions naturally try to create negativity in a company.”

Is this clown for real?

To pile onto this example, in some cases the mastermind behind these blind deduplication changes doesn't notice that the somewhat similar code blocks reside in entirely different modules. Refactoring these code blocks into a shared function ends up introducing a build time dependency where previously there was none, and as a result at best your project takes longer to build because independent modules are now directly dependent or at worsr you just introduced cyclic dependencies.

I think you're referring to coupling. Deduplicating code ends up coupling together code paths that are entirely unrelated, which ends up increasing the complexity of an implementation and increase the cognitive load required to interpret it.

This problem is further compounded when duplicate code is extracted to abstract and concrete classes instantiated by some factory, because some mastermind had to add a conditional to deduplicate code and they read somewhere that conditionals are for chumps and strategy patterns are cleaner.

Everyone parrots the "Don't Repeat Yourself" (DRY) rule of thumb and mindlessly claim duplicate code is bad, but those who endure the problems introduced by the DRY principle ended up coining the Write Everything Twice (WET) rule of thumb to mitigate those problems for good reasons. I lost count of all the shit-tier technical debt I had to endure because some mastermind saw two code blocks resembling the same shape and decided to extract a factory with a state patter turning two code blocks into 5 classes. Brilliant work don't repeating yourself. It just required 3 times the code and 5 times the unit tests. Brilliant tradeoff.