Podcasts about settimeout

Fostering Conversations with Utah Foster Care

Play Episode Listen Later Dec 4, 2024 56:01

Scott and Wes dive into your questions on Hono and SvelteKit, partitioned cookies, redirect codes, and using Rspack instead of Vite. Plus, they share insights on quoting projects, interview best practices, and whether you should slow down those speedy loading spinners. Show Notes 00:00 Welcome to Syntax! 00:50 Brought to you by Sentry.io. 02:23 Apple developer accounts and certificates. 06:58 Hono, SvelteKit, and using them together. 11:14 Rspack & Rsbuild over Vite? Rspack, Rsbuild. Rolldown, Rollup. oxc. Turborepo. 21:01 Quoting projects without seeing under the hood. 25:26 HTTP cookies, partitioned cookies, and chips. Partitioned Cookies. 30:29 Redirect codes; 301, 302, 303, 307 418 I'm a teapot. 36:22 Gaining inspiration for talks and posts. 40:02 My loading state is too fast! Should I use setTimeout? setTimeout Docs. 42:29 Interviews and landing the job. 49:50 Sick Picks & Shameless Plugs. Sick Picks Scott: Stainless Steel Cookware. Wes: Dim Lightbulbs, steelpan.guy on TikTok. Shameless Plugs Scott: Potluck Submissions. Wes: Syntax on YouTube. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

tiktok apple interview conference types gaining rust socials loading vite redirects quoting sentry roll up syntax webpack sveltekit settimeout

Ep 49: Looking Back ~ 25 Years of Utah Foster Care

Play Episode Listen Later Jul 2, 2024 49:12

What began as a bold experiment in Utah now celebrates 25 years of nurturing families and transforming lives. As we reflect on a quarter-century of dedicated service in foster care, we take a moment to appreciate the profound impact that Utah Foster Care has had on countless children, families, and communities Building on Bold Beginnings Twenty-five years ago, a visionary idea took root in Utah—to create an organization solely focused on recruiting, training, and supporting foster families. Through the leadership of Governor Mike Leavitt and partnerships with community and state agencies, Utah Foster Care emerged as a unique entity dedicated to serving the needs of foster children and the families who care for them. Commitment to Children First At the heart of Utah Foster Care's mission is an unwavering commitment to putting children's needs first. As shared by Brian Young, a regional trainer, the primary goal is to ensure that every child in foster care feels safe, understood, and supported. Brian’s moving recollection of a time when the reality of a child's loss deeply resonated with him emphasizes the importance of empathy and awareness in foster care. Supporting Foster Families The organization’s success also lies in its continuous support for foster families. Debra Lindner and Liz Rivera, co-hosts of the podcast, illustrate how Utah Foster Care goes beyond initial training by maintaining long-term relationships with foster parents. This ongoing support helps equip families with the skills needed to provide nurturing and stable environments for children who have experienced trauma. Recognizing and Addressing Challenges Utah Foster Care has always been proactive in addressing systemic challenges. From embracing cultural diversity to implementing inclusive practices, the organization has made significant strides. Mike, a clinical consultant, and Les, a trainer, discussed efforts to understand and honor the cultural backgrounds of children in care, particularly those from Native American and Latino communities. The Evolution of Training and Understanding In the early years, foster training was more behavior-focused. Over time, it has evolved into a trauma-informed approach grounded in brain science. Understanding the brain's development and the impact of trauma has revolutionized the training provided to foster parents, emphasizing the need for compassion and tailored support. A Vision for the Future Looking ahead, Utah Foster Care aspires to have families waiting for children, not the other way around. The organization remains committed to adapting based on continuous learning and the evolving needs of children and families. The involvement of Governor Cox and First Lady Abby Cox has brought unprecedented attention and resources to the cause, promising even greater progress in the years to come. Conclusion As we commemorate 25 years of Utah Foster Care, we celebrate the resilience of the children, the dedication of foster families, and the passion of the staff. With over 16,000 families trained since 1999, Utah Foster Care stands as a beacon of hope and compassion. For those inspired to join this journey, remember that you don’t need to know everything to become a foster parent—you just need to be willing to learn. To find out more about foster parenting and other ways to get involved, visit utahfostercare.org. Here’s to another 25 years of making a difference, one child at a time. var gform;gform||(document.addEventListener("gform_main_scripts_loaded",function(){gform.scriptsLoaded=!0}),window.addEventListener("DOMContentLoaded",function(){gform.domLoaded=!0}),gform={domLoaded:!1,scriptsLoaded:!1,initializeOnLoaded:function(o){gform.domLoaded&&gform.scriptsLoaded?o():!gform.domLoaded&&gform.scriptsLoaded?window.addEventListener("DOMContentLoaded",o):document.addEventListener("gform_main_scripts_loaded",o)},hooks:{action:{},filter:{}},addAction:function(o,n,r,t){gform.addHook("action",o,n,r,t)},addFilter:function(o,n,r,t){gform.addHook("filter",o,n,r,t)},doAction:function(o){gform.doHook("action",o,arguments)},applyFilters:function(o){return gform.doHook("filter",o,arguments)},removeAction:function(o,n){gform.removeHook("action",o,n)},removeFilter:function(o,n,r){gform.removeHook("filter",o,n,r)},addHook:function(o,n,r,t,i){null==gform.hooks[o][n]&&(gform.hooks[o][n]=[]);var e=gform.hooks[o][n];null==i&&(i=n+"_"+e.length),gform.hooks[o][n].push({tag:i,callable:r,priority:t=null==t?10:t})},doHook:function(n,o,r){var t;if(r=Array.prototype.slice.call(r,1),null!=gform.hooks[n][o]&&((o=gform.hooks[n][o]).sort(function(o,n){return o.priority-n.priority}),o.forEach(function(o){"function"!=typeof(t=o.callable)&&(t=window[t]),"action"==n?t.apply(null,r):r[0]=t.apply(null,r)})),"filter"==n)return r[0]},removeHook:function(o,n,t,i){var r;null!=gform.hooks[o][n]&&(r=(r=gform.hooks[o][n]).filter(function(o,n,r){return!!(null!=i&&i!=o.tag||null!=t&&t!=o.priority)}),gform.hooks[o][n]=r)}}); Want to learn more about becoming a foster parent? First Name* Last Name* PhoneE-Mail Town State*Select a StateUtahOut of StateCounty*Select a CountyBeaver CountyBox Elder CountyCache CountyCarbon CountyDaggett CountyDavis CountyDuchesne CountyEmery CountyGarfield CountyGrand CountyIron CountyJuab CountyKane CountyMillard CountyMorgan CountyPiute CountyRich CountySalt Lake CountySan Juan CountySanpete CountySevier CountySummit CountyTooele CountyUintah CountyUtah CountyWasatch CountyWashington CountyWayne CountyWeber CountyOUT OF STATEHow did you hear about us?*How did you hear about us?BillboardCare CommunityChurchDCFSEventFacebookFamily/FriendFoster/Adoptive ParentInstagramPartner AgencyPresentation (digital)Presentation (in person)Previously LicensedPrint MediaRadioRaise the FutureTelevisionUFC EmployeeWebsiteWhich type of Care Community?*ChurchBusinessWhich Church Organization?* Which Business?* Δ /* = 0;if(!is_postback){return;}var form_content = jQuery(this).contents().find('#gform_wrapper_1');var is_confirmation = jQuery(this).contents().find('#gform_confirmation_wrapper_1').length > 0;var is_redirect = contents.indexOf('gformRedirect(){') >= 0;var is_form = form_content.length > 0 && ! is_redirect && ! is_confirmation;var mt = parseInt(jQuery('html').css('margin-top'), 10) + parseInt(jQuery('body').css('margin-top'), 10) + 100;if(is_form){form_content.find('form').css('opacity', 0);jQuery('#gform_wrapper_1').html(form_content.html());if(form_content.hasClass('gform_validation_error')){jQuery('#gform_wrapper_1').addClass('gform_validation_error');} else {jQuery('#gform_wrapper_1').removeClass('gform_validation_error');}setTimeout( function() { /* delay the scroll by 50 milliseconds to fix a bug in chrome */ }, 50 );if(window['gformInitDatepicker']) {gformInitDatepicker();}if(window['gformInitPriceFields']) {gformInitPriceFields();}var current_page = jQuery('#gform_source_page_number_1').val();gformInitSpinner( 1, 'https://utahfostercare.org/wp-content/plugins/gravityforms/images/spinner.svg', true );jQuery(document).trigger('gform_page_loaded', [1, current_page]);window['gf_submitting_1'] = false;}else if(!is_redirect){var confirmation_content = jQuery(this).contents().find('.GF_AJAX_POSTBACK').html();if(!confirmation_content){confirmation_content = contents;}jQuery('#gform_wrapper_1').replaceWith(confirmation_content);jQuery(document).trigger('gform_confirmation_loaded', [1]);window['gf_submitting_1'] = false;wp.a11y.speak(jQuery('#gform_confirmation_message_1').text());}else{jQuery('#gform_1').append(contents);if(window['gformRedirect']) {gformRedirect();}}jQuery(document).trigger("gform_pre_post_render", [{ formId: "1", currentPage: "current_page", abort: function() { this.preventDefault(); } }]); if (event && event.defaultPrevented) { return; } const gformWrapperDiv = document.getElementById( "gform_wrapper_1" ); if ( gformWrapperDiv ) { const visibilitySpan = document.createElement( "span" ); visibilitySpan.id = "gform_visibility_test_1"; gformWrapperDiv.insertAdjacentElement( "afterend", visibilitySpan ); } const visibilityTestDiv = document.getElementById( "gform_visibility_test_1" ); let postRenderFired = false; function triggerPostRender() { if ( postRenderFired ) { return; } postRenderFired = true; jQuery( document ).trigger( 'gform_post_render', [1, current_page] ); gform.utils.trigger( { event: 'gform/postRender', native: false, data: { formId: 1, currentPage: current_page } } ); if ( visibilityTestDiv ) { visibilityTestDiv.parentNode.removeChild( visibilityTestDiv ); } } function debounce( func, wait, immediate ) { var timeout; return function() { var context = this, args = arguments; var later = function() { timeout = null; if ( !immediate ) func.apply( context, args ); }; var callNow = immediate && !timeout; clearTimeout( timeout ); timeout = setTimeout( later, wait ); if ( callNow ) func.apply( context, args ); }; } const debouncedTriggerPostRender = debounce( function() { triggerPostRender(); }, 200 ); if ( visibilityTestDiv && visibilityTestDiv.offsetParent === null ) { const observer = new MutationObserver( ( mutations ) => { mutations.forEach( ( mutation ) => { if ( mutation.type === 'attributes' && visibilityTestDiv.offsetParent !== null ) { debouncedTriggerPostRender(); observer.disconnect(); } }); }); observer.observe( document.body, { attributes: true, childList: false, subtree: true, attributeFilter: [ 'style', 'class' ], }); } else { triggerPostRender(); } } );} ); /* ]]> */

110. Jasmine Tea と日本の中高生向けIT教育 w/ yoichiro

Fukabori.fm

Play Episode Listen Later Jan 27, 2024 42:01

Tably CTOのyoichiroさんに、Jasmine Tea、プログラミング言語を新たに実装、日本の中高生向けIT教育などについて語っていただきました。話したネタJasmine Tea とは？ブロックプログラミングとは？ファミリーベーシック現代の言語で、プログラミング初学者がGUIアプリを作るのは大変Jasmine Tea の想定ユーザー新たに言語を作ると考えたときに何から考え始めるのか？インタープリタの自作、とは？Web上に言語を実装する場合に大変だったことは？JavaScript のメインスレッド専有への対応setTimeout() によるペナルティブラウザの差とデバイスの差による苦労中学生向けの技術の授業でのIT教育高校の情報Ⅰ で教わる内容教育を起因とする日本のIT業界の課題教材の重要性@JasmineTeaProgJasmine Tea に関する問い合わせSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

web javascript settimeout

8 Tricks When Using the Fetch() API

Play Episode Listen Later Aug 21, 2023 19:39

In this Hasty Treat, Scott and Wes talk about 8 tricks to try when using the Fetch() API. Show Notes 00:23 Welcome 02:14 1) Stream The Result // Create a new TextDecoder instance const decoder = new TextDecoder(); // Make the fetch request fetch('https://api.example.com/streaming-data') .then(response => { // Check if the response is valid if (!response.ok) { throw new Error('Network response was not ok'); } // Stream the response data using a TextDecoder const reader = response.body.getReader(); // Function to read the streamed chunks function read() { return reader.read().then(({ done, value }) => { // Check if the streaming is complete if (done) { console.log('Streaming complete'); return; } // Decode and process the streamed data const decodedData = decoder.decode(value, { stream: true }); console.log(decodedData); // Continue reading the next chunk return read(); }); } // Start reading the chunks return read(); }) .catch(error => { // Handle errors console.log('Error:', error); }); 06:05 2) Download Progress Download progress example 09:40 3) Cancel Streams - Abort Controller // Create an AbortController instance const controller = new AbortController(); // Set a timeout to abort the request after 5 seconds const timeout = setTimeout(() => { controller.abort(); }, 5000); // Fetch request with the AbortController fetch('https://api.example.com/data', { signal: controller.signal }) 11:32 4) Testing if JSON is returned 13:18 5) async + await + catch const data = await fetch().catch(err => console.log(err)); 14:42 6) to awaited - return error and data at top level const [err, data] = collect(fetch()) if(err) // .... await-to-js - npm 16:58 7) Dev tools - Copy as fetch 17:54 8) You can programatically create a Request, Response and Headers objects const myRequest = new Request('https://traffic.libsyn.com/syntax/Syntax_-_641.mp3', { headers: { 'Content-Type': 'text/plain', } }); fetch(myRequest)

testing tricks stream copy function dev handle fetch decode json syntax headers settimeout

Potluck - How to Pick a Tech Stack × useEffect × setTimeout × Staying Focused

Freedom Biker Church Fayetteville

Play Episode Listen Later Sep 7, 2022 62:45

In this episode of Syntax, Wes and Scott answer your questions about picking the right tech stack, whether useEffect is still useful, benefit to use uses setTimeout, and more! Linode - Sponsor Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with a $100 in free credit for listeners of Syntax. You can find all the details at linode.com/syntax. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/syntax and click on the “Create Free Account” button to get started. LogRocket - Sponsor LogRocket lets you replay what users do on your site, helping you reproduce bugs and fix issues faster. It's an exception tracker, a session re-player and a performance monitor. Get 14 days free at logrocket.com/syntax. Auth0 - Sponsor Auth0 is the easiest way for developers to add authentication and secure their applications. They provides features like user management, multi-factor authentication, and you can even enable users to login with device biometrics with something like their fingerprint. Not to mention, Auth0 has SDKs for your favorite frameworks like React, Next.js, and Node/Express. Make sure to sign up for a free account and give Auth0 a try with the link below. a0.to/syntax Show Notes 00:23 Welcome 02:39 What's the best way of comparing the efficiency of object literals created from a factory function vs objects created by new'ing a class. Perf.link 06:54 How can I always see the full signature in VS Code? 10:40 What's your process for picking a stack when starting a project? 14:41 Sponsor: Linode 15:23 Is snapshot testing really worth it? TS QuickFixes 20:54 What are your thoughts on ISR Incremental Static Regeneration? 25:20 Is useEffect public enemy #1? Goodbye, useEffect: David Khourshid 29:02 Sponsor: LogRocket 30:17 Is there any benefit to use uses setTimeout instead of setInterval? MongoDB Prisma 37:13 HTML to PDF a great solution I use is gotenberg.dev gotenberg.dev 40:12 Although async/await might make for code that is easier to grok, I find it worse for chaining functions. Pipeline Operator proposal 45:07 How do you guys stay focused for meaningful periods of time? 48:36 How should code formatters be configured and combined? Prettier ES Lint Editor Config No-Sweat™ Eslint and Prettier Setup 51:56 What's your opinion on the latest Sveltekit changes with load, file based routing, and more? Major Svelte Kit API Change - Fixing load, and tightening up SvelteKit's design before 1.0 Astro Nano Store 55:53 Sponsor: Auth0 56:47 SIIIIICK ××× PIIIICKS ×××

react goodbye simplify linux html s3 staying focused potluck sdks tech stack syntax vs code auth0 perf linode sveltekit settimeout setinterval

08-07-22 – The Right Foundation…JESUS “Genesis Introduction” – JD Tew

Play Episode Listen Later Aug 8, 2022 49:03

jesus christ right foundation jesus genesis addeventlistener settimeout attachevent documentelement

JS One Liners

deeper javascript settimeout

Play Episode Listen Later Jan 3, 2022 22:53

