gitgud

Mainframes survive, but serving a much tinier portion of the market than they used to.

I would argue mainframes rebranded to "cloud" which is ubiquitous and more people interact with this computer than any other type of device... only difference is that it's a browser instead of a terminal

So at that tiny 500kb size I imagine it could be compiled to web assembly, and run entirely in the browser right?

Couldn’t find a link, is that hard to do?

This is one of the reasons why native proprietary coding agent runners like claude-code, codex, grok-build etc are so dangerous for privacy… you just don’t know what “secret sauce” they’ll add in the next update…

It’s much safer to use something like opencode and use models via their API… however, the tradeoff is that it will never perform as well as it does in their native agent runners…

Not allowing full screen is the most insane thing for a “chat app ported from the web”… the browser probably has a better experience now…

Kirsten: All of this, to me, illustrates how quickly things are moving. I mean, when you really think about it, the whole tokenmaxxxing thing has become a thing, peaked, and now is seen disfavorably, within six months

Pretty sure from inception the phrase “tokenmaxxing” was never seen in a positive light…

Article and this post seems to be AI generated… but this is a good quote

AI coding assistants hallucinate package names. They confidently suggest npm install some-plausible-sounding-package for packages that do not exist. Attackers monitor those hallucinations and register the names - a technique now called slopsquatting

Slopsquatting is a hilarious name for this

I realize I don’t have much knowledge about the best way to architect applications

There is no “best way”, it always depends on what you are building.

The main advice I would give is to always remember that there’s trade-off’s in every architectural choice…

I guess some general tenants might be… “great architectural solutions…”

- Allow new features to be added, without much complexity

- Have reliable and clear abstraction layers

- Allow tests and typing to validate it’s correctness

- Manage clearly understood limitations, rather than implicit surprise limitations

we need to stop filming people, and we need a societal norm that treats a violation of this ban on par with spitting someone in the face.

Agreed. Filming strangers in public is making everyone scared to have fun trying anything new, as they’re afraid of online mockery…

I started believing at 4 years old when going to a christian school, then stopped believing a few years later when I realised I couldn’t see any proof of any god watching, planning or influencing the world in any way at all…

Finding bugs in PR’s are exactly what GitHub copilot, GitHub cursor bot and tonnes of other PR bots already do…

What does the AS stand for?

A polite fyi, when skim reading this, it looked like it said AssNotes…

Well damn, start the countdown till the inevitable exploit of this.

I’m thinking maybe 1 or 2 weeks from now…

It's cheap to change code, it doesn't mean you have to add more of it...

Considering they’ve become a 1 trillion USD company, they’re truely moving fast and breaking things…

I’m a new solo dev with almost no audience. If a large org or a well-known developer sees the idea and ships a similar implementation, they can get more attention immediately than I can get in months. And in the end I get nothing for open-sourcing my project.

This has always been a fear of open source development… but in reality it’s over exaggerated, thousands of FOSS ideas are posted every day…

My advice would be to treat posting your project like a launch, and get all the readme’s, docs etc ready before posting, so it has the best chance of growing an audience, which seems to be your goal.

But if you really don’t want other people to recycle your idea, then open source is not for you…

Putting this here in the hope that someone at Anthropic reads it.

Needs more sensationalism to get their attention, like “Tell HN: Claude won’t implement this basic feature!” /s

I don’t think they “got lucky”. nextjs is an old project now, and for a long time it was the simplest framework to run a React website.

This is why most open source landing pages used nextjs, and if most FOSS landing pages use it, then most LLM’s have been trained on it, which means LLM’s are more familiar with that framework and choose it

There must be a term for this kind of LLM driven adoption flywheel…

Really interesting! Is there a list of all supported CAD operations? Can I “revolve” 2D sketches? Can I make assemblies?

For instance it does not make sense to have an MCP to use git.

What if you don’t want the AI to have any write access for a tool? I think the ability to choose what parts of the tool you expose is the biggest benefit of MCP.

As opposed to a READ_ONLY_TOOL_SKILL.md that states “it’s important that you must not use any edit API’s…”

Another feature idea for you:

There’s an extension that I loved called “Proven” (now archived) which uses keybase.io proofs to show other proven accounts next to hn users

https://github.com/dschep/proven

Also about this:

Mermaid Diagram Rendering

Honest question, how often are people posting raw mermaid diagrams in comments here?… I’ve never seen one

Was made using https://cables.gl/ (not by me though)

We built machines that learned every single solution from StackOverflow… so developers don’t need it anymore

Well yeah, business has literally always extracted value from open source software, that’s one of the main benefits of it… (although license violations have been unprecedented with AI)

“Creating value” in open source has never been about capturing value at all, it’s always been about volunteering and giving back, and recognising the unfathomable amount of open-source software that runs the modern world we live in

“Capturing value” is the opposite of this, wall-gardens, proprietary API’s, vendor lock-in, closed-source code… it’s almost antithetical to the idea of open source

so projects are built whether or not they're good ideas

Let’s be honest, this was always the case. The difference now is that nobody cares about the implementation, as all side projects are assumed to be vibecoded.

So when execution is becoming easier, it’s the ideas that matter more…

Just like with CNC though, you need to feed it with the correct instructions.

CNC relies on precise formal languages like G-code, whereas an LLM relies on the imprecise natural languages

How is this different from a README.md with a code block?

There’s also the much more common case of a competitor coming in with a similar product that has a few more features matching the customers’ requirements… which explains the endless product development treadmill that companies find themselves on.

Software doesn’t win by being “finished” it wins by out competing other software

Fine I’ll chime in… The main advantage tailwind has is that utility css can be composed without needing to worry about hierarchy. This is not true for bootstrap.

This makes tailwind much more predictable for component based UI architecture, in your example you would define a <Button> component so that verbosity of css is explicitly defined once where it’s used, not buried within a bootstrap framework somewhere.

If you’re not using a component based architecture, then tailwind is much more verbose, but still useful, as copying/pasting tailwind HTML is insanely easy and reliable. This is not true for bootstrap.

Bootstrap has it’s place, it’s good for cases where you’ I don’t care about the details of how it looks. But with component based architectures, tailwind is a much more flexible and better abstraction in my opinion.

I guess the main argument is that there will always be technical and non-technical people in companies. Some people don’t even like prompting to get an AI image, let alone prompting to fix/maintain software…

No, managers don’t want to be using Claude Code… tools change