nathanappere

The experience of "you push, provision databases & dependencies in 3 clicks, and it just works" is sadly still unmatched.

I think people just mean "using vector databases to enable RAG".

But we need contracts that go way further what static typing provides. If they add dependant types + ability to enforce the types at runtime so that you can use it on various inputs, then maybe it will be truly useful.

What's a better offering that makes it easier to push projects in production?

But their offering is "frontend oriented", what you describe doesn't work for django / laravel / rails / etc, no ?

Don't know how much you have used ember, but I disagree, it's quite sane as a programming model and ember data is still ahead in terms of developper comfort for client apps.

100% this! I'm amazed at how most issues with React are non-issues with Ember, and still saddened by how often React dev are completely unaware of how these issues have been solved elsewhere.

You can just rephrase it as "an idea alone is worthless without proper execution" which is what is meant.

Curious, have you tried entering people houses when the door is open?

It does if you have blocking calls or you cannot yield to the event loop in time consuming code.

It assumes there is a need for that software. It's not because I can ship the nth clone of flappy bird in minutes that I will?

Note that you do not on websites that are not trying to use your data without your consent. Rephrased: the issue might not be the law.

What are the good projects?

Because most software doesn’t need to be good, but just hit the “kind of does the job well enough” line. It improves velocity for this usecase.

I laughed

After having used Ember for several years I find it very sad they didn't develop a "mobile" offering, the dev experience is fastly superior (especially as it relates to state handling).

Hooks are a bit of a cancer, they leak absolutely everywhere on top of making it quite difficult to reason about re-renders.

"React very much feels like programming using only side-effects" this absolutely nails it.

Fix the rules if the rules are stupid"

"Pay excellent people out of band, for example." why not fix the band ?

You're mistaking corporations for people.

So for you it's the same than being paid by a private corporation?

This doesn't work with the constraint of "staying on AWS" though.

I use a functional version of this that can chain any "callables" + support extensions on the calling interface https://docs.rubykit.org/kit-organizer/edge/Kit.Organizer.Se...

And what's wrong with shedding some light on this behaviour so that it changes and starts complying with the law?

Also: "Your jumping to defend YC companies make me wonder if you're not just a fan boy. Maybe come down form your high horse thinking that you need to defend these YC companies breaking the law?" See where I took it from & how bad it looks?

How does this answer the parent comment at all?!

Really curious, how is it worse with Ruby?

You pretty much only "take responsibility" if you step down.

"Perhaps the War" by Ada Palmer. Incredibly good SG, what a mind she has!

"Not publicly available" is not the same as "there is no service".

The parent comment is about adjusting pay for productivity, what is the reasoning behind "in a world where you compensate for productivity, you'll have to pay more employees that are less productive"?

Interesting use case.

Some quick feedback on the homepage: - "predictable": serverless is not exactly "predictable". On the other end, having a set number of instances is :) - "low cost": this assumes specific patterns of usage under a threshold where it's profitable to use serverless. That's entirely "use-case dependant" & a bit misleading. - "constant speed": so you're saying that the worst case scenario is bounded to 150ms, no matter the data set?

Pointing these out because it makes it read as "yet another DB vendor with some unrealistic claims" :)