snowflake VS React

If you're not distributed, use an incrementing integer.

If you're distributed, look into vector clocks[1] or snowflake[2]

[1] https://en.wikipedia.org/wiki/Vector_clock

[2] https://github.com/twitter-archive/snowflake/tree/snowflake-...

MongoDB ObjectId Time, Clocks, and the Ordering of Events in a Distributed System Snowflake

There are so many of them in big data, e.g. Kafka, Spark, Flink, Delta, Snowplow, Finagle, Deequ, CMAK, OpenWhisk, Snowflake, TheHive, TVM-VTA, etc.

Twitter built Snowflake https://github.com/twitter-archive/snowflake/tree/snowflake-2010

that being said, I have seen people acting weird about the whole thing, I don't care if you're mad at HYBE or BIGHIT for not telling him, what I care about are these people acting as if Jimin cannot deal with this or handle it himself. why they are THEY asking an explanation to be given to them? this is none of your business, he's a grown man and he can handle it himself. it's funny because even if he was to talk to someone about this, we will never know and that will be him dealing with his issue. they sit on twitter.com and try to play BTS manager and think they how BTS should be managed and HYBE needs to do things their way. they have managers for a reason and we are not the ones, I can't even believe this whole thing blew up so much.

React Official Site

Websites and Web Apps: Popular for high-performing "Jamstack" sites on modern frameworks like React and Next.js.

Note: Astro supports a variety of popular frameworks including React, Preact, Svelte, Vue, SolidJS, AlpineJS and Lit with official integrations. While for other frameworks e.g. Angular and Qwik, you may still benefit from this tutorial and you would need to further set up the community maintained framework integrations.

The most common and well known is React, with many others sharing this space, such as Svelte, SolidJS, Angular, Vue, Qwik and more. All are impressive feats of engineering and come with bold statements.

GitHub | npm | website

React (GitHub: Facebook/react)

In conclusion, the use of good practices and the components’ adjustment to the official React documentation is crucial. Correct state management, components’ atomization after SRP (Single Responsibility Principle, centralizing logic after DRY (Don't Repeat Yourself) decoupling from external components and the achievement of a highly cohesive internal logic are practices that minimize problems' solving time, lower error rate and allow for stability and scalability in our applications.

Next, I selected the technologies and frameworks I want to focus on during this challenge. For frontend development, I'll be exploring Reactjs, Vue.js, Bootstrap, Next.js, and MUI. For backend development, I'll be diving into Express, Django, Node.js, PHP, and Firebase. Additionally, I'll be learning Kotlin, React Native, and Flutter for mobile development, and APIs, PostgreSQL, Cloud, and MongoDB for full stack projects.

To understand more in depth how both {useState, useEffect} work you can visit the official React website. In addition, another helpful source is w3schools website, that is my personal favorite. It goes straight to the point with examples that you can try in their own browser. Lastly, if you need a more technical source, the mdn web docs will help you.

> but it's not the primary selling point of React - in fact, it's not a selling point at all. Don't believe me? Just go to http://react.dev and look - no where on the site does it say that React is a hyper-performant library

Because now everybody know that it's not the case. But if you check the first video announcement from Facebook a decade ago or so, performance was definitely at the front, above everything else.