emptysea

One caveat with testing library’s getByRole function is that it’s really really slow.

In my experience with medium side components it would take seconds to find the element vs a few milliseconds for getByTestId.

I’m curious if remix will remain general purpose or if it will gradually drift into just being used for Shopify things.

I'm curious how you'd compare yourselves to https://metronome.com which is another player in the space?

I think the issues you encountered may be due to the specific libraries. Lots of the pre-typing libraries haven’t adopted static typing, like Django and Celery and then when your project is 95% Django and Celery you’re SOL.

I’m not even sure it’s possible to have Django typed without reworking the ORM, I’m thinking about reverse relations, .annotate(), etc.

Yes, there are type stubs for these libraries but they’re either forced to be more strict, preventing use of dynamism, or opt for being less strict but allowing you to use all the library features, at the cost of safety.

I think in the end, new libraries built with static typing in mind, like Pydantic, FastAPI, and Edgedb, are the answer.

I specifically liked the discussion on how tool making is often discouraged @ 20:37 - end.

Curious what dark patterns you’ve noticed in Discord?

Yeah it's really straightforward to setup Github/Gitlab/Circle/etc. to run your various deploy / ssh commands for you, then you don't need actually access to the box.

Really nice being able to open up GitHub and manually kick off a deploy -- or have it deploy automatically.

I found the option repricing history fascinating.

"what about me", cries the person with a $300 RSU price while the stock is trading at $100 -- it always seems like the first thing that comes up in company chat when the company stock tanks. Part of the deal I suppose. Other option is to jump ship, but that's scarier in a bear market.

Also jibed with:

> my general advice to folks would be to stay where you are as long as you’re reasonably happy day to day and feel like you’re learning at a good rate. Even if your effective compensation has declined a bit, it’s very hard to determine if the compensation at any other company will hold up either.

I dig the Netflix style navigation, I'm curious if there are plans to support arbitrary ROMs for classic games. Probably can't host them, but maybe an easy way to load one from local?

edit: should have scrolled down in the readme more, they say in the non-goals section:

Directly playing locally stored game content (ROMs, etc.) (Technically possible by using a local web server, but not a primary use case)

their desktop clients are electron but their iOS app is native, and works pretty well IMHO

I think it’s pretty common for open source projects and even companies to use a combination of Discord and Discourse. Discord entering the forum space makes a lot of sense.

If they can figure out how to make the forums public / exposed to search engines then it could entirely remove the need for Discourse.

Ah I think this was mentioned in a comment on a previous thread:

https://news.ycombinator.com/item?id=29595441

Glad to see it finally open sourced!

Wow I'm surprised they only got a $8 million penalty.

I wonder how much the execs benefited from it

They do some very strange stuff in the celery codebase like most of the classes inheriting from dict and splitting things into multiple packages and repos. Like is anyone actually going to resuse kombu (celery’s messaging package)?

I think that’s actually the Slack origin story you’re thinking of, but honestly discord could have the same origin.

Ably is solid and generally much cheaper than the alternatives like pubnub.

Also they come with reliable message delivery built in (pusher doesn’t I think). Not really sure how it compares to this project.

Anyways just a happy user of ably, used it at work.

I'm interested to hear more about your tailwind rewrite? Any interesting challenges and any plans on open sourcing it?

I’m curious if you worry about Airtable incorporating your add on into their core offering? I feel that’s always my worry about building on top of someone else’s platform.

Interesting, only about 36MB for the wasm postgres

from the article:

> If a component has a bunch of props and not a lot of descendants, it can actually be slower to check if any of the props have changed compared to re-rendering the component. (I don't have a source for this claim, but I've seen prominent developers like Dan Abramov make this case on Twitter)

It might vary from application to application but this seems like something that could be tested.

Also on the other side of the coin, you have memo all the things: https://attardi.org/why-we-memo-all-the-things/

How do you limit the queries allowed in the UI aka prevent someone from making a really slow / large query? Do you general not use supabase directly in the UI and write an API that your front end can call instead?

I’ve never used TRPC but curious to learn more about the slowdown. Is that a slowdown with Typescript or a runtime thing?

The quote from the article specifically mentions the Google Cloud sales org:

> Employees who work in the Google Cloud sales department said that senior leadership told them that there will be an “overall examination of sales productivity and productivity in general.”

Yeah that’s interesting. Flow uses OCaml, ditto for their Python type checker. Hack is C++, and Relay uses Rust. (Although I think some of the other type checkers are migrating from OCaml to Rust).

Curious about the perf implications with using a JVM language for a compiler vs native.

The company that google bought for flights (ITA?) was built on SBCL and flights is still written in it. Pretty huge codebase from what I heard

Yeah the QR code login is slick, TikTok also uses that.

The only caveat for implementing is that you essentially need to have a mobile app for your site, while SMS/email auth are more universal.

Curious how Parcel stacks up to Vite.

Vite seems to have the Vue community behind it which is pretty larger.

Both have much better performance than webpack, so between the two probably doesn't matter too much.

I find the big difference for me when building an API vs working on a UI is the testing. I think backend APIs tend to be much easier to test than UIs. For the backend, it's mostly Request in Response out, check they look good and the side effects (database, caches, queues, etc.) are performed etc. For the UI you have a lot of async stuff going on and writing non-flakey tests is tricky and verbose with the current tooling - using react testing library which is better than enzyme, but still harder than testing a Django endpoint.

I've given Slate and Draft.JS a go in the past and they both aren't great from a developer experience perspective and are generally buggy. Slate also had issues where it would throw a type error and break the page, Draft.JS struggles with cursor placement issues.

Yeah the rolling deployments gotcha really stuck out to me. I think most PaaS will provide that by default anyways because who wants downtime during deploys?