MurphyA/hacker-news huggingface dataset:
by ben_w | 2025-08-19 15:57:39+00:00
What WASDAai says is entirely fair (though caveat: a shockingly large number of production apps have really mediocre implementations from the war stories I've heard).

But:

This description sounds less like "I am making a CRUD app" and more like "I am making a generic CRUD app framework/dev tool".

Which is fine, and yes LLMs are not yet good enough to vibe their way at that scale, but it's not the same thing as any specific, concrete, CRUD app that such a tool may or many not also produce.

Actually, it gets worse:

> - Choosing the best UI framework for the requirements of the app. I actually had to write a custom react-like library for this.

Danger, Will Robinson, danger!

UI frameworks sure are fun to write. Done it loads of times myself. But one of those times was before jQuery existed, and was because it was before jQuery existed. Another was before Cocos2d existed, and because it was before Cocos2d existed.

If this was a fun side project then sure, have at it, but as a startup? I've seen people want to reinvent every part of their stack, as you are doing, and it took them 14 years to ship as Early Access.

Unless you're literally one of the FAANG companies, then devs — including ones you may need to hire, even if I'm reading the wrong thing between the lines and this isn't a CRUD-maker, you'll probably need to hire people at some point — aren't going to want to learn yet another UI framework to customise the output of your product.
by dinfinity | 2025-08-19 15:57:39+00:00
> autophagy [...] usually takes at least 18 hours of continued fasting to even start

False. That would mean cellular debris would pile up unconstrained for pretty much everybody, which is clearly absurd.

> It is also an extreme cell response that is associated with high levels of cellular stress

Also false. It is a very essential cellular process. Read up on it, please.
by eszed | 2025-08-19 15:57:42+00:00
Ha! Shout out to CSS Zen Garden. I didn't go as far down the rabbit hole as you did (noped out before XSLT made its way into my mix), but around that time I made sure all of my html was valid XML (er, XHTML), complete with the little validation badge at the bottom of the page. 80:20 form to content ratio sounds about right.
by Y_Y | 2025-08-19 15:58:05+00:00
This is my favorite kind of software, to write and to use. I am reminded of Upton Sinclair's evergreen quote:

> It is difficult to get a man to understand something, when his salary depends upon his not understanding it!

in the special case where the thing to be understood is "your app doesn't need to be a Big Fucking Deal". Maybe it pleases some users to wrap this in layers of additional abstraction and chrome and clicky buttons and storefronts, but in the end the functionality is already there with a couple of FOSS projects glued together in a bash script.

I used to think the likes of Suckless were brutalist zealots, but more and more I think they (and the Unix patriarchs) were right and the path to enlightenment is expressed in plain text.
by lucb1e | 2025-08-19 15:58:18+00:00
I thought XML was that big hype, not XSLT. That I somehow never saw mentioned that you can do actual webpages and other useful stuff with it is probably why I never understood why people thought XML was so useful ^^' I thought it was just another data format like JSON or CSV, and we might as well have written HTML as {"body":{"p":"Hello, World!"}} and that it's just serendipity that XML was earlier
by vanous | 2025-08-19 15:58:36+00:00
Very cool! A while ago i did something similar and tried to learn vim more in depth by creating some more complex macros - several of them, to convert some text snippets into markdown. Problem was, that several months later i could not exactly remember some details of these "reusable" macros - where exactly to place cursor when starting them, the order of execution and so on. Thankfully, vim has the amazing ability to run commands/script on text selection, so i rewrote my macros in a scripting language. It has several bonus points: i can store them in git and track changes, code can be self-documented via comments. My macros were not too complex, but still, using a proper scripting ended up being much better.
by protimewaster | 2025-08-19 15:58:48+00:00
I wonder if it has different implications for different types of adblocking, then. A DNS-level block doesn't modify any copyrighted data, unless they're contending that the addresses returned by DNS servers are copyrighted. And that would seem to potentially pose major hurdles for the functionality of the internet.

I also wonder how it's made distinct from an addon that does something like block malware on a website. Surely that must be modifying copyrighted data too? Are some modifications allowed, I guess? Surely if something like an accessibility addon modifies the data, that's acceptable, right?
by alexc05 | 2025-08-19 15:59:54+00:00
I'll admit that it's a little shoehorned in at the end :)