In this Hasty Treat, Scott and Wes talk about some Javascript one liners that speed up your coding experience in one line. Sponsor - Linode Whether you're working on a personal project or managing enterprise infrastructure, you deserve simple, affordable, and accessible cloud computing solutions that allow you to take your project to the next level. Simplify your cloud infrastructure with Linode's Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Get started on Linode today with a $100 in free credit for listeners of Syntax. You can find all the details at linode.com/syntax. Linode has 11 global data centers and provides 24/7/365 human support with no tiers or hand-offs regardless of your plan size. In addition to shared and dedicated compute instances, you can use your $100 in credit on S3-compatible object storage, Managed Kubernetes, and more. Visit linode.com/syntax and click on the “Create Free Account” button to get started. Sponsor - Sentry If you want to know what's happening with your code, track errors and monitor performance with Sentry. Sentry's Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up. Show Notes 00:24:12 Welcome 01:24:11 Sponsor: Linode 02:11:02 Sponsor: Sentry 03:54:18 Twitter ask for One Liners 04:24:05 Math random const getPsuedoID =() => Math.floor(Math.random() * 1e15); 05:43:09 Random color Paul Irish random color '#'+Math.floor(Math.random()*16777215).toString(16); 06:41:06 Console.log as an object. console.log({ dog, person }); VS Marketplace Link 08:29:17 Edit anything document.designMode = "on" 10:15:15 Temporal date export const today = Temporal.Now.plainDateISO(); 11:44:05 Console(log) const myFunc = (age) ⇒ console.log(age) || updateAge() 13:26:13 Remove a prop const { propToRemove, ...rest } = obj; 15:29:01 PHP style debugging preElement.innerText ={JSON.stringify(val, '', ' ')}` 16:31:00 First and Last Destructure var {0: first, length, [length - 1]: last} = [1,2,3]; 17:34:17 Speed up audio video document.querySelector('audio, video').playbackRate = 2 Overcast 19:44:15 Sleep function let sleep = (time = 0) => new Promise(r => setTimeout(r, time)) 20:26:00 If statements on one line If (!thing) return 'something' Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

math simplify linux javascript temporal s3 sentry syntax one liners linode paul irish settimeout tostring queryselector

Episode 78: setTimeout(newEpisode)

Enjoy the Vue

Play Episode Listen Later Oct 18, 2021 33:43

This episode is sponsored by Clouflare Pages! (https://enjoythevue.io/cloudflare-pages) This week, The Enjoy the Vue panel digs into the topic of asynchronous event loops: how it can save you time, but also how it can trip you up. Asynchronous update queues are an efficient way for platforms like Vue to save time and energy by recognizing a group of similar commands and doing a batch run at the same point in time. We get into event loops, how the term ‘next tick' came about, and how synchronous stacking can cause a Stack Overflow Error. You'll also hear some of our favorite terminal commands, including a special tidbit on how to say ‘please' to your computer! Lastly, we share our picks of the week that will add joy, intrigue, and deliciousness to your life, so make sure you tune in to hear it all! Key Points From This Episode: Introducing today's topic: asynchronous event loop in JavaScript. An asynchronous update queue and why Vue uses one. Why an asynchronous update queue is so efficient. How an asynchronous update queue can also sometimes cause problems. Where the term ‘next tick' originated and how it is applied today. A breakdown of event loops and stack heaps. Tessa shares her understanding of blocking. Why a blocking operation is synchronous. Alex explains what the heap is and how items transition to the stack. Recursive functions and the stack overflow error message. The team shares their favorite terminal commands. Hear our picks for the week, which include gourmet sour gummies, intriguing portraits, and a fascinating new board game! Tweetables: “When you make a change to your data in Vue, it doesn't happen right away because that would potentially be inefficient. What it does is it groups all the changes together and then batch runs through them at a set point in time. That's the queue that they all get added to.” — @EnjoyTheVueCast (https://twitter.com/EnjoyTheVueCast) [0:02:04] “Basically, it's like doing your math without showing the work. That's what Vue does. Teachers love it.” — @EnjoytheVueCast (https://twitter.com/EnjoyTheVueCast) [0:03:20?] “My understanding is that blocking doesn't mean it never happens. It's just like I'm going to save all of these user interactions until the next time that the queue is free. Then, I'm going to jam all of them in there. You're going to get all 500 clicks in one second.” — @EnjoytheVueCast (https://twitter.com/EnjoyTheVueCast) [0:18:25] “There is this nebulous event that may or may not happen. When it happens, that click, that event doesn't necessarily fire immediately. It gets put on the end of the event queue, the event loop queue.” — @EnjoytheVueCast (https://twitter.com/EnjoyTheVueCast) [0:19:16] Links Mentioned in Today's Episode: repl.it (http://repl.it) Back to the Vueture: Stuck in the Event Loop (https://www.vuemastery.com/conferences/vueconf-us-2019/back-to-the-vueture-stuck-in-the-event-loop), tessa (VueConf US 2019) * What the heck is the event loop anyway? (https://www.youtube.com/watch?v=8aGhZQkoFbQ), Philip Roberts (JSConf EU) Olivia Beaumont (https://oliviabeaumont.com/) Obscurio (https://boardgamegeek.com/boardgame/273477/obscurio) (Boardgame) The Legend of Zelda™: Skyward Sword HD (https://www.nintendo.com/games/detail/the-legend-of-zelda-skyward-sword-hd-switch/), Nintendo Switch Candy Kittens (https://candykittens.co.uk) Web Exclusive Gourmies Bundle (https://candykittens.co.uk/collections/gourmies/products/limited-edition-gourmies-bundle), Candy Kittens

teachers legend of zelda javascript frontend vue asynchronous recursive javascript frameworks candy kittens event loop settimeout vueconf us

[Weekend Drop] Temporal: React for the Backend

The Swyx Mixtape

Play Episode Listen Later Oct 9, 2021 26:31

Video: https://youtu.be/Cxaf8E00GMMSlides: https://docs.google.com/presentation/d/1sJSqNy-t-kVxzrWlqMTp_03nI7Zo8Znr7k0f0C6L9ig/edit?usp=sharingTimestamps:[00:00:00] Intro[00:02:17] Part 1 - Components: Code Organization for Real Apps [00:04:26] What we learned from React [00:07:46] Part 2 - Architecture: Choreography vs Orchestration [00:13:05] Retries and Timeouts [00:14:37] Part 3 - Time: React vs Temporal[00:16:34] Elevator Pitch [00:17:13] Programming Model [00:18:44] Comparing React and Temporal Principles [00:19:11] Live Demo: Amazon One Click Button [00:23:49] Talk Recap [00:24:16] React and Temporal Full Comparison [00:24:42] Conclusion: EnablementTranscript [00:00:00] Once again, I want to thank you all for tuning in and joining, React New York 2021 without further ado, I'll pass it on to Shawn. All right, so hi everyone. Hello, React new York. It is my home town in the U S and I miss everyone back in New York. I am currently based in Seattle, but I'm here to talk about React for the Backend. In 2020 I actually thought that I had given my last React talk because I was all tapped out. I had said everything I wanted to say, and then React New York came by and said, do you want to speak? And I was like, oh, I really wanted to speak for React New York. So here's my presentation about what I've been working on and what I think the parallels have been for React. And I think there's some generalizable lessons, even if you don't end up using Temporal. So, the inspiration for this talk came from Guillermo Rauch, the creator of Next.js. And he was the first person to point out that Temporal.io, does to backend and infra what React did to frontend. Temporal engine is quite complex, much like React, but the surface exposed to developers a beautiful render function and I'm a bit upset because he realized there's before me and I have been working on Temporal for a few months now. So important caveats before I start this talk. What I'm presenting to you is alpha for TypeScript. Temporal is typically a goal or Java based application, but we're developing TypeScript and hopefully launching it soon. And then finally "React for the backend" is an analogy, not a design goal. The way I treat this is like, it's a, it's basically like crabs. And one of the most entertaining facts that I've ever found is that nature has apparently tried to evolve crabs five independent times. And in fact, there's a word in evolutionary biology for it called Carcinization. And of course, this is really good for a lot of memes. So tired convergent evolution is not uncommon, especially when species have similar selecting pressures in their environments, wired. Everything is Crab. And perhaps everything is React, because we have similar design space problems. So I'll tell a little bit of the story through three parts there's Components, and we'll tell it through the story of Uber, talk about architecture, we'll talk through the story of YouTube, and Time will tell you through the story of Amazon. So a lot to cover, I'm going to try to go really fast. Don't worry. I'll share the slides on my Twitter later on. Okay. [00:02:17] Part 1 - Components: Code Organization for Real Apps So part one is about components. You see this a lot on YouTube. Probably you're watching now on YouTube or live streaming. And yeah, you know, like three hour live stream and that's it. Very cool. I think we, we know how to break things down and React has really helped us be more productive by being able to break things down into the components and knowing how to compose them together in a predictable way. But there's a lot of things unanswered in things like this in, in full stack, clones of major well-known apps, which is the hard parts. What like a typical Uber trip, we'll have all these steps like search pricing match. Pick-up drop-off rating tipping, payment, email, uh, and so on and so forth. And typically the naive way of organizing all this is basically one after the other, right? Like this is search goes to pricing, goes to matching, goes to pick upgoes to dropoff goes to rating goes to tipping goes to payment, goes to email, imagine that these are all managed by separate teams and scaled independently. Then you realize, like, this is only the happy path. Then you have to throw in a whole bunch of things that can happen along the way. An Uber trip is basically a long running process with humans in the loop and humans are very, very messy by nature. So how would you write an Uber clone? good luck with a lot of data technologies that you would typically reach for just naively, because you will have to discover all these systems and all these use cases and edge cases along the way. So when people say full stack, they often really mean like this half drawn horse meme. I think this is particularly funny so I take every opportunity I can get to show it, but to be honest, a lot of us front end developers are probably the other way the half-drawn Dragon where we're frontend a very good and in the backend, we'll just like, you know, stick some stuff on Firebase and something. And in reality, if you look at the backend systems, most companies, especially at scale, go towards some form of very complex micro service, system. I don't have the chart for Uber, but Hail-0 is probably a good comparison. Netflix, Twitter, and It's not really avoidable. If you want to scale a company to any significant size, you probably have to break them up into independent services because you're going to ship your org chart anyway. [00:04:26] What we learned from React The thing I realized as a React developer, as a front end developer, is that actually we had a pretty good run in the past seven, eight years of React in terms of the fact that front end developers know how to organize code at least in terms of the component level. So we moved from the jQuery era where everything was just kind of spaghetti all over the place to at least something more organized where event handlers are strongly tied, locally tied with renders, but essentially managed by React's runtime. So a few key lessons from React that I personally draw [00:05:00] is that you want to have a component and a renderer model. Like, so essentially the user or the developer writes components. And then the react core team writes the render and that handles a lot of the boilerplate that you might typically forget. And this is everything to do with on mounting or having local states. And it gives you a very nice, non-leaky abstraction that you can write. Second, you can also guarantee work and correctness, which is originally what drew Jordan walk to make something like React because he was working on Facebook messenger and there was a lot of inconsistent state within Facebook manager because of the spaghetti code. So correctness, meaning that we embrace functional programming to produce a virtual DOM view is a pure function of state. If you look at the old enough React talks, you will see a lot of v = f(d), so view as a pure function of data. And finally the programming model. We like to say that it's just JavaScript. There's no custom syntax with templating syntax to learn. I think all these three lessons , there are actually a lot more, but all of these three lessons are where I'm going to focus on for this talk. And I think whenever you tackle any programming paradigm, any framework, any design question, you might want to run it through some of these ideas. So whenever I talk about React principles, I always like to bring up the fact that there's this often overlooked repo called react-basic. And it's actually in the official React organization on GitHub. And this is Sebastian Markbage, who is the tech lead of React. And he wrote down six years ago, his principles on what he thinks makes up React on a fundamental basis? No, JSX just like, what are the principles that we're designing for? We are designing for a simple, pure transformation, abstraction, composition, state, memoization. The words that he uses are very theoretical sometimes, but you feel it every single day when you write React. So there's a lot of things else apart from that, that reacts has done for front end programming. Apart from deterministic renders, we have useState with a reduction of boiler plate with unmounting, child components in con in the very careful design composition, um, side effects where, you know, we have used effect or use memo. And actually a lot of people don't know. I don't, I forget my source. I think it's Sophie Alpert, but, one-third of the React code base is actually just normalization of events across browsers. So you don't even have to worry about it. And creating synthetic events for that. They also produce a dev tool and manage a central scheduler and obviously the success of React over the past five, six years has really shown Testament to how great all these decisions have been. If you want to learn more about the talks that I've done and my perspectives on some of these React principles, I've done three talks. One is at React Rally. The second at JSConf and the third, ,at React Summit. So you can check out my YouTube for more conversations on that. I don't have time here. Okay. [00:07:46] Part 2 - Architecture: Choreography vs Orchestration So that was part one where we talked about Components and the React revolution. So part two, we're going to talk about architecture. So a bit, one level higher than just components. And I'm going to motivate this question with a question of how would you write YouTube. And again, if you look on YouTube for how to write YouTube tutorials, you can get full-stack clones of YouTube, which is pretty impressive, you know, write YouTube in three hours using Firebase. That's very impressive. Unfortunately the hard parts of YouTube also come in. And there are a bunch of Googlers actually who actually went and interviewed YouTube engineers on how YouTube works on the backend. There's a bunch of work that goes on in the background. So you need to upload your file. You need to analyze for metadata. You need to split it up into chunks. You need to process these chunks in parallel, and then you need to stitch it back. And by the way, processing, you have to produce an array of formats, right? From like, 240 P to like 1400 P or something like that. And then you have to stitch all these chunks back into the continuous videos that you actually see in stream. You need to notify subscribers, you need to produce automatic captions and you need to produce thumbnails. And that is again, just the happy path. Right. So, what about all these other features? It's. For example, YouTube premiere is a scheduled release of a YouTube video or feeding into the recommendation algorithm. That must be the most craziest batch job in the world. And you need to scale this process, whatever, whatever you design for 30,000 hours of video uploaded every hour. That's the sheer amount of volume that's going on YouTube today, which is just insane. Like, like any design that you make at scale is going to break in some respect. So I think, I think that's, that's really interesting to consider. And I learned about this actually, and I thought more about this because I interviewed one of our users who is Descript (hi! I'm editing this transcript in Descript rn lol). Descript is a audio transcription platform and their entire business is transcribing audio and then making it easy for you to edit audio. I do it for my podcast every single day and millions of people use it. I think it's really cool. So their problem was that when a user hits transcribe, it kicks off asynchronous multi-stage and parallelized process that involves reading, encoding audio, chunk splitting. external API calls, merging results that may potentially arrive out of order and then verifying their alignment. So there's a lot of [00:10:00] nuance here that can get really tricky. And if any part of the process fails, you need to try it again. So, this is typically the kind of architectures that people build up incrementally over time, as they discover all these use cases and then find holes and patch them because it's too late to rewrite something. There's a lot of decisions that goes into here. And this is normal. This is natural. I think you run into basically the eight fallacies of distributed computing, which has actually discussed or discovered back in 1994 by people at Sun Microsystems. I love these cartoons but it can be a little bit hard to read. So here's a more organized version of them. At the bare minimum, don't forget distributed computing fallacy number one, which is that the network may or may not be reliable or compute may or may not be reliable. So, what that means in practice is that when you're calling system a, B, C, D E F G you may actually need to introduce hardening layers because at every point and you cross system boundaries, you have a chance of failure and that multiplies exponentially, as you have more and more services tied up in your systems like we saw for the Uber example, like we saw for the YouTube example. You need to add in timeouts and retries. And what that means is that you need to persist the number of times you timed out, when you timed out, what jobs you timed up. So you need a database every single time, and then you need a scheduler or a timer to say when the next time is going out, I'm going to try this again. And you need to write this for every service. If the ma the maintainer for every service needs to maintain both the code and the infrastructure for this. This is a lot of how I was talking about things when I was exploring the serverless world. So here's a real life example from the AWS blog where they said that you were using dead letter queues to replay messages when such things as failures occur. This is a fine looking example until you try to scale it. And again it looks like a complete mess, complete track, and it's very hard to keep in your head, and pretty soon when you're explaining this to your CTO you look like the Pepe Silvia meme. So the solution that I found is really to have a central orchestrator, right? Instead of every single system maintainer writing their own API hardening layer, which is a production requirements, as you find more and more of these bugs, you should centralize it with a centralized team that takes care of the orchestration of all these different services. And that's in the business, what we call choreography, which is A to B to C versus orchestration, which is a central orchestrator coordinating the dance between AB and C, and then storing both the infrastructure and the code for the scheduler and the database. So there's a really good article on this by Yan Cui in the burningmonk.com so I highly recommend checking it out where he talks about choreography versus orchestration, with real life examples that people use in AWS, but also it's not specific to any cloud. It's a architecture design pattern, which I think fundamentally, if you start off with this, it's really hard to rearchitect to this. I mean, it's, it's possible because people are doing it, but also it's a conscious, architectural choice that you might not know that you're making if you don't know about it. So, I guess a lot of my message here is to tell you that orchestration is a thing. [00:13:05] Retries and Timeouts Also, so you want to declaratively put into your framework retries and timeouts, so for example, this is actually our API. You want to be able to say, all right, here's the default retry policy. Whenever I fire off an activity, an activity is just like an external API call, for example. So when I fire up an activity, I want it to be retried every second. If it fails, I need a backoff coefficient, like exponential backoff. This is very similar to the TCP protocol so that if the endpoint is failing or getting rate limited, I don't keep retrying, and then building up a DDoS attack on myself, I actually back off and put more and more intervals in between until some maximum interval, let's say a hundred seconds. And then I give myself a maximum attempt, so I can say like, all right. I don't want any retries. I can just say have a maximum attempt of one. Or let's say, I want a linear back off and not an exponential for whatever reason. And I want to try to a maximum of five times - you want to have this all declarative so that you can tweak this as you understand your system and you scale your system. Right? So I think this is a really interesting programming model that just puts retries into the code that you write. And that's only possible when you have your centralized orchestrator, no matter what system, not just Temporal. Okay. So the case that I'm making is really for choreography versus orchestration. And I, the analogy that I make for front end versus the back end is that it's kind of like vanilla or jQuery versus react. React has a react as the central orchestrator, orchestrating all the components. And I think that's a really interesting architectural analogy that you can make and learn from React. All right. [00:14:37] Part 3 - Time Part three - Time. I'm doing very good on time. I think better than I thought, which means that we'll have time for a live demo, which is really awesome. So let's talk a little bit about Temporal. [00:14:45] What is Temporal? What is Temporal? Temporal is the open source platform for orchestrating highly reliable mission-critical applications at scale. I love talking a little bit about the history, the reason because our CEO started at Amazon as the tech lead for what became Amazon SQS. Our [00:15:00] CTO was at Microsoft and it was the principal architect of the Durable Task Framework, which became a Microsoft's version of Durable Functions, and then finally they joined Uber and worked on Cadence, which is the open-source version of their workflow orchestration platform and Cadence became so popular that they spun out and became Temporal. And since then it's been adopted by a lot of well-known household name companies, especially in the developer world. There are a lot of people hiring for Temporal developers, which I really like to see because it's not just being used, but also it's creating jobs for people and it's becoming a desirable skillset. And most recently last week we had Netflix presenting about how they used Temporal for their CI/CD. Temporal has three components or produces three products that are used in sync. The main star is Temporal server, which is comparable to the React runtime that you might see, then there's Devtools, which is the UI that you might want to inspect the state of things. And then the SDK is, which is what you use to code. So I think all those are really comparable to what we have in React and having been in the React world for while, like, it's really amazing to see the analogies that we have. We have exactly the same thing. For me, the really sort of the seal of approval comes from Mitchell Hashimoto who, created Hashi Corp, saying that without Temporal, we would have spent a significant amount of time rebuilding Temporal, which actually to me is the best form of validation because Mitchell is one of the best developers in distributed systems and he says it's hard and he says it does it well. All right. Enough social proof you want actual facts? I would just give it straight to you. [00:16:34] Elevator Pitch So because your workloads like the YouTube encoding, or like the Uber journey and this technology was developed at Uber i s long running and it ties together multiple services. You want to standardize timeouts and retries and you want to make it easy for every team to have production grade retries and timeouts. Because this work is so important. You must never drop any work. You must log all progress. In other words, you must use event sourcing. And then finally, because this work is so complex, you want to use generic programming languages, instead of Domain specific languages. So you want to model a dynamic, asynchronous logic, and then you want to reuse, test, version and migrated it. So that's the pitch in one screen. But I'll just break it down for what it means, and then we'll go into a demo. [00:17:13] Programming Model So to me, The, the closest analogy to React is the programming model, because React spends a lot of time on API design and in the workflow orchestration world there are a lot of JSON or DAG based domain specific languages. So you, you write a bunch of JSON or you do boxes and arrows boxes and arrows boxes and arrows, sometimes you've even write XML, which is very interesting as well. What I find with all these is that they're actually really good for manipulating visually. But they get very tricky when you need to do programming language constructs, like variables, functions, loops, branching statements and all the things that we've invented in programming languages over the past few years. So if you use "just JavaScript" or "just programming languages", you have all the tooling available. You can use all the libraries that are available. You can use all the testing and code version, quality controls available. If you write your own, you have to rebuild all this dev tooling from scratch for yourself. So that's essentially what this is. Here's an example from one of the big clouds where this is their workflow orchestrator model, where you write Jason and it's really hard. It actually goes off the screen and I couldn't really fit everything on one screen. And with Temporal literal just JavaScript you call an endpoint you use that the result of that end point to call other end points, for example. It's a very simple example, but in built here is default retry policies that have been worked out. So both of these handle reliability on rails, it's just, we differ in the programming model and the engineering that it takes to maintain one of these SDKs is I'm learning. It's very, very immense. So it's really interesting. [00:18:44] Comparing React and Temporal Principles So, again, back to the core principles that we talked about early on from React. React d ecided on using a framework, decided on correctness and decided on a programming model, and Temporal, in a very similar way. The developer writes workflows and the Temporal core team writes the orchestrator, which is Temporal server. In terms of correctness, React insists on functional programming, Temporal insists on event sourcing in deterministic workflows and then programming model, you want "just JavaScript" or just programming languages, not any custom DSL syntax. [00:19:11] Live Demo: Amazon One Click Button So the final example that I'm gonna motivate is which is like, I'm, I've been trying to re progressively reduce the complexity of my examples. So we met from Uber, which is like a super long running, a lot of humans in the loop to YouTube, which is not so much humans in the loop. You upload it once and then everything else takes over from there. Now I just want to build one feature, which is a one-click buy button in React or in front end. It's actually super easy. It's a button. That's the literal simplest thing you can possibly do. You put an onclick handler. You're done. If you want to do a one-click buy, you do a setTimeout, and then say like, okay, if you want to cancel this within some window, with Amazon is 30 minutes, we can cancel it. But if you want to persist it, imagine if some person clicks, closes the browser and then changes their mind, opens the browser again, and it's gone. You're screwed. You don't have any other way to implement one-click [00:20:00] purchases. You need to implement timers on the backend to do this. I was watching this old talk from Joel Spolsky where he talks about the engineering for the one-click buy button. And I put it up on my YouTube because this is such an old talk. And I was afraid to link to the timestamp, but you can check it out as it's just a three minute video where he tells the story about how Amazon moved from shopping cart to one-click buy I mean they still have a shopping cart but it's that important because in online e-commerce actually even up to today the abandonment rate for shopping carts is 70%. So imagine if you implement this one feature, you improve your sales by I don't what's the inverse of 70%, three times. That's really amazing. So I think it's just fascinating and it's not just about Amazon. It's not about one click buy. It's about user experience. It's about making things easy and intuitive and that often involves turning synchronous things into asynchronous things and in persisting them so that they persist in the background. So I have a little demo here. I'm going to go really, really fast, but you can check out the code in temporalio/samples-node. There's the specific path this year but it's basically a Next.js demo where I have a Next.js folder here. This is going to be pretty standard for a lot of React developers. Hopefully you're familiar with Next.js, so you can learn it. It's got some pages and an API routes where I have serverless functions that call and send signals to my workflow functions. I have also a Temporal folder where I have written my workflows and activities. The activities are just a little logs obviously, cause they don't interact with any backends, but they could. And then the workflow coordinates the states in the background of all of these. So I can show you the code, but essentially I kick off a one-click buy with a purchase and then I set a timer and promise.race with a five second wait. So if I receive a cancel signal during that timer then that cancels if not, it goes through and the purchase is confirmed. Obviously I can. And what's fascinating about Temporal is that every single step is persisted in automatically saved. So in other words, I can sleep for 30 days. I can sleep for a year. I can sleep for five years and it doesn't matter because it's all persisted and wakes up automatically. So the compute the, this serverless function can be. The worker or a Temporal server itself can go down. You can just bring you back up again and it carries on as though nothing happened because of event sourcing. So, I'm gonna, I'm going to go ahead and run this. I think it's uh, demos I'm always stressed out about live demos. Okay. I mean, I did test it before the talk. It's just that whenever I'm streaming, like it adds an extra latency thing and that goes haywire. So, Let's see if I have this demo available. All right. So I also want to pull this out, which is the UI layer. These are the my test runs. But I have here at one-click purchase UI, and literally, I, you know, I, I want to implement this without a shopping cart, but I want to be able to cancel within some certain amount of time. So if I click buy, uh, it clicks, it handles it's. It sends a workflow. And that workflow starts in starts in the background and it's running, right. It's waiting for the timer to proceed. So I'm going to hit the timer, uh, and you can see that a timer started and time of ended, uh, within that five second window that I specified, obviously I should make it longer if I, if I really wanted to show this along the way. Um, so, uh, this, this is, this is as is purchased, um, and we can, uh, and now we've confirmed it. Um, but if I ever want to click buy, and then I can click the. That also fires off a different workflow, uh, where it sees that it receives the cancel signal from me. Uh, so, so I signaled it to cancel. And that's a very useful model as well. So this actually shows off a lot of the core principles of Temporal, which is you kick off a workflow, you can set durable timers, you can send it human signals and you can get out data as well with queries. There's a lot of interesting elements behind that, but that's the core demo that I wanted to show off. So maybe I'll write a YouTube example and then I'll go on to an Uber example and be a billionaire. [00:23:49] Talk Recap So ultimately I just want it to recap again, what we covered. We covered components, we covered architecture we covered time, and these are all the three elements I wanted to compare reacts and Temporal, and explain a little bit of how we think about doing the hard parts of making clones of very popular projects. Why is it so interesting? It's a little bit like the crabs story, you know. Obviously the founders of Temporal are not front end developers. They didn't even know react at all. [00:24:16] React and Temporal Full Comparison But they independently evolved a lot of the same principles and this that's, I haven't even gone into like the full comparison. So we talked a little bit about deterministic functions and local state and composition, but we haven't talked about normalization and how that compares dev tools. Testing is also super interesting thing as well as the central runtime. So there's a lot here, which I think. And fascinated by, and I'm obsessed by applying the lessons from React to things that are not React. [00:24:42] Conclusion: Enablement And I think overall, when I asked my CEO, like, what is the core message that we want to deliver is actually about enablements. Like we enable people to do things that they're not formally trained to do because we wrapped it up rapid all in a central runtime or central framework. So, uh, I always loved the Alfred north Whitehead quote that [00:25:00] civilization advances by extending the numberof things that we can do without thinking about it. So for me, my version of it is that B2B software advances by extending the number of jobs we can perform without formal training. And the message overall here is that Temporal lets backend developers or, just general full stack developers do distributed systems right? So that's it. I blasted through that. I only took 26 minutes. Really great for me, cause I was worried that it would take 50 and I'm happy to answer any questions you can hit me up on Twitter at Swyx. You can read my long form blog posts about why Temporal and then you can join our mailing list, YouTube or Slack. Thank you. Alright, thank you very much things. So I think that was a really, really nice. And you did, uh, went through that quite quickly. Uh, when I see the comments, people love the, like the most right there, because I could fail because I could fail. It's always like that. So, uh, yeah. Um, the nice thank you for the presentation. With this talk, I think it's actually the last talk of the event and I want to thanks everyone for joining us and thanks to everyone, thanks to all the speakers, of course, for being part of this event, uh, React New York 2021 and the sponsors. Um, I think this would be a good afternoon, I guess, or good night, depending on where we are in the world. Right. Have a good one. Everyone.

[Weekend Drop] Sunil Pai: React and the Meta of the Web

The Swyx Mixtape

Play Episode Listen Later Sep 19, 2021 80:04

A wideranging convo with Sunil covering the future of React, the Third Age of JavaScript, and the Meta of online discourse.Watch on YouTube: https://www.youtube.com/watch?v=H3h1WICelqsFollow Sunil: https://twitter.com/threepointoneChapters: [00:01:40] React and Temporal, Declarative vs Imperative My Temporal Explainer: https://twitter.com/swyx/status/1417165270641045505 https://www.solidjs.com/ [00:12:57] State Charts and Lucylang https://lucylang.org/ XState and Stately https://stately.ai/viz [00:17:08] The Future of React [00:25:03] React Streaming Server Rendering vs SSR/JAMstack/DSG/DPR/ISR ReactDOMServer.renderToNodeStream() Sunil's Slides: https://www.icloud.com/keynote/0MyOJkDIOVfFit76PqJFLvPVg#react-advanced https://react-lazy.coolcomputerclub.com/ [00:33:13] Next.js and the Open Source Commons [00:38:46] The Third Age of JavaScript Third Age of JS Benedict Evans (not Sinofsky) on Word Processors: https://www.ben-evans.com/benedictevans/2020/12/21/google-bundling-and-kill-zones [00:45:16] ESbuild vs SWC vs BunBun (Jarred Sumner) https://twitter.com/jarredsumner/status/1390084458724741121 [00:50:46] Let Non-X Do X: Figma vs Canva, Webflow vs Wix/Squarespace Canva vs Figma valuations https://twitter.com/swyx/status/1438102616156917767 [00:52:42] JavaScript Twitter and Notion's 9mb Marketing Site Notion 9mb JS Site Tweet mrmrs' Components.ai [01:06:33] React Server Components and Shopify Hydrogen/Oxygen https://twitter.com/swyx/status/1410103013885108229 [01:09:18] Categorical Imperatives of Web Platforms: Cloudflare vs AWS, MongoDB vs Auth0, Gatsby vs Netlify https://auth0.com/blog/introducing-auth0-actions/ [01:18:34] Wrap-up Transcript [00:01:40] React and Temporal, Declarative vs Imperative [00:01:40] swyx: Okay. So the first topic we want to talk about is React and Temporal, right? [00:01:43] Sunil Pai: I feel Temporal is introducing a shift into the workflow ecosystem, which is very similar to the one that React introduced to the JavaScript framework system. [00:01:54] swyx: That's the hope. I don't know if like my explanation of Temporal has reached everybody or has reached you. There are three core opinions, right? The first is that whenever you cross system boundaries, when you call it external API. So when you call internal microservices, there's a chance of failure and that multiplies, the more complex the system gets. [00:02:11] So you need a central orchestrator that holds all the retry states and logic, as well as timers And it tracks all the events and is able to resume from it from failure. [00:02:21] Second opinion that you should have is you should do event sourcing rather than try to just write your business logic and then instrument with observability logs after the fact you should have your logs as the source of truth. And if it's not in the log, it did not happen. [00:02:34] And then the final piece is the workflows as code, which is the one that you're focusing on, which is the programming model, in the sense that like all the other competitive workflow engines, like, Amazon step functions, Apache airflow, Dagster, like there's a bunch in this category. [00:02:48] They're all sort of JSON and YML DSLs, and the bind that you find yourself in is that basically you're reinventing a general purpose programming language inside of these JSON and YML DSLs because you find a need for loops, branching, variables functions, all the basic stuff. And, people find that like at the end of the day, all this tooling is available, you just have to make it run in inside of a general purpose programming language. So that's what Temporal offers. [00:03:12] But it's very interesting because it kind of straddles the imperative versus declarative debate, right? [00:03:17] React, people view as declarative. And I think it's mostly declarative, like there's imperative escape hatches, and because it's declarative, people can have a single sort of render model of their entire app for the entire tree. And I think it makes sense to them. [00:03:32] And you're saying that that's better, right? That's better than the imperative predecessor of like jQuery and randomly hooking up stuff and not having things tied up together. You sounded like you want it to [00:03:42] Sunil Pai: interrupt. So it's actually two things. One is the jQuery had an imperative API, and then they went way too hard into the declarative side with templating languages and then started reinventing stuff there. [00:03:54] So really react was like, no, you need access to an imperative language to create, you need a fully featured programming language to generate description trees like Dom trees or in this case, a workflow graphs. [00:04:10] swyx: Got it. So it's kind of like a halfway solution, maybe, maybe anyway. So the problem with us is that we're trying to say that imperative is better than declarative, for the purposes of expressing general purpose business logic, which is an interesting sell for me because in all other respects, I'm very used to arguing to declarative is better. [00:04:33] Then there's also an idea that people should build declarative layers on top of us. And I, it's just a very interesting, like back and forth between declarative and imperative that I don't know where I really stands apart from like, wherever we are is never good enough. So we need to add another layer to solve the current problems [00:04:51] Sunil Pai: there. [00:04:51] So there's a phrase for it and I forget what it's called the mechanism. It says that, uh, the system that allows you to execute stuff should not be the same system that prevents you from doing bad things. So there's a core, which is basically a fully featured API. And then you put guard rails around like the experiences. [00:05:12] For example, as an example, this is like adding TypeScript on top of JavaScript, let's say, unlike reason ML, let's say like, OCAML or a lot of very strongly type a language where if your code doesn't compile, you can't really run the code in TypeScript. There are times when you're like, you know what? [00:05:29] I need an escape hatch to actually like, do something like really funky here, X, Y, and Z, that that's not even well expressed in either the type system or sometimes even the language itself. You need to like hack it. And like, you might even email a couple of things. Uh, and in react, this was, I think when react came. [00:05:47] It wasn't just that it was a, oh, like there's JSX. It was very much, uh, okay. Uh, I have a lot of existing code, so I can add, React to one part of it and then hook onto the DOM, it renders and then have like this whole jQuery widget that I would like render onto the thing. Uh, so it gave you this whole incremental part to adopting the system, but then like after a point, like react consumes all of it. [00:06:11] And the fuck up with react is if you go too hard into react, doing stuff like animations is like impossible, which is why like we are at least a year or two away from a good animation API in React, or while you use, Framer or whatever Framer has become right now. Like frame of [00:06:27] swyx: motion. No. Um, [00:06:31] Sunil Pai: Yeah, but he's working. [00:06:32] I think Matt is now working on like a new, new thing. That's got a really funky name. Like, it sounds like a robot or something. All right. But it was curious to me that React's biggest deal was that, Hey, like, They talk about it being declarative, but a whole lot of things you wrote were like in regular-ass JavaScript, you would say on click and get an event and start doing things [00:06:53] swyx: beautiful. [00:06:54] It's a perfect blend. [00:06:56] Sunil Pai: Right. And you would suffer with this in. So there was the jQuery prototype phase, which was like directly imperative. And then they went hard in the other direction with type templating languages, like Jade and dust. And, uh, there were a number of popular ones at the time. And that's when like even Angular 1 became super popular because they're like, here's the whole kit and caboodle full whole framework. [00:07:18] And then React came and said, oh, well just the view. But that's because they didn't want to release like really yet. And they were like, yeah, this is all you need and the whole ecosystem. But anyway, so in temporal temporal for me is particularly interesting for that because it is now clearly making that. [00:07:35] I hate the phrase, but it's a good one. The paradigm shift of like how you start thinking about these systems and you just write some fucking code and then like you start adding on bits and guardrails for the things you want to do, which is on for the few hours I spent going through the docs and failing to get it running on my laptop. [00:07:53] That's my understanding of it. Feel free to correct me. [00:07:56] swyx: Okay. Yeah. And I think you're right, actually, I'll try this messaging on you because, it's something that we're consciously designing for. In fact, I have a, one of my API proposals was, reacts like API for tempo. And so essentially what we enable you to do is bundle up each individual service or job into a component that we happen to call workflow. [00:08:21] And my struggle here is that I currently tie component to workflow because what is the component like? It's, it's something that's self-contained that is a deterministic. Like it has a strict rule of execution from top to bottom, right. It just does the same thing every single time, uh, where we differ and why I struggle with this is because we put all the side effects into things that we call activities. [00:08:44] That's where all the non-deterministic stuff goes. And that one gets retried, basically at Temporal's will and essentially Temporal is serving as the central runtime or framework that has knowledge of all these workflows and activities. And can re-render them based on its internal rules, I retries timeouts, uh, heartbeats, all that good stuff. So I struggled with things like, which is the component and which is the hook or the effect. [00:09:08] And then there's other concepts. So, uh, we have ways to send signals into individual workflows, right? That's a very important property of the system that you can send data in while it's running and you can get data out while it's running. I'm not sure that's reflected in React at all. So maybe I'm stretching the analogy too much, [00:09:24] Sunil Pai: Solid, had an answer for that the word signal. So like solid JS. This is by Ryan Carniato the Marco folks, signals are a first-class concept in the framework. Again, I haven't dived into it in detail in a while, but it feels like an important thing. And I always wondered why React actually didn't have it because props are something that you just like pass. [00:09:46] Right. And it's just a value, like if you like plot it on a graph, for example, it's, let's say if you had to have like a graph of binary values, it would be either zero or like one, and that would be the shape of the graph, but signals are something that can be like something that happens and yeah, just pops up and goes down, like pressing a key on the keyboard. [00:10:06] And that's actually not so easy to define in a, in a react like system, like, uh, which is why it's kind of hard to build like audio processing graphs with like React or JSX. Um, I don't have like a good answer. I'd probably have to like hack on Temporal a little more, but the idea of like signals as a channel, through which you can like send information and having it as a first class part of the system is something that's not represented well in well, in React at least. [00:10:33] Yeah. Well, [00:10:34] swyx: isn't that in an action? For reducers [00:10:38] Sunil Pai: and event effectively. Yes. Like it's basically one of those actions. [00:10:42] swyx: The problem is that everything just ties right into the component tree instead of just having the component B and sort of isolated unit that can function independently. [00:10:50] Sunil Pai: That's the other thing, which is a workflow engine isn't a directed acyclic graph. In fact, it could have cycles, it could have cycles and it could have a number of other things, which is the [00:11:00] swyx: beautiful thing, by the way. [00:11:02] For us coding, a subscription platform literally is charged Stripe sleeps 30 days, charged Stripe again, and then infinite loop until you cancel and then you break out of the loop. [00:11:13] That's it. [00:11:13] Sunil Pai: That's awesome by the way. So I was actually thinking that someone's going to implement not someone's going to implement, uh, someone's going to use Redux saga on top of Temporal, that's what I was thinking, because then you will have generators that define like long running processes that are just talking to each other. [00:11:30] I think that would be good. CloudFlare also loved Temporal, by the way, like we were talking about it, like for awhile, they're like, oh, this is like fundamentally a new thing. And as you can imagine, some engineers were like, well, why isn't this running on workers? I'm like, I don't know why isn't it running on workers? [00:11:43] Like maybe we should get it there. [00:11:45] swyx: It is fairly heavy duty right now. We're trying to reduce that to a single binary, which could maybe run a workers. I'm not sure about the memory requirements that you guys have. It could, it's just not a priority for us based on our existing users. [00:12:00] Sunil Pai: Um, I was just, I was saying what they're saying. [00:12:04] They want everything to run on workers and I'm like, dude, it's just like one small, weird isolated like condo. [00:12:10] swyx: Ironically we also using V8 isolates for our TypeScript runtime. And that's just to make sure that people don't do non-deterministic stuff. So we did mock out everything, which is also pretty cool because whenever you use a library with, like setTimeout inside of that library, that persists to us as well. [00:12:25] So we set the durable timer. Your system can go down and we, we bring it back up and you're using our timer, not the JavaScript runtime timer, which is like just awesome. There's a trade off to that, which is, things don't work when you import them, like you would in a normal, Node.js project. [00:12:39] So most of, because you have to inject them into the environment of the V8 Isolate, you can't just randomly import stuff that as freely as you would in a normal node environment. So dependency injection and becomes a topic for us. [00:12:57] State Charts and Lucylang [00:12:57] swyx: Um, yeah. We actually clashed a little bit with David Khourshid because David is on this warpath of like everything in a state machine, right. Everything in the time-tested 40 year old JSON format that describes state machines. And we actually thought we were going to be competitive with him for a while because for him, the thing about writing imperative code is that it's prone to bugs, right? Like you can not really see the full, possibly the full span of like all the possible states that you're exposing, but in a state machine everything's explicit so he was butting heads with our founder for awhile. [00:13:31] But I think recently he decided that he is better at building on top of us than trying to compete with us on the reliability front. So that's, that's kind of an interesting evolution that has happened over the past year on this topic of declarative versus imperative. [00:13:44] I'm still like coming to terms with it. Like I'm not fully okay with it yet, but, it clearly is more expressive and that's something I am Very in favor of, and I have genuinely looked at like the workflow solution from Google, the workflow solution from Amazon, and they are literally have you write the abstract syntax tree by hand in JSON and that's just absolutely no way that that's going to work. So I'm pretty down with the imperative approach for now. [00:14:09] Sunil Pai: Well, that's, I figured at some point you will run XState on it and extent should work fairly well. I think contemporary, I don't see why it would. I think that that would actually, [00:14:19] swyx: Honestly, I'm not really sure what he's going to charge for. He's pushing the idea of state machines and making it more of a commonly accepted thing. [00:14:26] Sunil Pai: Well, his pitch isn't even state machines. It's very specifically state charts and I love state charts. I even bought the book by the way, the Ian Horrocks $700. So when I got it on Amazon, it was $180. I was like, cheap. Let's do it. I got really lucky at the time. It, it fluctuates like mad by the way that that value, well, you should expense it now is what it is. [00:14:46] Um, but, uh, what struck me about the thing? Here's what I tried. I really liked it. And I took a course, a couple of steps back and I was trying to understand, well, why isn't it like a success? Why don't people get into it? And the truth is that this falls not just into the intersection of this is the intersection of like computers and humans in the sense that sure. [00:15:07] There are things that can be correct, but there are things that can be expressible as well. Like I don't even know what code I want to write when I'm sitting down to write it. I love to like discover it while I'm writing it and really. All the syntax that we have created and abstractions, we have created around programming languages have been purely to express these things and have let's call it implicit state machines, even though that implies that it's bad. [00:15:32] Um, so for example, if you look at state charts, there's no real good way to compose two state charts together. You have to like manually start wiring them together. And like, there's, you know, like you've got in react, you say, oh, combo, if you have two components to put it together, you put like a little, uh, function around it. [00:15:49] And now it's two components in one component. So it's important not just to have a good unit of computation, but to have it like be composable with each other so that you can gather it and then make this whole nesting doll react, Dom tree of things. And I think. Until there's an actual language that supports that has state charts as a first class primitive, much like Lucy, I think that's what Matthew Phillips built. [00:16:15] He wrote a, he wrote an actual language that compares to state charts called Lucy Lang. That was very cool by the way. Like, I really like it. Uh, well, and it's fairly young, so it's too early to say whether people like love it or not. And other than, but people like you and me who look at something like, wow, this is awesome. [00:16:33] Let's all use it. No, like to take a while to grow. But I think that's the state charts has a bit of dissonance with the languages that it's written in right now, because it's not a first-class thing. I mean, it's adjacent object with keys and. Okay. Like we can do better maybe. Uh, but I would not bet against David and the people he's hiring. [00:16:53] Like he's hurting some smart people, you know, they're all like pretty intelligent. So I'm curious to see how that plays out. [00:17:00] swyx: I'm just glad that we're not competing. Uh, so that's, that's something that, that, that resolved itself without any intervention from me, which is very good. [00:17:08] The Future of React [00:17:08] swyx: Well, let's have this conversation since it's related, should React to be more of a DSL, [00:17:14] you know, this conversation that happened over this week, so I'll pull it up. [00:17:20] Sunil Pai: Uh, wait, so I've, I'm seeing, is this the whole Svelte versus React thing that's been happening over the last two, three days? [00:17:25] swyx: Yes. So basically it's saying React is already so far down almost like its own language. [00:17:30] They should just embrace it more. And instead of using linting to catch rule violations, just make a DSL, people are gonna use it. It's fine. And just like build things in so that it's impossible to make these errors that, that people commonly make. [00:17:47] Sunil Pai: So this is Mike Sherov, uh, he was smoking about it. [00:17:51] He mentioned how it shouldn't be a lint rule. And since we already have customs, insects and GSX, he should introduce a couple of other things. So as you can imagine, the react team has thought about this a lot. So the big problem with this all boils down to that fucking dependency area on use effect, by the way, that's the one that trips, everything else is fine. [00:18:09] Like you stayed all that is like fine. You can get. This is [00:18:13] swyx: what it was. Yeah. People want like state something memos and things like, you know, just build the reactor primitives into the language. [00:18:22] Sunil Pai: So yeah, I think this, this actually, isn't a bad idea and I think that was the whole deal with hooks. Whereas what's the phrase that they use in the docks. [00:18:30] A sufficiently advanced compiler might comply with these things at some point, and you're like, oh wow, great job. On pushing that responsibility onto the community, React team, well done. [00:18:41] swyx: My joke is like it's the react teams equivalent of a assume, a frictionless spherical cow from physics. [00:18:48] Sunil Pai: Exactly. [00:18:48] That's a perfectly spherical code. [00:18:54] swyx: It will exist. [00:18:57] Sunil Pai: And it's just the five of them or six of six of them hacking on this. And they have to make sure they don't break like facebook.com whenever they're working on these things. Imagine it's taken this long for Concurrent to show up and Concurrent is nice by the way. And we can talk about the server rendering API. [00:19:14] Okay. Uh, so react right now is, uh, yeah, that's the one like that. It shouldn't just be an intruder, but, uh, inside the inside Facebook only, well, not everybody can see it, but it's an in an internal, uh, uh, Facebook Wiki page, which is a list of potential F projects. You know, how the react team has fiber, whatever the hell. [00:19:47] Right? So there's a list of these projects that, or when we do this, uh, project F F I forget what the one for, uh, uh, animation that's called, is it called flat? Flat was the dumb one. And so there are lists of them and there are about 15, 20. I'm pretty sure my India has done. So Hey, so, uh, there's a list of them. [00:20:09] And if you look at them and you start assigning values in terms of work, oh, this is about six months of work. This is about, uh, another six months of work. It strikes you that there's a roadmap for about five to 10 years. At least if not more than that, I mean, look at how long it took to get like this. Of course this was very more foundational. [00:20:26] Those could probably happen a little quicker when it comes, which means the react team is like solely aware of what's missing in react right now. And to an extent that they can talk about it because if they do it becomes like a whole thing and like don't really engage in that conversation. They don't, I, I, and I don't blame them for it. [00:20:44] It's very hard to have this discourse without somebody coming in and saying, well, have you considered CSS transitions? I like that. Yes, we have. We have, we have considered CSS a lot. Uh, so, uh, so. There are all these projects like a sufficiently advanced compiler that compiles down to hooks. There's the animation API. [00:21:04] There's a welcome current, et cetera. This whole data fetching thing has been going on for years. And now it's finally starting to come to light, thankfully with collaboration, with the relay team and effectively all of the core when they built out facebook.com and, and that is the length that those are the time periods that Sebastian looks at and says, yeah, this is how we can execute on this because it can be prioritized. [00:21:33] It has to be prioritized by either Facebook wanting it or making Facebook wanted. So for example, the pitch was, Hey, let's rewrite facebook.com the desktop version because they haven't, it's a film mishmash of like hundreds of react routes on one page. It should be a single react route that does this thing. [00:21:52] Now that we have gotten management to agree to a rewrite, let us now attach it to the concurrent mode thing. And that was also part of it, which is in the older version, there was a lot of CPU fighting that used to happen between routes, which is why the whole work for the share dealers started and took like two years to like fix effectively. [00:22:08] They're doing cooperative, multitasking VM in JavaScript, which sure. When you're a Facebook, I guess you've got to like do these things. Uh, and how does that all, [00:22:18] swyx: was that ever offloaded to the browsers, by the way? Like I know there was an effort to split it out of react. [00:22:24] Sunil Pai: So I think last, I checked they were talking to Chrome literally every week. [00:22:29] Uh, but I think it's also been down to, uh, well, what Chrome wants to prioritize at the time. I think it is still going ahead again. It's the sort of work that takes years, so it's not going ahead. Nice and slowly, uh, which is why. Which is why it's architected inside react for the same reason as like it's attached to global and then read off the global. [00:22:52] I think it's also why you can't have two versions of React on the same page. There's the whole hooks thing. But also if you have two versions of React, and they'll just start fighting with each other on the scheduler, because the scheduler would yield to one than to the other than to the other one. [00:23:08] And there would be no like central thing that controls what is on the scheduling pipeline. That's from the last, again, this conversation is at least two years, or maybe they fixed that, but that's the goal of the dealer. There has to be one scheduler for the thread that everybody comes on to, and like tries to pull stuff, uh, with it. [00:23:26] I think it will become a browser API. It's just a question of like, when, like, yeah, I mean, the shared dealer in react itself has undergone so much change over the last three years. Uh, so maybe we should be glad that it isn't in the browser yet, because like, it's changed so much. It's coming there. It's I mean, the fact that they're releasing in November is a big deal. [00:23:45] swyx: You said there's so many projects that you want to ship, and the way to ship it in Facebook is to either convince them that this feature itself is worth it, or you tie it together with something else, like the Facebook, I think it's called FB5 rewrite. [00:24:00] Sunil Pai: Oh yeah. I think it's good for them. Like it worked because the Facebook, facebook.com is now more performant. Like it actually works well and they don't have CPU fighting. The fact that Facebook itself is becoming slightly irrelevant in the world is a whole other conversation. [00:24:17] swyx: Well, you know, I still use my billions, so, uh, it's it's, it improves the experience for them. [00:24:23] Sunil Pai: I'm only being snarky. [00:24:25] swyx: Uh, but I, you know, hopefully hopefully you're like, you know, there's other properties like Instagram and WhatsApp and what is, uh, which hopefully it will apply there. And then obviously like there there's the VR efforts as well. Absolutely. Yeah. [00:24:39] Sunil Pai: And that is the future. In fact, uh, several components also happened because they suddenly realized what they could do for how the deal with server components and server-side streaming rendering was never about an SSR story, or even a CEO. [00:24:54] Facebook doesn't give a fuck about SEO, right. It was about finally they figured out how to use concurrent mode to have a better UX altogether. [00:25:03] React Streaming Server Rendering vs SSR/JAMstack/DSG/DPR/ISR [00:25:03] Sunil Pai: So, okay. I should probably just keep Server components aside for right now. [00:25:06] And I'll just talk about the new streaming rendering API. Okay. [00:25:09] Okay. So I know there's like about three styles of rendering. [00:25:14] I say legacy, but legacy is such a dirty word. I don't mean it in the form that it's old it's in fact, [00:25:20] swyx: traditionally, like, sorry. [00:25:24] Sunil Pai: Uh, heritage Facebook would say heritage, it's a heritage style rendering, um, which is the, Hey, you use something like a rails or spring or some, it could be node as well. And you spit out a bunch of HTML and then you progressively enhance it with sprinkling JavaScript, pick your metaphor there like three or four metaphors that you could use. [00:25:44] Uh, uh, web components actually falls square into this, where it just comes to life only on the browser and then like make stuff interactive. Uh, then there's the whole client fully client side rendered one. So this is create react app or, well, a number of like smaller players then there's server side rendered. [00:26:04] And so as I rendered is actually like, it's not just next year. It's also your Gatsby. I feel like pretty much every, uh, react framework now has some kind of service side rendering story. Okay. So the next slide goes into what types of server-side rendering things happen. [00:26:20] swyx: there are a lot of subdivisions within here, right? [00:26:22] Like, uh, Gatsby is up here trying to reinvent like D S R D P R or something like that, which is like deferred, [00:26:29] Sunil Pai: static, [00:26:32] swyx: DSG, deferred static generation. That's the one. My former employer, Netlify also DPR, and is all, these is all like variations of this stuff with, [00:26:41] Sunil Pai: like, it's a question of where you put the cache is what it is. [00:26:46] It's a TLA three letter acronym to decide where you put the caching in. [00:26:49] Yeah, so there's the whole JAMstack and that's like the whole Netlify story, but also CloudFlare pages, or even GitHub pages. [00:26:56] There's no real runtime server rendering. You just generate a bunch of static assets and you Chuck it and it just works. Then there's fully dynamic, which would be next JS without any caching. Right? Like every request gets server-side rendered then like a bundle loads on top of it. And, um, like suddenly makes it alive, like sort of like it hydrates it. [00:27:16] And then after that it's effectively a fully clients rendered application then there's okay. So I just said ISR, but like you said, there are like three or four after this as well. There's this whole DSP. Yeah. Oh wait. So the new streaming API is actually fundamentally new because. I don't know if people even know this, but react already has a streaming rendering API. [00:27:37] It's called a render to node stream. I think that's the API for it. And the reason that that exists is so that, uh, only for a performance thing on the server where otherwise synchronous renders would block like other requests. And it would make like if for a server that was very, uh, uh, there was heavily trafficked. [00:27:57] It would become like really slow. So at least with the streaming API, yeah. That's the one learner to notice the stream, at least with this one, it wouldn't clash and you could interleave requests from there happening, but it didn't solve like anything else, like nothing, you couldn't actually do anything asynchronous on it, which is kind of that fucking sucks because like, it looks like it's an asynchronous API, but you can't do anything asynchronous through it. [00:28:18] It's the only thing that, okay, so vendor to readable stream is cool because I can, even if you go to the very last slide last bit, once. You know what this is, where the very first link open it up. Like it says react, lazy.cool computer club. So this is the demo that they have that exists with this new API. [00:28:36] This is what they link to. So if you refresh it a couple of times and I'll show you something that happens here, so you see the little spinner that shows up there and then the content loads. Yep. So, um, you know what, maybe I can share my screen because I want to show like a couple of things. Uh, [00:28:53] swyx: yeah. I'll fill in some context, like I knew that the renderToNodeStream API was not good enough, basically because everyone who is doing SSR was doing like a double pass render just to get the data in. Um, and I noticed a very big sticking point for Airbnb so much that they were almost like forking react to something like that to, [00:29:11] Sunil Pai: they invented a caching API. [00:29:13] They did like a whole bunch of things. Okay. So if you have a look here, you'll see that there's a little bit of spinner and then the content comes in. But now what I'm going to do is I'm going to show you the actual HTML. So let's just go to prettier and just pretty far this, for that, we can see the content and I'll show you something that's very like fundament. [00:29:32] That's the playground playground paste, big HTML. All right. So are you looking at this HTML it's rendering rendering by the way, this, these are special comments that mark suspense boundaries. It's very cool. If you come down here, you'll see a dev, which is the spinner. So this is the spinner that you see when you refresh the page. [00:29:52] So this is. And then the rest of like then, like the, like the bits that are below that close and the HTML closes, but content still start stream is streaming in at that point. So like, this is the actual, like devs that are coming in with the content. And then a script tag gets injected that says, Hey, this thing that just came in, shove it into where the spinner was. [00:30:13] This template [00:30:14] swyx: tag is so small. I would, I would have imagined it was much bigger. [00:30:18] Sunil Pai: It's not. So by the way, at this point, the react has not loaded. This is happening without react. This is just a little DOM, much like swelled ha uh, just a little operation that does it. So you, you, you get this content. And, uh, so, so that's the first feature which is that suspense. [00:30:35] It not only works out of the box, but fallbacks and replacing or fallbacks with actual content also happened. Um, I want to pull this outside of this main window to show you something. Um, so you can see the content load in, but keep an eye on the loading spinner. Okay. Just to prove a point. So the content loads in, oh man. [00:30:56] Oh, is it cash just that way? Uh, the content loads in, but the spinner is still going on. That's because there's an artificial delay for the react bundle to show, to show up. That's the point of this demo, which is to show that it can do async. Now you can imagine that it's not just one part of the page. [00:31:13] There could be multiple suspense boundaries here, some with something heavy, something with something asynchronous and they're potentially streaming in effectively in parallel in the, like after the HTML tag closes and they load nicely the, the other cool feature, which is a feature, every framework should steal is if you do a second refresh and here, I think if the, if you do a second refresh and at this point, the react bundle, the JavaScript bundle is cached. [00:31:42] So it loads before the react, the server. Finish the streaming. So at that point, the react says, fuck you, I don't care about the streaming bit anymore. I'm taking over, it's now a client set up like just automatically out of the box, because now that would be faster. So it basically raises the client and suicide. [00:31:58] So suspends working out of the box itself is like a big deal first. So people will start using it like with react dot lazy, but then with data fetching and a bunch of slate styling solutions, which they're also working on. Um, but this is the new server entering API. The reason I was talking about this, I keep losing context about these things. [00:32:19] I should stop sharing, I guess. Um, the absolute best feature of this of course is the reason why is something that comes out of Facebook, which is it works with existing applications and you can incrementally add it. So the first thing you will do is you'll take your render to string that one line somewhere in your code base, which says rendered to. [00:32:39] And you'll replace it with vendor to notable readable string. I mean, [00:32:43] swyx: either way 99% of users have never used render to string. Right. That's what next year is for. [00:32:51] Sunil Pai: Well, that's the, that's all my God. That's part of a whole other conversation, right? [00:32:54] swyx: This is rendered a string as a service. [00:32:59] Sunil Pai: The moment you update next, year's your version of next year? So work on yes. [00:33:04] swyx: Which is good, which is good. Right? Because, uh, people won't even know and they will just benefit, but it's, it's a little bit bad. Okay. [00:33:13] Next.js and the Open Source Commons [00:33:13] swyx: And this is a little bit of my criticism, which is that your blessing, a meta framework, at the expense of all the others, right? Like which admittedly have not been as successful, but, uh, basically reacts Chrome, picked a winner and it was next year. [00:33:27] Sunil Pai: I've been thinking about this so much. Oh, look, it let's get into them at our conversation now. So let's standard disclaimers. I think Guillermo is a mench. [00:33:35] I think the people who work there are incredible. There are some people I'm close to. I'm so happy for them. I know people on the Chrome team who work with these folks. I love them as well. Nicole for me is, uh, is a hero. Uh, and of course the React team at all my buddies, I love them. Okay. That being said, the React team is six people and they don't have the time to build the meta framework and Guillermo, uh the one thing he's incredible at is he's great at building relationships. [00:34:03] He's just amazing at that. Like he, uh, in a very genuine way, like this, there's nothing like ulterior about it. Next JS is open-source and runs on any node runtime and it's designed to do so. There's nothing about it. That's become special on Vercel. Because of that the React team felt, feel like, okay, fine. [00:34:20] We can have a primitive and meta frameworks will solve it. And let's just make sure it works with next two years, because so many other people who are just reach out to them and say, Hey, this new API is showing up. Uh, this is not just with next.js. It's a similar thing is with like react testing library. [00:34:34] When the new activity I showed up, right. I made the PRS to react testing library. I was like, what you should do is have every function and react testing library be wrapped in back act. So nobody really has to like use the API by hand. I just, it's now it's the D and it's a very good testing framework, the Chrome team. [00:34:53] And this is my, I'm not saying this, like, it's a bad thing. I think they did the right thing. The Chrome team realized that if they provide performance enhancements to next years directly, they can have so much impact on the internet because so much of the react tool is running on next year. So fixing how the images are loaded in next year certainly makes the internet faster. [00:35:15] Yeah. And maybe that's what we should do also like for the accessibility, just ship acts in, uh, all the acts rules in development mode, either in like react Dom directly, or at least the next years. Oh yeah. The sweatshop, the axles. Yeah. [00:35:33] swyx: Oh, they're enabled by default. And, uh, your, your app one compile, uh, actually I think it would warn you won't fail by a worn. [00:35:40] Sunil Pai: Okay. So you should be making the swag folks should be making way more noise about that. That is such an incredible draw for accessibility. [00:35:48] swyx: The thing is like, uh, if you encourage, if you think that your, your problems are solved by X, then you're taking a very sort of paint by numbers approach to accessibility. [00:35:57] Right. Which is actually kind of against the spirits of, of, uh, what people really want, which is, um, real audits with like tap through everything. Like the stuff that machines could catch is so little, [00:36:08] Sunil Pai: I agree. The whole point of actual SIS to make sure that all the low hanging fruit is done by default. [00:36:15] It's like TypeScript, like I guess, which is a TypeScript. Doesn't solve all your bugs, but the stupid undefined is not a function once it does. Yeah, exactly. Make sure that your images have. Just by default, like we can have stronger conversations about tab order once you make sure all your images have all tags. [00:36:35] swyx: Uh, okay. Anyway, so, so yeah. So first of all, yeah, I agree with you on the, on this Chrome. And, uh, I think this is opensource winning, right? Like, uh, there's a, there's a commons. Vercel built the most successful react framework, Nate. They went the investor really hard at it. They had the right abstraction level, you know, not too much, not too little, just the right one. [00:36:55] Uh, and now everyone is finding them as like the Schelling point, which is a word I'm coming to use a lot, uh, because you know, that is the most impact that you reach. Uh, so no hate on any of them. It's just like it happens that a venture backed startup benefits from all of this. [00:37:11] Sunil Pai: Can you imagine how hard it makes my job? [00:37:13] We don't run, not on CloudFlare workers, which means Next.js doesn't run on it. It's annoying. [00:37:19] swyx: Oh, is there any attempt to make it run? [00:37:22] Sunil Pai: There are a couple of ways where we can get it to work, but it like, it's a lot of polyfill and, uh, we'll get that. Like, I expect it to be fixed within the next three to six months, but out of the box, it doesn't run on it. [00:37:35] And for me in my head, it doesn't, it's not even about CloudFlare workers. I'm like, oh shit. That's what makes Bezos like even richer because everyone's got, has, if you want to use Nadia using AWS or Lambda. And that just means more folks are using AWS. I'm just like, okay, I guess. Sure. I know you work there as well, but it's just very annoying to me where I'm like, shit. [00:37:56] What's even more interesting is that node is now moving to implementing web standard APIs inside of it. So they already have the streams implementations. They will have fetch fetch will be a node API. Like it will be implemented based on standards, which means the request response objects. And once that happens and people, if people build frameworks on that, then you can say that it will run on CloudFlare workers because the cloud fed worker's API is also like a standards based thing. [00:38:21] So it's an interesting shift of like what's happening in the, in the runtime world. Also conveniently the person who implemented the web stream implementation at node just started at CloudFlare like last month, like James. Oh, James [00:38:38] swyx: now. Okay. Yeah. I recognize [00:38:39] Sunil Pai: a great guy by the way. Uh, very, I just love these people who have like clarity of thought when they talk James as well. [00:38:46] The Third Age of JavaScript [00:38:46] swyx: We're kind of moving into the other topic of like JavaScript in 2021. Right. So first of all, I have a meta question of how do you keep informed of all this stuff? Like I ha I had no idea before you told me about this Node stuff. How do you know? [00:38:57] Sunil Pai: I have an internet information junkie problem. [00:39:00] I replaced the weed smoking habit with a Twitter habit. This is what it is. [00:39:05] swyx: You're not unlike some magic mailing lists that like tells you all this stuff. Okay. [00:39:09] Sunil Pai: Like reading the tea leaves is what it is. Like. I keep trying to find out what's going on. The problem [00:39:14] swyx: is I, I, I feel like I'm ready. I'm relatively plugged in, but you're like, you're way more plugged in than me. [00:39:22] and then this development with node adopting web standard APIs, um, is this a response to Deno? [00:39:28] Sunil Pai: I don't know if it's a response to Deno because I know Mikeal Rogers wrote about this. Like your. That we made a mistake by trying to polyfill note APS and browser code with like modules and stuff. [00:39:41] Right? Like that's what the whole browser, if I, during those days, when we started actually using the same module system and the word isomorphic came up, what ended up happening was naughty APIs were polyfill in web land, but what should have happened is we should have gone the other way. And it would have kept like bundle this bundle size problem would have been a web smaller pro problem right now, just because of that. [00:40:07] So I know that the folks at not have been thinking about it for awhile, maybe Deno finally pushed them to do it, but I don't, I don't, I don't, I don't think it's like that reductive. I don't think it's just, it's just dental. It's very much a, this is the right time to do it and we actually can do it now. [00:40:22] So let's like flesh it out and do it the right way. Uh, and it's hard to do it in, in no, right. It's not just that you can just implement this thing. Like, what does making an HTTP server mean now? Because the request response objects are slightly different in shape. So you have to make sure that you don't break existing code. [00:40:39] So it's not as simple as saying, oh, we're just implementing the APS. That being said, having fetch inside node proper is going to be great. I think. Excellent. [00:40:47] swyx: Yeah. Yeah, no more node fetch. Um, yeah. You know, my other thoughts on I've been, I've been doing this talk called the third age of JavaScript. Right. [00:40:55] Which is a blog post that I wrote last year that, um, honestly I feel quite a bit of imposter syndrome around it because all I did was name a thing and like it was already happening. It was, you already saw, like, I think basically when, when COVID hit, a lot of people were. I have a lot of time on my hands, I'm going to make new projects or something. [00:41:14] Um, uh, and then, yeah, so I just, I named it and I just called it a few trends. So the, the trends I I'm talking about are the rise of IES modules first, you know, in, in development and in production, uh, concurrently the death of 11, which I'm also tracking. [00:41:30] Sunil Pai: Yes, those are, those are both come to fruition. [00:41:34] swyx: Which, by the way, I think the us government will have to drop by 11, uh, sometime in the next six months or so because, uh, the, the use, the usage levels have plummeted. [00:41:43] 3.6% of all visits to the U S government website in November, 2020 was I 11 and now that has dropped to 1.6, um, all [00:41:51] Sunil Pai: accelerating the drop is actually accelerating. [00:41:53] swyx: Uh, I don't know if it's accelerated it's everything, but it's under the 2% mark that the us government sets for itself. [00:41:59] They have an opportunity to essentially say like once it's stable, you know, there's no chance that it'll ever go back up again. Uh, they could just deprecate 11 for all government websites and then that, that will be the signal for all enterprises. And that's it. Yeah. So, um, and then the second. [00:42:15] Oh, I was going to move on the second bit. But what was your calling? [00:42:19] Sunil Pai: Oh, just saying that this happened, like, while I was working in JP Morgan over the last year, they did the same shift, but they're like, yeah, we are now a Chrome company. Literally none of our clients are asking for this and you know, it, it was just in rules somewhere, or we need to target, I 11, some people looked at it and said, okay, fine. [00:42:35] What happened is people are spending money on something that wasn't giving them the returns. And that's when a bank is like, yeah, we don't need [00:42:41] swyx: to do this anymore. Like you, you can deprecate free support. Right. And, and just make, just charge for 11 support, stop spreading it out among all the other users who are bearing the cost of development and maintenance. [00:42:54] The other one was collapsing layers, which is the death of Unix philosophy. Like , we used to have one tool does one thing, but now we want to combine everything. So, uh, Deno and Rome both have ambitions of linter format or test runner, all of that into a single binary, because the idea of what we want out of a default runtime has changed, uh, from a, for a very minimalist thing. And I always made the comparison to what word processors used to be like. [00:43:18] So, are you aware of Benedict Evans? He has a blog post, which is amazing about what a job of a platform should be. And he talks about like in 1980s word processors used to only let you type words. And if you wanted a horizontal layout, if you wanted word counts, if you wanted footnotes, these are all plugins that you buy and install separately. [00:43:38] Right. Okay. So, but as we evolve, as we just use all these things, we realize that these are just like the same tool that we want out of a word processor. So then they absorb all these features instead of plugins. They're just part of the platform now. They're there now in the new table stakes. [00:43:53] So I make that analogy to the runtimes that already doing, right. Like, Node used to be this like much more minimal thing. And, uh, but now we are expecting more and more out of our default setup with all these tools . Um, it's also very wasteful because when each of these tools don't know each other, they're all parsing their own ASTs running, running their own code. And then yeah, that's the whole [00:44:12] Sunil Pai: proposition, but yeah. [00:44:14] swyx: Any, any tool that collapses layers will, we will meet this, like, ESBuild, um, collapsed. Like a standard web pack would do like five or six AST runs. ESBuild collapsed it to two to three. That's a source of its speed as well. [00:44:27] Sunil Pai: One of my favorite facts about ESBuild is that it is faster to minify the code than to not modify the code when you run. Yes. And the reason for that is because when you try, when it tries to do the full AST, keep comment notes, everything else, it has to do a lot more bookkeeping, but the moment it just ditches all those things, because ESBuild doesn't do like full magnification, like something like a torso, but it does do like a smaller symbol substitution, white space, uh, uh, removes all white spaces. [00:44:59] And it does like some dead code elimination. Uh, and it's a lot more work to keep the bookkeeping for everything and all the white space notes than to not do it. So he has built is actually faster when you have a modification turned on, love it. [00:45:14] swyx: It's amazing. It's amazing. [00:45:16] [00:45:16] ESbuild vs SWC vs Zig [00:45:16] swyx: Do you have opinions on ESBuild versus SWC? [00:45:18] Sunil Pai: Okay. So I like ESBuild. Uh, because I was very strongly looking for something a lot more opinionated. I've noticed that the reason that code basis Surat usually boiled down to the acute decisions that you make. Like in the very beginning of the project, you can do anything. I mean, whichever dumbass came up with the idea of baby plugin, macros has like ruined a lot of lives. [00:45:41] It was me. I came up today, but that is like, then you're like tight. So the thing that ESBuild does is very like its creator, Evan Wallace, which is that it's, it's one of a kind like, he's not really interested so much in having community, uh, uh, PRS or like having suggestions on how it should be built. He has a very strong vision of what it should be like, which is why there are no AST level plugins and all that jazz. [00:46:08] And because of that, because of, like I said, because he's collapsed the lyrics and collapse, the size of the development team to just himself, he has like such a clear vision on what it should be. So it w is good. It would be great for, I want to say 95% of projects that fall under the things he has designed at four. [00:46:28] Okay. Uh, and that's a lot of applications. That's a shit ton of applications. That's like everything, but your host, if you need anything, uh, unique, I'll give you one. That's like a very good use case that is bill will never use. Do you know what, um, uh, really has this idea of persistent queries. Okay. So like for whoever's hearing who doesn't know it, right? [00:46:52] Like you can write a query inside Java. And when it compiles it out, it takes out the query and replaces it just with an identifier, like, like a little eight character identifier. And it hosts that query instead of like on the service side. And it says, oh, that eight, eight character query, you can just hit it as a restaurant point now. [00:47:11] So you can write the code internally in JavaScript where it belongs, but it doesn't add like to your bundle or whatever it is. So ESBuild will never support this, which means if you want to do really optimizations on your react code base, you won't be able to do it all. You have to like add on to yours, which you could do. [00:47:29] I guess like you can still use Babel would, uh, SWC is meant to be a platform and which is why next years will use it because next gen is the meta framework, not just for react, but also for like some programming opinions, extracting get server props, get started, props, which one you want to be that this thing after server components comes into play, but a number of things like there will be people who always want to do. [00:47:54] The emotion macro now is like fairly, uh, popular that they will want to use it. So I assume they will implement it in, uh, interest. I know. Do you know what bun is by the way? Do you mean, do you know, how are you following Jared Sumner? Some [00:48:10] swyx: summers, no, wait, so [00:48:13] Sunil Pai: key is reimplementing ESB, but in a language called Zig it's another systems programming language. [00:48:20] And he's his claim is that it's about three times faster than you spell it right now, which is already some 200 times faster than Babel loader. It is just our web pack, but it's a language you said it? No. So the language is called Zig lines at AIG, but the thing he's building is called a, B U N. He hasn't shared it in public yet. [00:48:41] I think he's actually planning on sharing it like next week. Like I think it's that imminent. He's been sharing numbers right now. Yeah. That's the guy, Jared. Uh, I love, I should've followed him like a while ago, create great feed, uh, excellent content. And like, he's, he he's thinking that he's going to like implement. [00:48:57] He might actually implement an AST level, uh, uh, plugin, micro API, possibly just implement the emotion one. I think he was just, yeah. See, oh, that's like literally the tweet would write under the main one right there where he's like, Hey, what if we actually just did this in? Uh, oh, [00:49:14] swyx: he's right. He's he's right with you. [00:49:17] Yeah. Like he's [00:49:17] Sunil Pai: just talking about it, like right there. So, uh, so SWC versus ESBuild, I don't think is the conversation. I think ESBuild will have a rise. A bunch of people will use it. The nice thing, the best feature about ESBuild is because there are aren't any like cute decisions. You will be able to move away from it to whatever succeeds. [00:49:39] Th there's nothing customer [00:49:40] swyx: that I believe that was Evan's original idea. That IES build was a proof of existence that day there's a better way. And that he stuck to it for way longer than I thought he would. [00:49:51] Sunil Pai: People are using it in production and everything know everything about the designers that it's replaceable. [00:49:56] That it's just a, [00:49:59] swyx: that's wonderful. Isn't that amazing when people design their stuff? W. You know, it [00:50:04] Sunil Pai: isn't kind of pressure that he would have had the best. Thank goodness. It was the successful CTO of Figma with money in the bank who is implementing this and didn't have anyone to impress. You know what I mean? [00:50:16] It was like, yeah, let's put a macro API and what else do you want? Like, whatever. No, he doesn't [00:50:21] swyx: go. Yeah. But he just needs to police himself and no one else. Right. If you don't like it, [00:50:26] Sunil Pai: this is during his downtime from Figma that he's working on this. [00:50:30] swyx: Um, my, my secret theory is that he's doing this as an, as a Figma ad. [00:50:33] Like, you know, if he, if the CTO of Figma does this for fun, imagine what it's like to work inside of Figma, you know, like of, I've heard it's pretty great, [00:50:42] Sunil Pai: pretty great working inside of Figma too. Well, the code is like, it's really cool. [00:50:46] Let Non-X Do X: Figma vs Canva, Webflow vs Wix/Squarespace [00:50:46] Sunil Pai: Did you actually point out. Uh, Ken was like six times bigger than Figma. [00:50:51] Now [00:50:52] swyx: you wanna talk about that? [00:50:53] Sunil Pai: Oh God. That's. I didn't realize until you pointed it out. [00:50:58] swyx: Incredible. Imagine all the geniuses working in Figma and go looking at Canada and like, yo, like I, I have like a thousand times your features and your six times in my size as a business. [00:51:10] Sunil Pai: Uh, but I hope every one of those engineers understands the value of sales and like reaching out to your actual customers because [00:51:17] swyx: I don't think it's just sales. [00:51:18] It's more like, uh, they're always going to be more non, like, this is a category of software called let Nanex do X, right? Let non-designers do design. Whereas Figma is clearly for designers doing design. Um, and there's always going to be like a tool, three orders of magnitude more non-experts uh, who just want to do basic shit. [00:51:37] Sunil Pai: Oh man. I hope that flow has a multi-billion dollar buyout and at some point, [00:51:42] swyx: uh, I mean, I, yeah, I mean there's clearly something that w the problem with flow is that. They're too close to code. Right? You have to learn CSS the box model. [00:51:56] Sunil Pai: Yeah. I mean, they do say there's no code, but really they're a visual, [00:52:00] swyx: if you don't know CSS when using Webflow you're screwed. [00:52:03] Like [00:52:04] Sunil Pai: that's right. It's uh, they have, they have the best grid editor on the market too. I have to say that. I [00:52:10] swyx: mean, the UI is just amazing, right? It's just like, um, yeah, I mean, you know, there's a reason why like the Wix is, and the Squarespaces are actually worth more than the workflow and it's not just cause they were around earlier. [00:52:22] Like, um, they're, they're just easier to use for non-technical people. [00:52:26] Sunil Pai: That's a good, you you're talking about why did we even start talking about this? What did you want to talk about? Uh, we were talking [00:52:33] swyx: about like, uh, 32 JavaScript. Um, so I think we kind of like dealt with those, those, uh, those topics. [00:52:39] Was there anything else that you want to talk about? [00:52:40] Didn't JavaScript land, [00:52:42] JavaScript Twitter and Notion's 9mb Marketing Site [00:52:42] Sunil Pai: I don't know if you have noticed, but I've kind of actually stopped engaging in the JavaScript discourse on Twitter specifically, which actually hurts me like a little bit, because that's where all my jobs could friends are. And that's kind of like, I've seen it all. I've seen JavaScript router now for the last 11 years, I would think 10, 11 years that I've seen it. [00:53:02] And I used to like participate very heavily. And back to the thing that you, uh, that we were just discussing about the conversations that happened too, about like SBA versus MPA and about like the whole notion blow up about how they made them thing into like 800 KB. Yep. Uh, the easiest kind of discourse to have is to have like one absolutist opinion, uh, that I saw a number of people in like those threads and the surrounding threads have, which is a, well, this is bad or this is good. [00:53:35] And, uh, that's, that's all I got to say about it. Now give me like 40 likes on this reply industry. Uh, whereas like there's real opportunity here to understand how and yeah, that's the one, that's the one with treat by the way. Clearly it got like attention. No, [00:53:51] swyx: by the way I phrased it very neutrally. I actually was pretty careful. [00:53:54] Cause I knew that it's going to attract some buzz. I had no idea what's going to be this much, but [00:54:00] Sunil Pai: no, no, no. But like I'm so interested in talking about, uh, so this is what I was talking to you about, which is like, it's not just about a website at one point of time. It's about the system that generates these kinds of like artifacts, uh, of, so for example, with what, what did they say? [00:54:24] They're there 8 47 KB right now. They're not 8 47 KV today. They were 8 47 KB. When you, uh, Uh, tweeted this, uh, on the 11th, they are not in 47 KB. Now they might be 852, or they might be 841. Are you about to check? [00:54:43] swyx: No, no, no, no, I'm not. I'm not, it doesn't matter. The exact number. Doesn't matter. I'm going to give you another example, which also came up, which is Netflix. [00:54:49] Remember they ripped out react and he said they have react back [00:54:54] Sunil Pai: on Netflix. I use, are you serious on that? Wait, did they have like both Netflix, they have both react and jQuery, jQuery and react on that page right now. It's just, but like, for me, it's interesting that, which is like, I think the most insightful tweet in this was very pointed out that nobody noticed this until they told it to us. [00:55:16] Nobody saw it. It bothered. Yeah. That's the one, like nobody bothered about it. It was still making the money. They were happy about it. And they wanted to share that. And we need more of them. We need more people to be like sharing the process because if we react very badly to these things, then fewer people will want to actually share the numbers. [00:55:34] And you won't learn from the industry, but I don't know whether it's a good thing or a bad thing. It does mean that you can make a multi-billion dollar company with a marketing site. That's nine MB of Charles' script. And I think, I think people who have very strong opinions about how much jealous should be on a page to take a step back and wonder how do you make it? [00:55:55] So like, how do you, from the very beginning of like running your company, how do you make it so that it doesn't go up beyond that? Also, what opportunities are you abandoning by focusing on making sure your marketing page, uh, has like 100 KB of JavaScript instead of like nine MB [00:56:17] swyx: shipping velocity, right? [00:56:19] Sunil Pai: You are somewhere, you are spending effort on it somewhere. Just so we're clear because somebody will look at it and say, fuck you, are you suggesting that we all put in that's not what I'm saying. I'm just saying that the resources, that word, but resources at these companies are limited and they are, they they're prioritized and sequenced and you should ask yourself in what order you want to do it and who you're trying to please, are you trying to please your customers and your users or the peanut gallery on Twitter? [00:56:48] And I think that's something that like, I, it's why I don't engage so much anymore because it's so hard to communicate in once and somebody will come in with a, well, fuck you, you work for Facebook or used to work for Facebook. What would you know? I'm like, you got me that kind of ends the conversation that, right. [00:57:04] Like I'm studying contributed to babies being burned alive or whatever it is like, this is what it is. [00:57:12] swyx: Um, it's a nuanced debate, like, uh, because they also did some like notion clearly did some stupid stuff here. Right? Like it, it, they could have spent a day. Uh, so do you know why it was 9.9 megabytes? [00:57:25] Sunil Pai: If I understand it was the whole notion that that was being used, the [00:57:27] swyx: whole app. [00:57:28] Yeah. They were shipping the whole, there was actually someone from notion, uh, answering me. Uh, it's here. Yeah. This guy's, this guy works at notion before the marketing site was another route in our, at the time 9.1 NBME and app, we load the whole app just to show the sign up button. [00:57:44] So what, [00:57:45] Sunil Pai: what it's worth Facebook sign up page does start prefetching actual Facebook code so that once you log in it loads instantaneously. So there's a reason to do it. It's just that it shouldn't be nine and B of course. That's [00:58:00] swyx: yeah, they could have like took a day every, every six months or something like perfect day, you know, and do that. [00:58:06] So that's why I'm hesitant, uh, giving them a pass for like, okay, so what your multi-billion dollar company? This is embarrassing. This is just an unprofessional. Um, so yes,

covid-19 god ceo amazon netflix game canada learning australia google business technology future australian drop wrap utah rome nfts whatsapp airbnb vr seo finish incredible honestly jeff bezos dom cto react flat babel shopify ux api redux ironically chrome jp morgan ui canva picasso ml aws java server github notion components apis cms hydrogen stripe vm sis javascript html mb apache temporal slides sba book of mormon imperative cpu css u s kb ast oh god sql wix node js kv mpa gatsby prs cloudflare v8 figma cdn lambda sunil dst surat aps dsp angular aig concurrent mongodb unix json zig typescript graphql isr dsl webflow framers jquery cdm deno ssr tla esb uda dpr ies schelling netlify auth0 jamstack stouffer svelte dsg third age declarative swc turpentine stately jsx benedict evans ecmascript matthew phillips adam morris ocaml asts cloudfare otrs eular gsx dagster james allworth react server components xstate david khourshid settimeout mikeal rogers glen martin sinofsky sunil pai fb5 nanex

Deeper JavaScript: setTimeout Is Way More Important Than You Think

Building Livewire

Play Episode Listen Later May 28, 2021 10:07

setTimeout is a little utility I always thought was just for... well.. setting a timeout. It's so much more.

What Do Your Actions Speak of You?

Play Episode Listen Later Dec 18, 2020 14:33

Greg wraps up the week reviewing the lessons Joseph taught us in Matthew 1:18-25. Ways to help support HOPE is HereTexting the word GIVE to 833-713-1591Website https://www.hopeisheretoday.org/donate Shopping on Amazon, select HOPE is Here as your favorite charity (EIN: 83-0522555)Login through this link > https://smile.amazon.com/ch/83-0522555 (function() {var iFrame = document.createElement('iframe'); iFrame.style.display = 'none'; iFrame.style.border = "none"; iFrame.width = 310; iFrame.height = 256; iFrame.setAttribute && iFrame.setAttribute('scrolling', 'no'); iFrame.setAttribute('frameborder', '0'); setTimeout(function() {var contents = (iFrame.contentWindow) ? iFrame.contentWindow : (iFrame.contentDocument.document) ? iFrame.contentDocument.document : iFrame.contentDocument; contents.document.open(); contents.document.write(decodeURIComponent("%3Cdiv%20id%3D%22amznCharityBannerInner%22%3E%3Ca%20href%3D%22https%3A%2F%2Fsmile.amazon.com%2Fch%2F83-0522555%22%20target%3D%22_blank%22%3E%3Cdiv%20class%3D%22text%22%20height%3D%22%22%3E%3Cdiv%20class%3D%22support-wrapper%22%3E%3Cdiv%20class%3D%22support%22%20style%3D%22font-size%3A%2025px%3B%20line-height%3A%2028px%3B%20margin-top%3A%2029px%3B%20margin-bottom%3A%2029px%3B%22%3ESupport%20%3Cspan%20id%3D%22charity-name%22%20style%3D%22display%3A%20inline-block%3B%22%3EHope%20Is%20Here.%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%3Cp%20class%3D%22when-shop%22%3EWhen%20you%20shop%20at%20%3Cb%3Esmile.amazon.com%2C%3C%2Fb%3E%3C%2Fp%3E%3Cp%20class%3D%22donates%22%3EAmazon%20donates.%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fa%3E%3C%2Fdiv%3E%3Cstyle%3E%23amznCharityBannerInner%7Bbackground-image%3Aurl(https%3A%2F%2Fm.media-amazon.com%2Fimages%2FG%2F01%2Fx-locale%2Fpaladin%2Fcharitycentral%2Fbanner-background-image._CB485922134_.png)%3Bwidth%3A300px%3Bheight%3A250px%3Bposition%3Arelative%7D%23amznCharityBannerInner%20a%7Bdisplay%3Ablock%3Bwidth%3A100%25%3Bheight%3A100%25%3Bposition%3Arelative%3Bcolor%3A%23000%3Btext-decoration%3Anone%7D.text%7Bposition%3Aabsolute%3Btop%3A20px%3Bleft%3A15px%3Bright%3A15px%3Bbottom%3A100px%7D.support-wrapper%7Boverflow%3Ahidden%3Bmax-height%3A86px%7D.support%7Bfont-family%3AArial%2Csans%3Bfont-weight%3A700%3Bline-height%3A28px%3Bfont-size%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.when-shop%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.donates%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A21px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D%3C%2Fstyle%3E")); contents.document.close(); iFrame.style.display = 'block';}); document.getElementById('amznCharityBanner').appendChild(iFrame); })();

amazon speak 3d shopping 3b login 7d createelement iframe settimeout setattribute

What is God Asking You to Do Today?

Play Episode Listen Later Dec 17, 2020 14:38

Greg continues discussing the lessons learned from the first Christmas found in Matthew 1:18-25. Joseph did not want to do what God was asking of him. Are you doing what God is asking you to do? Ways to help support HOPE is HereTexting the word GIVE to 833-713-1591Website https://www.hopeisheretoday.org/donate Shopping on Amazon, select HOPE is Here as your favorite charity (EIN: 83-0522555)Login through this link > https://smile.amazon.com/ch/83-0522555 (function() {var iFrame = document.createElement('iframe'); iFrame.style.display = 'none'; iFrame.style.border = "none"; iFrame.width = 310; iFrame.height = 256; iFrame.setAttribute && iFrame.setAttribute('scrolling', 'no'); iFrame.setAttribute('frameborder', '0'); setTimeout(function() {var contents = (iFrame.contentWindow) ? iFrame.contentWindow : (iFrame.contentDocument.document) ? iFrame.contentDocument.document : iFrame.contentDocument; contents.document.open(); contents.document.write(decodeURIComponent("%3Cdiv%20id%3D%22amznCharityBannerInner%22%3E%3Ca%20href%3D%22https%3A%2F%2Fsmile.amazon.com%2Fch%2F83-0522555%22%20target%3D%22_blank%22%3E%3Cdiv%20class%3D%22text%22%20height%3D%22%22%3E%3Cdiv%20class%3D%22support-wrapper%22%3E%3Cdiv%20class%3D%22support%22%20style%3D%22font-size%3A%2025px%3B%20line-height%3A%2028px%3B%20margin-top%3A%2029px%3B%20margin-bottom%3A%2029px%3B%22%3ESupport%20%3Cspan%20id%3D%22charity-name%22%20style%3D%22display%3A%20inline-block%3B%22%3EHope%20Is%20Here.%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%3Cp%20class%3D%22when-shop%22%3EWhen%20you%20shop%20at%20%3Cb%3Esmile.amazon.com%2C%3C%2Fb%3E%3C%2Fp%3E%3Cp%20class%3D%22donates%22%3EAmazon%20donates.%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fa%3E%3C%2Fdiv%3E%3Cstyle%3E%23amznCharityBannerInner%7Bbackground-image%3Aurl(https%3A%2F%2Fm.media-amazon.com%2Fimages%2FG%2F01%2Fx-locale%2Fpaladin%2Fcharitycentral%2Fbanner-background-image._CB485922134_.png)%3Bwidth%3A300px%3Bheight%3A250px%3Bposition%3Arelative%7D%23amznCharityBannerInner%20a%7Bdisplay%3Ablock%3Bwidth%3A100%25%3Bheight%3A100%25%3Bposition%3Arelative%3Bcolor%3A%23000%3Btext-decoration%3Anone%7D.text%7Bposition%3Aabsolute%3Btop%3A20px%3Bleft%3A15px%3Bright%3A15px%3Bbottom%3A100px%7D.support-wrapper%7Boverflow%3Ahidden%3Bmax-height%3A86px%7D.support%7Bfont-family%3AArial%2Csans%3Bfont-weight%3A700%3Bline-height%3A28px%3Bfont-size%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.when-shop%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.donates%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A21px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D%3C%2Fstyle%3E")); contents.document.close(); iFrame.style.display = 'block';}); document.getElementById('amznCharityBanner').appendChild(iFrame); })();

christmas god amazon 3d shopping 3b login 7d createelement iframe settimeout setattribute

The First Christmas

Play Episode Listen Later Dec 16, 2020 14:36

Follow along in Matthew 1:18-25 as Greg reviews the lessons learned from Joseph during the first Christmas. Ways to help support HOPE is HereTexting the word GIVE to 833-713-1591Website https://www.hopeisheretoday.org/donate Shopping on Amazon, select HOPE is Here as your favorite charity (EIN: 83-0522555)Login through this link > https://smile.amazon.com/ch/83-0522555 (function() {var iFrame = document.createElement('iframe'); iFrame.style.display = 'none'; iFrame.style.border = "none"; iFrame.width = 310; iFrame.height = 256; iFrame.setAttribute && iFrame.setAttribute('scrolling', 'no'); iFrame.setAttribute('frameborder', '0'); setTimeout(function() {var contents = (iFrame.contentWindow) ? iFrame.contentWindow : (iFrame.contentDocument.document) ? iFrame.contentDocument.document : iFrame.contentDocument; contents.document.open(); contents.document.write(decodeURIComponent("%3Cdiv%20id%3D%22amznCharityBannerInner%22%3E%3Ca%20href%3D%22https%3A%2F%2Fsmile.amazon.com%2Fch%2F83-0522555%22%20target%3D%22_blank%22%3E%3Cdiv%20class%3D%22text%22%20height%3D%22%22%3E%3Cdiv%20class%3D%22support-wrapper%22%3E%3Cdiv%20class%3D%22support%22%20style%3D%22font-size%3A%2025px%3B%20line-height%3A%2028px%3B%20margin-top%3A%2029px%3B%20margin-bottom%3A%2029px%3B%22%3ESupport%20%3Cspan%20id%3D%22charity-name%22%20style%3D%22display%3A%20inline-block%3B%22%3EHope%20Is%20Here.%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%3Cp%20class%3D%22when-shop%22%3EWhen%20you%20shop%20at%20%3Cb%3Esmile.amazon.com%2C%3C%2Fb%3E%3C%2Fp%3E%3Cp%20class%3D%22donates%22%3EAmazon%20donates.%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fa%3E%3C%2Fdiv%3E%3Cstyle%3E%23amznCharityBannerInner%7Bbackground-image%3Aurl(https%3A%2F%2Fm.media-amazon.com%2Fimages%2FG%2F01%2Fx-locale%2Fpaladin%2Fcharitycentral%2Fbanner-background-image._CB485922134_.png)%3Bwidth%3A300px%3Bheight%3A250px%3Bposition%3Arelative%7D%23amznCharityBannerInner%20a%7Bdisplay%3Ablock%3Bwidth%3A100%25%3Bheight%3A100%25%3Bposition%3Arelative%3Bcolor%3A%23000%3Btext-decoration%3Anone%7D.text%7Bposition%3Aabsolute%3Btop%3A20px%3Bleft%3A15px%3Bright%3A15px%3Bbottom%3A100px%7D.support-wrapper%7Boverflow%3Ahidden%3Bmax-height%3A86px%7D.support%7Bfont-family%3AArial%2Csans%3Bfont-weight%3A700%3Bline-height%3A28px%3Bfont-size%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.when-shop%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.donates%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A21px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D%3C%2Fstyle%3E")); contents.document.close(); iFrame.style.display = 'block';}); document.getElementById('amznCharityBanner').appendChild(iFrame); })();

christmas amazon 3d shopping 3b first christmas login 7d createelement iframe settimeout setattribute

Wise Things Dad Used to Say

Play Episode Listen Later Dec 15, 2020 14:35

Today recognizes his dad's birthday by reflecting on words of wisdom from his dad. You'll want a pencil and paper to jot these downs. They are gems! Ways to help support HOPE is HereTexting the word GIVE to 833-713-1591Website https://www.hopeisheretoday.org/donate Shopping on Amazon, select HOPE is Here as your favorite charity (EIN: 83-0522555)Login through this link > https://smile.amazon.com/ch/83-0522555 (function() {var iFrame = document.createElement('iframe'); iFrame.style.display = 'none'; iFrame.style.border = "none"; iFrame.width = 310; iFrame.height = 256; iFrame.setAttribute && iFrame.setAttribute('scrolling', 'no'); iFrame.setAttribute('frameborder', '0'); setTimeout(function() {var contents = (iFrame.contentWindow) ? iFrame.contentWindow : (iFrame.contentDocument.document) ? iFrame.contentDocument.document : iFrame.contentDocument; contents.document.open(); contents.document.write(decodeURIComponent("%3Cdiv%20id%3D%22amznCharityBannerInner%22%3E%3Ca%20href%3D%22https%3A%2F%2Fsmile.amazon.com%2Fch%2F83-0522555%22%20target%3D%22_blank%22%3E%3Cdiv%20class%3D%22text%22%20height%3D%22%22%3E%3Cdiv%20class%3D%22support-wrapper%22%3E%3Cdiv%20class%3D%22support%22%20style%3D%22font-size%3A%2025px%3B%20line-height%3A%2028px%3B%20margin-top%3A%2029px%3B%20margin-bottom%3A%2029px%3B%22%3ESupport%20%3Cspan%20id%3D%22charity-name%22%20style%3D%22display%3A%20inline-block%3B%22%3EHope%20Is%20Here.%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%3Cp%20class%3D%22when-shop%22%3EWhen%20you%20shop%20at%20%3Cb%3Esmile.amazon.com%2C%3C%2Fb%3E%3C%2Fp%3E%3Cp%20class%3D%22donates%22%3EAmazon%20donates.%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fa%3E%3C%2Fdiv%3E%3Cstyle%3E%23amznCharityBannerInner%7Bbackground-image%3Aurl(https%3A%2F%2Fm.media-amazon.com%2Fimages%2FG%2F01%2Fx-locale%2Fpaladin%2Fcharitycentral%2Fbanner-background-image._CB485922134_.png)%3Bwidth%3A300px%3Bheight%3A250px%3Bposition%3Arelative%7D%23amznCharityBannerInner%20a%7Bdisplay%3Ablock%3Bwidth%3A100%25%3Bheight%3A100%25%3Bposition%3Arelative%3Bcolor%3A%23000%3Btext-decoration%3Anone%7D.text%7Bposition%3Aabsolute%3Btop%3A20px%3Bleft%3A15px%3Bright%3A15px%3Bbottom%3A100px%7D.support-wrapper%7Boverflow%3Ahidden%3Bmax-height%3A86px%7D.support%7Bfont-family%3AArial%2Csans%3Bfont-weight%3A700%3Bline-height%3A28px%3Bfont-size%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.when-shop%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.donates%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A21px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D%3C%2Fstyle%3E")); contents.document.close(); iFrame.style.display = 'block';}); document.getElementById('amznCharityBanner').appendChild(iFrame); })();

amazon 3d wise shopping 3b login 7d createelement iframe settimeout setattribute

May the God of HOPE Fill You with Joy

Play Episode Listen Later Dec 14, 2020 14:42

As Greg reflects on his 3-year anniversary of HOPE is Here Ministries, he reviews the many issues that 2020 brought to us. Greg hopes your soul has gotten reconnected with Jesus during this year of a the pandemic and to remember Romans 15:13. Ways to help support HOPE is HereTexting the word GIVE to 833-713-1591Website https://www.hopeisheretoday.org/donate Shopping on Amazon, select HOPE is Here as your favorite charity (EIN: 83-0522555)Login through this link > https://smile.amazon.com/ch/83-0522555 (function() {var iFrame = document.createElement('iframe'); iFrame.style.display = 'none'; iFrame.style.border = "none"; iFrame.width = 310; iFrame.height = 256; iFrame.setAttribute && iFrame.setAttribute('scrolling', 'no'); iFrame.setAttribute('frameborder', '0'); setTimeout(function() {var contents = (iFrame.contentWindow) ? iFrame.contentWindow : (iFrame.contentDocument.document) ? iFrame.contentDocument.document : iFrame.contentDocument; contents.document.open(); contents.document.write(decodeURIComponent("%3Cdiv%20id%3D%22amznCharityBannerInner%22%3E%3Ca%20href%3D%22https%3A%2F%2Fsmile.amazon.com%2Fch%2F83-0522555%22%20target%3D%22_blank%22%3E%3Cdiv%20class%3D%22text%22%20height%3D%22%22%3E%3Cdiv%20class%3D%22support-wrapper%22%3E%3Cdiv%20class%3D%22support%22%20style%3D%22font-size%3A%2025px%3B%20line-height%3A%2028px%3B%20margin-top%3A%2029px%3B%20margin-bottom%3A%2029px%3B%22%3ESupport%20%3Cspan%20id%3D%22charity-name%22%20style%3D%22display%3A%20inline-block%3B%22%3EHope%20Is%20Here.%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%3Cp%20class%3D%22when-shop%22%3EWhen%20you%20shop%20at%20%3Cb%3Esmile.amazon.com%2C%3C%2Fb%3E%3C%2Fp%3E%3Cp%20class%3D%22donates%22%3EAmazon%20donates.%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fa%3E%3C%2Fdiv%3E%3Cstyle%3E%23amznCharityBannerInner%7Bbackground-image%3Aurl(https%3A%2F%2Fm.media-amazon.com%2Fimages%2FG%2F01%2Fx-locale%2Fpaladin%2Fcharitycentral%2Fbanner-background-image._CB485922134_.png)%3Bwidth%3A300px%3Bheight%3A250px%3Bposition%3Arelative%7D%23amznCharityBannerInner%20a%7Bdisplay%3Ablock%3Bwidth%3A100%25%3Bheight%3A100%25%3Bposition%3Arelative%3Bcolor%3A%23000%3Btext-decoration%3Anone%7D.text%7Bposition%3Aabsolute%3Btop%3A20px%3Bleft%3A15px%3Bright%3A15px%3Bbottom%3A100px%7D.support-wrapper%7Boverflow%3Ahidden%3Bmax-height%3A86px%7D.support%7Bfont-family%3AArial%2Csans%3Bfont-weight%3A700%3Bline-height%3A28px%3Bfont-size%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.when-shop%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A25px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D.donates%7Bfont-family%3AArial%2Csans%3Bfont-size%3A15px%3Bfont-weight%3A400%3Bline-height%3A21px%3Bcolor%3A%23333%3Btext-align%3Acenter%3Bmargin%3A0%3Bpadding%3A0%3Bbackground%3A0%200%7D%3C%2Fstyle%3E")); contents.document.close(); iFrame.style.display = 'block';}); document.getElementById('amznCharityBanner').appendChild(iFrame); })();

jesus christ amazon romans 3d shopping fill 3b login 7d createelement iframe settimeout setattribute

#282 - Se preparando para certificação JavaScript Developer I - Parte 3

souforce.cloud

Play Episode Listen Later Aug 14, 2020 74:01

- Explicação da Prova - Variables, Types, and Collections: 23% - Objects, Functions, and Classes: 25% - Como será a nova Série - Abordaremos hoje - Browser and Events: 17% - Mão na massa - DOM - Criar novos elementos - Manipular os existentes - Remover elementos - Dev Tools - Console - Network - Inspecionar - Applicativo - Event - Listenning - Fire - Browser APIs - window.location - Obtem dados da URL - window.location.href - 'nova url' - window.localStorage - setItem("key", "value") - getItem("key"); - removeItem("key"); - window.sessionStorage - setItem("key", "value") - getItem("key"); - removeItem("key"); - clear(); - window.alert() - window.confirm - window.prompt() - window.setInterval() - window.clearInterval() - window.setTimeout() - window.clearTimeout() - https://trailhead.salesforce.com/help?article=Salesforce-Certified-JavaScript-Developer-I-Exam-Guide - https://github.com/souforce/Prep-JavaScriptDev1 - Live - #272 - Parte 1 - https://youtu.be/rdxucvBau2s - Live - #277 - Parte 2 - https://youtu.be/uf5VoegSYUs Acompanhe as live de segunda a sexta às 21:41 em https://youtube.com/souforce Siga-nos no Instagram @iFernandoSousa & @Anellinv & @souforce Blog: https://souforce.cloud Cursos: https://souforce.cloud/cursos Youtube: https://youtube.com/souforce Telegram: https://t.me/souforce

events types classes objects collections explica functions browsers preparando remover abordaremos certifica manipular javascript developers settimeout setinterval

Hiring + Interviews

iteration

Play Episode Listen Later Apr 27, 2020 43:58

Welcome to Iteration, a weekly podcast about programming, development, and design.Article that inspired the episodeQuick notes from this article:problem statement: interviewing can be annoying because it's an interruption from deep workproblem statement: after you've done a ton, it can be boringtwo critical skillsets: attracting talent (making candidates want to work with you) + spotting talent (accurately assessing whether you want the candidate to work with you)then it goes on to talk about beginner, competent, proficient, and expert interviewersread this article to see where you are in both attracting and assessing talentContextHow many interviews have you conducted?JP: At 2 years of Opendoor, I have conducted somewhere between 30-40 interviews. I wouldn't consider this a lot, but my last 10 have definitely been an improvement from my first 10.John: Pre-tech I did around 50+ interviews. In tech I've done as well 30-40 interviewsWhat type of interviews do you conduct? Behavioral? Technical?JP: I've only ever conducted technical interviewsJohn: I cover mostly behavioral/cultural and cover technical as well.Take me through your interview process:what should a candidate expect if they were to be interviewed by you?JP: I set expectations really early on and give candidates a whole layout for the entire interview. The basic format for my interview is:quick intros, try to keep this to a maximum of: 3 minutesintroduction to the question + planning before execution: 5 minutespair programming: 45-50 minutesclosing questions: the remainderJohn: I always over-communicate and try to "do" as little as possible during the interview. I prioritize "Async" interviews as much as possible.More recent process:Job Listing Job listing with very clear compensation listedApplications Applicants Apply (150+ for last open position)Shortlist Pick the top 10 (or so) I am interested in ignoring name or email address (Hide the columns) and look at the objective experience, read their writing (because we are remote)Code Challenge Email that top 5-10 and offer $100 to do a code challenge, takes anywhere from 2-4 hours. Last time it was implementing an API, they get the $100 when they submit a PR for review. Again set expectations on the start date, role, compensation etc. Set expectations for a review. It's a small test to see how we work together.Async Code Review Sr Developer and I leave comments, ask questions about the implementation Async.Real-time interviews — Then pick the top 2-3 from that phase and do real-time interviews.Re-iterate the position, compensation and expectationsWe talk background, career goals and motivations for applying to this jobThey walk me through their code challenge, why they wrote it the way they did.Then I allow time for them to ask me questions about the position.What would it take for someone to pass your interview?JP: We have to fill out a form after we conduct interviews so there is some grading criteria. i.e. code quality, tests, communication, algorithm speed, etc. I try not to nit pick language specific, trivia-like things. For example, it doesn't matter to me if a candidate doesn't know off the top of their head the syntax of setTimeout if they've spent the last year coding mostly in Python.Things are obviously different for hiring a new grad vs. a senior engineer. The bar variesJohn: Core things I am looking for: effective communication (written and spoken), self-motivated individuals (managers of one), skilled learner, Very competent in at least one language or framework (not even my own stack).Hot tips / Things to keep in mindJPDon't let a candidate spin their wheels - try to unblock them. See what working with them would actually be like.JohnMy interview style is a bit different.Honest — Never set any kind of false expectation, be yourselfUnpretentious — No trick questions or techno-bableReal — Try to communicate and work with candidates as you would in the job.You'd never toss out a question "just to stump" a coworkerPicksJP: https://github.com/ayu-theme/ayu-vim - I've moved away from DraculaJP: https://whimsical.com/John: Book: Every Tool's a Hammer by Adam Savage — Yes, Mythbusters guy but also incredible maker and leader of technical teams building really complex thingsso many great similarities to tech.Planning, Working, Creativity, burnout, estimating,plus a whole chapter on types of glue and random stories from his special effects days.I've really dug this book, doing the audiobook, will be buying a physical copy.

pr real planning creativity hiring hide hammer technical api python behavioral open door mythbusters iteration async settimeout

[PODCAST] Suricato interroga 9

Another71 CPA Exam Podcast

Play Episode Listen Later Dec 11, 2018 109:25

00Suricato Interroga - Ricardo Ameixa ou o caso da peruca no banheiro Bem vindos a mais um suricato interroga, e dessa vez a história se passa em um ambiente conhecido por muitos que passaram apuros na BGS, mas quem decide e você, será que a pistolinha do Ameixa é mesmo perigosa assim? function CP_Polls_pform_doValidate_1(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_1.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_1").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_1").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_1").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_1").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_1" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_1").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_1" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_1" ).hide(); $dexQuery( "#CP_Polls_presults_1" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_1() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "12"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_1" ).hide(); $dexQuery( "#CP_Polls_presults_1" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_1()', 300); } } function CP_Polls_cerror_1(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_1").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_1").outerHeight());$dexQuery("#hdcaptcha_error_1").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luciano "Alucard" - Gamertag: Luciano Alucard Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Bruno "Suricamper" Delacqua - Gamertag delacquab Apoio: Esse cast é um oferecimento dos nossos apoiadores: • Will Mordoceng • Cleiton Castro • Eurico Borges • Hugo Bustilho • Junior Xavier • Thiago "Bogus" • Thiago Torquato

bogus cabelo bgs participaram alucard getelementbyid settimeout ameixa removeclass

Synchronous vs Asynchronous Programming in Salesforce

Salesforce Casts Podcast

Play Episode Listen Later Nov 22, 2018 7:48

In this episode let’s look into what’s Synchronous and Asynchronous Programming and how do we do it Salesforce platform. Synchronous Programming In Synchronous programming statements will be executed one after the other. Say, we have 10 lines of code, then each and every line will be execute one after the other. So first line has to be executed it's only then the execution jumps to the second line. Likewise, second line has to be executed, only after that execution jumps on to the third line, so one and so forth. So, If our first statement is dealing with fetching list of Account records, until we get the data, execution will not jump on to the next line. Asynchronous Programming Asynchronous Programming is a methodology in which statements will not be executed one after the other. let’s say we have 10 lines of code and one of the statements in these 10 lines is a setTimeout() statement and lets go with the assumption that we want it to get executed after 10 secs. Then the execution comes to this setTimeOut statement and the moment the execution hits this statement, we are telling the computer I want to run this function but I don’t want to do it at least for a 10000 milliseconds in the future. So once 10 seconds from now gets passed that’s when I want this statement to get executed. Often we use this format of coding when we want to get data from other systems or when we make AJAX calls and etc. So we make the call and the thread doesn’t know when the response is going to comeback. This is Asynchronous Programming. We also discussed about other things in this episode. Please check it out. × × × SIIIICK ××× PIIIICKS × × × A concept inspired from wesbos Echo (2nd Generation) - Smart speaker Ring Wi-Fi Enabled Video Doorbell Subscribe You can subscribe to my course at Salesforce Casts Links: My Gear Teja on Twitter Teja's Instagram

account salesforce ajax synchronous settimeout asynchronous programming

CPA Exam Failure Pity Party – CPA Exam Podcast #90

Play Episode Listen Later Oct 10, 2018 28:35

Subscribe/Comment/Review*: Apple Podcasts | Google Play | YouTube * (even if you hate it) :) CPA Exam Failure Pity Party - Another71 CPA Exam Podcast #90 - Failed four CPA Exam sections - had a pity party + wake-up call - REG Section 179 - use 2017 or 2018 numbers? - Passed 4/4 CPA Exam sections with NINJA only - Failed FAR (48) & AUD (63) - 72/74 on REG with 18 month window closing - Lack of DRS SIM practice to blame for a 71? Have a CPA Exam Study Question? Send it below and I'll personally answer as soon as possible. First Name*Email* Question?*Please tell us about your CPA Exam status.AUD Exam Status*Select OneCurrently StudyingNeed to PassPassedBEC Exam Status*Select OneCurrently StudyingNeed to PassPassedFAR Exam Status*Select OneCurrently StudyingNeed to PassPassedREG Exam Status*Select OneCurrently StudyingNeed to PassPassed window.addEventListener('load', function () {setTimeout(function(){ apbct_sendAJAXRequest( {action: 'apbct_js_keys__get'}, {callback: apbct_js_keys__set_input_value, input_name: 'ct_checkjs_e995f98d56967d946471af29d7bf99f1'} ); }, 1000);}); To Your CPA Exam Success, Jeff Elliott, CPA (KS) Another71.com & NINJA CPA Review

failure lack ninjas failed passed reg aud pity party cpa exam addeventlistener settimeout

[PODCAST] Suricato interroga 8

Another71 CPA Exam Podcast

Play Episode Listen Later Sep 9, 2018 117:08

Suricato Interroga - Marcelo Brambz ou o caso romântico da Serra Elétrica Bem vindos a mais um suricato interroga, e agora o bicho pegou, confere com a gente e nos ajude a esclarecer se esse foi o caso de um bizarro crime passional ou se foi apenas um mal entendido.. function CP_Polls_pform_doValidate_4(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_4.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_4").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_4").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_4").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_4").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_4" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_4").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_4" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_4" ).hide(); $dexQuery( "#CP_Polls_presults_4" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_4() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "11"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_4" ).hide(); $dexQuery( "#CP_Polls_presults_4" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_4()', 300); } } function CP_Polls_cerror_4(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_4").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_4").outerHeight());$dexQuery("#hdcaptcha_error_4").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luciano "Alucard" - Gamertag: Luciano Alucard Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Marcelo Brambilla - Gamertag: Vingador Brambz Apoio: Esse cast é um oferecimento dos nossos apoiadores: • Will Mordoceng • Cleiton Castro • Eurico Borges • Hugo Bustilho • Junior Xavier • Thiago "Bogus" • Thiago Torquato • Waltter Junior • Vinicius Santos • Christian Karlo • Getulio Garcia • Ricardo Freitas • Luiz Fernando Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbrTwitter: www.

bogus cabelo participaram alucard getelementbyid settimeout ameixa removeclass

Video – Another71 CPA Exam Podcast #88

Play Episode Listen Later Aug 27, 2018 55:25

Another71.com CPA Exam Podcast #88 - NINJA Plus CPA Exam Videos - CPA Exam Weekly Progress Tracker - Two Weeks to Study for the CPA Exam - CPA MCQ Trending Score - CPA Exam Active Learning - Which CPA Exam to Take First in 2018 - CPA Exam REG Study Tips Have a CPA Exam Study Question? Send it below and I'll personally answer as soon as possible. First Name*Email* Question?*Please tell us about your CPA Exam status.AUD Exam Status*Select OneCurrently StudyingNeed to PassPassedBEC Exam Status*Select OneCurrently StudyingNeed to PassPassedFAR Exam Status*Select OneCurrently StudyingNeed to PassPassedREG Exam Status*Select OneCurrently StudyingNeed to PassPassed window.addEventListener('load', function () {setTimeout(function(){ apbct_sendAJAXRequest( {action: 'apbct_js_keys__get'}, {callback: apbct_js_keys__set_input_value, input_name: 'ct_checkjs_ec5decca5ed3d6b8079e2e7e7bacc9f2'} ); }, 1000);}); To Your CPA Exam Success, Jeff Elliott, CPA (KS) Another71.com & NINJA CPA Review

study cpa exam addeventlistener settimeout

Suricato Interroga – S01E07 #Podcast

Play Episode Listen Later Jul 28, 2018 82:32

Suricato Interroga - Major Suricato ou o caso do ingresso alterado Fala Suricatos Jogadores, beleza? Bem vindos Suricato Interroga. E o interrogado de hoje é o Suricato mais forte do mundo, o Mr. Instagram, Major Suricato... Confere aí esse interrogatório mais do que estanho... function CP_Polls_pform_doValidate_7(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_7.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_7").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_7").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_7").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_7").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_7" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_7").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_7" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_7" ).hide(); $dexQuery( "#CP_Polls_presults_7" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_7() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "10"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_7" ).hide(); $dexQuery( "#CP_Polls_presults_7" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_7()', 300); } } function CP_Polls_cerror_7(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_7").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_7").outerHeight());$dexQuery("#hdcaptcha_error_7").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luciano "Alucard" - Gamertag: Luciano Alucard Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Bruno Delacqua - Gamertag: DelacquaB Francisco Ramos - Gamertag: MrXcao - cgcorp.com.br Apoio: Esse cast é um oferecimento dos nossos apoiadores: • Will Mordoceng • Cleiton Castro • Eurico Borges • Hugo Bustilho • Junior Xavier • Thiago "Bogus" • Thiago Torquato • Waltter Junior • Vinicius Santos • Christian Karlo • Getulio Garcia • Ricardo Freitas • Luiz Fernando

bem bogus confere cabelo alucard getelementbyid settimeout ameixa removeclass

Episode 255: What Are You Pointing At | BSD Now 255

BSD Now

Play Episode Listen Later Jul 18, 2018 80:27

What ZFS blockpointers are, zero-day rewards offered, KDE on FreeBSD status, new FreeBSD core team, NetBSD WiFi refresh, poor man’s CI, and the power of Ctrl+T. ##Headlines What ZFS block pointers are and what’s in them I’ve mentioned ZFS block pointers in the past; for example, when I wrote about some details of ZFS DVAs, I said that DVAs are embedded in block pointers. But I’ve never really looked carefully at what is in block pointers and what that means and implies for ZFS. The very simple way to describe a ZFS block pointer is that it’s what ZFS uses in places where other filesystems would simply put a block number. Just like block numbers but unlike things like ZFS dnodes, a block pointer isn’t a separate on-disk entity; instead it’s an on disk data format and an in memory structure that shows up in other things. To quote from the (draft and old) ZFS on-disk specification (PDF): A block pointer (blkptr_t) is a 128 byte ZFS structure used to physically locate, verify, and describe blocks of data on disk. Block pointers are embedded in any ZFS on disk structure that points directly to other disk blocks, both for data and metadata. For instance, the dnode for a file contains block pointers that refer to either its data blocks (if it’s small enough) or indirect blocks, as I saw in this entry. However, as I discovered when I paid attention, most things in ZFS only point to dnodes indirectly, by giving their object number (either in a ZFS filesystem or in pool-wide metadata). So what’s in a block pointer itself? You can find the technical details for modern ZFS in spa.h, so I’m going to give a sort of summary. A regular block pointer contains: various metadata and flags about what the block pointer is for and what parts of it mean, including what type of object it points to. Up to three DVAs that say where to actually find the data on disk. There can be more than one DVA because you may have set the copies property to 2 or 3, or this may be metadata (which normally has two copies and may have more for sufficiently important metadata). The logical size (size before compression) and ‘physical’ size (the nominal size after compression) of the disk block. The physical size can do odd things and is not necessarily the asize (allocated size) for the DVA(s). The txgs that the block was born in, both logically and physically (the physical txg is apparently for dva[0]). The physical txg was added with ZFS deduplication but apparently also shows up in vdev removal. The checksum of the data the block pointer describes. This checksum implicitly covers the entire logical size of the data, and as a result you must read all of the data in order to verify it. This can be an issue on raidz vdevs or if the block had to use gang blocks. Just like basically everything else in ZFS, block pointers don’t have an explicit checksum of their contents. Instead they’re implicitly covered by the checksum of whatever they’re embedded in; the block pointers in a dnode are covered by the overall checksum of the dnode, for example. Block pointers must include a checksum for the data they point to because such data is ‘out of line’ for the containing object. (The block pointers in a dnode don’t necessarily point straight to data. If there’s more than a bit of data in whatever the dnode covers, the dnode’s block pointers will instead point to some level of indirect block, which itself has some number of block pointers.) There is a special type of block pointer called an embedded block pointer. Embedded block pointers directly contain up to 112 bytes of data; apart from the data, they contain only the metadata fields and a logical birth txg. As with conventional block pointers, this data is implicitly covered by the checksum of the containing object. Since block pointers directly contain the address of things on disk (in the form of DVAs), they have to change any time that address changes, which means any time ZFS does its copy on write thing. This forces a change in whatever contains the block pointer, which in turn ripples up to another block pointer (whatever points to said containing thing), and so on until we eventually reach the Meta Object Set and the uberblock. How this works is a bit complicated, but ZFS is designed to generally make this a relatively shallow change with not many levels of things involved (as I discovered recently). As far as I understand things, the logical birth txg of a block pointer is the transaction group in which the block pointer was allocated. Because of ZFS’s copy on write principle, this means that nothing underneath the block pointer has been updated or changed since that txg; if something changed, it would have been written to a new place on disk, which would have forced a change in at least one DVA and thus a ripple of updates that would update the logical birth txg. However, this doesn’t quite mean what I used to think it meant because of ZFS’s level of indirection. If you change a file by writing data to it, you will change some of the file’s block pointers, updating their logical birth txg, and you will change the file’s dnode. However, you won’t change any block pointers and thus any logical birth txgs for the filesystem directory the file is in (or anything else up the directory tree), because the directory refers to the file through its object number, not by directly pointing to its dnode. You can still use logical birth txgs to efficiently find changes from one txg to another, but you won’t necessarily get a filesystem level view of these changes; instead, as far as I can see, you will basically get a view of what object(s) in a filesystem changed (effectively, what inode numbers changed). (ZFS has an interesting hack to make things like ‘zfs diff’ work far more efficiently than you would expect in light of this, but that’s going to take yet another entry to cover.) ###Rewards of Up to $500,000 Offered for FreeBSD, OpenBSD, NetBSD, Linux Zero-Days Exploit broker Zerodium is offering rewards of up to $500,000 for zero-days in UNIX-based operating systems like OpenBSD, FreeBSD, NetBSD, but also for Linux distros such as Ubuntu, CentOS, Debian, and Tails. The offer, first advertised via Twitter earlier this week, is available as part of the company’s latest zero-day acquisition drive. Zerodium is known for buying zero-days and selling them to government agencies and law enforcement. The company runs a regular zero-day acquisition program through its website, but it often holds special drives with more substantial rewards when it needs zero-days of a specific category. BSD zero-day rewards will be on par with Linux payouts The US-based company held a previous drive with increased rewards for Linux zero-days in February, with rewards going as high as $45,000. In another zero-day acquisition drive announced on Twitter this week, the company said it was looking again for Linux zero-days, but also for exploits targeting BSD systems. This time around, rewards can go up to $500,000, for the right exploit. Zerodium told Bleeping Computer they’ll be aligning the temporary rewards for BSD systems with their usual payouts for Linux distros. The company’s usual payouts for Linux privilege escalation exploits can range from $10,000 to $30,000. Local privilege escalation (LPE) rewards can even reach $100,000 for “an exploit with an exceptional quality and coverage,” such as, for example, a Linux kernel exploit affecting all major distributions. Payouts for Linux remote code execution (RCE) exploits can bring in from $50,000 to $500,000 depending on the targeted software/service and its market share. The highest rewards are usually awarded for LPEs and RCEs affecting CentOS and Ubuntu distros. Zero-day price varies based on exploitation chain The acquisition price of a submitted zero-day is directly tied to its requirements in terms of user interaction (no click, one click, two clicks, etc.), Zerodium said. Other factors include the exploit reliability, its success rate, the number of vulnerabilities chained together for the final exploit to work (more chained bugs means more chances for the exploit to break unexpectedly), and the OS configuration needed for the exploit to work (exploits are valued more if they work against default OS configs). Zero-days in servers “can reach exceptional amounts” “Price difference between systems is mostly driven by market shares,” Zerodium founder Chaouki Bekrar told Bleeping Computer via email. Asked about the logic behind these acquisition drives that pay increased rewards, Bekrar told Bleeping Computer the following: "Our aim is to always have, at any time, two or more fully functional exploits for every major software, hardware, or operating systems, meaning that from time to time we would promote a specific software/system on our social media to acquire new codes and strengthen our existing capabilities or extend them.” “We may also react to customers’ requests and their operational needs,” Bekrar said. It’s becoming a crowded market Since Zerodium drew everyone’s attention to the exploit brokerage market in 2015, the market has gotten more and more crowded, but also more sleazy, with some companies being accused of selling zero-days to government agencies in countries with oppressive or dictatorial regimes, where they are often used against political oponents, journalists, and dissidents, instead of going after real criminals. The latest company who broke into the zero-day brokerage market is Crowdfense, who recently launched an acquisition program with prizes of $10 million, of which it already paid $4.5 million to researchers. Twitter Announcement Digital Ocean http://do.co/bsdnow ###KDE on FreeBSD – June 2018 The KDE-FreeBSD team (a half-dozen hardy individuals, with varying backgrounds and varying degrees of involvement depending on how employment is doing) has a status message in the #kde-freebsd channel on freenode. Right now it looks like this: http://FreeBSD.kde.org | Bleeding edge http://FreeBSD.kde.org/area51.php | Released: Qt 5.10.1, KDE SC 4.14.3, KF5 5.46.0, Applications 18.04.1, Plasma-5.12.5, Kdevelop-5.2.1, Digikam-5.9.0 It’s been a while since I wrote about KDE on FreeBSD, what with Calamares and third-party software happening as well. We’re better at keeping the IRC topic up-to-date than a lot of other sources of information (e.g. the FreeBSD quarterly reports, or the f.k.o website, which I’ll just dash off and update after writing this). In no particular order: Qt 5.10 is here, in a FrankenEngine incarnation: we still use WebEnging from Qt 5.9 because — like I’ve said before — WebEngine is such a gigantic pain in the butt to update with all the necessary patches to get it to compile. Our collection of downstream patches to Qt 5.10 is growing, slowly. None of them are upstreamable (e.g. libressl support) though. KDE Frameworks releases are generally pushed to ports within a week or two of release. Actually, now that there is a bigger stack of KDE software in FreeBSD ports the updates take longer because we have to do exp-runs. Similarly, Applications and Plasma releases are reasonably up-to-date. We dodged a bullet by not jumping on Plasma 5.13 right away, I see. Tobias is the person doing almost all of the drudge-work of these updates, he deserves a pint of something in Vienna this summer. The freebsd.kde.org website has been slightly updated; it was terribly out-of-date. So we’re mostly-up-to-date, and mostly all packaged up and ready to go. Much of my day is spent in VMs packaged by other people, but it’s good to have a full KDE developer environment outside of them as well. (PS. Gotta hand it to Tomasz for the amazing application for downloading and displaying a flamingo … niche usecases FTW) ##News Roundup New FreeBSD Core Team Elected Active committers to the project have elected your tenth FreeBSD Core Team. Allan Jude (allanjude) Benedict Reuschling (bcr) Brooks Davis (brooks) Hiroki Sato (hrs) Jeff Roberson (jeff) John Baldwin (jhb) Kris Moore (kmoore) Sean Chittenden (seanc) Warner Losh (imp) Let’s extend our gratitude to the outgoing Core Team members: Baptiste Daroussin (bapt) Benno Rice (benno) Ed Maste (emaste) George V. Neville-Neil (gnn) Matthew Seaman (matthew) Matthew, after having served as the Core Team Secretary for the past four years, will be stepping down from that role. The Core Team would also like to thank Dag-Erling Smørgrav for running a flawless election. To read about the responsibilities of the Core Team, refer to https://www.freebsd.org/administration.html#t-core. ###NetBSD WiFi refresh The NetBSD Foundation is pleased to announce a summer 2018 contract with Philip Nelson (phil%NetBSD.org@localhost) to update the IEEE 802.11 stack basing the update on the FreeBSD current code. The goals of the project are: Minimizing the differences between the FreeBSD and NetBSD IEEE 802.11 stack so future updates are easier. Adding support for the newer protocols 801.11/N and 802.11/AC. Improving SMP support in the IEEE 802.11 stack. Adding Virtual Access Point (VAP) support. Updating as many NIC drivers as time permits for the updated IEEE 802.11 stack and VAP changes. Status reports will be posted to tech-net%NetBSD.org@localhost every other week while the contract is active. iXsystems ###Poor Man’s CI - Hosted CI for BSD with shell scripting and duct tape Poor Man’s CI (PMCI - Poor Man’s Continuous Integration) is a collection of scripts that taken together work as a simple CI solution that runs on Google Cloud. While there are many advanced hosted CI systems today, and many of them are free for open source projects, none of them seem to offer a solution for the BSD operating systems (FreeBSD, NetBSD, OpenBSD, etc.) The architecture of Poor Man’s CI is system agnostic. However in the implementation provided in this repository the only supported systems are FreeBSD and NetBSD. Support for additional systems is possible. Poor Man’s CI runs on the Google Cloud. It is possible to set it up so that the service fits within the Google Cloud “Always Free” limits. In doing so the provided CI is not only hosted, but is also free! (Disclaimer: I am not affiliated with Google and do not otherwise endorse their products.) ARCHITECTURE A CI solution listens for “commit” (or more usually “push”) events, builds the associated repository at the appropriate place in its history and reports the results. Poor Man’s CI implements this very basic CI scenario using a simple architecture, which we present in this section. Poor Man’s CI consists of the following components and their interactions: Controller: Controls the overall process of accepting GitHub push events and starting builds. The Controller runs in the Cloud Functions environment and is implemented by the files in the controller source directory. It consists of the following components: Listener: Listens for GitHub push events and posts them as work messages to the workq PubSub. Dispatcher: Receives work messages from the workq PubSub and a free instance name from the Builder Pool. It instantiates a builder instance named name in the Compute Engine environment and passes it the link of a repository to build. Collector: Receives done messages from the doneq PubSub and posts the freed instance name back to the Builder Pool. PubSub Topics: workq: Transports work messages that contain the link of the repository to build. poolq: Implements the Builder Pool, which contains the name’s of available builder instances. To acquire a builder name, pull a message from the poolq. To release a builder name, post it back into the poolq. doneq: Transports done messages (builder instance terminate and delete events). These message contain the name of freed builder instances. builder: A builder is a Compute Engine instance that performs a build of a repository and shuts down when the build is complete. A builder is instantiated from a VM image and a startx (startup-exit) script. Build Logs: A Storage bucket that contains the logs of builds performed by builder instances. Logging Sink: A Logging Sink captures builder instance terminate and delete events and posts them into the doneq. BUGS The Builder Pool is currently implemented as a PubSub; messages in the PubSub contain the names of available builder instances. Unfortunately a PubSub retains its messages for a maximum of 7 days. It is therefore possible that messages will be discarded and that your PMCI deployment will suddenly find itself out of builder instances. If this happens you can reseed the Builder Pool by running the commands below. However this is a serious BUG that should be fixed. For a related discussion see https://tinyurl.com/ybkycuub. $ ./pmci queuepost poolq builder0 # ./pmci queuepost poolq builder1 # ... repeat for as many builders as you want The Dispatcher is implemented as a Retry Background Cloud Function. It accepts work messages from the workq and attempts to pull a free name from the poolq. If that fails it returns an error, which instructs the infrastructure to retry. Because the infrastructure does not provide any retry controls, this currently happens immediately and the Dispatcher spins unproductively. This is currently mitigated by a “sleep” (setTimeout), but the Cloud Functions system still counts the Function as running and charges it accordingly. While this fits within the “Always Free” limits, it is something that should eventually be fixed (perhaps by the PubSub team). For a related discussion see https://tinyurl.com/yb2vbwfd. ###The Power of Ctrl-T Did you know that you can check what a process is doing by pressing CTRL+T? Has it happened to you before that you were waiting for something to be finished that can take a lot of time, but there is no easy way to check the status. Like a dd, cp, mv and many others. All you have to do is press CTRL+T where the process is running. This will output what’s happening and will not interrupt or mess with it in any way. This causes the operating system to output the SIGINFO signal. On FreeBSD it looks like this: ping pingtest.com PING pingtest.com (5.22.149.135): 56 data bytes 64 bytes from 5.22.149.135: icmpseq=0 ttl=51 time=86.232 ms 64 bytes from 5.22.149.135: icmpseq=1 ttl=51 time=85.477 ms 64 bytes from 5.22.149.135: icmpseq=2 ttl=51 time=85.493 ms 64 bytes from 5.22.149.135: icmpseq=3 ttl=51 time=85.211 ms 64 bytes from 5.22.149.135: icmpseq=4 ttl=51 time=86.002 ms load: 1.12 cmd: ping 94371 [select] 4.70r 0.00u 0.00s 0% 2500k 5/5 packets received (100.0%) 85.211 min / 85.683 avg / 86.232 max 64 bytes from 5.22.149.135: icmpseq=5 ttl=51 time=85.725 ms 64 bytes from 5.22.149.135: icmp_seq=6 ttl=51 time=85.510 ms As you can see it not only outputs the name of the running command but the following parameters as well: 94371 – PID 4.70r – since when is the process running 0.00u – user time 0.00s – system time 0% – CPU usage 2500k – resident set size of the process or RSS `` > An even better example is with the following cp command: cp FreeBSD-11.1-RELEASE-amd64-dvd1.iso /dev/null load: 0.99 cmd: cp 94412 [runnable] 1.61r 0.00u 0.39s 3% 3100k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 15% load: 0.91 cmd: cp 94412 [runnable] 2.91r 0.00u 0.80s 6% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 32% load: 0.91 cmd: cp 94412 [runnable] 4.20r 0.00u 1.23s 9% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 49% load: 0.91 cmd: cp 94412 [runnable] 5.43r 0.00u 1.64s 11% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 64% load: 1.07 cmd: cp 94412 [runnable] 6.65r 0.00u 2.05s 13% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 79% load: 1.07 cmd: cp 94412 [runnable] 7.87r 0.00u 2.43s 15% 3104k FreeBSD-11.1-RELEASE-amd64-dvd1.iso -> /dev/null 95% > I prcessed CTRL+T six times. Without that, all the output would have been is the first line. > Another example how the process is changing states: wget https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-dvd1.iso –2018-06-17 18:47:48– https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-dvd1.iso Resolving download.freebsd.org (download.freebsd.org)… 96.47.72.72, 2610:1c1:1:606c::15:0 Connecting to download.freebsd.org (download.freebsd.org)|96.47.72.72|:443… connected. HTTP request sent, awaiting response… 200 OK Length: 3348465664 (3.1G) [application/octet-stream] Saving to: ‘FreeBSD-11.1-RELEASE-amd64-dvd1.iso’ FreeBSD-11.1-RELEASE-amd64-dvd1.iso 1%[> ] 41.04M 527KB/s eta 26m 49sload: 4.95 cmd: wget 10152 waiting 0.48u 0.72s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 1%[> ] 49.41M 659KB/s eta 25m 29sload: 12.64 cmd: wget 10152 waiting 0.55u 0.85s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 2%[=> ] 75.58M 6.31MB/s eta 20m 6s load: 11.71 cmd: wget 10152 running 0.73u 1.19s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 2%[=> ] 85.63M 6.83MB/s eta 18m 58sload: 11.71 cmd: wget 10152 waiting 0.80u 1.32s FreeBSD-11.1-RELEASE-amd64-dvd1.iso 14%[==============> ] 460.23M 7.01MB/s eta 9m 0s 1 > The bad news is that CTRl+T doesn’t work with Linux kernel, but you can use it on MacOS/OS-X: —> Fetching distfiles for gmp —> Attempting to fetch gmp-6.1.2.tar.bz2 from https://distfiles.macports.org/gmp —> Verifying checksums for gmp —> Extracting gmp —> Applying patches to gmp —> Configuring gmp load: 2.81 cmd: clang 74287 running 0.31u 0.28s > PS: If I recall correctly Feld showed me CTRL+T, thank you! Beastie Bits Half billion tries for a HAMMER2 bug (http://lists.dragonflybsd.org/pipermail/commits/2018-May/672263.html) OpenBSD with various Desktops OpenBSD 6.3 running twm window manager (https://youtu.be/v6XeC5wU2s4) OpenBSD 6.3 jwm and rox desktop (https://youtu.be/jlSK2oi7CBc) OpenBSD 6.3 cwm youtube video (https://youtu.be/mgqNyrP2CPs) pf: Increase default state table size (https://svnweb.freebsd.org/base?view=revision&revision=336221) *** Tarsnap Feedback/Questions Ben Sims - Full feed? (http://dpaste.com/3XVH91T#wrap) Scott - Questions and Comments (http://dpaste.com/08P34YN#wrap) Troels - Features of FreeBSD 11.2 that deserve a mention (http://dpaste.com/3DDPEC2#wrap) Fred - Show Ideas (http://dpaste.com/296ZA0P#wrap) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) iXsystems It's all NAS (https://www.ixsystems.com/blog/its-all-nas/)

power google interview guide local team price connecting saving os ps status active gotta architecture ac rewards nas applications function bugs nic how to tutorials linux github bug feld bleeding tails controller vm offered resolving pointing plasma ubuntu cpu embedded news roundup minimizing exploit google cloud qt trident kde tomasz irc transports poor man ieee extracting unix dispatchers dva vms payouts ftw digital ocean verifying implements bsd debian continuous integration core team freebsd configuring centos rce 1g george v 23m fetching vap zfs always free pub sub openbsd calamares 58m bleeping computer zerodium lpe john baldwin netbsd settimeout allan jude philip nelson ixsystems kris moore dvas digikam trueos 31mb ctrl t 83mb dragonflybsd crowdfense hiroki sato ed maste

23 – Kamil Kozieł czyli od miłości do luksusowych samochodów do teorii czerech warstw prezentacji

Pogaducha

Play Episode Listen Later Jun 25, 2018 61:11

Od kilku lat przemierza Polskę głosząc dobrą nowinę. Przeanalizował setki godzin nagrań, rozłożył na czynniki pierwsze najlepsze światowe wystąpienia i opracował strukturę czterech warstw prezentacji. Uczy jak mówić, by przekazać to, co najważniejsze. Jak zaintrygować słuchacza i sprawić, aby przekaz był nie tylko jasny, ale i interesujący. Wygrywał największe konferencje, a dziś w godzinnej rozmowie opowiada, co go motywuje, kto był dla niego inspiracją i skąd w nim ta ciągła potrzeba rozwoju. Facebooku var container = document.getElementById('fm-pu-container'); function hide(){container.style.display = 'none';}; var fmFCF26kblpix1s=function(e){if(e.data.type == 'resize'){ document.getElementById('fm-fc-f-26kblpix1s').style.minHeight=e.data.size+'px'}else if(e.data.type == 'hide'){hide();}else if(e.data.type == 'timeout'){setTimeout(function(){document.getElementById('fm-pu-container').style.display = 'flex';}, e.data.time * 1000 );}};window.addEventListener?addEventListener('message',fmFCF26kblpix1s,!1):attachEvent('onmessage',fmFCF26kblpix1s);container.addEventListener("click", hide); Zobaczcie koniecznie wystąpienie, w którym Kamil Kozieł oraz Piotr Bucki opowiadają o narracji, którą udostępnisz. Kamila możecie śledzić na instagramie: Facebooku: Jeśli wolicie czytać niż oglądać a chcecie wiedzieć więcej o prezentacjach, wpadajcie tu. Wolisz czytać? Proszę bardzo ;) Robiłeś kiedyś slajdy w excelu? KK. – Tak, szczerze mówiąc, tak. Robiliśmy kiedyś grę w węża w excelu ,którą potem prezentowaliśmy. Nieważne w jakich okolicznościach, trudno to będzie wyjaśnić dość szybko i uzasadnić tę historię, ale powiem tylko tyle, że to był zakład, więc nie mogliśmy go przegrać. Musieliśmy napisać go w VB, tę grę w excelu – węża, a później prezentowaliśmy ją na dużym rzutniku. Czyli nic odkrywczego nie wymyśliłam. Starałam się… jesteś moim gościem, ponieważ robisz fajne rzeczy. Aktualnie robisz prezentacje, ale zanim zacząłeś je robić, zajmowałeś się zupełnie innymi rzeczami, jak wszyscy ludzie, bo chyba nikt się nie urodził robiąc prezentacje. Chodziłeś do szkoły, chodziłeś do liceum... o, właśnie… czy już wtedy miałeś jakieś plany na życie? KK. – Zupełnie inne - szczerze mówiąc - zupełnie inne niż to, co robię teraz w życiu zawodowym. Plan był dość prosty. Chciałem się dostać na SGH i studiować ekonomię, potem zahaczyć się w jakimś korpo na praktyki, piąć się po szczeblach etycznej drabiny. Taki oto był mój pomysł na życie! Właściwie była to kopia tego, co robił z fajnym efektem mój brat. Bo muszę dodać, że mój brat jest dużo racjonalniejszą i fajniejszą wersją mnie, sześć lat starszą! Tak to trochę jest, że jak dobrze żyjesz z rodzeństwem, to kopiujesz jego plany. Mój był właśnie taki, ale - jak to bywa w życiu - czasem ono płata figla! Mój plan padł w momencie, kiedy nie dostałem się na SGH z powodu olania jednego z czterech najważniejszych egzaminów. To jest bardzo zły pomysł, żeby wysłać kogoś, kto nigdy w życiu nie imprezował razem z 10 jego kolegami na cykl przygotowawczy. Dużo się nie uczyliśmy! Nie dostałem się na SGH, dostałem się na akademię ekonomiczną, a potem poszło jakoś wszystko zupełnie inaczej niż planowałem. Ilustracja do podkastu Pogaducha Czyli jak poszło? KK. – Gdybym chciał przedstawić najszczerszą wersję tej historii, to dostałem się na Akademię Ekonomiczną w Poznaniu za sprawą przypadku. W liceum wymyśliłem sobie, że będę się uczył hiszpańskiego. Moja wada wymowy okazała się w nauce tego języka akcentem! Też się uczyłam hiszpańskiego i strasznie mi odpowiadało to, że jak coś seplenię to mówią, że to akcent z innego regionu hiszpańskiego. I możesz robić co chcesz. KK. – I inny dialekt. Mój brat był na studiach w Hiszpanii przez rok i stąd też ta moja małpia miłość do tego języka. Nauczyłem się go bardzo szybko. Zdałem maturę z hiszpańskiego prawie na 100% i byłem niezły z matmy, więc te dwa wyniki wystarczyły mi,

plan tak jak nie czyli kk kamil moja taki polsk vb chcia chodzi stara poznaniu nauczy uczy hiszpanii zda prosz zupe aktualnie gdybym getelementbyid wygrywa sgh teorii zobaczcie niewa robili samochod addeventlistener piotr bucki settimeout ilustracja attachevent

[PODCAST] Suricato Interroga 6

Another71 CPA Exam Podcast

Play Episode Listen Later Jun 22, 2018 99:56

Suricato Interroga 6 Suspeito #6: Getúlio Garcia Fala Suricatos, Beleza? Bem vindos ao XBOX BRAZUCAST. Dessa vez a gente precisa da sua ajuda pra desvendar esse roubo que aconteceu em um lugar bem diferente. E como envolver Dragon Ball e as sete esferas nessa bagunça? function CP_Polls_pform_doValidate_10(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_10.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_10").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_10").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_10").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_10").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_10" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_10").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_10" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_10" ).hide(); $dexQuery( "#CP_Polls_presults_10" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_10() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "9"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_10" ).hide(); $dexQuery( "#CP_Polls_presults_10" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_10()', 300); } } function CP_Polls_cerror_10(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_10").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_10").outerHeight());$dexQuery("#hdcaptcha_error_10").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Luciano "Malucard" - Gamertag: Luciano Alucard Getúlio "Mano Gegê" - Gamertag: Mano Gege Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbr Twitter: www.twitter.com/xboxbrazucas Facebook: www.fb.com/xboxbrazucas Grupo do Facebook: http://www.fb.com/groups/xboxbrazucasbr Instagram: www.instagram.com/xboxbrazucas Google Plus: https://plus.google.com/b/116408053564764452192 Brazucas no Telegram: https://t.me/joinchat/AAAAAEMcZKCRy_LHMBK8EQ

telegram grupo dessa dragon ball google plus cabelo participaram luiz fernando getelementbyid brazucas settimeout ameixa removeclass

CPA Exam Score Release & Taking 19 Exams – Another71 Podcast #85

Play Episode Listen Later Jun 11, 2018 29:05

CPA Reviewed Podcast #85 - What is the CPA Exam Score Release? - BEC overhead variances – an easy way to remember? - Multiple choice question topics that aren’t discussed in CPA Review study materials? - Studying out of order? - REG – 2018 – Is this for CPA Test takers this year? - Business Law 40% of Regulation MCQ? - Taken 19 Exams and doubting myself. Have a CPA Exam Study Question? Send it below and I'll personally answer as soon as possible. First Name*Email* Question?*Please tell us about your CPA Exam status.AUD Exam Status*Select OneCurrently StudyingNeed to PassPassedBEC Exam Status*Select OneCurrently StudyingNeed to PassPassedFAR Exam Status*Select OneCurrently StudyingNeed to PassPassedREG Exam Status*Select OneCurrently StudyingNeed to PassPassed window.addEventListener('load', function () {setTimeout(function(){ apbct_sendAJAXRequest( {action: 'apbct_js_keys__get'}, {callback: apbct_js_keys__set_input_value, input_name: 'ct_checkjs_90794e3b050f815354e3e29e977a88ab'} ); }, 1000);}); To Your CPA Exam Success, Jeff Elliott, CPA (KS) Another71.com & NINJA CPA Review

score studying exams reg business law cpa exam addeventlistener settimeout

[PODCAST] Suricato Interroga 5

Play Episode Listen Later May 12, 2018 112:42

Suricato Interroga 5 Suspeito #5: Cabelo Fala Suricatos, Beleza? Bem vindos ao XBOX BRAZUCAST. Mistério, magia e um ritual pra lá de atrapalhado estão presentes nessa investigação, É possível realizar um sonho com um machado e uma manga? Nos ajude a desvendar esse caso já sabendo que, onde tem Cabelo, tem zueira. function CP_Polls_pform_doValidate_13(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_13.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_13").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_13").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_13").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_13").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_13" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_13").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_13" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_13" ).hide(); $dexQuery( "#CP_Polls_presults_13" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_13() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "8"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_13" ).hide(); $dexQuery( "#CP_Polls_presults_13" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_13()', 300); } } function CP_Polls_cerror_13(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_13").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_13").outerHeight());$dexQuery("#hdcaptcha_error_13").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Luciano "Malucard" - Gamertag: Luciano Alucard Getúlio "Mano Gegê" - Gamertag: Mano Gege Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbr Twitter: www.twitter.com/xboxbrazucas Facebook: www.fb.com/xboxbrazucas Grupo do Facebook: http://www.fb.com/groups/xboxbrazucasbr Instagram: www.instagram.com/xboxbrazucas Google Plus: https://plus.google.com/b/116408053564764452192

nos mist grupo google plus cabelo participaram luiz fernando getelementbyid settimeout ameixa removeclass

[Podcast] Suricato interroga 4

Play Episode Listen Later Apr 14, 2018 113:02

Suricato Interroga 4 Suspeito #4: Francisco Ramos Fala Suricatos, Beleza? Bem vindos ao XBOX BRAZUCAST. Dessa vez a gente precisa saber como sumiram 2 milhões de estalecas da conta do Bruno Delacqua, será que o Chicão aproveitou um momento de distração molhada dele? A gente investigou e você decide. function CP_Polls_pform_doValidate_16(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_16.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_16").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_16").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_16").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_16").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_16" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_16").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_16" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_16" ).hide(); $dexQuery( "#CP_Polls_presults_16" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_16() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "7"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_16" ).hide(); $dexQuery( "#CP_Polls_presults_16" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_16()', 300); } } function CP_Polls_cerror_16(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_16").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_16").outerHeight());$dexQuery("#hdcaptcha_error_16").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Luciano "Malucard" - Gamertag: Luciano Alucard Carlos "Leitovisk" - Gamertag: TheIronBalls Francisco Ramos - Gamertag: MrXcao Link da página do CGCorp Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbr Twitter: www.twitter.com/xboxbrazucas Facebook: www.fb.com/xboxbrazucas Grupo do Facebook: http://www.fb.com/groups/xboxbrazucasbr Instagram: www.instagram.com/xboxbrazucas Google Plus: https://plus.

grupo dessa chic google plus cabelo participaram luiz fernando getelementbyid settimeout ameixa removeclass

Mysteries of the Internet

Go Folk Yourself

Play Episode Listen Later Mar 29, 2018 7:16

internet mysteries new line settimeout scrolltop

[Podcast] Suricato Interroga 3

Play Episode Listen Later Mar 15, 2018 102:32

Suricato Interroga 3 Suspeito #3: Cleverizzo Fala Suricatos, Beleza? Bem vindos ao XBOX BRAZUCAST. Você já imaginou um eletrodoméstico que viaje quase o país inteiro e que ainda esteja envolvido em um crime suspeito? Pois é, nos ajude a investigar isso. function CP_Polls_pform_doValidate_19(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_19.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_19").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_19").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_19").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_19").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_19" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_19").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_19" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_19" ).hide(); $dexQuery( "#CP_Polls_presults_19" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_19() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "6"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_19" ).hide(); $dexQuery( "#CP_Polls_presults_19" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_19()', 300); } } function CP_Polls_cerror_19(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_19").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_19").outerHeight());$dexQuery("#hdcaptcha_error_19").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Luciano "Malucard" - Gamertag: Luciano Alucard Cleverson Izzo - Gamertag: CleversonIzz0 Link sobre a história do Game & Watch Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbr Twitter: www.twitter.com/xboxbrazucas Facebook: www.fb.com/xboxbrazucas Grupo do Facebook: http://www.fb.com/groups/xboxbrazucasbr Instagram: www.instagram.com/xboxbrazucas Google Plus: https://plus.google.com/b/116408053564764452192 Brazucas no Telegram: https://t.

game voc telegram grupo pois google plus cabelo participaram luiz fernando getelementbyid brazucas settimeout ameixa removeclass

01 – Czy jesteś już za stary na zmianę pracy?

Pogaducha

Play Episode Listen Later Feb 3, 2018 30:34

Zmiana pracy jest stresująca nawet jeśli jesteśmy do niej dobrze przygotowani. Słuchając tego odcinka dowiesz się, czy jest dobry czas na zmianę? Czy po czterdziestce jest sens ryzykować? Może to pięćdziesiąte urodziny są tą granicą po której przekroczeniu powinniśmy przygotowywać się do emerytury? var fmFCFnhgiiqgkx8=function(e){document.getElementById('fm-fc-f-nhgiiqgkx8').style.minHeight=e.data.size+'px'};window.addEventListener?addEventListener('message',fmFCFnhgiiqgkx8,!1):attachEvent('onmessage',fmFCFnhgiiqgkx8); var container = document.getElementById('fm-pu-container'); function hide(){container.style.display = 'none';}; var fmFCF26kblpix1s=function(e){if(e.data.type == 'resize'){ document.getElementById('fm-fc-f-26kblpix1s').style.minHeight=e.data.size+'px'}else if(e.data.type == 'hide'){hide();}else if(e.data.type == 'timeout'){setTimeout(function(){document.getElementById('fm-pu-container').style.display = 'flex';}, e.data.time * 1000 );}};window.addEventListener?addEventListener('message',fmFCF26kblpix1s,!1):attachEvent('onmessage',fmFCF26kblpix1s);container.addEventListener("click", hide);

czy jeste pracy zmiana stary getelementbyid addeventlistener settimeout attachevent

[Podcast] Suricato Interroga 2

Play Episode Listen Later Jan 31, 2018 96:05

Suricato Interroga 2 Suspeito #2: Patrão Fala Suricatos, Beleza? Bem vindos ao XBOX BRAZUCAST. Dessa vez investigamos um crime em uma grande área pública em Suricatolândia, o suspeito Malucard, patrão da bagaça toda e que tem um álibi mais que suspeito, precisa te convencer que é inocente e como sempre você julga pra sabermos o final dessa história. function CP_Polls_pform_doValidate_22(form) { $dexQuery = jQuery.noConflict(); document.CP_Polls_pform_22.cp_ref_page.value = document.location; $dexQuery = jQuery.noConflict(); { var cpefb_error = 0; $dexQuery("#CP_Polls_pform_22").find(".cpefb_error").each(function(index){ if ($dexQuery(this).css("display")!="none") cpefb_error++; }); if (cpefb_error==0) { $dexQuery("#CP_Polls_pform_22").find("select").children().each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_22").find("input:checkbox,input:radio").each(function(){ $dexQuery(this).val($dexQuery(this).attr("vt")); }); $dexQuery("#CP_Polls_pform_22").find( '.ignore' ).parents( '.fields' ).remove(); /** submit here */ $dexQuery( "#CP_Polls_pform_22" ).find(".pbSubmit").removeClass("pbSubmit").html(''); document.getElementById("form_structure_22").value = ''; $dexQuery.ajax({ type: "POST", async: true, url: '/', data: $dexQuery( "#CP_Polls_pform_22" ).serialize() }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_22" ).hide(); $dexQuery( "#CP_Polls_presults_22" ).html(msg); }); } return false; } } function CP_Polls_cpSeeResults_22() { try { $dexQuery = jQuery.noConflict(); $dexQuery.ajax({ type: "POST", async: true, url: '/', data: {CP_Polls_loadresults: "1", CP_Polls_id: "4"} }) .done(function( msg ) { $dexQuery( "#CP_Polls_pform_22" ).hide(); $dexQuery( "#CP_Polls_presults_22" ).html(msg); }); } catch (e) { setTimeout( 'CP_Polls_cpSeeResults_22()', 300); } } function CP_Polls_cerror_22(){$dexQuery = jQuery.noConflict();$dexQuery("#hdcaptcha_error_22").css('top',$dexQuery("#hdcaptcha_CP_Polls_post_22").outerHeight());$dexQuery("#hdcaptcha_error_22").css("display","inline");} Votar [Ver resultado] /* Participaram desse podcast: Luiz Fernando "Cabelo" - Gamertag: LFC Brasil Ricardo "Ameixa" - Gamertag: Caul SUBR Waltter "MajorSuricato" - Gamertag MajorSuricato Luciano "Malucard" - Gamertag: Luciano Alucard Link Brazucas: Youtube: www.youtube.com/c/xboxbrazucasbr Twitter: www.twitter.com/xboxbrazucas Facebook: www.fb.com/xboxbrazucas Grupo do Facebook: http://www.fb.com/groups/xboxbrazucasbr Instagram: www.instagram.com/xboxbrazucas Google Plus: https://plus.google.com/b/116408053564764452192

grupo dessa google plus cabelo participaram luiz fernando getelementbyid settimeout ameixa removeclass

[Podcast] Suricato Interroga 1