1st1

29 ms·

331.
by 1st1 9y ago
We created a number of business applications that used earlier versions of EdgeDB. The list of companies we worked with is on our magic.io page :)
332.
by 1st1 9y ago
Maybe. This is something that we'll have to figure out later.
333.
by 1st1 9y ago
It's closer to the storage layer: postgres is in the core and not directly exposed (i.e. you won't be able to access it).
334.
by 1st1 9y ago
We don't want to distance EdgeDB from graph databases. We just want to clearly show the difference between EdgeDB and, for example, neo4j.
335.
by 1st1 9y ago
We don't want to focus on scalability at this point. Getting the data model and query language right is our top priority. As for scaling, citusdata clearly demonstrates that its possible to scale Postgres, so we are not particularly w
336.
by 1st1 9y ago
Yes, automatic UI generation is something we've been doing with EdgeDB for years in our products. Having a uniform object data model and introspection makes it easy to automatically generated complex nested forms and grids. We'l
337.
by 1st1 9y ago
Thanks for the interest! We'll release a technology preview (along with the source code) in just a few weeks.
338.
by 1st1 9y ago
We'll soon offer a public preview of the database. The license will likely be some form of GPL.
339.
by 1st1 9y ago
EdgeDB is very far from being an "ORM in the database". It properly implements an object data model on top of relational model, along with a properly designed query language.
340.
by 1st1 9y ago
redcrowbar (Elvis) and I (Yury) are the authors of the post. Happy to answer questions ;)
341.
EdgeDB: A New Beginning(edgedb.com)
116 points by 1st1 9y ago|65 comments
342.
A high-performance immutable Map type for Python(github.com)
1 points by 1st1 9y ago|0 comments
343.
Ptracer, a syscall-tracing library for Python(medium.com)
2 points by 1st1 9y ago|0 comments
344.
PEP 550: Execution Contexts in Python(python.org)
4 points by 1st1 9y ago|0 comments
345.
by 1st1 9y ago
Crazy things happen when one abandons his projects.
346.
by 1st1 9y ago
> The event loop is only used when there is nothing going on. In async applications event loop is what actually executes your code and performs IO. In essence, event loops are under load all the time.
347.
by 1st1 10y ago
Development is very active, will release a public beta in a couple of months.
348.
by 1st1 10y ago
Thanks! Did you use new async generators in your tool?
349.
by 1st1 10y ago
Thanks ;)
350.
by 1st1 10y ago
Surprised to see this here :) I'm the author of the PEP, feel free to ask questions.
351.
by 1st1 10y ago
Then for-loops are goto as well.
352.
by 1st1 10y ago
You can call old style coroutines (generators wrapped in asyncio.coroutine) from async/await code directly. @coroutine def foo(): return 123 async def bar(): await foo()
353.
by 1st1 10y ago
I suggest to proceed with the PEP if you have a good idea about the API. Get it out there, it's not required to spend hours on mailing lists - other people can do that if they like it.
354.
by 1st1 10y ago
That was irony :)
355.
by 1st1 10y ago
Can't wait to install Kaspersky on it! :)
356.
by 1st1 10y ago
I have to say this is the first time in years when there's a feeling that MS has outpaced Apple. The product looks amazing.
357.
Microsoft Surface Studio(theverge.com)
599 points by 1st1 10y ago|552 comments
358.
by 1st1 10y ago
As far as I know, the only issue is that we don't support Windows atm. Which in most cases is fine -- you can develop on windows using vanilla asyncio, and use uvloop when deploying on *nix.
359.
by 1st1 10y ago
> Do you guys have any plan to support porting from Django/Flask to Uvloop? I don't think it makes a lot of sense to run Django/Flask on top of uvloop--the performance benefits will be negligible, if any. > If I have a
360.
by 1st1 10y ago
> At what scale(in terms of number of users or server load) would choosing async based web frameworks over traditional web frameworks like Django/Pylons make sense? Using async makes sense where you want to handle 100s/1000s of

More ›