... but you know how editors are with writing the headline for clicks against the wishes of the journalist writing the article. You'll always see Journos sayign stuff like "don't blame me, that's my editor, I don't write the headlines"

I did toy with the idea of going with something like: `Prompt Engineering is a wrapper around Attention.`

But my editor overruled me *FOR THE CLICKS!!!*

Full disclosure: I'm also the editor
by somenameforme | 2025-08-19 16:00:07+00:00
I applaud you having the dignity to define 'group' instead of weaseling around it. But the issue you immediately run into is that it's not like non-white individuals are homogenous, yet the Democratic party's polling on most issues is. In any case, society isn't buying this stuff.

For instance the most recent election was decided by the economy. People that thought the economy was excellent/good voted for Harris by a margin of about 92%. Those who thought it was mediocre/poor voted for Trump by a margin of 70%. [1] And it turned out that way more people thought the economy was bad than those that thought it was good.

This led to the best result ever for a Republican for both blacks and hispanics, with Trump outright winning Hispanic males. All the while the Democrat party flailed about with this identity stuff that not only do people mostly not care about, but that also pushes away folks like me that are liberal but vehemently against political correctness, identity politics, etc.

[1] - https://www.nbcnews.com/politics/2024-elections/exit-polls
by redwall_hp | 2025-08-19 16:00:26+00:00
The W3C spec was. But WHATWG and HTML5 represent a coup by the dominant browser corporations (read: Google). The biggest browser dictates the "living standard" and the W3C is forced into a descriptivist role.

The W3C's plan was for HTML4 to be replaced by XHTML. What we commonly call HTML5 is the WHATWG "HTML Living Standard."
by herval | 2025-08-19 16:00:50+00:00
Lovable was (is?) heavily vibe-coded AFAIK. Allegedly there’s a lot of 1-2 people startups making good money out there, and those were likely impossible without vibe coding (they’d take much more time to build)

The “toy app” feel is really not a big problem if you put some effort into it. It’s very easy to see landing pages made with a one-shot request on Cursor, but if you put some effort into adjusting things, you can get to pretty good design in a fraction of the time.

To be clear, my position is “vibe coding” _must_ include _some_ level of coding by hand (not entirely prompting an AI), at least with the current generation of tools.

Another tidbit, in my personal experience, is that lovable & co are enabling completely non-technical people to push out hot sites, marketing material, etc (including simple interactive experiences, for instance) quite flawlessly and quickly. This would require a dedicated engineer at least, in the past. It’s what the “no code” promise of years past was supposed to enable (IMO it didn’t, webflow/etc are clunky and hard to use even for non-coders).
by int_19h | 2025-08-19 16:01:15+00:00
I've been there at the time, and the pushback against XHTML always struck me as disingenuous. XHTML was not at all difficult to write! The only real argument against it was that it wasn't always valid HTML, and browsers didn't want to support it specifically, so when people published XHTML pages it would sometimes break if the browser tried to interpret it as HTML. But they have broken HTML backwards compatibility so much worse many times since then...
by volkk | 2025-08-19 16:01:25+00:00
i disagree. Faceit and others have really done a great job. Riot's anticheat is also fairly effective. Anyway, it all depends on what you're trying to achieve. If it's casual gameplay, then who cares (although I wouldn't want to play in a server with cheaters even casually). But if you have ranks and a competitive scene, then anticheat is crucial
by rimunroe | 2025-08-19 16:02:45+00:00
Wow! Of course I remember you! I've actually tried to hunt you down in the past to say hi and thank you for all the good times. I thought I found you on Steam recently. If you see a friend request from a Stealth Penguin (https://steamcommunity.com/id/stealthpengu1n), that's me.

I'm doing great these days and hope you are too! That was such a fun time. If you want to get in touch, my gmail address is rimunroe. I'd love to catch up!
by fithisux | 2025-08-19 16:03:18+00:00
Actually, I think removing XSLT is bad because it means we are more tied to javascript or other languages for XML transformation instead of a language designed for this specific purpose, a DSL.

Which means more unreadable code.

