ClojureScript: I can't believe this is JavaScript

Oct 12, 20180 likes38 views

There are 6 difficult problems frameworks and libraries try to solve in JavaScript, but never quite get there. Learn how these problems (and more!) are solved by ClojureScript and how it can provide a platform for new solutions.

ClojureScript:
I can't believe this is
JavaScript
Eric Normand

ClojureScript
I can’t believe this is JavaScript!

For the video and transcript
of this presentation,
click here:
https://lispcast.com/clojurescript-cant-believe-javascript/

Callback Hell
• JavaScript uses callback-style for async
• Not just about indentation
• About inversion of control
• I don’t know when or in what order or even if
my code will be called!

JavaScript vs Callback hell
• Promises
• Helps a lot!
• Still have promises within promises within
promises
• async/await
• nice!
• Together: wow, a really good solution!

ClojureScript vs Callback Hell
• core.async
• A library that turns sequential code into
callbacks
• Never give up control
• Based on Communicating Sequential Processes
• (the same thing Go is based on)

Code Optimization
• Milliseconds === $$$$
• Minify code
• Remove dead code
• Split code

JavaScript vs Optimization
• webpack
• minification
• dead code elimination
• splitting
• Rollup
• tree shaking

ClojureScript vs Optimization
• Google Closure Compiler
• heavily tested
• optimizes Gmail
• “just works”

Stateful DOM
• Dynamic apps need to modify the DOM
• DOM and your data get out of sync

JavaScript vs DOM
• JavaScript sprinkles
• Just use JS for making small improvements to a static page
• Angular/Ember
• Make a new HTML that is responsive to changes to state
• React
• Build new components that manage their view state
• Vue

ClojureScript vs DOM
• React
• Re-frame, Om, Rum — Basically just the Virtual DOM
• Manage app state in one place, View in another
• Really fast
• Very functional
• Hoplon
• Spreadsheet cells for changes

Application State
• Applications have a lot data to keep track of
• It’s hard to tell what has changed and when
• It’s hard to keep in synch with the server

JavaScript vs State
• Mutable objects and variables
• Component state
• Redux
• Immutable.js
• GraphQL
• Falcor

ClojureScript vs State
• One mutable variable with immutable data
• Re-frame + Om Next
• Redux was inspired by these
• Manage their own “databases”
• Encourage a “pull model” with the server

Build tool fatigue
• There’s a lot of stuff a modern project needs
• linting
• transpiling
• dependency management
• bundling

JavaScript vs Tools
• Many options
• Webpack
• Grunt
• Gulp
• Browserify
• NPM
• Rollup
• These are just the bundlers!!
• No clear winner
• Broken promises
• Bad documentation

ClojureScript vs Tools
• Leiningen
• Configuration / declarative
• Plugins
• Boot
• Procedural / task-based
• Libraries

Development flow
• Web development is very visual
• We want to see changes right away

JavaScript vs Flow
• “Plain” flow
• Save changes to JS + CSS.
• Watcher recompiles on change.
• Reload the browser.
• Click around to where you were in your app.
• Hot Module Reloading
• Save changes to JS + CSS.
• Watcher recompiles on change.
• Watcher sends new code to browser.
• Works for some applications.

ClojureScript vs Flow
• Figwheel
• Compiles ClojureScript and sends it to browser
• See changes in less than a second
• Application state is untouched

Eric Normand
Follow Eric on:
Eric Normand @EricNormand
eric@lispcast.comlispcast.com

The document provides an overview of the modern JavaScript ecosystem. It discusses the main execution environments (browsers, Node.js, io.js), web servers (Express, Hapi, Koa), package managers (NPM, Bower), task runners (Grunt, Gulp, Broccoli), front-end frameworks (jQuery, Backbone, Angular, Ember, React), module systems (AMD, CommonJS, ES6 modules), and JavaScript flavors/transpilers (CoffeeScript, TypeScript, Dart, ES6). It also outlines the typical development workflow from writing code to compilation/packaging to deployment on a web server to usage in a browser.

Saigon Ruby Meetup 06/10/2015 - Changeful GemFutureworkz

How NOT to get lost in the current JavaScript landscapeRadosław Scheibinger

