eager_eagle

eager_eagle, 14 hours ago

my favorite JS framework is HTMX for making me write less JS or even none at all.

eager_eagle, 1 day ago

same

as an alternative to pinching, you can tap, hold, and drag in that order to control the zoom level with one finger.

eager_eagle, 2 days ago

it feels like they’re shooting gem* products everywhere to see what sticks

then they’ll kill 90% of them in a couple of years

eager_eagle, 2 days ago

Search sucks for some time now. I’d say the best thing google offers today is Gmail - but there are plenty of arguments against that too.

eager_eagle, 2 days ago

Well, it’s not exactly impossible because of that, it’s just unlikely they’ll use a discriminator for the task because great part of generated content is effectively indistinguishable from human-written content - either because the model was prompted to avoid “LLM speak”, or because the text was heavily edited. Thus they’d risk a high false positive rate.

eager_eagle, 2 days ago

True. I wanted to replace it with OSM or similar, but my main use of Maps after navigation is exploring places, reading reviews, and browsing pictures. They have a database that is tough to replace.

eager_eagle, 2 days ago (edited 2 days ago)

So you have to do dumb workarounds like declaring every bool values as bool | np.bool_ or casting bool_ down to bool.

these dumb workarounds prevent you from shooting yourself on the foot and not allowing JS-level shit like “1” + 2 === “12”

eager_eagle, 2 days ago

we know it’ll never happen, but if they…

• have content from most studios available indefinitely in one place - or even better, a federated platform - at no additional cost.
• drop all this drm stupidity and allow the best quality streams on any general computing device.

only then, in my view, it’d equal the convenience I have today and I wouldn’t mind paying a reasonable amount for that.

eager_eagle, 2 days ago (edited 2 days ago)

the thing is - there’s a lot of variables that shift the balance towards renting when looking within a time frame, even from a financial perspective.

• how long you can stay in one place and whether that fits your needs both today and in a few decades
• % of down payment and missed earnings if this money went towards another investment
• interest rates
• property taxes
• HOA fees, if any
• likely higher insurance rates over renting
• maintenance costs

In the end of the day, since many variables have a large uncertainty, that’s a bit of a gamble. Home ownership tends to win over time, but the longer one looks into the future, the higher this uncertainty also is.

eager_eagle, 2 days ago

I’m missing all advantages of owning (or renting), that was not the intent.

eager_eagle, 21 hours ago

it seems like a general preference to system settings, even after ranking applications higher

https://lemmy.world/pictrs/image/8a5e9570-d340-4130-b62c-4f8342f7c919.png

eager_eagle, 3 days ago

i believe some cultures call it ransom

eager_eagle, 3 days ago

nothing wrong with that - it is an exception, as in, the customer is likely lost after that anyway.

eager_eagle, 3 days ago

that’s still a docstring, idk of linters that take docstrings into account at all. We need a semantic approach for this kind of annotation.

eager_eagle, 3 days ago

some heroes don’t wear caypes

eager_eagle, 1 day ago

I don’t think so. A half-measure using docstrings would likely take more processing power and require an ad-hoc implementation because comments are not broken down into ast components afaik. It would also be more costly in the long run if they decide to convert it into a proper syntax, as a result of docstrings not having a single standard way of being written.

Python has introduced several syntactic changes for type annotations, this is not unreasonable.

eager_eagle, 3 days ago

I’ve been using copilot for a while to know it’ll be something like timeBottom and timeTop.

But if anyone’s getting this recommendation there’s probably not much code in that file or the code is trash. Garbage in, garbage out.

eager_eagle, 5 days ago

that’s 6am or 2pm for anyone interested

eager_eagle, 4 days ago

fair, i’m not a synesthesentic person

https://m.media-amazon.com/images/I/71fB-6KteML._AC_SL1000_.jpg

eager_eagle, 6 days ago

I thought it was just incrementing the address and dereferencing it, but I don’t write C or C++. What is being overloaded there?

eager_eagle, 6 days ago

I hate it when some blame early returns for the lack of maintainability.

Early returns are a great practice when doing argument validation and some precondition checks. They also avoid nested blocks that worsen readability.

What’s being described there is a function that tries to do too much and should be broken down. That’s the problem, not early returns.

eager_eagle, 6 days ago

You can say any execution flow controls are like gotos - continue, break, exceptions, switch, even ifs are not much more than special cases of gotos.

This is true regardless of the size of the function which shows that the size of the function isn’t the determinant

Logical clarity does tend to worsen as the function grows. In general, it is easier to make sense of a shorter function than a longer one. I don’t know how you could even say otherwise.

Early returns are still great for argument validation. The alternative means letting the function execute to the end when it shouldn’t, just guarded by if conditions - and these conditions any reader would have to keep in mind.

When a reader comes across an early return, that’s a state they can free from their reader memory, as any code below that would be unreachable if that condition was met.

eager_eagle, 6 days ago (edited 3 days ago)

Any validation you can write with a few early returns you can write with an equivalent conditional/s followed by a single nested block under it, followed by a single return. The reader is free to leave the validation behind just the same.

And that conditional indents your entire function one level - if you have more validation checks, that’s one level of indentation per check (or a complicated condition, depends whether you can validate it all in one place). It’s pretty much the case the other user illustrated above.

Returns inside business logic past validation is where the problematic bugs of this class show up

That much we agree. But again, this is not an early return issue, putting too much logic in a function is the issue. Rewriting it without early returns won’t make it much clearer. Creating other functions to handle different scenarios will.

eager_eagle, 7 days ago

ａｅｓｔｈｅｔｉｃｓ

eager_eagle, 8 days ago

<span style="color:#323232;">:D
</span><span style="color:#323232;">Ye
</span>