polygonjs VS Vue.js

- some corners will connect less than 4 tiles. This does the opposite of the previous point, as this removes diagonals. This limits your moves in a specific direction, but can also protect you from your opponents. It's the kind of features that can be used both as a defense and as attack.

And the boards are procedurally generated, so you can play unique games each time (or you can re-use the same boards if you like). It is done with my engine Polygonjs ( https://polygonjs.com/ ), and if you're curious about how the grid is built, here is an example scene you can play with: https://polygonjs.com/gui/irregular_quad_relaxation/edit .

The game is not free on Steam/iOS, but the demo has no time limit, it just gives you a handful of boards to play with.

I hope that's fun!

- Trailer: https://www.youtube.com/watch?v=GAfUvwuLueI

That's the path I took with Polygonjs ( https://polygonjs.com ), and a game I've just released ( https://polyreplay.com/minesweepertwist ), with more coming shortly.

But it didn't start like that. It only started as a tool I could use to deliver client projects, as I was trying to become a freelance for interactive 3D scenes for the web.

Project after project ( some examples here: https://polygon-lab.com/ ), I could improve Polygonjs. Then I found clients who would be interested enough to buy licenses, and would give valuable feedback which would help the project grow even more.

And a few clients asking for not just interactive sites, but also games. This pushed Polygonjs further, and after several games released, it definitely qualifies as a game engine.

So this is generally an advice I give to people who want to become freelancers. Build a tool that solves a problem in your space, as this gives you an edge, and you'll also get the chance to confront that tool to reality, which will help it - and you - grow. This becomes a virtuous circle very quickly.

You can have a look how I do it in Polygonjs (which is a node-based design tool based on threejs), in this example scene.

If you're familiar with Houdini, I invite you to try Polygonjs, which is based on threejs and inspired by Houdini. You can basically build threejs in a procedural way, with just nodes.

You could try Polygonjs. It's inspired by Houdini, so has a lot in common with TouchDesigner (it's fully node-based, you can create audio reactive apps), and it works on the web, which makes scenes very easy to share.

Can I invite you to try Polygonjs as well?

you can generate an SDF from a mesh with [Polygonjs](https://polygonjs.com). Here is an [example scene](https://polygonjs.com/examples/bynode:mat:raymarchingbuilder...).

It won't generate a function, though. Instead it creates a 3D texture which is used inside the raymarching material. In my experience this is much more performant, and also art-directable.

(disclaimer, I'm building Polygonjs)

It sounds like you need a dynamic system that runs in the browser. Maybe try Polygonjs ( https://polygonjs.com )? The the 3rd interactive scene on the front page gives an idea of a dynamic model. I run it, if that of interest, happy to give more examples

If you ever wanted to do a vegetation modelling tool for the web, I invite you to try it on Polygonjs, it has a lot of similarities with Houdini (node-based, procedural modeling, HDA system, etc) and is all web/realtime. And open source.

Vuejs

Vue.js is a big favorite for making websites because it's easy to use and fits in well with other stuff. Many people worldwide are using it, and the community keeps growing.

Vue has a thriving ecosystem with a wide range of third-party libraries and plugins available for extending its functionality. These libraries cover everything from state management to routing, making it easy for developers to find solutions to common problems and enhance their development workflow. As of this writing, Vue has 200k GitHub stars.

6. Vue.js

I have got the privilege of working on Vue 2 couple of months ago and its really amazing framework to work with .

Angular is as little innovative for web frameworks as Firefox-ESR is for browsers. It merely keeps copying features from other frameworks - just many years later. It is a chronically outdated framework that always struggles to keep up with its competitors. It would be ok if those were deliberate design decisions, but if the features get copied some day anyway, what is the point? Why not do it the right way from the start?

For example, this update brings us computed properties, an essential feature for any complex performant web application that was made popular by Vue.js 10 years ago [1]. And now in 2023 we get it in Angular, essentially a confirmation by its devs that its lack has always been a design error.

I also cannot understand the "mature" argument. For example, it took five years for documentation on `` to arrive [2]. This is something I'd expect from the side project of a lone programmer, not an enterprise-level framework.

The only upsides of Angular are its "batteries included" approach and the (debatable) default of RXJS, while the downsides are plenty.

[1] https://github.com/vuejs/vue/tree/218557cdec830a629252f4a9e2...

It's down since months. https://github.com/vuejs/vue/issues/11867

{ "user": "vuejs", "repo": "vue", "url": "https://github.com/vuejs/vue", "stars": 201555, "description": "🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.", "topics": [ "javascript", "framework", "vue", "frontend" ], "label": "repository", "commitCount": 3544 }

Vue.js is a progressive open-source MVVM frontend JavaScript framework that is designed to be implemented incrementally since the core library focuses only on the presentation layer. Nevertheless, this framework is used for building UI (user interfaces) and complex single-page applications with modern tools and libraries to support them. It enables you to take advantage of libraries for client-side routing and state management when you need it.