Although not in the language yet, I'm excited to see top-level await, pattern matching as well as the null coalesce operator progress and land in the language. Top-level await is already at stage 3, so that is pretty much a shoe in.

Daniel Ehrenberg

@littledan

I'm thrilled with the big stage advancements in this past week's TC39 meeting:
- import() and BigInt reached Stage 4
- top-level await and WeakRefs reached Stage 3
- Optional?.Chaining reached Stage 2
- The Emitter proposal was introduced
- Several smaller PRs reached consensus

08:35 AM - 08 Jun 2019

53 199

Here's the repos for those interested:

// awaiting.mjs
import { process } from "./some-module.mjs"
let output
async function main() {
  const dynamic = await import(computedModuleSpecifier)
  const data = await fetch(url);
  output = process(dynamic.default, data);
}
main();
export { output };

// awaiting.mjs
import

const response = {
  settings: {
    nullValue: null
    height: 400
    animationDuration: 0
    headerText: ''
    showSplashScreen: false
  }
};

const undefinedValue = response.settings?.undefinedValue || 'some other default'; // result: 'some other default'
const nullValue = response.settings?.nullValue || 'some other default'; // result:

Soon?.you?.will?.be?.able?.to?.dig?.through?.objects?.like?.this

github.com/tc39/proposal-optional-...

svelte: it's more reactive than react and makes programming more inclusive which is my mantra ;)

I find TypeScript to be exciting right now. It seems that the community became a lot more open to it and even excited about it. It improves the way we interact with 3rd party libraries, with our own code, and makes things better and cleaner. I believe that the next steps for JavaScript / TypeScript will be, like for most other modern languages, to adapt more standards in writing clean code. We may see more things like dependency inversion and separation of concerns.

I find framework wars to be mostly distracting (e.g. recent thing between React and Svelte). They implement and reimplement the wheel, they try to solve the same problem, each time slightly differently, but they don't solve new problems, and, in the end, don't make developers that much more efficient. My hope is that people will realize this and start separating their business logic away from the frameworks rather than putting it in the components, and use frameworks as plug-in if they choose so.

Microfrontends - My twitter feed is filled with people fighting over what micro frontends are and not. Then there's Jamstack, how do we even keep up with technology?

electron is one area where you need to pay attention. Though personally I feel its a crap due to its super bloat and bad performance (a browser container for each app, really?), there is no denying that there are very few players in that niche (seamless OS independence).

Unless Microsoft comes up with a fully platform independent version for WinForms/WPF or Oracle steps up their game with JavaFX, electron has a very super-bright future on desktops.

React Native still has to essentially compile to what’s available in the native ecosystem right?

As long as the user experience is solid it doesn’t seem like something Google and Apple would be overly concerned about eh?

They’d still be gatekeepers even if the downstream implementation details change.

Still waiting for decorators. Looking forward to Vue 3.

Microfrontends, lerna with tailor and cloud functions

Const thing = const {something: here}

I hope the const on the value is decided to be immut or something else. The immutable keyword for values would be a game changer.