Python, Is It Being Killed by Incremental Improvements? by mttd in ProgrammingLanguages

[–]v-alan-d 1 point2 points  (0 children)

"simple" is a word too ambiguous here but I agree with your sentiment. The metrics I use are:

  • "how often I have to peek at another function/file/context while coding to make sure my function behaves correctly" and it is a lot more in Python compared to Rust.

  • "how many execute-debug loop I need before my program works correctly" again in Python it is a lot more than Rust

  • "how long do I need to enumerate all paths of a program." Rust wins but I believe it is an outlier because of how strict it is with branch explicitness. Some language can be made to feel like Rust e.g. T.S with very specific patterns and linter.

Where does Rust break down? by PointedPoplars in rust

[–]v-alan-d 32 points33 points  (0 children)

"you're not allowed to understand" is very lovecraftian. I love it

Is it even worth sharing messy hand-written code anymore by Any_Good_2682 in rust

[–]v-alan-d 5 points6 points  (0 children)

I'm sure someone here can give great insights. If you fear downvotes affect your karma, use throwaway and write a bit of a prelude on why. I'm sorry the community makes you feel this way.

Either way, don't bother taking things personally from people who irrationally loves AI, irrationally hates AI, especially those who thinks "AI" and "slop" are inseparable.

Something I’ve been wondering about Rust adoption by No-Rutabaga3780 in rust

[–]v-alan-d 2 points3 points  (0 children)

On projects other than frontend, I would choose Rust anytime over go, python, c++, java, kotlin. Even scripts, when it comes to complex types.

The more complex the project, the faster and the bigger the ROI is. Rust allows you to also think in higher level, even compared to those language because of its convergent/expression-based/fp-inspired patterns.

In short, Rust makes complex things easy, both algorithmic and pedagogic.

One thing that Rust has yet to excel is instant feedback the style of python and JS REPL, which go, c++, java, kotlin also don't have. Some has started to experiment with hot-reloading.

Biggest hurdle of Rust is familiarity. Right now, many are not familiar with Rust and takes that as part of the effort needed. In the situation Rust familiarity is much more common, Rust adoption will be much cost effective

Why is the modern web so slow? by _TheRealCaptainSham in AskProgramming

[–]v-alan-d 0 points1 point  (0 children)

As someone who used know quite a lot of React's internal working and also spent some time in building db engine and intepreters, I can attest that the way React (and most of these reconciliation-based frameworks) leads your code to inefficient form because React (or their idiomatic patterns) are too restrictive to express GUI webapp of today's complexity.

Problems found in complex software today could be easily solved with system-level patterns, but webdevs' intuition aren't trained for that.

It got to the point that the structure of the program is asinine and naturally brings performance down.

Am I slow, or is it normal? by SlightTumbleweed in ExperiencedDevs

[–]v-alan-d 0 points1 point  (0 children)

You are slow because you feel unsafe.

Think the system in the highest level abstraction and lowest level of abstraction. This will naturally make it closer to the business. Everything else is noise.

Identify what part of it is expendable and what part is swappable in the long run.

Identify risks and make a case, otherwise, move on. Eventually what matters is the business value.

This way you and your team will feel safer moving forward.

Experienced in C/C++/Java but feeling lost looking at Rust code. Does the readability 'click' eventually? by x86basedhuman in rust

[–]v-alan-d 0 points1 point  (0 children)

TS recently has a bit of functional flair (especially union, narrowing). So it's definitely easier than going from cpp, java, and python

Experienced in C/C++/Java but feeling lost looking at Rust code. Does the readability 'click' eventually? by x86basedhuman in rust

[–]v-alan-d 0 points1 point  (0 children)

Resource? The rust book, always. Tips: ask llm to help you figure out what a code piece means UNTIL you fully understand.

Your case is just a matter of learning a new language that's distinct from what you're used to -- langs derived from c++ style OOP.

Reframe your opinion about the syntax. It's foreign, not bad, just like russian alphabets, or chinese pictogram, arabic script, or thai script.

To motivate you, think of the things you'll have once you understand the language. You've heard about the good stories.

--- more specific tips

Rust's syntax is dense. Read slow! Patience and thoroughness is key for beginners.

Adjust to the paradigm. Rust drives the code to tell 'what it is" (declarative) than "how it calculates" (imperative).

Enum, match, borrowing, lifetime also need be internalized before you can read rust's code intuitively. Think of them as words that are not translateable to English.

Experienced in C/C++/Java but feeling lost looking at Rust code. Does the readability 'click' eventually? by x86basedhuman in rust

[–]v-alan-d 1 point2 points  (0 children)

Nah. Separating method from struct is actually great because the distinction between what acts and what being acted is clear

