jdauriemma

Hi there - I work at Apollo and I'd be happy to help you migrate off our old CLI. That utility was sort of a hodgepodge of tools that we ended up either replatforming to our `rover` CLI or, in the case of code generation, recommending that folks use GraphQL Code Generator. It's a testament to that utility's sprawl that I can't guess your use case just by your name-drop of it. I realize the irony in my saying that since it sort of plays into this narrative, but FWIW all the functionality (and then some) of `apollo` is still actively maintained, just not in that particular codebase or form factor. Let me know if there's anything I can do to assist.

FWIW Apollo Client is actively maintained, has a lot of new features, and is preparing a v4 release (currently in Alpha). We'll be celebrating 10 years next year :)

That's not true (the deprecation part, anyway) and I know of at least one React team member who has spoken publicly to that fact.

I work for a SaaS company and a frequent refrain is "the most important thing we sell is trust." I suspect our users would be extremely upset with us if one of our engineers decided to learn about our production systems by turning things off and seeing what breaks. If you insist on reducing the State Department or any other government function to a "complex system," then DOGE is doing exactly that - FAFO in prod on a service that's 239 years old and has nukes. It's beyond irresponsible.

With enough ketamine and frog memes you might actually convince a certain senior advisor that's a good idea. Then in a few weeks some credulous Hacker News readers will be there to congratulate them!

> RoR is great at first but in my experience quickly becomes full of hard to diagnose bugs, its magic metaprogramming seems too tempting for developers to use and leads to all sorts of problems.

I think this is true. With Rails you want to be very deliberate about who you hire (there are lots of "Advanced Beginners" out there) and how you vet and manage abstractions outside of the MVC architecture. But if you can stick to those tenets, you'll be rewarded with a very productive engineering org.

I think API design in general is hard to do well, GraphQL isn’t going to help or hurt that.

I think you might be operating under some incorrect assumptions.

> anytime a client requires knowledge of your DB schema

GraphQL is very explicitly _not_ a representation of your database schema. The “schema” being referred to here is the GraphQL schema, not the SQL schema. I might be missing some nuance in your comment, but I do think this is a very important point to drive home.

Normalized caching, pagination, and code generation are some features that many developers find appealing and are supported out of the box by many GraphQL clients.

Yeah that’s a fair point. The protocol may be open but much of the discovery/hosting is siloed in maybe 2-3 services. It doesn’t take much imagination to see where that could lead.

Apologies, I’m probably missing some nuance but I don’t see anything in your reply that is meaningfully different from the comment above. The existence of major platforms does not necessarily challenge the notion that podcasting is open by design. The advent of exclusivity deals seems to confirm the standing assumption that podcasters are in control of distribution.

Could you elaborate a bit further? I don’t see why this is necessarily true.

The state of the art of GraphQL tooling around securing and versioning has evolved significantly. You may want to take another look at what’s out there.

Whenever I encounter a really strongly-worded, abrasive opinion like this I look for context. Does anyone know what relationship the author has with the ESM standardization process? Did they offer feedback that was dismissed by TC39? If so, I might be able to empathize with someone who feels that they have been left out or unfairly treated. Otherwise I think the tone distracts from the substance of the article and is also a lousy way to talk about others’ good faith efforts to move JS forward.

I’m guessing king’s pawn or e5 openings

Looks amazing, I think the Professional tier seems like a great value in particular. I would absolutely pay more than $10/mo for this tool if UI design were part of my day-to-day.

Holy moly, i.reddit.com is so much better. Thank you for the recommendation!

You might also be interested in https://github.com/bignimbus/game-of-life-n

Behold the Long Covid Experts of the Hacker News Comment Section! Check your expertise and empiricism at the door; we have enough contrarianism, anecdotes, and spurious correlation to explain everything!

Gray branding? Label spam?

As a person who has successfully worked from home for six years alternating between management and software engineering, this brand of nonsense and hypocrisy really bugs me. I take pride in my hard work, empower my team and yes, I feel “a part of something” while doing my job remotely. Some people desire an office environment. That’s great! Don’t impose that preference on those of us whose effectiveness does not require it. There’s no hard data that conclusively proves one way is better than the other. If Gladwell cares so much about my showing up to an office, I invite him to pick my kids up from preschool when there’s a COVID closure and open the door when my oldest gets home from school.

The author's conclusion is intuitively true to me. I suspect, though, it wouldn't convince a skeptic because of a complete lack of empirical evidence.

You could save a lot of overhead using regular shell scripts (sh) instead of flask

We are making progress on CO2, it's just not nearly fast enough. This solution potentially treats the symptoms quickly while we slowly cure the disease.

TIL, thank you!

I think vi is short for visual-insert

Maybe this is a bit too forgiving of Twitter, but do they even see Mastodon as a threat worthy of stifling in this manner?

Source?

If you ever ship an Airflow integration, consider this an official request to call it Air Bud.

If anyone's interested in a Web Audio API trombone, I made one a while back:

https://jdauriemma.com/trombone.js/

https://github.com/bignimbus/trombone.js

I don't see Airtable here yet. That team managed to make relational databases user-friendly to a consumer market without compromising the core features a power user might expect. Hats off to them!