But if they decide to remove XSLT from spec, I would be more than happy if they remove JS too. The same logic applies.
by neurostimulant | 2025-08-19 16:03:30+00:00
> In addition to water and cell-cultivated salmon, our saku contains fats derived from canola, sunflower seeds, and algae, soy (an allergen), potato starch, konjac (a root vegetable), beta-carotene and lycopene (natural colors), carrageenan (an extract from red seaweed), and natural flavors.

So, basically a salmon-flavored jelly? I'm actually ok with this as long as there is no harmful substances involved. I wonder how's the texture once it's cooked or grilled.
by spankalee | 2025-08-19 16:03:38+00:00
A few things to note:

- This isn't Chrome doing this unilaterally. https://github.com/whatwg/html/issues/11523 shows that representatives from every browser are supportive and there have been discussions about this in standards meetings: https://github.com/whatwg/html/issues/11146#issuecomment-275...

- You can see from the WHATNOT meeting agenda that it was a Mozilla engineer who brought it up last time.

- Opening a PR doesn't necessarily mean that it'll be merged. Notice the unchecked tasks - there's a lot to still do on this one. Even so, give the cross-vendor support for this is seems likely to proceed at some point.
by herval | 2025-08-19 16:03:52+00:00
there’s no evidence “Tea” was vibecoded (especially because it was launched in early 2023, when tools like Cursor weren’t really widely used). All evidence seems to point to the usual issue 9 out of 10 startups face (and have always faced) - unprotected S3 buckets (this was Tea’s issue), misconfigured firebase or supabase RLS (I made some good money helping startups close these holes a few times) or unauthenticated APIs.
by LegionMammal978 | 2025-08-19 16:05:04+00:00
Oh hey, that thing happened that one could easily see was going to happen [0]. The writing was on the wall for XSL as soon as the browsers tore out FTP support: their desire to minimize attack surface trumps any tendency to leave well enough alone.

I wonder what the next step of removing less-popular features will be. Probably the SMIL attributes in favor of CSS for SVG animations, they've been grumbling about those for a while. Or maybe they'll ultimately decide that they don't like native MathML support after all. Really, any functionality that doesn't fit in the mold of "a CSS attribute" or "a JS method" is at risk, including most things XML-related.

[0] https://news.ycombinator.com/item?id=43880391
by jauntywundrkind | 2025-08-19 16:05:14+00:00
Windows gained a WaitForMultipleObjects, which Linux 5.16 (end 2021) aped with a new Futex2. https://www.phoronix.com/news/Linux-5.16-sys_futex_waitv

There's been a nice stream of improvements to futex2 since.

NUMA support (finally landing!), https://www.phoronix.com/news/FUTEX2-NUMA-Small-Futex https://www.phoronix.com/news/FUTEX2-Improvements-Linux-6.16 (see also this fantastic recent submission on NUMA in general, absolutely critical performance stuff, https://news.ycombinator.com/item?id=44936575)

Io_uring support in 6.7 (2024), (with a nice write up on it speeding up postgresql aio), https://www.phoronix.com/news/IO_uring-FUTEX-Linux-6.7

Small requeue and single wait additions in 6.7, https://www.phoronix.com/news/Linux-6.7-Locking-FUTEX2
by sebmelki | 2025-08-19 16:05:40+00:00
I built Sebuf, a small Go library that generates pure HTTP APIs directly from protobuf definitions — no gRPC required.

Features: auto-generated OpenAPI v3.1 docs, built-in validation (via buf.validate + custom required headers check), helpers for oneofs, and mock servers.

Opinionated: POST-only endpoints to keep RPC semantics pure.

Why: I love protobuf tooling but found grpc-gateway/Connect too heavy for some use cases, especially web/mobile.

Still WIP, expect breaking changes before v1.0, would love feedback and feature ideas!
by griffzhowl | 2025-08-19 16:06:15+00:00
I did check the claims in the post and found they're factually correct, within the vagaries of name meanings and etymology. Here's the post:

--

"No, "Satoshi Nakamoto" does not translate to "Central Intelligence" in Japanese. Here's a breakdown of the name: - Satoshi (さとし) is a common Japanese given name, often meaning "wise" or "clear-thinking." - Nakamoto (中本) is a common Japanese surname, with "naka" (中) meaning "middle" or "center," and "moto" (本) meaning "origin" or "foundation."