This document discusses how to avoid getting lost in the current JavaScript landscape. It begins by looking at modern web development trends like HTML5, CSS3, ES6, and expectations of fast page loads. It then examines traditional page lifecycles versus single page applications and various JavaScript frameworks. The document advocates for progressive enhancement and outlines strategies like "Hijax" and using the HTML5 History API to improve traditional approaches. It also discusses issues like code duplication, the benefits of isomorphic JavaScript, and tools for frontend development including Grunt, Gulp, asset bundlers, and test runners. It concludes by providing recommendations on technologies to adopt, consider, or stop using to develop with a progressive enhancement approach.

Creating Hyper Performant Web Apps with ReactJp DeVries

The document discusses creating high performing web apps with React. It emphasizes reliability over speed, noting that reliability means the experience works under different circumstances like without JavaScript. It lists challenges to reliability like poor networks or outdated browsers. It recommends using HTML, CSS, and JavaScript responsibly, using HTML for initial content delivery and JavaScript for interactivity. Server-side rendering with Node.js is suggested to deliver meaningful initial HTML with React components for both reliability and SEO. Caching techniques like versioning assets are also recommended to improve performance.

Coffee script finalpriyankazope

This document provides an overview of CoffeeScript, including: - CoffeeScript compiles one-to-one into equivalent JavaScript code and runs as fast or faster than JavaScript. - To use CoffeeScript, write code in a .coffee file, compile it to a .js file, and include the .js file in an HTML page like a regular JavaScript file. - CoffeeScript simplifies JavaScript syntax by removing the need for semicolons, curly braces, and variable declarations and allowing whitespace as delimiters in arrays and functions. It also includes features like an existential operator and simplified switch statements.

Introduction to CoffeescriptIndies Services

CoffeeScript is a programming language that compiles to JavaScript. It adds syntactic sugar like Ruby and Python to make JavaScript more readable and concise. CoffeeScript code compiles directly to equivalent JavaScript code without runtime interpretation. This allows seamless use of existing JavaScript libraries. CoffeeScript code is more readable and maintainable due to its indentation-based syntax and lack of semicolons. While it simplifies JavaScript programming, an additional compilation step is required and errors can be difficult to debug due to obfuscated compiled code. Overall, CoffeeScript aims to remove rough edges from JavaScript for a smoother programming experience.

Javascript for Wep AppsMichael Puckett

JavaScript frameworks allow business logic to run on the client by sending JSON data on page load rather than dynamic HTML. This allows JavaScript to set up objects and classes to make assumptions without round trips to the server, improving performance. Popular frameworks like Backbone, Ember, Angular, Knockout, and Meteor emphasize separating UI from logic, data binding, templating, and routing to enable single-page applications. Meteor stands out by using the same syntax on client and server and web sockets for automatic UI updates.

More efficient, usable webChris Mills

The document discusses ways to improve the efficiency, extensibility, and flexibility of the web, including through streams, WebAssembly, web components, service workers, and progressive web apps. Streams allow programmatic access to streams of data from the network. WebAssembly allows running compiled code in the browser faster than JavaScript. Web components define custom elements with encapsulated code. Service workers enable offline functionality and caching. Progressive web apps provide native app-like experiences through features like installing offline, home screen icons, and full screen.

RubyhostingArtit Rubybox

This document discusses various options for hosting Ruby applications, including common Ruby web frameworks, web servers like WEBrick and Mongrel, and FastCGI. It notes the pros and cons of each option and how they are impacted by common hosting limitations. It recommends considering deployment tools and control panels to assist with hosting and concludes by offering help from Redgem projects and thanking the event organizers.

ReactJS - Re-rendering pages in the age of the mutable DOMMarc Cyr

Back to the future with static site generatorsChris Ward

If you remember when web sites were all created with plain HTML pages, then you'll know that CMSs and dynamic web frameworks saved us and solved all our problems. Or did they? In fact, we instead spend a lot of time customising existing code to meet our requirements, grappling with deployments and then whacking caching on top of over-powered servers to get an ounce of speed. Static Site Generators aim to sit somewhere in the middle and are perfect for semi-dynamic sites and with a little learning, better for content creators. In this session, Chris will look at an overview of the principles and options for static site generators and deep dive into one or two to explain further how the work and can fit into your projects.

Next Generation Web Development Techniques with Cloud FoundryMalachi Smith

Reef: AJAX the way it should be ESUG

