React Miami

5K posts

React Miami banner
React Miami

React Miami

@ReactMiamiConf

React developers conference, April 29-30, 2027 🌴 Organized by @g2i_co | Get tickets to @aiemiami happening the same week!

Miami, FL Katılım Mayıs 2021
1.1K Takip Edilen5K Takipçiler
React Miami
React Miami@ReactMiamiConf·
Congratulations again, @_christinacodes, on your first ever conference talk! It was inspiring 👏
React Miami tweet mediaReact Miami tweet media
English
0
3
18
527
React Miami retweetledi
CodeTV
CodeTV@codetv_dev·
We asked developers: what are you excited about right now? @ReactMiamiConf
English
1
4
8
944
React Miami
React Miami@ReactMiamiConf·
React Miami's first ever Spanish talk, 'El futuro de React es ahora', delivered by the incredible @midudev!
React Miami tweet mediaReact Miami tweet mediaReact Miami tweet mediaReact Miami tweet media
English
2
5
56
6.8K
React Miami retweetledi
CodeTV
CodeTV@codetv_dev·
How are developers upskilling now that everything is changing? We asked at @ReactMiamiConf, and the answers weren't what we were expecting to hear.
English
0
4
12
746
React Miami
React Miami@ReactMiamiConf·
This year's impactful keynote delivered by @aurorascharff on 'Designing the In-Between States with Async React'
React Miami tweet mediaReact Miami tweet media
English
0
0
16
3.7K
React Miami
React Miami@ReactMiamiConf·
The iconic React Miami shirts designed again this year by our talented friends at @basementstudio 🔥
React Miami tweet mediaReact Miami tweet media
English
0
0
16
495
React Miami retweetledi
React Miami retweetledi
The Narcan Plug
The Narcan Plug@deanna_dunne_·
@ReactMiamiConf genuinely one of the most fun conferences I’ve attended. Met some super cool people after being pretty isolated over in corporate big tech for a while. Still looking to keep that momentum and connect with more women in tech 💕
The Narcan Plug tweet mediaThe Narcan Plug tweet mediaThe Narcan Plug tweet mediaThe Narcan Plug tweet media
English
1
1
14
614
React Miami retweetledi
Devlin Duldulao
Devlin Duldulao@devlinduldulao·
Outstanding job by the whole @g2i_co crew at @ReactMiamiConf for organizing such an amazing event. I highly recommend it for learning and networking with some of the best React developers in the community. Will definitely be back next year 🫶🏼 Peace out.
Devlin Duldulao tweet media
English
1
1
11
466
React Miami
React Miami@ReactMiamiConf·
Massive thank you to our small but powerful team of volunteers! We couldn't have done this without you! A special shout out to @lrusinou, our Head of Volunteers, whose been helping since the first ever React Miami!
React Miami tweet mediaReact Miami tweet media
English
4
0
30
726
React Miami
React Miami@ReactMiamiConf·
The people are truly what make React Miami so special - not their job title but the amazing energy and positivity they show up with!
React Miami tweet mediaReact Miami tweet mediaReact Miami tweet mediaReact Miami tweet media
English
0
3
22
3.6K
React Miami
React Miami@ReactMiamiConf·
Hallway? You mean runway? 💅
React Miami tweet mediaReact Miami tweet media
English
0
2
32
2.8K
React Miami retweetledi
Anselm Eickhoff
Anselm Eickhoff@anselm_io·
As promised, yapping more on @jazz_tools After launching the v2 alpha at @ReactMiamiConf our focus has been polish and perf, and there is a lot to do. Often, refactoring and nailing down semantics go hand in hand with performance. We realized this again over the last couple days, working on clarifying the difference between “batches” and “transactions”. Jazz v2 is unique in that it offers both globally consistent MVCC-style ACID transactions as well as local-first, eventually consistent writes (this is actually the default). But then we realized that even for the eventually consistent writes, it sometimes makes sense to group them into units, which we called “batches”. Initially, we thought of this as a pure perf optimization primitive and were quite loose with their semantics compared to transactions, where strictness really mattered. For example, in transactions you clearly want all-or-nothing and rollbacks, but we didn’t really think this was important for batches. But then, trying to actually implement the perf optimizations, we realized that per-row bookkeeping in large batches made them basically pointless. So perf guided us towards a clearer meaning for batches: they should also be all-or-nothing, now only being separated from transactions by one clear distinction: multiple concurrent batches can all be accepted and participate in merge-previews, while only one of multiple transactions gets accepted, resulting in global consistency and linearizability. With all the rows per batch sharing one fate, the bookkeeping overhead disappears and the decision for which tool to use in each case becomes crisp: - eventual consistency ok but need operations to have truly independent fates? Use separate batches. - eventual consistency ok and operations sharing fate ok or even desired as a logical unit? Use one batch. - need global consistency? Use a transaction. It’s fun to see how this loosens up complexity throughout storage format, query subscription updates, sync protocol etc.
Anselm Eickhoff tweet media
English
2
4
23
1.6K
React Miami
React Miami@ReactMiamiConf·
React Miami wouldn't exists without our Founder, @gabegreenberg! Thank you for everything you do for our incredible community!
React Miami tweet mediaReact Miami tweet media
English
2
1
25
874
React Miami
React Miami@ReactMiamiConf·
Honored to have @sethwebster, Executive Director of the React Foundation, make a surprise appearance and talk about the future of React 👏
React Miami tweet media
English
0
1
5
825