HackerTrans
TopNewTrendsCommentsPastAskShowJobs

moritzwarhier

1,695 karmajoined قبل 6 سنوات

Submissions

Papiamento

en.wikipedia.org
3 points·by moritzwarhier·قبل 27 يومًا·0 comments

Just-World Fallacy

en.wikipedia.org
4 points·by moritzwarhier·قبل 27 يومًا·1 comments

Emergent Self-Assembly of Sustainable Plastics Based on Amino Acid Nanocrystals

pubs.acs.org
3 points·by moritzwarhier·قبل 4 أشهر·0 comments

comments

moritzwarhier
·أمس·discuss
Treating medical care like this, similar to a racketeering scheme, should not be a thing anywhere.

Instead of punishing people for seeking medical care (or plainly requiring it), it would be preferable to have a robust protocol for rejecting patients that do not require care, whether at the hospital or before the ambulance ride.

For this, people would need to want medical care be a humanitarian right and basic pillar of a functioning society, not a business or a bureaucratic system to perform a selection process decreasing the life expectancy of less-affluent people.

Ironically, when there is free medical care and universal insurance, there are also perverse incentives. For example unneeded expensive procedures, prescribing patented, newer drugs where cheaper ones would work, providing ineffective or even detrimental services, etc.

But humanitarian values are out of fashion, because they were never achieved globally.

So the only right people care about increasingly is their right to own property.
moritzwarhier
·أمس·discuss
Not the same issue, but makes me nostalgic for these simpler times:

https://www.wired.com/2011/04/amazon-flies-24-million/
moritzwarhier
·أمس·discuss
There was an HN comment pointing out this exact fact in some Anthropic thread recently, that agents are not suitable for indeterminate questions that would better fit a chatbot.

I couldn't bother to find it yesterday, but I think this article was just generated by another user who read that comment and thought it's suitable to bloat into a blogspam submission.

Probably finding suitable comments or other content that can be bloated and used for monetization or engagement farming is already feasible to automate, too.