Reef is an AJAX/Javascript component framework for Seaside that models HTML/Javascript components as Smalltalk objects. It hides the complexity of communication by handling interactions through callbacks like Seaside. An extra request is sometimes required but Reef has optimized by introducing #asReefTriggerCallback. New features include composites and Magritte-Reef which brings web 2.0 effects to Magritte-Seaside. Future work includes optimizing the dispatcher, renaming protocols, writing documentation, and collecting more feedback.

Flexible UI Components for a Multi-Framework WorldKevin Ball

improving the performance of Rails web ApplicationsJohn McCaffrey

This presentation is the first in a series on Improving Rails application performance. This session covers the basic motivations and goals for improving performance, the best way to approach a performance assessment, and a review of the tools and techniques that will yield the best results. Tools covered include: Firebug, yslow, page speed, speed tracer, dom monster, request log analyzer, oink, rack bug, new relic rpm, rails metrics, showslow.org, msfast, webpagetest.org and gtmetrix.org. The upcoming sessions will focus on: Improving sql queries, and active record use Improving general rails/ruby code Improving the front-end And a final presentation will cover how to be a more efficient and effective developer! This series will be compressed into a best of session for the 2010 http://windycityRails.org conference

Conquering AngularJS LimitationsValeri Karpov

The document discusses strategies for addressing common AngularJS challenges including SEO, responsive design, and integration testing. It recommends using Prerender.io to generate static HTML for search engines to index Single Page Apps. For responsive design, it suggests using reactive directives that emit events in response to screen size changes rather than having directives know about screen size. Finally, it outlines an approach to integration testing AngularJS directives in isolation using Karma and bootstrapping directives for testing DOM logic.

VTi Knowledge Database: a LinkedData projectTom Klaasen

The document discusses a knowledge database being developed by VTi using LinkedData and Ruby on Rails. It describes key concepts like LinkedData, Ruby, Rails, MVC architecture, and REST. The knowledge database was migrated from a Microsoft SQL Server database to PostgreSQL. The system represents data as RDF, links to external data sources, and has potential for ontology plugins and data enrichment.

Embracing the FutureJemuel Young

Mobile WebDriver SelendroidMichael Palotas

The document discusses Selendroid, a tool for automating tests on mobile web and native Android applications. It begins with an overview of Selenium and the need for mobile test automation. Selendroid is introduced as an open source tool that allows controlling Android devices and applications using the WebDriver protocol. It supports testing native and hybrid mobile applications as well as mobile web. Key features highlighted include compatibility with the JSON wire protocol, no app modification requirement, and support for gestures, grid infrastructure and an inspector tool.

Static is just a cacheVsevolod Zaikov

Code Generation with giant CRUDTom Klaasen

The document discusses using code generation to create generic CRUD screens for a domain model that contains hundreds of classes. Manually coding all the required classes, interfaces, JSPs, XML files, etc. for each domain class would require typing thousands of lines of code and make ongoing changes difficult. The approach involved generating as much code as possible from the domain model and database, while allowing parts to be hand-coded when patterns emerged. This balanced automatic generation with manual flexibility. Overall, code generation provided flexibility to be responsive over time as the domain knowledge and needs evolved.

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Ember.js is being adopted more and more broadly as time passes, and is an excellent choice for highly complex data-driven UIs. With the recent release of the "2.0" version of the framework, things are faster, smarter, and easier than ever. With a focus on productivity and reducing the number of trivial decisions developers must make while building an app, it's astonishing how quickly one can get up and running, and how well the abstractions hold up as the codebase scales in size and complexity. I'd like to give a general overview of Ember, and pause to reflect on some important differences that may be important when considering what the best tool is for your project.

Cloud toolsJohn McCaffrey

John McCaffrey gives a presentation on cloud tools for development. He discusses terminology related to hosting and deploying applications. Some hosting options he covers include self-hosting, Amazon Web Services, EngineYard, Heroku, and AppHarbor. John then demonstrates deploying applications to Heroku and monitoring tools. He finishes by discussing collaboration tools like email, chat, screen sharing, and code repositories on services like GitHub.

ESNext, service workers, and the future of the webJemuel Young

Alfresco Mvc - a seamless integration with Spring MvcDaniel Gradecak

