kvirani

But isn't that just a few refactoring prompts away?

Imho it just speaks to importance of first mover advantage, land grab, and most importantly distribution distribution distribution.

It's not fake, it's reality. And things have always has been this way.

Was just about to write this. Glad I'm not alone.

We're in the 56k modem era of generative AI, so I wouldn't be surprised if we had that in the next few years, or weeks.

Aren't AAA game companies hurting at least partly because of the blowback from those models?

Isn't UE4/5 fully source available?

Yes! #3 is key to making one humble

You have my curiosity. Like what and how did you find it?

I don't come here for Reddit threads.

I agree and like this article, but something about calling those that believe otherwise Grifters feels a bit too harsh and polarizing to me. I know some who do believe AI will cause immense software role displacement, and wouldn't label them this way.

Nothing a bumper sticker can't fix (seriously)

Wow... It's only January. I'm so excited to see what you release in February and beyond!

I only made it through 1/4 of the paper before running out of time.

Very interesting though.

Maybe the article mentions it, but is a sustainable countermeasure for job seekers only applying on websites where employer has to pay to post?

This is why I still come to HN. Thank you!

> Provide so much syntactic sugar as to cause any C developer a diabetes-induced heart attack.

Haha love this!

Nice, congratulations. It must feel so surreal launching this!

One of my biggest learnings from doing a bunch of web MVC through Rails over the years is that the framework should heavily discourage business logic in the model layer.

Some suggestions:

- Don't allow "callbacks" (what AR calls them) ie hooks like afterCreate in the data model. I know you don't have these yet in your ORM, but in case those are on the roadmap, my opinion is that they should not be.

- That only really works though if you not strongly encourage a service aka business logic layer. Most of my Rails app tend to have all of these as command aka service objects using a gem (library/package) like Interactor.*

* It's my view that MVC (and therefore Rails otb) is not ideal by itself to write a production-ready app, because of the missing service layer.

Also, curious why existing ORMs or query builders from the community weren't leveraged?

Disclaimer: I haven't written a line of Rust yet (more curious as the days go by). I'm more curious than ever now, thanks to you!

And that right there is a solid moat

Maybe with something like instant messaging vs community platform it's justified? Unclear myself tbh

Or water even

Why re v3?

This is a great idea, thank you! What about details in the original comment, though? Can you easily add a link to the original HN comment?

I hope that feedback didn't discourage you from continuing with your approach to software development and teamwork.

This is awesome. Why do you think you never found success with it?

You have my attention re crackhead kids. Source?

I see. So you can still use these assistants without the privacy concern then. So why abandon?

Wait what. When I hold the main button on android and say exactly that, it means I have an always on microphone??

Nice! How big in size of FTEs is this company and what industry is it in?

Interesting about exposure via YT. Any links to share there?

Sorry what does alpha mean here?

Does each web request to an app server have to hit the disk on the same server? And if so, for the entire request duration? Also, what about horizontal scaling which also means that the db is on a different server (likely with secondary / replicated DBs)