While "Naka" could be loosely interpreted as "center," and "moto" as "origin," this does not equate to "Central Intelligence." The name does not directly relate to any specific phrase or concept like "Central Intelligence." It's a common Japanese name with meanings unrelated to intelligence agencies or organizations."

--

I checked the commenter's history after your comment and I agree it's often trollish, but this is just ad hominem and nothing to do with evaluating the accuracy of the content of this particular post.

It also sounds unrealistic to me that there are actually hundreds of kanji for "Satoshi", but here there are 130 https://japanese-names.info/first-name/satoshi/, so it's a large number.

What that means is that in fact there are a huge number of possible interpretations, and saying that it "literally translates" to central intelligence is misleading if you don't mention that it "literally translates" to more than a hundred different meanings too.

You could say "one possible loose translation is central intelligence". That would be fair enough.

Here's a discussion of the meaning on stackexchange: https://bitcoin.stackexchange.com/questions/83886/do-%E3%82%...
by lucb1e | 2025-08-19 16:06:18+00:00
So is metaverse, at least depending on the definition. Second Life is mentioned as an example of one on Wikipedia and that died pretty quickly because it was more of a mechanism instead of a destination in itself. The general concept of hanging out online with an avatar and friends is not gone at all

5G was another hype word. Can't say that's not useful! I don't really notice a difference with 4G (and barely with 3G) but apparently on the carrier side things got more efficient and it is very widely adopted

I guess there's a reason the Gartner hype cycle ends with widespread adoption and not with "dead and forgotten": most things are widely picked up for a reason. (Having said that, if someone can tell me what the unique selling point of an NFT was, I've not yet understood that one xD)
by const_cast | 2025-08-19 16:06:23+00:00
> that a sizable portion of their voting base is too dumb to get an ID

Literally not a single soul on Earth has ever said this.

Rather, what they're saying, which is an indisputable fact is:

- getting an ID requires money and access to a DMV

- DMVs are segregated by race because of prior factors like districting and redlining.

- Black Americans are more likely to vote Democrat.

- Black Americans are more likely to be poor and therefore are less likely to have an ID.

- therefore, Democrats on average have less ID.

Again, this isn't an opinion, it's just factual based off of very simple logic and statistics.

You can literally go look up, right now, what percentage of Black Americans have ID versus white Americans.

Its not a talking point, it's just real. The US is complex and has hundreds of years of extreme racism under it's belt.

Newsflash - that means not everything is perfectly split by race or equality accessible.

> The solution, if this problem exists as they say, is to get everyone proper ID

Wow, you make it sounds so easy.

Why then is it that, despite decades peddling voted ID laws, the GOP absolutely refuses to even humor the idea of making ID more accessible?

Could it be that their intentions arent as pure as yours?
by ameliaquining | 2025-08-19 16:06:27+00:00
The "implicitly tagged as unsafe" thing is not an ABI issue. Extern declarations are necessarily unsafe because the compiler has to trust them to be correct. As of Rust 1.82, extern "C" functions can be declared safe to call: https://blog.rust-lang.org/2024/10/17/Rust-1.82.0/#safe-item...

As for the "shared-library-centric OS" idea, I'm not sure anyone is really strongly clamoring for this (mostly because of the difficulties in getting adoption of any kind of novel OS at all), so it basically makes sense for the Rust project not to prioritize it. Niko's broader definition of "foundational software" seems more presently applicable. But if such a thing were to be attempted then figuring out a good ABI would be an important step.
by quesera | 2025-08-19 16:06:30+00:00
So use profiles for what profiles are good at, and containers for what containers are good at. This works well for me.

I have a work profile with several containers inside, so that I can be logged into, e.g. GitHub and AWS, with multiple accounts at the same time.

I also have a primary personal profile, with a few containers primarily for cookie pollution separation.

I've never struggled with the "Profiles have bad UX" complaint, because I created a few different launchers for Firefox: work, personal, (a few others for special purposes like retail sites), and a default profile that launches the profile manager dialog at startup so I can select from a few dozen less-frequently-used (sometimes single-purpose) profiles. I like to keep separate things separated.