This document discusses Alfresco Mvc, which provides a seamless integration of Spring Mvc with Alfresco. It allows developers to write Alfresco controllers and APIs using Spring Mvc annotations and conventions rather than traditional webscripts. This improves productivity for Java developers and simplifies configuration, testing, exception handling and other aspects. The library includes modules for REST, AOP and querying that enhance Alfresco development. Many companies use it successfully in production environments.

Visual resumeMilan Skorić

Supporting large scale React applicationsMaurice De Beijer [MVP]

- The document discusses best practices for supporting large scale React apps, including handling HTTP requests, scaling out to multiple servers, programming language and code quality tools, optimizing Webpack builds, and logging errors. - It recommends using middleware like Chaos Monkey to simulate failing HTTP requests during development, retrying requests on errors after a pause, and caching static data while handling cache invalidation. - For scaling, it suggests planning for multiple servers from the start and using a tool like Chaos Monkey to randomly route requests during development.

A web app in pure ClojureDane Schneider

Reactive All the Way Down the StackSteve Pember

Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack. In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.

DrupalSouth 2015 - Performance: Not an AfterthoughtNick Santamaria

More Related Content

What's hot (19)

RubyhostingArtit Rubybox

ReactJS - Re-rendering pages in the age of the mutable DOMMarc Cyr

Back to the future with static site generatorsChris Ward

Next Generation Web Development Techniques with Cloud FoundryMalachi Smith

Reef: AJAX the way it should be ESUG

Flexible UI Components for a Multi-Framework WorldKevin Ball

improving the performance of Rails web ApplicationsJohn McCaffrey

Conquering AngularJS LimitationsValeri Karpov

VTi Knowledge Database: a LinkedData projectTom Klaasen

Embracing the FutureJemuel Young

Mobile WebDriver SelendroidMichael Palotas

Static is just a cacheVsevolod Zaikov

Code Generation with giant CRUDTom Klaasen

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Cloud toolsJohn McCaffrey

ESNext, service workers, and the future of the webJemuel Young

Alfresco Mvc - a seamless integration with Spring MvcDaniel Gradecak

Visual resumeMilan Skorić

Supporting large scale React applicationsMaurice De Beijer [MVP]

RubyhostingArtit Rubybox

ReactJS - Re-rendering pages in the age of the mutable DOMMarc Cyr

Back to the future with static site generatorsChris Ward

Next Generation Web Development Techniques with Cloud FoundryMalachi Smith

Reef: AJAX the way it should be ESUG

Flexible UI Components for a Multi-Framework WorldKevin Ball

improving the performance of Rails web ApplicationsJohn McCaffrey

Conquering AngularJS LimitationsValeri Karpov

VTi Knowledge Database: a LinkedData projectTom Klaasen

Embracing the FutureJemuel Young

Mobile WebDriver SelendroidMichael Palotas

Static is just a cacheVsevolod Zaikov

Code Generation with giant CRUDTom Klaasen

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Cloud toolsJohn McCaffrey

ESNext, service workers, and the future of the webJemuel Young

Alfresco Mvc - a seamless integration with Spring MvcDaniel Gradecak

Visual resumeMilan Skorić

Supporting large scale React applicationsMaurice De Beijer [MVP]

Similar to ClojureScript: I can't believe this is JavaScript (20)

A web app in pure ClojureDane Schneider

Reactive All the Way Down the StackSteve Pember

DrupalSouth 2015 - Performance: Not an AfterthoughtNick Santamaria

Node.JS: Do you know the dependency of your dependencies dependencyWim Selles

React Tech SalonChenguang ZHANG

React is a JavaScript library for building user interfaces that aims to solve issues with data changing over time in large web applications. It introduces components, re-rendering on data changes rather than mutating data, and a virtual DOM for efficient re-rendering. React uses a unidirectional data flow and one-way data binding that improves design architecture and code reusability. Related technologies like JSX, Flux, GraphQL, Relay, and React Native further enhance React's capabilities.

React introductionKashyap Parmar

React is a JavaScript library for building user interfaces and applications. It uses components rather than templates, implements a one-way data flow downwards and re-renders components on data changes rather than mutating them directly. The virtual DOM in React allows for simple and fast re-rendering. Key aspects of React include components, one-way data flow, re-rendering without mutation, the virtual DOM, JSX syntax and React Native for building mobile apps. Flux is an architecture pattern used for state management in React, implementing unidirectional data flow through actions, a dispatcher, stores and views.

