mbtrhcs

u/mbtrhcs@feddit.org
1 posts · 98 comments

Recent posts

Recent comments

I don't have any answers unfortunately but here is what it looks like on an iPhone on iOS 26:

in the browser: ::: spoiler Spoiler :::

as a PWA: ::: spoiler Spoiler :::

it seems that the safe area inset is correct here.

on Wolf in sheeps clothing · c/memes · 1 pts · 1y

My goodness. What is your point? Don't bother trying to help the Palestinian people if you don't say exactly the right things? You think he'd have an easier time getting support for the bill if he used the word genocide?

It must be nice to live a life of such luxury that you can care more about the phrasing than the actions.

namespaces, decorators

Decorators are also a fairly niche feature and if you wanted to use the equivalent to a namespace in JS you'd have to write code for it too. Neither of which would explain a 5x energy consumption jump.

and some cases even async / await (when targeting ES5 or ES6)

..which is exactly what I said the researchers probably did, putting TS at a significant disadvantage. Thank you for proving my point, I guess.

Yeah sure, you found the one notorious TypeScript feature that actually emits code, but a) this feature is recommended against and not used much to my knowledge and, more importantly, b) you cannot tell me that you genuinely believe the use of TypeScript enums – which generate extra function calls for a very limited number of operations – will 5x the energy consumption of the entire program.

Only if you choose a lower language level as the target. Given these results I suspect the researchers had it output JS for something like ES5, meaning a bunch of polyfills for old browsers that they didn't include in the JS-native implementation..

I'm an empirical researcher in software engineering and all of the points you're making are being supported by recent papers on SE and/or education. We are also seeing a strong shift in behavior of our students and a lack of ability to explain or justify their "own" work

let's see if we can find supporting information on this answer elsewhere or, maybe ask the same question a different way to see if the new answer(s) seem to line up

Yeah, that's probably the best way to go about it, but still requires some foundational knowledge on your part. For example, in a recent study I worked on we found that programming students struggle hard when the LLM output is wrong and they don't know enough to understand why. They then tend to trust the LLM anyways and end up prompting variations of the same thing over and over again to no avail. Other studies similarly found that while good students can work faster with AI, many others are actually worse off due to being misled.

I still see them largely as black boxes

The crazy part is that they are, even for the researchers that came up with them. Sure we can understand how the data flows from input to output, but realistically not a single person in the world could look at all of the weights in an LLM and tell you what it has learned. Basically everything we know about their capabilities on tasks is based on just trying it out and seeing how well it works. Hell, even "prompt engineers" are making a lot of their decisions based on vibes only.

I don't know if it's just my age/experience or some kind of innate "horse sense" But I tend to do alright with detecting shit responses, whether they be human trolls or an LLM that is lying through its virtual teeth

I'm not sure how you would do that if you are asking about something you don't have expertise in yet, as it takes the exact same authoritative tone no matter whether the information is real.

Perhaps with a reasonable prompt an LLM can be more honest about when it's hallucinating?

So far, research suggests this is not possible (unsurprisingly, given the nature of LLMs). Introspective outputs, such as certainty or justifications for decisions, do not map closely to the LLM's actual internal state.

on *Permanently Deleted* · c/asklemmy · 5 pts · 1y

kind've

Ok not to be nitpicky but this is the first time I've ever seen the opposite (complementary?) mistake to "could of". That's actually kinda fun :D