guggle

Yes... for a second I thought I would have to rewrite all the QT apps I made. This is the stuff of nightmares.

This is really hilarious... I just followed the third given example (https://kristaps.bsd.lv/absdcon2017/database-conclusions.htm...) and that's how it goes: "the simplicity of SQLite is a lie". Ok, thanks, I'll pass on the "BCHS" stack then. I now consider this website satire.

If you're going to promote a stack, try at least to showcase all its components in the first example you give. Where is the SQLite part in your "BSD, C, httpd, SQLite" ? https://learnbchs.org/easy.html

Hello world apps don't mean much.

"With regard to Rails and Django specifically then that is a matter beyond comprehension. Neither Ruby nor Python should ever have been utilized for web development. They are simply ill-suited because they are too slow."

In what alternate reality does the author live ? Or in what alternate reality do I live ? Because in more than 20 years, in all web projects I've worked, the backend language (be it python, php, java, whatever) has never been the bottleneck. Granted, I've not worked in Google-scale evironments, but saying any web development should be done in Go is incredibly misleading. And I have nothing against Go, I quite like it actually.

Thanks !

I see jesper's Request has its body as a string. How would you manage (very) large request body ?

What's the state on:

- web frameworks / servers ? (ie. is there something like Sanic that is actively maintained ?) I imagine it's too early for a consensus.

- database drivers ? (postgresql is important here. I can live without an ORM)

Looks like what we used to do more than 15 years ago with taconite. I guess I'm now old enough to see history repeating in web development tools.

Somehow I managed to miss the obvious warning... thanks !

I get roughly 46ms from a cheap distant vps with no particular care for performance in my Django app so these numbers are strange.

> While I agree that Qt is an excellent tool in itself, and I love using it for development, it remains a fact that people wanting to use it will need to first learn a not so excellent programming language, C++

I won't comment about C++, but anytime I had to use QT, it was with the official Python binding. The "developer experience" was rather nice I must say.

> Edit: One thing that would be nice in PHP is decorators.

15 years I used to say "I wish PHP had feature X just like in language Y". But there's a moment where it's better not to wait and just to use language Y.

Indeed... and if one is not convinced, a simple walk along the beaches of Normandy will make it very clear.

"if it happened to 30 people -without any facts- out of millions and if it's relayed by greedy attorneys then it's worth posting on HN"

First there was the horror stories about the SSDs dying prematurely. And now another story, even more FUD non-sense.

Meanwhile I'm enjoying the best laptop I ever had.

"Which program is easier to read?"

For me it was the second. Am I the only one ?

> consistent across OS versions and platforms.

This is an upside for the developer only. And a downside for the user as the GUI will probably not be consistent with its OS.

> over the past decade it seems like many apps have eschewed this anyway

And I regret it.

I found this one even more boring than disgusting. And it was pretty disgusting.

I had one of these. It's still considerably behind. Thermal design is terrible, overall build quality is passable and battery autonomy is very bad.

> Gemini is a really cool protocol but i appreciate some aspects of the web like images and videos (with the builtin players, no JS please).

With Gemini it's up to the client to add the appropriate players. lagrange does this just fine when presented and audio link.

I second this (although I'd just stick with JSON-RPC 1.0). REST has its uses case, but alas it's now so ubiquitous that developers don't even think about wether they should or should not use it.

For machine to machine communication between heterogenous systems, the simplicity of JSON-RPC means one can implement a client easily in any language. Also creating method stubs is trivial. The payload is still human-readable should you use it from the browser and it's not prone to debates and interpretations around the meaning of HTTP verbs. All you have to know is what method you want to call and with what arguments... something that is natural to all developers, while they almost always get the endpoints/resources/verbs thing wrong.

It took me a while too :-P

Sure.

All good things if you ask me.

Also, this measure is not really about french culture. It is about culture in general. If you visit an art museum most of time it's filled with art from everywhere. The quai Branly museum comes to my mind here, but really most museum have exhibits of foreign works.

> The things inexperienced users think are a big deal (in your example, line count) usually end up not being a big deal.

Indeed... like Python novices complaining about significant white-space.

It really reminds me of this hilarious 2008 keynote by Cal Henderson: https://youtu.be/i6Fr65PFqfk?t=2255

(relevant graphic: https://ibb.co/yV6bN9H )

> most software seems to typically get only heavier over time!

It's often the case for end-user applications, but I find that most languages/runtimes tend to get better with time (and work of course !). There's a similar trend with the PHP runtime.

Upvoting that.

Indeed. Convienience vs. freedom. Ignorance vs. knowledge.

Way to go...

Yes, I get it and my comment was intended tongue-in-cheek. But still... not everyone goes to YT for monetization in which case I really think it's just better not to use it. I'm probably too old but I remember a time when we had plenty of visibility on the web without platforms dictating the content.