Clojurescript slideselliando dias

Angular js 1.0-fundamentalsVenkatesh Narayanan

This document provides an overview of AngularJS fundamentals including controllers, services, directives, dependency injection, routing, forms, and testing. It discusses key AngularJS concepts like scopes, expressions, filters, and the digest loop. Sample code is presented to demonstrate modules, controllers, and directives. Various options for server communication, caching, debugging, localization, and animation are also covered. Guidelines for optimizing AngularJS applications are provided at the end.

Dropwizard and Groovytomaslin

This document provides an overview of using Dropwizard, a Java framework for building production-grade RESTful web services, with Groovy. It discusses how Dropwizard combines popular Java libraries and frameworks, highlights some companies using Dropwizard with Groovy successfully, and describes key parts of a Dropwizard application like configurations, resources, representations, metrics, and deployment. The document emphasizes how Dropwizard enables service-oriented architectures and provides advantages like performance, testability, and easy deployment.

Meteor + ReactTaggart Bowen-Gaddy

Ohio Devfest - Visual Analysis with GCPWesley Workman

The document discusses visual analysis using Google Cloud Platform. It provides an overview of Google Cloud services including App Engine, Container Engine, Compute Engine, Datastore, Cloud SQL, and Spanner for building and deploying applications at scale. It also mentions Machine Learning services for tasks like natural language processing, image analysis, and translation. The presentation then demonstrates a photo sharing application built on these services and discusses ways to enhance it further using App Engine Flex, video processing, document parsing, BigQuery, and analytics. It concludes by inviting Python developers interested in visual analysis to discuss job opportunities.

Road Trip To ComponentMarketa Adamova

@MarketaAdamova Slides from 'Road Trip To Component' talk (Dutch Clojure Days 2017) 'Few months ago our company NomNom decided to move all its backend services from Ruby to Clojure. And I think a road trip is best comparison for this migration. There was excitement at start, then panic a few hours down the road wondering what was left behind, but now a constant joy of discovering new things. In this talk I’d like to share how we eventually arrived at Stuart Sierra’s Component. Let’s take a look at how components improved our quickly growing codebase and testing, as well as some of the trade-offs we had to make. Finally I’ll show how components can help with managing running code in production.'

Full-Stack Development with Spring Boot and VueJSVMware Tanzu

Indic threads pune12-typesafe stack software development on the jvmIndicThreads

Build your own analytics power toolsAlban Gérôme

JHipsterYuen-Kuei Hsueh

What is Mean Stack Development ?Balajihope

The document provides an overview of the MEAN stack, which is a full-stack JavaScript solution for building web applications. It consists of MongoDB (a NoSQL database), Express (a Node.js web application framework), AngularJS (a client-side framework), and Node.js (a JavaScript runtime). The document discusses each component, how they work together, advantages like using a single programming language throughout and ability to build fast applications, and disadvantages like MongoDB not being as robust as SQL databases. It concludes that MEAN provides a fast, easy way to create modern, responsive dynamic web sites.

Tech Headline - JavaScript PerformanceRodrigo Castilho

Drupal commerce performance profiling and tunning using loadstorm experiments...Andy Kucharski

Drupal commerce performance profiling by load testing a the kickstarter drupal commerce site on an AWS instance and comparing how the site performa after several well known performance tuning enhancements are applied. We try to compare performance improvements after druapl cache, aggregation, varnish, and nginx reverse proxy. This presentation was first given at Drupal Mid Camp in Chicago. We used loadstorm and new relic to analyze results.

Frontend as a first class citizenMarcin Grzywaczewski

Frontend development skills are more and more demanded from our clients and stakeholders. Thanks to Facebook, they know what a dynamic UI is and they want it too in their products. It can be a scary situation for people working mostly on a backend side of web applications. In this presentation I want to show that JavaScript can be really fun to write and mature enough to cope with backend technologies.

A web app in pure ClojureDane Schneider

Reactive All the Way Down the StackSteve Pember

DrupalSouth 2015 - Performance: Not an AfterthoughtNick Santamaria

Node.JS: Do you know the dependency of your dependencies dependencyWim Selles

React Tech SalonChenguang ZHANG

React introductionKashyap Parmar

Clojurescript slideselliando dias

