zerr

Since vibe-coding solved the issue of manpower, why stick to Electron and js frameworks?

I believe it would be helpful for those who would want to continue development, contribute to the project.

Pro-AI people now argue that the code is ephemeral nowadays, we should not look at it like we don't look at generated assembly (most of the devs). So in this regard, sharing only the "assembly" doesn't make sense, it's like sharing only the binaries and calling that open source (before LLM days).

For vibe coded open-source projects, I believe the prompt session/history should be shared as well.

I mean, is it OpenGL, Vulkan, Metal? etc...

What do they use for graphics and audio?

Not sure how long the current subsidized pricing would last. Also, the vast majority of software shops can't afford those subsidized prices anyway.

If you are product-driven why not go into Product Ownership roles? It certainly will be more satisfying compared to prompt "engineering" clerk "career".

I have an opposite concern - how do you find companies that don't force devs to become prompt engineers?

You are doing it right. Publicly shaming them on HN is the only way to get a real customer service.

If we follow that logic, I believe it means that you would be quite happy in the Product Owner role, or in the role of a client who outsources the actual development activities. I wouldn't.

Yes, engineer experience/happiness is part of the equation. The company also thinks that agentic workflow will clutter the codebase.

As an engineer, the enjoyment from the process is not less important, or should I say more important, than the enjoyment from shipping a final product.

I code by hand (sigh) and copy paste some snippets once in a while from a web chat LLM. This also means every single line of such snippets gets reviewed and anaylzed. Usually, these are some arcane Win32 API usage where otherwise I'd have to dig into old forums. I don't want to become a prompt engineer so I stay away from "agentic" workflows.

Also, those "smart" TVs aren't really smart, besides that data grabbing, and are really slow. So connecting some mini PC is the way to go.

Yeah. I thought maybe someone from Gracie family joined something :)

Self-assigned moderation doesn't belong to HN. Also, considering the wide cultural background of the userbase. I have no idea what's your "gotcha" style means. Neither your explanation helps.

As for the specific wording, replace "Most" with "Many", the point still stands.

Again, please refrain from moderation and silencing attempts. Thank you.

The point is to eliminate the birth lottery - so if you happen to be born in a bad place, moving to a better place should be just a matter of your wish.

> No becuase citizenship implies deep cultural and philosophical values as well.

If that was the case, most existing citizens would lose their status :)

> You cant switch those that quickly

It is much faster with the globalization and youtube-ization. After all, "We all live in Amerika".

Btw, the notion of what we call today a citizenship arose just at late 18th century. So, it's not something fundamental that has always been there.

So citizenship is yet another contract - between an individual and a society. To eliminate the unfairness of lottery, changing citizenships should be as easy as changing jobs.

The point is to have a system that does not discriminate based on lottery.

How is discrimination by citizenship more acceptable than e.g. discrimination by ethnicity or race? All of these are outcomes of birth lottery.

While the language is interesting, sadly, nobody is using it in the wild. Maybe due to cumbersome deployment options? The ability to produce native standalone executables would boost its usage I believe.

No, I'm talking about C++Builder specifically. They made it sub-par to Delphi.

No. While it did had cross-platform support years ago, nowadays it is Windows-only, including targets.

I wish Lazarus had support for C++ as well. Pascal/Ada's English prose syntax is a deal breaker.

C++Builder as well? Any updates regarding cross-platform support?

Or just replace all of the apps? Why would a user use apps if everything (eventually) can be achieved with an AI?

Cocamidopropyl betaine is a must for me.

Ah, yes, it is much better now!

Any plans for upgrading to cheese grater Mac Pro 2019? :)