Disclaimer: didn't click because the headline already tells this and follows an overused generic phrasing.
moritzwarhier
·قبل 8 أيام·discuss
As a Western German myself (who doesn't vote AfD), I'm inclined to agree.

Division and looking down on people, especially using attributes like "braindead", is arrogant and also just adds to the political capital of the far right.

Things that are not direct calls to violence or tearing down democracy must be acceptable parts of the discussion. And calling people who have opinions you consider hostile or wrong "stupid" has never helped anyone. Even when these opinions already cross the line of what's acceptable or are really "stupid" in your best-faith interpretation.

The Ossi/Wessi thing is especially problematic to bring up I feel. Also, the German East has been attracting industry and science facilities for quite a long time. And parts of Western Germany still seem to have issues with losing their perceived cultural hegemony.

But this process should be welcome to anyone who honestly wants a united Germany state.

Sowing division by looking down on the "former DDR" is a poison to democracy, just like yearning for autocracy.

The term "former DDR" is only recently going out of style in Western Germany, and that already says a lot.

Looking down on the AFD is understandable when you detest right-wing ideology, but it is no more helpful than laughing about people who were nostalgic about parts of the former DDR.

Adding arrogant arguments about wealth, the economy or cosmopolitanism will only increase this division and also the success of the AFD in the West.

For example, rejecting to celebrate and awe at cosmopolitanism and multiculturalism is not "Nazi".

That being said, yes, there are violent Nazis in Germany, many but not only in Eastern Germany.

Pointing fingers at only this problem just further sows division though, and it should also be clear that the far right that is active in the East is not a seperate entity from the far right in Western Germany.

Some regions in Western Germany also have strong far right hegemony, or are shifting to it, especially the poorer regions.

Sowing division about wealth and relating it to xenophobia is not helpful in increasing tolerance or decreasing frustration of working people.

And there is a shrinking part of the German left that ostentatiously is about human values, but has an ambivalent relationship towards capitalism, while rejecting any and all remotely critical sentiments regarding immigration. Often, even rejecting the German state: considering themselves leftists, but at the same time being deeply intertwined with the dominant cultural and political currents, and often enjoying a lot of wealth.

The arrogance of this "wealthy liberal establishment" as an issue is not much different from what helped Trump get elected, I feel.

The contradictory combination of being anti-right, pro-immigration, demanding of material wealth and at the same time claiming the moral arrogance of being on the morally "good" side will not slow down the decline of the left party of the political spectrum.
moritzwarhier
·قبل 9 أيام·discuss
The whole premise of a "giant secure open source C codebase" seems questionable

Because code review is sometimes not much different from an idealized version of the halting problem, where you would have access to a formalized version of a specification.

In other words, there is no strict definition of what is a security issue.
moritzwarhier
·قبل 16 يومًا·discuss
Or using it correctly... depends on what your system is, or more accurately, your policy on reviewing or quickly merging PRs with "Draft" status.

As long as it's taken as an indicator for WIP, it works. It just doesn't work when acting illiterate of this distinction; and I have often have had PRs switched to "ready", reviewed + merged in a couple of hours.

But when the change list grows, and the PR ages, while still being intentionally maintained, the Draft signal is strong and helpful IMO. Switching an old Draft PR to "ready" after reviving it with changes seems like a useful signal to me.
moritzwarhier
·قبل 26 يومًا·discuss
undefined is not less absurd because there are parts of the standard that allow you to differentiate between

  undefined 
and a non-initialized value.

Of course you shouldn't do that, but I once encountered a library that behaved differently depending on whether an option in an options bag object was not present or explicitly set to undefined.

You can run into similar ugliness with function parameters, if you do evil things like using

  arguments
And of course you can explicitly check keys of objects, including parameters that are going to be destructured.

All not things you should do, but taints the "purity" argument, doesn't it? :D
moritzwarhier
·قبل 26 يومًا·discuss
https://tc39.es/ecma262/multipage/indexed-collections.html#s...

> Arrays are exotic objects that give special treatment to a certain class of property names. See 10.4.2 for a definition of this special treatment.

I just meant these special properties. The behavior, apart from the square-bracket syntax for construction, can be emulated using Object property descriptors, Symbol.iterator etc, but AFAIK, much of this is retro-fitted.

Not disagreeing with the fact that arrays are almost just regular objects in JS, but the "just" in "just objects" does have nuances, AFAIK.

JIT Optimizations for non-sparse arrays might just be part of a larger hot-path optimization system, but I think there are still differences.

Is it possible to create an object for which

  Array.isArray
returns true without it being instantiated using an array constructor or other array-returning function, the Array prototype, or square-bracket syntax?

E.g.

  Array.from({"0": 1, "1: 2})

  Array.from({length: 2}, (i) => i + 1)

  [1, 2]

  [...Object.values{"a": 1, "b": 2})]
...

all implicitly use the built-in Array prototype.

I'm not sure if it's possible to build an array using only primitives and functions from the

  Object.
namespace, for example.
moritzwarhier
·قبل 27 يومًا·discuss
If this is true, it really would be impressive.
moritzwarhier
·قبل 27 يومًا·discuss
I intentionally corrected it, because vanilla JS arrays used to behave like this in some contexts, but I'm not even sure about which ones still.

Since the "Array" is a reference to the prototype, I think it might be outdated due to changes in undefined behavior of runtimes when serializing array objects, or logging them.

I'm pretty sure that [object Array] used to be the result of logging an array at some point.

  Object.prototype.toString
always returns the result of

  Array.prototype.join

per spec, afaik, so for an empty array it's the empty string.
moritzwarhier
·قبل 27 يومًا·discuss
Thanks for the factual clarification. This is so important when everyone already has their trigger finger on politics. Not meaning that politics are irrelevant here, see sister comment by jobim.

But it's impossible to form a nuanced opinion when political association has a higher priority than the facts; which, again, don't look flattering for the implementers.
moritzwarhier
·قبل 27 يومًا·discuss
I do it this way, but this led to people asking me in reviews why I use NULL^^

My explanation was that it signals intent to me, and is different from some property not being part of the expected object shape or not having been initialized because of some accident or logic failure.

Since then, I've sticked to it, and am "allowed" to use NULL ^^

It can lead to some annoying checks in TS for primitively-typed properties, so for these, I still allow explicit usage of undefined when it's simpler given the surrounding code.

But I agree with you in principle. Using "undefined" as a "second nullish value" and explicitly checking for it is a programming error.

When there's object/areay vs null/undefined, thankfully, the truthiness narrowing often allows me to interface with code relying on "undefined" without explicitly handling this "value" in my own parts of the code base :)
moritzwarhier
·قبل 27 يومًا·discuss
Thanks a lot! I'll give this a try next time I feel like coding for a hobby.

I've tried exactly this "project idea" in a half-assed way some time ago with next.js, Postgres and Prisma before I was out of free-time-in-front-of-computer.

Then abandoned it again it when I started coding for a living again. It was exactly the "modest RT capabilities" thing when I abandoned it. Because I started using Firebase (2023, Supabase was not known to me then) and then I felt like "OK, I managed to get full next.js running properly on shared hosting with limited server-side JS, but now I again need an external cloud provider for a hobby project" (Firebase).

I read a bit about their pricing models and lost interest.

I think next time I'm gonna try see what this stack can do.

In 2024, I heard a very interesting conference presentation about Erlang and its concurrency model, that was after the hobby experiment, and made me want to revisit losely functional languages with strong pattern matching (OCaml too, but that's a different topic).
moritzwarhier
·قبل 27 يومًا·discuss
Previously submitted here a couple of times, last one is 2 years ago.

So I thought, why not re-submit it. Relevance is probably timeless, although it's a neologism that doesn't present a particularly new idea.
moritzwarhier
·قبل 27 يومًا·discuss
Good point. Since I've never owned a Chromebook, I didn't even know that they are capable of installing arbitrary Android apps.
moritzwarhier
·قبل 27 يومًا·discuss
I wanted to try out Erlang + Elixir since forever, do you think Phoenix LiveView would be a good starting point? For example, to create something like a simple game with modest persistence and only very limited RT-features? I was thinking about sth like a quiz app, not a web MMORPG of course :)

Or is LiveView only useful to optimize partial page reloads and SEO?
moritzwarhier
·قبل 27 يومًا·discuss
Is there a technical reason you don't mention ChromeOS?

Just asking out of curiosity.

Also, the screenshots I've seen of webOS makes me long for a revival... not only on smart TVs
moritzwarhier
·قبل 27 يومًا·discuss
To be fair there were a couple of disasters, such as [object Array] and undefined.

Feels like the world is hanging on a single thread by now.
moritzwarhier
·قبل 27 يومًا·discuss
It's a refusal to engage with the reported information, not an argument.

Note that the general sentiment on HN when it comes to other topics is that every slight simplification in reporting on science is unforgivable, Gell-Mann-amnesia-effect, bla bla...

For example, it is clickbait to say "cancer" instead of "some types of cancer which we further need to specify" in headline.

But it is of course impossible to take scientists seriously when their results are reported as "they observed X, and are there are indications that it could mean Y".

Who says "could"? It's way too risky to engage with people who don't tell me exactly what to think!
moritzwarhier
·قبل 27 يومًا·discuss
To be fair, implementing something like the Spotify client does require a web app, not "just" a web site.

But even document rendering with light scripting is not trivial so yeah, the required browser is the bottleneck.

I always wonder (layman question): couldn't native Electron apps (and similar technologies) save a great deal of RAM by using the same sandboxing model for apps that browsers use for tabs, instead of fully-fledged instances?

Was that an idea that Tauri also tries to implement, or am I remembering this wrongly?