This took 20 minutes to set up, 15+ years ago(?) and has been perfectly convenient for me, but I've also recently read that Mozilla is working to improve profile switching.
by diggan | 2025-08-19 16:07:03+00:00
The Obsidian Sync (official) plugin isn't very clever with its syncing, it does one file at a time, seemingly new requests for each file.

I recently had to sync a new Obsidian vault from scratch, a vault with thousands of files, and it took minutes to complete because of this, even though most files are a couple of KB at most.

Easy to fix and low hanging fruit, but still an issue for us with many files in our vaults.
Show HN: Bloogle – Turn Google Docs into a blog in 5 minutes
by webzz | 2025-08-19 16:07:14+00:00
Hi HN,

I built Bloogle because I was frustrated with how much time it takes to set up and maintain a blog. WordPress felt bloated, static site generators required too much config, and even "simple" platforms had friction.

With Bloogle, you just:

1. Write your post in Google Docs (where you’re already comfortable). 2. Paste the link into Bloogle. 3. Get a live blog instantly, already optimized for SEO.

Some details: - Instant publishing: no CMS, no setup. - Automatic SEO-friendly pages (structured data, indexing, sitemap). - You can map it to your own domain or use a free yourname.bloogle.blog. - You own analytics dashboard

Why I built this I noticed that a lot of indie founders and freelancers never launch a blog because setup takes too much effort. But a blog can be a huge source of traffic and credibility. My thought: why not just use the tool most people already use for writing a.k.a Google Docs and skip the CMS entirely?

What I’d love feedback on - Is this useful enough as-is, or do you need more customization (themes, analytics, comments)? - Who do you think would benefit most: solo founders, agencies, or casual writers? - Any red flags you see in terms of SEO / scaling?

You can check it and try it for free here: https://bloogle.blog

Thanks! I’d really appreciate any thoughts or brutally honest feedback.
by lyu07282 | 2025-08-19 16:07:38+00:00
I don't think anybody thinks this has anything to do with child safety. It's not a coincidence that the UK, US and the EU, all working on implementing similar surveillance and censorship regimes. The platforms will develop the infrastructure, similar to the GFoC just privatized. The legacy media lost all influence with younger generations, just look at what the vast majority of young people think of Israel now. If the media can't fulfill its role anymore they need a big stick.
by madamelic | 2025-08-19 16:07:52+00:00
Very neat! Great job. I am always interested in these sorts of projects that rethink how we communicate and aren't built on the assumption of always-on, always connected to global web.

Few questions:

With the nodes registration being centralized to a single server, doesn't that make that server the main target for attacks? As if an attacker could get into that, they could add themselves, drop people, etc.

Rather than just using something like a single shared secret, have you considered something like Shamir's Secret Sharing where you need the network consensus / multiple people to make modifications to the list. This would distribute the risk, making the central server less 'tasty'.

With this being targeted towards privacy-conscious / high-risk targets such as journalists, what are your thoughts on the privacy being breached if one person gets co-opted / snatched and the other party/parties being "the bad guys". Is that outside the scope or unreasonable? I was trying to think of how you could avoid that, but all of them get killed by thinking if one of the secrets/parties gets compromised, the network itself is compromised, so no amount of keys, checks, consensus, etc would fix it.

I think that last point _does_ break your model of the network being inherent trust vs zero trust.
by xcrjm | 2025-08-19 16:08:09+00:00
I get the impression they are ripping it out because they don't want to sponsor the FOSS volunteer working on it or deal w/ maintaining it themselves. The tracking/advertising take doesn't hold much water for me as adding those things to the page is something developers and companies choose to do. You could just as easily inject a tracking script tag or pixel or whatever via XSLT during transformation if you wanted.
by dragontamer | 2025-08-19 16:08:22+00:00
To clarify, I believe the issue is C++ unordered map iterators and when / where they are allowed to go invalid.

OpenAddressing means that an address of map[thing] could change on insert. Which means iterators and pointer invalidation concepts can go stale on insert.

C++11 standard for unordered_map guarantees this won't happen. But that forces slower implementations.

And now people rely upon the standard so we can't change it. At best we do fast_unordered_map or unordered_map2 with different guarantees.