Tweetovi

	Yury Selivanov @1st1	12 h
	Odgovor korisniku/ci @zeeg Are stacktraces in core dumps considered normal? ;)
	Prikaz razgovora ·

	Yury Selivanov @1st1	3. velj
	Odgovor korisniku/ci @JLdork edgedb.com/blog/edgedb-1-…
	Prikaz razgovora ·

	Yury Selivanov @1st1	31. sij
	Odgovor korisniku/ci @sethmlarson @Apple That was the main motivation for HTTP/2 I believe!
	Prikaz razgovora ·

	Yury Selivanov @1st1	31. sij
	Odgovor korisniku/ci @zooba @valignatev @Apple This makes it even more terrifying.
	Prikaz razgovora ·

	Yury Selivanov @1st1	31. sij
	Odgovor korisniku/ci @Apple And why would you even put a upper limit on password length? I see this stuff to often, there must be some "security" practice that some companies follow...
	Prikaz razgovora ·

	Yury Selivanov @1st1	31. sij
	Odgovor korisniku/ci @Apple I like how apple thinks that the password is weak because it's longer than 32 characters.
	Prikaz razgovora ·

	Yury Selivanov @1st1	31. sij
	Really, @apple? :( pic.twitter.com/XbJuxylmEo
	Prikaz fotografije ·

	Yury Selivanov proslijedio/la je tweet
	David Cramer @zeeg	29. sij
	An early concept of what you’ll see later this year from Sentry. Come help us build it! sentry.io/careers/ pic.twitter.com/dDmnb2xVWG
	Prikaz fotografije ·

	Yury Selivanov @1st1	30. sij
	Odgovor korisniku/ci @paulbiggar @vimota @ancil11 Check out EdgeQL edgedb.com/docs/edgeql/ov… It's strictly typed and query arguments / output is binary so you can get rich types (or json) out of it.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @asumaran @rauchg Was simply a typo in the blog post.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @nicolasparada_ @rauchg We call it EdgeQL: edgedb.com/docs/tutorial/…
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @danimad2000 @rauchg i 3 ostali 🎯 We plan to gradually start using rust for slow python parts.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @danimad2000 @rauchg @postgrest_org EdgeDB is based on Postgres and is currently written in a mix of Python and C (although that's about to change). Client libraries can be in any language; we currently have native Python and JS drivers. Also GraphQL via HTTP. More coming soon.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @JefferyHus @rauchg Solving n+1 is the top of the iceberg :)
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @joegaudet @JefferyHus @rauchg Surely it's possible. Also EdgeDB isn't an ORM and doesn't have lazy execution semantics. Quite the contrary, we designed EdgeQL to be able to fetch any complex nested object data in one query so that you don't need to rely on lazy loading semantics.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @JefferyHus @rauchg Yes. Querying an n+1 relation can cause an extra JOIN operation internally but this is what relational DBs are good at when done correctly (and EdgeDB inherits PostgreSQL strengths). Also EdgeQL/GraphQL queries in EdgeDB are always compiled into one atomic data fetch operation.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @_drakels @rauchg You can use GraphQL out of the box with EdgeDB. When you need something on top of what GraphQL and SQL give you can consider trying EdgeQL.
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @_JustinMoon_ @rauchg Also check out edgedb.com/blog/a-path-to… which talks a bit about history & motivation
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @_JustinMoon_ @rauchg the only way to challenge the status quo :)
	Prikaz razgovora ·

	Yury Selivanov @1st1	28. sij
	Odgovor korisniku/ci @_JustinMoon_ @rauchg We've been working on it for some time :) Although we started to call it EdgeDB and really focused on it about 3 years ago.
	Prikaz razgovora ·