Angular js 1.0-fundamentalsVenkatesh Narayanan

Dropwizard and Groovytomaslin

Meteor + ReactTaggart Bowen-Gaddy

Ohio Devfest - Visual Analysis with GCPWesley Workman

Road Trip To ComponentMarketa Adamova

Full-Stack Development with Spring Boot and VueJSVMware Tanzu

Indic threads pune12-typesafe stack software development on the jvmIndicThreads

Build your own analytics power toolsAlban Gérôme

JHipsterYuen-Kuei Hsueh

What is Mean Stack Development ?Balajihope

Tech Headline - JavaScript PerformanceRodrigo Castilho

Drupal commerce performance profiling and tunning using loadstorm experiments...Andy Kucharski

Frontend as a first class citizenMarcin Grzywaczewski

More from Eric Normand (9)

You are in a maze of deeply nested maps, all alikeEric Normand

The document discusses encapsulating data operations and avoiding deep nesting when working with nested data structures like maps. It recommends separating code into distinct layers based on rates of change, with each layer only depending on the layer below. This stratified design approach aims to make the code easier to understand and maintain by programing at a higher level of abstraction closer to the domain concepts.

The elements of a functional mindsetEric Normand

All I Needed for Functional Programming I Learned in High School AlgebraEric Normand

Are you tired of forgetting which keys go in which maps? Are your data transformation pipelines reaching trans-continental proportions? A smidgen of high school algebra may go a long way to eliminating your deeply nested headaches. In this talk, we will explore several functional programming concepts and techniques, lifted right out of high school algebra, that can deepen your functional programming skills and get you slicing your problems along new dimensions.

Lies My OO Teacher Told MeEric Normand

What is Functional Programming?Eric Normand

This document discusses the problems of complexity in software development and proposes functional programming as a solution. It outlines three main sources of complexity: time, state, and architecture. Functional programming aims to master these through an immutable data and stateless function model where functions take inputs and produce outputs without side effects. This reduces complexity by avoiding unintended interactions between different parts of a program over time and through state changes.

Functional Programming for BusinessEric Normand

A Theory of Functional Programming LambdUpEric Normand

There are two common questions we hear from outside the functional programming community: ‘What is functional programming?’, and ‘Why should I use it?’. I have struggled to find good answers to these questions. In this talk, we will look at the existing definition and I will present a formulation I’ve been working on that attempts to answer both of these questions, and also why functional programming is so special.

Testing stateful, concurrent, and async systems using test.checkEric Normand

Generative testing is great for testing pure functions, but it is also used to test the behavior of stateful systems that change over time. Those systems are often designed for highly concurrent usage, such as queues, databases, and storage. And then sometimes your code is also asynchronous, such as in JavaScript. Learn several patterns to find inconsistencies across platforms, race conditions, and corner cases. This talk assumes basic understanding of generative testing.

Building Composable AbstractionsEric Normand

You are in a maze of deeply nested maps, all alikeEric Normand

The elements of a functional mindsetEric Normand

All I Needed for Functional Programming I Learned in High School AlgebraEric Normand

Lies My OO Teacher Told MeEric Normand

What is Functional Programming?Eric Normand

Functional Programming for BusinessEric Normand

A Theory of Functional Programming LambdUpEric Normand

Testing stateful, concurrent, and async systems using test.checkEric Normand

Building Composable AbstractionsEric Normand

Recently uploaded (20)

Artificial Intelligence (AI) basics.pptxaditichinar

Compiler Design_Lexical Analysis phase.pptxRushaliDeshmukh2

QA/QC Manager (Quality management Expert)rccbatchplant

Smart_Storage_Systems_Production_Engineering.pptxrushikeshnavghare94

railway wheels, descaling after reheating and before forgingJavad Kadkhodapour

Compiler Design Unit1 PPT Phases of Compiler.pptxRushaliDeshmukh2

MAQUINARIA MINAS CEMA 6th Edition (1).pdfssuser562df4

Metal alkyne complexes.pptx in chemistrymee23nu

15th International Conference on Computer Science, Engineering and Applicatio...IJCSES Journal

Development of MLR, ANN and ANFIS Models for Estimation of PCUs at Different ...Journal of Soft Computing in Civil Engineering

