Can someone explain what this does differently to the status quo under the hood?
HN user
markl42
GraphQL Nerd @ Yelp // https://twitter.com/mark_larah
Apparently the source code has been lost so probably not
We use https://github.com/Yelp/pgctl heavily, which uses s6!
Has any streaming service trained a model to actually understand the music itself to work out what other songs would be of a similar vibe/genre?
My favorite band (vulfpeck, and more recently jack's solo stuff) often branch out into different genres, and it's a bit of whiplash when it goes to another song just because the artists are similar / appear together in other places.
At the risk of hijacking the comments, I've been trying to use OTel recently to debug performance of a complex webpage with lots of async sibling spans, and finding it very very difficult to identify the critical path / bottlenecks.
There's no causal relationships between sibling spans. I think in theory "span links" solves this, but afaict this is not a widely used feature in SDKs are UI viewers.
(I wrote about this here https://github.com/open-telemetry/opentelemetry-specificatio...)
How big of an issue is this for GQL servers where all queries are known ahead of time (allowlist) - i.e. you can cache/memorize the ast parsing and this is only a perf issue for a few minutes after the container starts up
Or does this bite us in other ways too?
Don’t use flaxseed!
https://www.reddit.com/r/castiron/comments/b4pxaq/yay_kenji_...
I wonder if the price is inflated
I’m not familiar with the work that OWASP does, other than the cheat sheet series.
The cheat sheet series is amazing - a great resource to defer to when you don’t know or want to think about how to do <x>, you just want to look up and implement the industry standard.
It’s a great reference, and I use it lot. <3 to the folks working on that :)
I kinda thought Apollo would buy GraphCDN. Both great products!
Oh, this is a good idea. Can’t wait to try it out.
Well I was actually just trying to make a dumb joke about “chip plants” but I see how that comes off now…
Maybe only kinda sorta relevant, but I interned at RefME for a summer - basically a Zotero competitor. There was a lot of value (for users) in scraping web pages to autofill to author, title, date etc so it could generate the references, something I started to work on (but then they got bought out so not sure what ended up happening)
Any I could've imagining this being a paid pro feature down the line
So you know how we were talking about Dostoevsky earlier
GraphQL makes a lot more sense at the scale of a big company where every team rewrites the same AJAX endpoint logic to fetch the same set of core entities (except in delightfully subtly different ways). Having “the one true” representation of your User object or Business object, but having the flexibility to fetch subsets of fields is huge.
And having a smaller team plug their page-specific types into the graph and just provide the foreign keys and have it “just work” is great.
GraphQL for me solves more of an organizational challenge rather than a pure technical challenge.
how did they um...."defuel" their bodies and such in the air?
More security layers doesn’t always == better security
The “nth nth and nth” character of your password means they’re storing your password in plaintext, and Auntie Nora is more likely to have it written on a postit cos she can’t use a password manager.
“Name of your first school” etc type questions are obviously awful
My favorite is HSBC kept asking me to enable “voice identification” every time I phoned up as a “more secure way” of authenticating myself...which to me smells like a cat and mouse game between who has the better ML model. Oh also https://www.computing.co.uk/news/3010450/hsbc-voice-recognit...
Good.
When I moved to the US from the UK, I already had British HSBC accounts, so thought it made sense to open up an HSBC account and credit card. Got a $200 credit limit (thanks?), awful app, terrible customer service...eventually got fed up and closed all my accounts. Good riddance.
Also side note while I’m on the topic - to log into chase and do stuff, I enter my password. That’s it.
To log into HSBC or any other UK bank, you need to enter the 8th, 3rd and 19th letter of your password, app generated security token, digital security key password, the 822nd digit of Pi and the current orbital trajectory of Jupiter.
Can I please please just have normal 2FA...
Big fan of sourcegraph, we use it at work. super excited to see this happen.
(I've been using grep.app until now which is awesome too!)
Cool! Similar project I maintain: https://programming.protips.wiki/
Might be worth checking the code but
tree shaking eliminates unused functions from across the bundle by starting at the entry point and only including functions that may be executed
Is what this code (tries to!) do
It's undeniable that there's a learning curve to GraphQL - but at the end of the day, it's just adding another investment that developers may choose to make their lives easier in the long run.
As in industry, we're okay with a frontend JS framework - React (or vue or angular) being part of the baseline set of investments you make when building a website. It's just considered the cost of doing business. (But that wasn't always the case! I for one don't miss using jQuery...)
I imagine GraphQL will get to a similar place - where the investment is more well understood and accepted.
(Of course common sense still applies - if a website is simple enough that it doesn't need a frontend js framework then don't use one - same goes for graphql, don't use it if you really don't need it)
I'll throw a shoutout for a top tier project - https://github.com/zgoat/goatcounter
Using it for some personal stuff, and does absolutely everything I need it to, and then some.
I love the ethos of the project, and whilst it's open source, there's a hosted option that looks super reasonable too.
Shameless plug opportunity! On the topic of "more complication on top of cloudformation", I made a tool that lets you split up cloudformation files with import syntax.
Shameless plug time! I made https://composerize.com/ for exactly this - converting all the docker run commands from tutorials and such into reusable compose files :)
Nice! I wonder if there will be a mapping between compose and the cli maintained as part of this?
(Disclaimer, I maintain https://composerize.com/, hoping this helps us track parity)
Care to share?
If you already have static type checking, is that not enough? Are there scenarios where proptypes will throw/show warnings at runtime that flow wasn't able to catch at build time?