flying_sheep

joined 11 months ago
[–] flying_sheep@lemmy.ml 2 points 4 days ago* (last edited 4 days ago) (1 children)

… I'm just joking, I didn't attack anyone, only a multi-billion tech conglomerate. I don't understand howi can possibly be an ass here.

[–] flying_sheep@lemmy.ml 4 points 6 days ago (3 children)

Cancer? Eating feces? Stabbing forks in your own eyes?

There's loads of alternatives!

[–] flying_sheep@lemmy.ml 2 points 1 week ago (1 children)

We know the lethal dose of LSD is high enough that nobody can afford one!

[–] flying_sheep@lemmy.ml 1 points 1 week ago

No reason. It's just that when there wasn't anything to experience it, nobody asked themselves that question.

So the question is a consequence of our existence, and that's the answer

[–] flying_sheep@lemmy.ml 17 points 1 week ago

Negative rings are a horrible proprietary liability.

That's been clear from their inception, and this changes nothing.

[–] flying_sheep@lemmy.ml 4 points 1 week ago* (last edited 1 week ago) (1 children)

Huh, I really like code like that. Having a multi-step process split up into sections like that is amazing to reason about actual dependencies of the individual sections. Granted, that only applies if the individual steps are kinda independently meaningful

To adapt your example to what I mean:

Baz do_stuff(int count, boolean cond) {
	Foo part1 = function1(count);
	Bar part2 = function2(cond);
	return function3(part1, part2);
}

This allows you to immediately see that part1 and part2 are independently calculated, and what goes into calculating them.

There are several benefits, e.g.:

  1. if there is a problem, you can more easily narrow down where it is (e.g. if part2 calculates as expected and part1 doesn't, the problem is probably in function1, not function2 or function3). If you have to understand the whole do_stuff before you can effectively debug it, you waste time.
  2. if the function needs to be optimized, you know immediately that function1 and function 2 can probably run in parallel, and even if you don't want to do that, the slow part will show up in a flame graph.
[–] flying_sheep@lemmy.ml 2 points 2 weeks ago

There's also a good loop hero port

[–] flying_sheep@lemmy.ml 5 points 2 weeks ago

Except for slice&dice

[–] flying_sheep@lemmy.ml 4 points 2 weeks ago

Not just all cultures, all eras as well. From Mesopotamian stone slates over medieval hogshide, paper to the internet: boomers gonna complain

[–] flying_sheep@lemmy.ml 2 points 2 weeks ago

How is the second one in any way controversial? React is a huge part of the reason why jQuery is much less of a thing than it was ~10 years ago

[–] flying_sheep@lemmy.ml 6 points 2 weeks ago

dbg!() for Rust users

[–] flying_sheep@lemmy.ml 37 points 2 weeks ago (4 children)

He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn't work as they thought it would.

view more: next ›