Passenger car unit (PCU) of a vehicle type depends on vehicular characteristics, stream characteristics, roadway characteristics, environmental factors, climate conditions and control conditions. Keeping in view various factors affecting PCU, a model was developed taking a volume to capacity ratio and percentage share of particular vehicle type as independent parameters. A microscopic traffic simulation model VISSIM has been used in present study for generating traffic flow data which some time very difficult to obtain from field survey. A comparison study was carried out with the purpose of verifying when the adaptive neuro-fuzzy inference system (ANFIS), artificial neural network (ANN) and multiple linear regression (MLR) models are appropriate for prediction of PCUs of different vehicle types. From the results observed that ANFIS model estimates were closer to the corresponding simulated PCU values compared to MLR and ANN models. It is concluded that the ANFIS model showed greater potential in predicting PCUs from v/c ratio and proportional share for all type of vehicles whereas MLR and ANN models did not perform well.

Machine learning project on employee attrition detection using (2).pptxrajeswari89780

"Feed Water Heaters in Thermal Power Plants: Types, Working, and Efficiency G...Infopitaara

A feed water heater is a device used in power plants to preheat water before it enters the boiler. It plays a critical role in improving the overall efficiency of the power generation process, especially in thermal power plants. 🔧 Function of a Feed Water Heater: It uses steam extracted from the turbine to preheat the feed water. This reduces the fuel required to convert water into steam in the boiler. It supports Regenerative Rankine Cycle, increasing plant efficiency. 🔍 Types of Feed Water Heaters: Open Feed Water Heater (Direct Contact) Steam and water come into direct contact. Mixing occurs, and heat is transferred directly. Common in low-pressure stages. Closed Feed Water Heater (Surface Type) Steam and water are separated by tubes. Heat is transferred through tube walls. Common in high-pressure systems. ⚙️ Advantages: Improves thermal efficiency. Reduces fuel consumption. Lowers thermal stress on boiler components. Minimizes corrosion by removing dissolved gases.

211421893-M-Tech-CIVIL-Structural-Engineering-pdf.pdfinmishra17121973

Explainable-Artificial-Intelligence-XAI-A-Deep-Dive (1).pptxMahaveerVPandit

The Gaussian Process Modeling Module in UQLabJournal of Soft Computing in Civil Engineering

We introduce the Gaussian process (GP) modeling module developed within the UQLab software framework. The novel design of the GP-module aims at providing seamless integration of GP modeling into any uncertainty quantification workflow, as well as a standalone surrogate modeling tool. We first briefly present the key mathematical tools on the basis of GP modeling (a.k.a. Kriging), as well as the associated theoretical and computational framework. We then provide an extensive overview of the available features of the software and demonstrate its flexibility and user-friendliness. Finally, we showcase the usage and the performance of the software on several applications borrowed from different fields of engineering. These include a basic surrogate of a well-known analytical benchmark function; a hierarchical Kriging example applied to wind turbine aero-servo-elastic simulations and a more complex geotechnical example that requires a non-stationary, user-defined correlation function. The GP-module, like the rest of the scientific code that is shipped with UQLab, is open source (BSD license).

DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...charlesdick1345

Introduction to Zoomlion Earthmoving.pptxAS1920

Smart Storage Solutions.pptx for production engineeringrushikeshnavghare94

ELectronics Boards & Product Testing_Shiju.pdfShiju Jacob

RICS Membership-(The Royal Institution of Chartered Surveyors).pdfMohamedAbdelkader115

Artificial Intelligence (AI) basics.pptxaditichinar

Compiler Design_Lexical Analysis phase.pptxRushaliDeshmukh2

QA/QC Manager (Quality management Expert)rccbatchplant

Smart_Storage_Systems_Production_Engineering.pptxrushikeshnavghare94

railway wheels, descaling after reheating and before forgingJavad Kadkhodapour

Compiler Design Unit1 PPT Phases of Compiler.pptxRushaliDeshmukh2

MAQUINARIA MINAS CEMA 6th Edition (1).pdfssuser562df4

Metal alkyne complexes.pptx in chemistrymee23nu

15th International Conference on Computer Science, Engineering and Applicatio...IJCSES Journal

Development of MLR, ANN and ANFIS Models for Estimation of PCUs at Different ...Journal of Soft Computing in Civil Engineering

Machine learning project on employee attrition detection using (2).pptxrajeswari89780

