@robbkidd Heck no! #RubyLang makes me happy. #Java is an example of a language I consider soul-sucking. I feel the same way about #JavaScript TBH, although #ES6 is less evil than many of the popular JS frameworks.
I'm just looking to pick up a new language that is commercially viable but neither painful nor a commodity skill. That's obviously going to solicit very opinionated answers, though.
#rubylang #java #javascript #es6
@GabeMoralesVR I am a complete newbie of Javascript. Modules have created a lot of difficulties as I do not yet understand how they work and the documentation is confusing as some Emscripten exemples refer to #CommonJS whereas browsers prefer #ES6.
@GabeMoralesVR thank you. What I don't understand is how to "link" the #ES6 code to the #C one. I tried --js-library keyp.js, but I get an error like "import initModule from "./function.js";
^^^^^^
SyntaxError: Cannot use import statement outside a module" But I haven't yet spend time on this stuff.
I think I can now call #C functions from #Javascript code. It is not so simple as things are not well documented and I'm a complete newbie in the #ES6 world. It remains to see how to call #Javascript functions fro the #C code. #Emscripten.
#c #javascript #es6 #emscripten
jQueryからVanilla JS(ピュアなJavaScript)に書き換える時によく使うもの
https://qiita.com/s-takayama/items/349d6bd414bc2f76a423?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#JavaScript #jQuery #es6 #es2015 #VanillaJS
#javascript #jquery #es6 #es2015 #vanillajs
A little #es6 #typescript tip.
When importing always enter in the from part first. Because, then you can autocomplete the things you want to import.
First enter:
import from 'module/path';
Then autocomplete works:
import { thisCompletesNow } from 'module/path';
Web Programmer be like :
> 8 SHADOW ROOT MISTAKES & HOW TO FIX THEM
ah yes
https://behindthechair.com/articles/8-shadow-root-mistakes-how-to-fix-them/
#rickrolling #webdevelopment #es6 #javascript #js #shadowdom #shadowroot #lol
#rickrolling #webdevelopment #es6 #javascript #JS #shadowdom #shadowroot #lol
And https://manifoldcad.org/ now uses gltf-transform by @donmccurdy and gl-matrix by @tojiro and it's even installable!
Our #npm package, manifold-3d, is now a proper #es6 #module, has much faster I/O, and handles multi-material meshes.
@villares I counter a runtime-heavy client-side scripting language in your scripting language yo dawg solution which was rejected years and years and years ago (ref: pypyjs.org — even having a JIT) with almost any #Python AST → #ES6 transpilation tool. JavaScripthon is one I seem to like; there are several.
Originally shared 2016, but I’ve got older bits around here somewhere. This used to construct a “pure Python” SPA/PWA: https://gist.github.com/amcgregor/9040e2e6be9249bcd73c
With like, zero, zip, nada runtime overhead.
What static site generators do you recommend? I want to play with #ES6 and #TailwindCSS. Is there something that would just work out the box? I'm too old and tired to learn all the bits in the middle.
@tomw I think you could (???) write modern, modularized #es6 and ship it to the browser now, using #importmaps to direct the browser to where your module files live. I haven't tried it yet, and the support may be limited, but... maybe that's The Future™.
That may eliminate #transpiling, but we still have to deal with concatenation. With updated protocols like #HTTP3, maybe multiple simultaneous connections will be less of a problem?
And then #minification? I dunno man, maybe gzipping on the wire is good enough.
But I feel your pain. I'm hopeful for the future.
#javascript #programming #webdevelopment
Also, I want native #css loops. I think that's the last thing we need #preprocessors for.
I haven't worked with built-in web components, but that could be the answer to the "always a new framework" problem. But if it was, it prolly would have more uptake by now.
I honestly spend to much time thinking about this.
#es6 #importmaps #transpiling #http3 #minification #JavaScript #programming #webdevelopment #css #preprocessors
I just learned something new to me about optional chaining in current jaavscript.
You always have to put a dot (.) after the question mark (?) so the compiler can distinguish this from a beginning ternary condition question mark.
#javascript #es6 #syntacticsugar
https://blog.bitsrc.io/why-is-my-jest-suite-so-slow-2a4859bb9ac0
I learned:
* to link the Chrome profile with Node scripts to profile performance
* using an eslint rule to NOT import from index files in tests
* that setupTests.ts runs NOT once ,on the startup of all tests
* to deactivate type checking for the tests
#es6 #js #javascript #ts #typescript #react #jest #babel #webpack #performance #test #unittest #profiling #eslint
#es6 #JS #javascript #ts #typescript #react #jest #Babel #webpack #performance #test #unittest #profiling #ESLint
Did you know #javascript underwent a major revolution in 2015?
Next February, join Joel Lord and Fast Forward your #JavaScript skills with #ES6 https://confoo.ca/en/2023/session/your-javascript-is-so-2015
「 However, despite the large wave of criticism in 2011, CoffeeScript was one of the most followed projects on GitHub. At that time, it enjoyed relatively high popularity in the Ruby-developers community. A large part of CS supporters said their code ran faster and was three times shorter than JS code 」
How CoffeeScript Got Forgotten
— Staszek Zaczek
#coffeescript #javascript #es6
「 CoffeeScript began as a fantastic idea (making it easier to write JavaScript code); ultimately, however, it didn’t stand the test of time and was pushed out by JavaScript. Currently, hardly anyone remembers it. Most new people in the front-end environment don’t even know such a language existed. Instead of being included in lists of the most popular new programming languages, it takes top spots on the lists of the worst languages to learn 」
#coffeescript #javascript #es6
「 There were many indications that CoffeeScript would be with us for a long time, but a lot changed to its disadvantage in 2015 after the introduction of JavaScript’s ES6 — which actually was an implementation of CS solutions into the language from which the story began. In ES6, JavaScript also added many interesting new features the CoffeeScript team’s engineers didn’t think about 」
How CoffeeScript Got Forgotten
— Staszek Zaczek
#CoffeeScript #JavaScript #ES6
https://betterprogramming.pub/how-coffeescript-got-forgotten-812328225987?utm_source=pocket_mylist
#coffeescript #javascript #es6
Amazing!! NIO just finished the free practice of Formula E in Mexico City on the 3rd place!! At the end of the last seasons NIO was always on the last places. Looking forward for the race tomorrow!
#BlueSkyComing #NIOLife #NIOPower #EP9 #ES8 #ET7 #ES7 #EL7 #EC7 #ES6 #ET5 #NIO
#nio #ET5 #es6 #ec7 #el7 #ES7 #ET7 #es8 #ep9 #niopower #niolife #blueskycoming
WebAssembly: Go vs Rust vs AssemblyScript vs TypeScript vs Javascript
https://ecostack.dev/posts/wasm-tinygo-vs-rust-vs-assemblyscript/
#wasm #webassambly #javascript #js #es6 #typescript #rust #wasmpack #go #golang #tinygo #assemblyscript #performance #speed #size #runtime
#wasm #webassambly #javascript #JS #es6 #typescript #rust #wasmpack #Go #golang #tinygo #assemblyscript #performance #speed #size #runtime