nodejs.dev VS wasm-bindgen

[ { "type_of": "article", "id": 1281931, "title": "When can you declare yourself a Full-stack Dev?", "description": "Hello 👋🏼 I was wondering if I should consider myself as a front-end or full-stack developer. Or at...", "published": true, "published_at": "2022-12-02T17:05:00.000Z", "slug": "when-can-you-declare-yourself-a-full-stack-dev-31j1", "path": "/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "url": "https://dev.to/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "comments_count": 29, "public_reactions_count": 34, "page_views_count": ----, "published_timestamp": "2022-12-02T17:05:00Z", "body_markdown": "Hello 👋🏼\n\nI was wondering if I should consider myself as a front-end or full-stack developer. Or at least how to present myself to companies.\n\nAnd then, I asked myself... **at what moment can you consider yourself a full-stack developer?** What are the basics to know to become one? \n\n\n> For example, \n> I suppose that to be a self-proclaimed full-stack developer in JavaScript, you have to know at least one front-end framework (like [`Vue`](https://vuejs.org), [`React`](https://reactjs.org/), [`Angular`](https://angular.io/), [`Svelte`](https://svelte.dev/), [`Astro`](https://astro.build/) etc...), know the basics of the backend and its specificities, especially [`Node.js`](https://nodejs.dev) and all its aspects, know one or more frameworks (I think of [`Express.js`](https://expressjs.com/) or [`Fastify`](https://www.fastify.io/)), know how to create an API and databases, and know the principle of MVC in order to set up a good architecture. \n> \n> _If there is something missing, don't hesitate to tell me_.", "positive_reactions_count": 34, "cover_image": "https://res.cloudinary.com/practicaldev/image/fetch/s--CzOg3CT7--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/15u06okn5tcdc0i92xhm.png", "tag_list": [ "discuss" ], "canonical_url": "https://dev.to/thomasbnt/when-can-you-declare-yourself-a-full-stack-dev-31j1", "reading_time_minutes": 1, "user": { "name": "Thomas Bnt", "username": "thomasbnt", "twitter_username": "Thomasbnt_", "github_username": "thomasbnt", "user_id": 18254, "website_url": "https://thomasbnt.dev", "profile_image": "https://res.cloudinary.com/practicaldev/image/fetch/s--zpCwDOpw--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/18254/c3e35d32-bfe2-48ed-93b7-f2caf9c60gd7.png", "profile_image_90": "https://res.cloudinary.com/practicaldev/image/fetch/s--Iv24f4-g--/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/18254/c3e35d32-bfe2-48ed-93b7-f2caf9c60gd7.pngg" }, "flare_tag": { "name": "discuss", "bg_color_hex": "#1ad643", "text_color_hex": "#FFFFFF" } }, ]

For example, I suppose that to be a self-proclaimed full-stack developer in JavaScript, you have to know at least one front-end framework (like Vue, React, Angular, Svelte, Astro etc...), know the basics of the backend and its specificities, especially Node.js and all its aspects, know one or more frameworks (I think of Express.js or Fastify), know how to create an API and databases, and know the principle of MVC in order to set up a good architecture.

nodejs.dev: Nodejs.org website Added a simple GitHub action to sync auto-generated docs daily, and added prettier formatting for .yml files

the Tutorial at nodejs.dev explains how node works and how it's different from other JS environments. They also have a version of the API docs which I find has better formatting than the one at nodejs.com

https://nodejs.dev/

I think this has been fixed here https://github.com/nodejs/nodejs.dev/pull/2713/files

Probably just pending release

I believe https://nodejs.dev/ is a third party site not officially related to the Node.js project.

Strapi is the leading open-source headless Content Management System (CMS). It is 100% Javascript, based on Node.js, and used to build RESTful APIs and GraphQL.

NestJS is a Node.js framework for building server-side applications. NestJS supports typescript out of the box. On the other hand, Passport is an authentication middleware for Node.js that supports over 500 authentication strategies, e.g., username and password, google, Facebook, etc.

Another strange issue could be seen in the strict class heritage organized definition of the DOM, which can not be handled very well by rust because of a still unsolved bindgen issue (#210).

For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.

We encountered quite a few hurdles on our journey. For one, we had to build our own yew-webtransport and yew-websocket integration from scratch by adding WebTransport definitions to wasm-bindgen (pull request link). We also had to add WebTransport support to the h3 crate (pull request link). co-created by @ten3roberts

Go with your WebAssembly module idea. Since it sounds like your chess engine does not draw a UI, it shouldn't be too difficult. wasm-bindgen will be your best friend.

I've never tried it, but apparently some bindings exist, e.g. https://github.com/rustwasm/wasm-bindgen

So you can either try manipulating the DOM w/ some bindings or draw to canvas.

Google also brings up this GitHub issue.

If you want to learn more on wasm-pack, there is a wasm-pack book as well as some fairly detailed wasm-bindgen docs. There are a few resources for learning Rust itself in the December newsletter. Finally, please get in touch if you would like to see more content on Deno and Fresh. I hope you found the content useful and am keen to hear about possible improvements.

Love the article.

In my mind I see the problem of dynamic linking in rust to have a bunch of overlap with the "I want this rust library to be exposed in my higher level GC'd language with minimal safety/handwritten bindings" problem.

My hunch is that the lack of expressiveness of the C ABI is holding back both. the thing I'd love to see some sort of "higher level than the C ABI" come out. And something like `wasm-bindgen`[0] to exist for more languages.

Here's a link to the rust "interopable_api" proposal! I don't understand all the implications, but it seems to be in the right direction https://github.com/rust-lang/rust/pull/105586

[0]https://rustwasm.github.io/docs/wasm-bindgen/

Rust has https://github.com/rustwasm/wasm-bindgen and https://crates.io/crates/sledgehammer, the latter of which batches together JS calls to reduce the FFI cost. https://dioxuslabs.com/ uses these to great effect.

This seems like it could be super useful for integrating with wasm-bindgen and TypeScript. Last I checked, the types generated by wasm-bindgen left a lot to be desired (no disrespect intended, wasm-bindgen is an awesome project). A few years ago, I contributed the skip_typescript attribute to wasm_bindgen that allowed you to override the type generation by hand-writing your own types (using a custom typescript section), but I wonder if this could simply generate higher quality types without the manual intervention.