"Feed Water Heaters in Thermal Power Plants: Types, Working, and Efficiency G...Infopitaara

211421893-M-Tech-CIVIL-Structural-Engineering-pdf.pdfinmishra17121973

Explainable-Artificial-Intelligence-XAI-A-Deep-Dive (1).pptxMahaveerVPandit

The Gaussian Process Modeling Module in UQLabJournal of Soft Computing in Civil Engineering

DATA-DRIVEN SHOULDER INVERSE KINEMATICS YoungBeom Kim1 , Byung-Ha Park1 , Kwa...charlesdick1345

Introduction to Zoomlion Earthmoving.pptxAS1920

Smart Storage Solutions.pptx for production engineeringrushikeshnavghare94

ELectronics Boards & Product Testing_Shiju.pdfShiju Jacob

RICS Membership-(The Royal Institution of Chartered Surveyors).pdfMohamedAbdelkader115

ClojureScript: I can't believe this is JavaScript

1. ClojureScript: I can't believe this is JavaScript Eric Normand

2. Clojure transpiled to JavaScript

3. ClojureScript I can’t believe this is JavaScript!

4. For the video and transcript of this presentation, click here: https://lispcast.com/clojurescript-cant-believe-javascript/

5. Callback Hell

6. Callback Hell • JavaScript uses callback-style for async • Not just about indentation • About inversion of control • I don’t know when or in what order or even if my code will be called!

7. JavaScript vs Callback hell • Promises • Helps a lot! • Still have promises within promises within promises • async/await • nice! • Together: wow, a really good solution!

8. ClojureScript vs Callback Hell • core.async • A library that turns sequential code into callbacks • Never give up control • Based on Communicating Sequential Processes • (the same thing Go is based on)

9. Code Optimization

10. Code Optimization • Milliseconds === $$$$ • Minify code • Remove dead code • Split code

11. JavaScript vs Optimization • webpack • minification • dead code elimination • splitting • Rollup • tree shaking

12. ClojureScript vs Optimization • Google Closure Compiler • heavily tested • optimizes Gmail • “just works”

13. Stateful DOM

14. Stateful DOM • Dynamic apps need to modify the DOM • DOM and your data get out of sync

15. JavaScript vs DOM • JavaScript sprinkles • Just use JS for making small improvements to a static page • Angular/Ember • Make a new HTML that is responsive to changes to state • React • Build new components that manage their view state • Vue

16. ClojureScript vs DOM • React • Re-frame, Om, Rum — Basically just the Virtual DOM • Manage app state in one place, View in another • Really fast • Very functional • Hoplon • Spreadsheet cells for changes

17. Application State Management

18. Application State • Applications have a lot data to keep track of • It’s hard to tell what has changed and when • It’s hard to keep in synch with the server

19. JavaScript vs State • Mutable objects and variables • Component state • Redux • Immutable.js • GraphQL • Falcor

20. ClojureScript vs State • One mutable variable with immutable data • Re-frame + Om Next • Redux was inspired by these • Manage their own “databases” • Encourage a “pull model” with the server

21. Build tool fatigue

22. Build tool fatigue • There’s a lot of stuff a modern project needs • linting • transpiling • dependency management • bundling

23. JavaScript vs Tools • Many options • Webpack • Grunt • Gulp • Browserify • NPM • Rollup • These are just the bundlers!! • No clear winner • Broken promises • Bad documentation

24. ClojureScript vs Tools • Leiningen • Configuration / declarative • Plugins • Boot • Procedural / task-based • Libraries

25. Development flow

26. Development flow • Web development is very visual • We want to see changes right away

27. JavaScript vs Flow • “Plain” flow • Save changes to JS + CSS. • Watcher recompiles on change. • Reload the browser. • Click around to where you were in your app. • Hot Module Reloading • Save changes to JS + CSS. • Watcher recompiles on change. • Watcher sends new code to browser. • Works for some applications.

28. ClojureScript vs Flow • Figwheel • Compiles ClojureScript and sends it to browser • See changes in less than a second • Application state is untouched

29. Extra slides

30. Embrace the host

31. Built-in

32. Platforms

33. React

34. Other Goodies

35. Module Systems

36. core.async

37. EDN

38. Google Closure Compiler

39. Eric Normand Follow Eric on: Eric Normand @EricNormand [email protected]