gr__or

sauce: https://brandur.org/job-drain

Regulations __can__ create monopolies. DMA is a regulation, but it does not have the shortcomings you mentioned.

https://bsky.app/profile/watwa.re/post/3lizpdz34522g

I'm working on a similar idea, it's been a while since I published about it but open to input and collabs!

Tangled (https://tangled.org) is the next social coding platform to believe in imo because

- no more silo-ing, moat BS, by design - they are working on vouching which is becoming more important in the age of AI PRs

I find this to be vile political posting, moving responsibility for Trump's rightwing fascism to a social theorists is just misguided, banal and does not belong here. Don't you have X for that?

thinking out loud: it'd be great if web servers could sign their responses+timestamp, so you could guarantee getting the right content even through such intermediaries

bit of a narrow focus point isn't it? this is a project that lives on despite the economics, throwing garden-wall-lingo in there feels a bit gross tbh

I'd say the article makes a pretty explicit case for why the general thesis of the book does not hold, which makes your comment stand out as comparatively superficial whataboutism

while this is a link to the malware site x.com, it is shown in a protective trustworthy hull, called xcancel.com

While I agree with the sentiment, I think it confuses ISPs with registrars. There are still many ISPs that do that service as well, it's less common than it used to be.

It is quite common for national TLDs (like .de, .jp or .cn) to be managed by not-for-profit entities, under contract with their respective governments... which might also not be great wrt censorship.

There is also the general issue of equal access, where shorter, more memorable domains get more expensive and hodling domain names is only disincentivized for people without enough funds. I would very much like to see an alternative system to domain names, probably something more in the web of trust space.

I meant programming-time, but runtime is also a good point.

Cross-language libraries don't seem to be super common for this. The recovering-sense-from-text tools I named all use different parsers in their respective languages.

Again, reading (and yes, technically that's also parsing) from an AST from a data-exchange formatted file is mags simpler. And for parsing these schemes there are battle-tested cross-language solutions, e.g. protobuf.

The complexity of a parser is orders of magnitude higher than that of an AST schema.

I'm also not saying we can have all these good things, but they are not free, and the costs are more spread out and thus less obviously noticeable than the ones projectional code imposes.

For me, that's what "short-sighted inability" means. The business ecosystem we have does not have the attention span for this kind of project. What we need is individuals grouping together against the gradient of incentives (which is hard indeed).

Even that is not without its cost. Most of these tools are written in different languages, which all have to maintain their own parsers, which have to keep up with language changes.

And there are abilities we lose completely by making text the source of truth, like a reliable version control for "this function moved to a new file".

Text surely is a hill, but I believe it's a local one, we got stuck on due to our short-sighted inability to go into a valley for a few miles until we find the (projectional) mountain.

All of your examples work better for code with structural knowledge:

- grep: symbol search (I use it about 100x as often as a text grep) or https://github.com/ast-grep/ast-grep

- diff: https://semanticdiff.com (and others), i.e.: hide noisy syntax only changes, attempt to capture moved code. I say attempt, because with projectional programming we could have a more expressive notion of code being moved

- sed: https://npmjs.com/package/@codemod/cli

- version control: I'd look towards languages like Unison to see what funky things we could do here, especially for libraries. A general example: no conflicts due to non-semantic changes (re-orderings, irrelevant whitespaces, etc.)

Bluesky/ATProto is a recent example of a self-guaranteeing promise

That's so fun to hear, I've been using taffy for layouting my little rusty eink calendar

I don't quite see it that way. Imo he's been to involved in anti-woke culture waring, but I still found him to be wonderfully interesting to read.

I don't think that's a necessary consequence. React is free, a sort-of recruitment loss-leader for Meta. Imo you can get to a moral zero on this pretty easily despite still using React, by supporting out-of-Meta React OSS and using your platforms to denounces Meta's carelessness.

On the other hand: Companies pay for Microsoft's offerings and they support the Israeli military in their genocidal campaign in Gaza, I think getting to a moral zero on that is significantly harder.

How does her attempt to change things from the inside, by confronting their higher ups, who constantly put her down for it and collectivizing with other insiders, still lead you to such a harsh judgment of her character?

Absolutely, it would be nice if we found the right abstraction to get rid of that part as well. Basically every non-React framework's answer to that is Signals (aka change tracking), where React is doubling down on unidirectional data flow and thus dependency arrays. React Compiler indeed solves the 99% of performance related memo-s.

For effects you still will have to understand the mental model (which I'd argue is inherent in the domain and not incidental to the tech).

From reading Nue's docs on Interactivity, it seems to opt-out of the discussion by going back to good old manual UI refreshs. I personally would not choose that, too many pre-React debugging nights spent on chasing state<->UI desynchronization bugs.

The FAQ (https://nuejs.org/docs/faq.html) describes pain points that seem pretty foreign to me, the exact thing I appreciate about React is that I can focus on the domain and the tech MOSTLY does fade into the background. It has been an improvement in that regard, to all the frontend MVC I've done before and the architectural pattern has been adopted for good reason by all the native platforms.

TBC in React and its offspring, you can still model business logic outside of components, we just learned that most UI development is better served by keeping UI and its state closer.

I can think of a DOOM that WILL run faster…

https://youtu.be/0mCsluv5FXA

You are confused about the issue, and the OP does its part in contributing to the confusion. It's not a VDOM issue, it's not React exclusive (that part the post is explicit about) and indeed Svelte is affected as well: https://github.com/sveltejs/svelte/issues/15090

When seeing issues like this one pop up with React in the title, one should really have a good think whether this is solved principally different in other fws OR, and this should be the null hypothesis, is React in the title because it is more widely used than all the others combined

Tailwind is a testament to the greatness of inline styles (styling a thing without naming it), the universality of strings and also the limits of strings.

I am excited for what comes after it, until then I'll use Tailwind (reluctantly)

not-federalized != walled-garden

A walled garden implies captured user data and social graph, which is the decentralized part of Bluesky (ATProto to be precise). The difference to Mastodon (ActivityPub to be annoyingly precise again) is in funding needed to host the entire thing.

With ActivityPub, you have to find recluse with a war-lord who will now own your data and handle, and spend a not-too-insignificant amount to keep up the infra (enough that instances have folded due to finances). With ATProto, one has to find a seemingly sympathetic oligarch who does NOT own your handle or your data, and has to spend an average european income on keeping up the infra.

Different threat models, different game theoretical plays really

For the curious ones who are not so excited about gifting page views to the fascist:

https://xcancel.com/elonmusk/status/1881923570458304780

If you do cloud infra stuff, AWS will try to undercut you on price but will never outdo you on D/UX. So I wouldn't let Beezus hold me back

Cookie dialogs are a medium-size meh.

Browser choice vs Microsoft were a big win.

GDPR is a big win.

I'd say it's 20:1

It's par for the course with HN libertarian virtue signaling