fleetfox

I don't understand how this or all these magic skill bundles and methodologies get traction and why they are so popular. It's either plain worse or has serious trade offs.

At that point this who submission should be auto filtered out since there are dozen of these and they are barely distinguishable except for couple of opinioned choices.

It also feels much less magical when you see what people actually waste it on.

And how exactly is your NATed ipv4 address better? This seems backwards.

I can't really talk about Ruby. But PHP is much more static and surface of things you have to care about at runtime is like magnitude smaller and there already was opache as a starting point. And speaking of something like JIT in V8 is of the most sophisticated and complicated ever built. There hasn't been near enough man hours and funding to cpython to make it fair comparison

Even for reducing the context size it's probably worth it. If you have to go back back and forth on both problem and implementation even with these new "large" contexts if find quality degrading pretty fast.

Is it really complaining about quality of AI? The dangerous part is that slop will be harder to detect.

I was hoping this would be a satire

If you are interested PEP703 describes the scenarios pretty well: https://peps.python.org/pep-0703/#motivation

SQLAlchemy does. I get that DjangoORM is more convenient and might be good enough. But powerful seems like wrong adjective.

In what way "most powerful"? If you do anything more involved than CRUD it falls apart pretty fast. You can't express most of the things you can do with raw SQL since there is not intermediate DSL like you do with SQLA. You can't hydrate arbitrary object graphs. It's slow, for deep queries building back objects is slower than actual SQL round trip.

It's very easy to use but it's also very limited and i often find myself dropping down to RawSQL or even having SQLA connection in my Django projects.

Faster this, faster that. Is it finally segfault free? I've tried it like 3 times in span of last year with different projects only to find out it segfaults at runtime or when installing package.

There are many applications where htmlx is objectively the best tool. But i really hate all the hype around it and people pushing it as react replacement.

Django is WSGI/ASGI framework not a webserver. What do they actually use to terminate HTTP?

It's an attempt to solve "player readability". It's common complaint in CS:GO. Many pros play with color vibrance cranked in driver or monitor settings.

What is the reason rust maintains llvm fork? I've looked at readme with no clear answer. Is it just convinience and turnaround time?

I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js

Metal API. I can not understand why they did not just go with Vulkan.

Great power metrics but performance seems disappointing? 5600x is generation old mid range CPU.

WebGPU is WebVulkan

Hopefully it's closer to Kotlin or TypeScript

Priecīgus Ziemassvētkus!

When it comes to REST it's important to return correct response code. As to what comes in body is mostly convention and there are no standards. Here is an example for rest: https://github.com/Microsoft/api-guidelines/blob/master/Guid...

JSON-RPC is a bit more concrete: https://www.jsonrpc.org/specification#error_object But again what you put into data is up to you.

Response structure might also depend on the client (content negotiation)

Do you know if the ORM solution have the same `a` suffix for async interface? I really hope there is more elegant solution for all this.

Interesting. What about web sockets?

Today there is little reason to use HHVM since modern PHP comes with JIT

I don't want to come off rude but i don't see anything "promising" or novel about this.

Probably large chunk of that difference is consumed by interconnect (infinity fabric)

Decorators and type hints are not the same thing.