veeralpatel979

Congrats on shipping!

I like how quickly GitHub is shipping new features now, compared to earlier: the mobile app, Actions, Sponsors, security scanning, etc.

That said, I was a little disappointed that Discussions is essentially identical to Issues :(.

While I can't pinpoint any specific issues I've had with Issues for discussions, I was hoping GitHub found, and found solutions for, pain points that users didn't know they had with Issues.

I think the problem of determining whether a company is secure, given a particular attacker, is one that needs to be worked on.

Unfortunately I haven't made any progress in discovering a solution that would accurately determine if a company is secure or not.

Given that an org's security team, or even the world (in case of zero days), may not be aware of vulnerabilities that exist in a company's infrastructure, how do you solve this problem?

If anyone wants to chat about this, I'm at veeralpatel4@gmail.com

Got it! And how do you identify users of your open source version who you can upsell your paid version to, since there's no sign up needed to start using PostHog?

Or is this something you don't do?

Hey - congrats on launching! I'm adding Posthog to my list of codebases to check out.

Can you talk more about your tech stack?

As an aside - it seems like most of the analytics companies I've heard of went through YC: MixPanel, Heap, Amplitude!

Congrats on launching!

How does this compare to something like OpenPhone (https://www.openphone.co/)?

Netlify (http://netlify.com/) works great for static sites as well!

Great work!

- Recognize that while the jargon is often complicated, the underlying ideas are not. As you read, keep asking yourself what the basic idea of what you've learned is.

- Think about the topic yourself from first principles as you read.

"Economics is the study of how we deal with scarcity.

One approach is a market-based approach where each item has a price and whoever pays the price gets it. However, this isn't really fair towards the poor.

Another solution is a socialistic approach where everyone is given equal amounts of everything. However, this can lead to rationing.

Another solution is the government decides who gets what. It doesn't have to give everyone the same amount of everything. But this is vulnerable to corruption and also this seems like a hard problem to solve.

Another solution to scarcity would be a lottery-based approach..."

- Watch videos on a topic if you're not getting something.

To be fair the bad choices are what allowed them to ship quickly, get to product-market fit, and get to the point where the bad choices started to hurt them.

Most startups never see the effects of their bad (or good) choices because they go out of business.

Hey - great work! This project can save me a lot of work writing integrations, which I find tedious at times, so I'll take a look at it.

One piece of feedback: it's confusing that the org's name is Polybit, the site is https://stdlib.com/, and there's also something called Autocode.

Please consider choosing one name for all of them (Standard Library, preferably).

Got it. If you don't have any data that's shared between pages, I can see how this works.

Hey - author here. This is my first time hearing of alt.js. How does it compare to more popular solutions like Redux and MobX?

Hi - author here. Thanks for mentioning Apollo. I've actually abandoned maintaining any data state in my global stores. I just use Apollo and provide a refetchQueries to my useMutation call to update my UI after mutations.

https://www.apollographql.com/docs/react/api/react-hooks/

Hi - author here. I haven't used react-easy-state unfortunately. But like when building a company, the best product doesn't always win: the company that executes the best does.

Executing well includes building a great product, but it also requires marketing, which the Redux community has done a great job of to the point where it's the de facto solution.

Hey - author here.

I agree that libraries for certain things, like MobX/Redux or Formik, may be overkill.

What's more important, though, is that people choose an appropriate equivalent to these libraries. Replace the library, but not the method of organizing state.

For example, feel free to replace MobX/Redux in my post with your own global state management solution. But I recommend replacing it with a global state management solution, not something else.

Another way of looking at it is that they are using their technology to help defend the country where the company was created.

> Unfortunately, finding these kinds of products is hard, and I don't quite understand why.

I'll reckon a guess: most companies aspire to differentiate themselves and retain customers by building brands.

The alternative is race-to-the-lowest-price commodification and continual, cutthroat competition.

Ok; ignore that specific example -- if you needed to share a piece of state among many components in different places in your component tree, how would you do it?

Hey - author here. React is just simpler for me to reason about. A app has many pages, a page has many components. I can write components; I can write Redux/MobX code; I can pass data between components. Things work.

But absolutely, my speed of development when using React is lower than when I'm using server-generated HTML in a Rails app.

On the other hand, I can do things with React I can't do with server-generated HTML.

Hey - author here.

Try Redux; acemarke has been evangelizing Redux Toolkit [1] recently and it looks great for a beginner not familiar to the Redux ecosystem.

But also - if Redux just isn't clicking for you, or if it is but you feel like writing it is unnatural - know that you're not alone.

Learn MobX, learn how to manage state with context and hooks [2], learn Apollo Client.

Yes it's a lot of up-front work, but you really do need to find a state management approach that works for you if you want to write non-trivial apps, in my opinion.

[1] https://redux-toolkit.js.org/ [2] https://kentcdodds.com/blog/application-state-management-wit...

Author here.

I see the appeal of the simplicity of this approach, and this is how I handled state in my application before I knew what state management was.

But how do you deal with the problem of many of the components in your tree needing to know what theme is set?

Hey! Author here.

You don't need to put the username of the logged in user into Redux, but if multiple components across different pages need to access this data, you should make it globally accessible.

You can choose Redux/MobX for this, or you can roll your own solution with context and hooks.

I'm actually learning more about the context/hooks approach myself.

Kent C Dodd wrote a great article on this topic I'd recommend:

https://kentcdodds.com/blog/application-state-management-wit...

Author here.

You can try this, but I don't think it'll turn out well!

You don't want to have a bloated, disorganized global store...what you're doing now, moving state into global state only if needed, is the right way to go.

Maybe! But also, as a user, I expect to do more and more in my browser.

I would find it strange, and probably switch to a competitor, if my preferred airline for example made me install (and keep updated) a desktop app in order to book a flight.

Author here. The way I think about it is, the web was designed for rendering static markup. JavaScript was designed for adding small amounts of interactivity.

Instead, we've managed to turn the web into a full-blown application platform. Do you think Tim Berners-Lee envisioned something like Google Maps being created in the browser?

Now, I concede that JavaScript isn't the best language for creating client-side apps. I hope someone applies some first-principle thinking and creates a language expressly designed for this purpose.

Considering how many people and developers use web apps, this could be an area where someone can have a massive impact.

I wonder if WebAssembly is the solution here?

> form libraries remain the one thing I've never really seen a need for

I felt this way too, until I used Ant Design's form component (which uses rc-form under the hood).

Form libraries take care of validation for you, allow you to specify an initialValues prop, and give you a handleFinish={values => ...} prop so it's easy to run your own API call when the user clicks "Submit".

Plus, Formik lets you model the form values using a TypeScript interface which I like.

To me, Formik provides several advantages over not using a form library, and no disadvantages except a small learning curve, so that's why I recommend it.

Hey - author here. I did not mean to imply that state management is only useful to mitigate the prop drilling problem. In fact, in #2, I give another example where state management is useful.

Measuring how productive software engineers are.

If you could solve this problem, you could convince management why engineers need offices, for one.

Strange. Deviceplane now only has 56 stars.

The solution isn't bankrupting fossil fuel companies.

The solution is finding viable replacements for these companies, whether it's solar, wind, nuclear, or something else, and then scaling them so they can serve everyone.

Finding viable replacements that people _want_ to use, along with carbon taxes, subsidies, etc should be sufficient to force some oil and gas companies to pivot to clean energy and make the rest die out or become substantially smaller.

And, this way, we would avoid a massive decrease in our quality of life, it would actually be practical, and consumers would benefit.