Skip to main content

Vue and React experiences

Recently I have been doing a cross-platform mobile app with React native and also a web app frontend with Vue.js. As a reluctant java bull, building front-ends with something different than Java has been indeed something I have been looking for for a while.

The React native mobile app is something I'm developing solo and is for a customer in importing tools for machine workshops business. It is a pretty straightforward shopping catalog-like app with a focus for customizable catalogs for each customer. I have found it to be pretty much perfect for a first project, the domain is simple and there are plenty of ready-made stuff and example applications where to look for inspiration

On the project where Vue is being used, the old technology was Angular, versions 1 and 4. There was a decision to use Vue for the new front-end components and I was fortunate enough to be in the team making the first one and participate in building a template project that would be used by all new front-ends.

There are numerous comparisons between Vue and React, here is another very opinionated one

JSX vs Vue components
We are writing the Vue templates with plain old HTML. The reasoning behind this that there would not be too many new things to learn when starting this new thing. There were some attempts to use Pug but that was not seen to be something we should continue.
Granted, 90% of my React experience has been with React native so I have not written very little web app templates with it but somehow I like the Vue experience here a bit better although personally, I would like to have continued using Pug

Unit testing
We have written the Vue tests with Jest using the vue-test-utils library. It has been ok, but there have been some issues with when to use the $nextTick, when to wait for promises to see all changes happen. Updating to version 1.0.0-beta.13 has helped here since it makes the watchers synchronous by default but yet there have still been some hard to debug problems related to when to wait for next tick.  Here React (native) wins since the testing is a bit more "in-built" to Jest itself so there are more examples and my gut feeling is that testing similar use cases would result in less code with React native

Flux implementation
Similar, but instead of using immutable reducers Vuex is using mutators so the state is a global object which mutates. Supposed to be a performance improvement. I don't have too strong an opinion here, I think both are just fine.

Guidelines / how-tos
The hard thing is to figure out what is the so-called right thing to do at a given time to use the framework. As the team was (and still is) inexperienced with Vue, we certainly struggled to figure out the most elegant way or the Vue way to solve problems. We have our template project based on a community made template and the development has been reasonable and even when the project has grown a tad larger, the structure itself has not slowed us down.

Overall, there are more examples and open-source components on the React camp but Vue also has plenty of choices on almost anything you would need in a typical web app. One interesting question is that when the app becomes more complex, which will handle it better? In other words, which has better performance, style guides, and examples how to handle a larger code-base.

Labels:

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

RocksDB data recovery

I recently needed to do some maintenance on a RocksDB key-value store. The task was simple enough, just delete some keys as the db served as a cache and did not contain any permanent data. I used the RocksDB cli administration tool ldb to erase the keys. After running a key scan with it, I got this error Failed: Corruption: Snappy not supported or corrupted Snappy compressed block contents So a damaged database. Fortunately, there's a tool to fix it, and after running it, I had access to the db via the admin tool. All the data was lost though. Adding and removing keys worked fine but all the old keys were gone. It turned out that the corrupted data was all the data there was. The recovery tool made a backup folder, and I recovered the data by taking the files from the backup folder and manually changing the CURRENT file to point to the old MANIFEST file which is apparently how RocksDB knows which sst (table) files to use. I could not access the data with the admin tool, ...
Post a Comment
Read more

Making dashboards more usable for LLMs

I’ve been looking into agentic workflows to act as an operations assistant for the SaaS I'm working on. A big part of that work is getting the assistant to make sense of all the alert and monitoring data that pours in every day. Passing a bunch of raw time-series data to an LLM generally doesn’t work that well. You need to tell the LLM to aggregate the data and give it the means to do so. Using aggregates will often lead to better insights from the LLM. This is a well-known fact to anyone who has tinkered with this (at least at the time of writing this). Humans, of course, like to build visualizations and dashboards to solve this issue (yes, yes, dashboards are often useless, but complaining about that is another blog post). LLMs can analyze them as well and in fact are pretty good at that, so the aggregate can be something both humans and LLMs can digest. I’ve been tinkering with the idea of appending some LLM-only content to a dashboard—for example, additional context, specific d...
Post a Comment
Read more