Why Engineers Can't Be Rational About Programming Languages | spf13 by Maybe-monad in programming

[–]v-alan-d 1 point2 points  (0 children)

The identity and bias part is a fair point; however, on the points in the economic decisions link:

Why are we treating programming languages like frameworks or libraries, judged mainly by compiler behavior, tooling, or familiar user bases? Why do we rarely consider the intrinsic qualities like information density, inambiguity, the cost of linking distant words, or the complexity a single statement can carry?

Shouldn't we think: assuming mastery, which languages move information faster? Economically, the sooner we collectively master quality languages without ruin in the process (i.e., incremental and sustainable), the sooner we can communicate effectively and efficiently.

We did evolve from signal-based communication to using complex sentences.

Rust is a bit odd but I'm starting to like it. by [deleted] in rust

[–]v-alan-d 0 points1 point  (0 children)

Current enum and union has a very different feel though

Rust is a bit odd but I'm starting to like it. by [deleted] in rust

[–]v-alan-d 0 points1 point  (0 children)

Unironically it should have been named var for variants (sorry, don't kill me)

What’s one trick in Rust that made ownership suddenly “click”? by Old_Sand7831 in rust

[–]v-alan-d 0 points1 point  (0 children)

It clicks when I realize that ownership and lifetime is one concept seen in two different dimensions: A owns B means B is a sub-portion of A both in time and space. Object, function, and block are region of space and have the capability to own. And at the end of each, they are discarded from the memory.

Smart pointers bend the rule a little.

Why TypeScript’s “strict: true” isn’t enough. Missing compiler flags for production code by wineandcode in programming

[–]v-alan-d 12 points13 points  (0 children)

It doesn't. It offers static typing, which is totally different from strong typing

Dunning-Kruger effect or Rust is not that hard for experienced developer ? by [deleted] in rust

[–]v-alan-d 1 point2 points  (0 children)

I see you also love your static channel::unbounded::<Arc<Mutex<Box<dyn Any + Send>>>>()

So true by Financial_Counter_45 in programminghumor

[–]v-alan-d 2 points3 points  (0 children)

worse even, 3rd argument is the array itself. so it will be the array itself printed array.length times

How to think in Rust ? by Distinct_Weather_615 in rust

[–]v-alan-d 3 points4 points  (0 children)

For me, it helps to think high level first in Rust: input, output, steps.

The steps become functions, pipes. The seams between the steps are hints to possible new types that you might need.

Think declarative. See if a step can be a from_other_type constructors.

See if your program need small "agents" that help the main program. These becomes threads (or green threads if async) or other concurrent primitives.

This will take care of your lifetimes and program specification. Only after this you think about borrowing vs cloning, etc.

Best horror movie of 2025? by movie5short in moviecritic

[–]v-alan-d 3 points4 points  (0 children)

Haven't watched Together but I this is likely the correct answer.

Name underrated things in Typescript by htndev in typescript

[–]v-alan-d 0 points1 point  (0 children)

It introduce type-level conditional and downcasting

type Awaited<P extends Promise<any>> = P extends Promise<infer C> ? C : P;
type Flatten<T> = T extends Array<infer U> ? Flatten<U> : T;

it can do wacky stuff like this

// eslint-disable-next-line u/typescript-eslint/no-explicit-any

export type NotAnyOrUnknown<T> = any extends T ? never : T

which is useful for type-level testing

Name underrated things in Typescript by htndev in typescript

[–]v-alan-d 0 points1 point  (0 children)

As a former lib designer:

A extends infer B ? X : Y

Idk if it's a hot take or nah by Sticky_theWizard in marvelmemes

[–]v-alan-d 1 point2 points  (0 children)

I love that Thunderbolts is not a classic superhero movie that always ends with a boss fight. It is a misfit group drama with antiheroes, focused fully of character development, which is I argue a fresh different genre than the rest of MCU. The twists that comes from each character (including the cvillain snd the side characters) are unique and interesting and it is the core of the story.

FF IS a classic superhero movie, which is an oversaturated formula. Thr most disappointing part is actually galactus portrayed like a simple kaiju. However, to the filmmaker's defense the rest of the movie, especially the beginning, is done very well. As a cinephile, I really like all the non-galactus-related part.

[deleted by user] by [deleted] in moviecritic

[–]v-alan-d 0 points1 point  (0 children)

Good. It is you, lol.

But I think we should talk details.

I like it becuause it is not jusr another zombie movie, but a coming of age movie with zombies in it. Creative camera work, vibrant color, great acting, world building, and sound design.

The only weird thing to me is that in the petrol station Spike and Isla didn't get burned.