And on the latent space bit, it's also true for classical models, and the basic idea behind any pattern recognition or dimensionality reduction. That doesn't mean it's necessarily "getting the right idea."

Again, I don't want to "think of it as a probability." I'm saying what you're describing is a probability distribution. Do you have a citation for "probability to express correctly the sentence/idea" bit? Because just having a latent space is no implication of representing an idea.

At the same time, your argument that "you'll be replaced by GPT in no time" is also an opinion that you've not supported with any data; the same thing that you're accusing the OP of.

I mean If I stopped reading opinions, 99% of the HN comments would disappear.

I understand the argument for things being "explicit" in Python, but then I just prefer Java if I'm going to be very verbose about what I want (I'm only talking about backend APIs here). It's just my opinion that whether explicit is good or not depends on the level of abstraction we're interested in, and I don't believe that explicit is always good. (I like the concept of meta-algorithms, for example)

But if there's a one-person project that needs to be scaled quickly, I prefer Rails. (The article mentions how Django makes model fields explicit in the models file, but doesn't talk about schema.rb in Rails which doesn't require you to view each migration to know how the database looks.)

Yes, big projects in any language can get messy, but that's a software engineering problem, not a framework problem.

I recently wrote a FastAPI project that was db-driven, with all the necessary test cases, etc. The amount of lines it took to express the controller, the schemas and models separately, the dependencies for auth and stuff, and especially elaborate test cases was pretty substantial. Yeah, the code was all explicit, but it was not enjoyable.

In today's era, however, I have not yet found a need to use a proprietary language.

Our bad assumption is in thinking that only the final output matters, regardless of when and where it is delivered. Like saying that it only matters if the train arrives at the station, regardless of when it does.

The problem is anyone depending on us downstream will get impacted. And yes, estimation is tough, requires foresight, and maybe a lot more things, but that's what being a professional means.

The whole world runs on deadlines and timelines. Even a president is elected for a specific duration. If you're in a B2B setting, the customer demands (sometimes even contractually binding) at least the Quarter when something will be delivered.

Time is the only common denominator by which different activities can be coordinated. Without some heed to time, there will be no coherence.

Comments URL: https://news.ycombinator.com/item?id=42162948

Points: 1

# Comments: 0

Being "built" on something does not in itself imply value. What has to be taken into account is also "value that is added." If the underlying platform had high intrinsic value in itself, then no value would have had to be built on it to profit from it, which would mean WP Engine would not be the only entity profiting from it.

And to add to the reductio ad absurdum, are PHP engineers required to "donate part of their salaries" to the project just because "they're profiting off of that language?" (/sarcasm)

Comments URL: https://news.ycombinator.com/item?id=41002082

Points: 1

# Comments: 0