Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jordic
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
jordic
4y ago
Google is no longer interested in returning good search results, their priority are ads. (Good results are on ads)
2.
▲
by
jordic
4y ago
I use acme as a personal wiki where I can store useful playbooks (executables from there). From sqls to kubectl commands. Just a big wiki with the unix at the mouse.
3.
▲
by
jordic
5y ago
Perhaps we need an expert on design history. Typefaces are a complex thing with lot's of design decisions behind.
4.
▲
by
jordic
5y ago
At my past job we have something like for newsletters and 250k/tasks per day was fine. The only design problem we have had is that if you keep past tasks on the queue table, when it grows it traches a lot cache due to index writes, so
5.
▲
by
jordic
5y ago
This is one of the firsts principes of critical thinking: it's not only about understanding something, it's about being ready to challange it.
6.
▲
by
jordic
6y ago
We do something like this, also we took some inspiration from hashura. Asyncpg it's so fast an ergonomic.
7.
▲
by
jordic
6y ago
Think on it like a middleware that wraps a transaction. It's fine, till you start consuming other Io based services (elastic/solar/...) And you find that this blocks one connection per request..
8.
▲
by
jordic
6y ago
Synthetic event system + render decoupling. Preact uses the event system of the platform (browser) and only renders to it (there's no react native support). Anyway we are using it at prod and allowed us to reduce our bundle sizes ;)
9.
▲
by
jordic
6y ago
Also it'so easy to start making new components dependent on the store, and ending with reusability.
10.
▲
by
jordic
6y ago
I'm more used to preact, it's small it's fast, and it's near the DOM. Last, with preact/htm it doesn't need any tooling :)
11.
▲
by
jordic
6y ago
Cool! Thinking so many times in something like this, but sql it's not easy composable...
12.
▲
by
jordic
6y ago
Our front service it's a nextjs/nodejs project. But I still prefer python :) and our API's are python based, typed async python.. but python..
13.
▲
by
jordic
6y ago
Someone should take care of it, but doesn't seem like a trivial problem.. btw, I also will be so happy to be able to reuse part of twisted core on asyncio services :)
14.
▲
by
jordic
6y ago
I must say that python3.8 does a better job detecting not awaited awaitables. Anyway,asyncio it's not new to python, the stdlib still has asyncore in it. There are still awesome web servers around (threaded) but using "asyncio&quo
15.
▲
by
jordic
6y ago
Mostly agree around reusing existing libs, and being and split point on the community, but I also can't understand why so many detractors. It's a tool and does it's job quit well. Anyway, in my test I prefer explicit and don&
16.
▲
by
jordic
6y ago
Nice one, but.. I prefer sqls that you can debug without rendering.. (it's not so manageable when you deal with ctes, window functions, joins different schemas, custom functions...
17.
▲
by
jordic
6y ago
On one project we use Databases, with a custom opensourced "adapter" for sqlalchemy models: https://github.com/vinissimus/asyncom Our cms, is based on Guillotina ( https://github.com/plone/
18.
▲
by
jordic
6y ago
For example: https://discuss.tryton.org/t/wsgi-server-choice/2766 https://mail.zope.org/pipermail/zodb-dev/2010-December/01389... https://docs.rhodecode.com/RhodeCod
19.
▲
by
jordic
6y ago
We are also using starlette and works quite well.. in combination with asyncpg..
20.
▲
by
jordic
6y ago
The thing is that you can serve a lot of requests on a single core.. (and at least us we pay per core)
21.
▲
by
jordic
6y ago
In our use case, from 12 cores to 2 :) (mostly for ha)
22.
▲
by
jordic
6y ago
With async Django views we can use Django with asyncpg... o_o but middlewares are still synch...
23.
▲
by
jordic
6y ago
Python context managers are a great way to prevent this type of issues. Anyway feels like a bit strange to not use the current connection (from between the transaction) to query things. Perhaps the problem is between the API, because it&#x
24.
▲
by
jordic
6y ago
I would also add to the article, that when you try to alter a busy table add it a timeout (otherwise you will lock the world). SET statement_timeout = 50; Alter .... ;
25.
▲
by
jordic
6y ago
Agree, at least for me, I don't discovered the sqlsuperpowers till I got inside it... I would love to see some of this pretty clever orm migrations applied on a busy potgresql server.. with a bit of concurrency... :)
26.
▲
by
jordic
6y ago
May Django work with multiple tenants on different postgresql schemas? Can Django migrations handle this in an easy way (better than sql).. When projects grow old (+10years), things trend to complicate (lot of hands, lot of changed require
27.
▲
by
jordic
6y ago
Does still django lacks a connection pooling? If I'm not wrong sometime ago I saw people using the sqlalchemy pool on Django projects.
28.
▲
by
jordic
6y ago
That's a nice feature, when landed it?
29.
▲
by
jordic
6y ago
Then you still need to upgrade Django.. (had seen so many sprint points spent on it.. :/)
30.
▲
by
jordic
6y ago
Haha, dB = database. My android keyboard is trolling me :/
More ›