Saumya

I generally prefer to stay on the stable versions of Linux and keep on doing the work on the same system. Tried Ubuntu and got used to it. Never bothered to install a second distro for work. The configurations to Ubuntu also as per my work requirements. This whole disro-hop thing is never my thing. Though on side, I use to see what is happening in that space. Configuring or ricing as it is said now, is also seems too much for me.

Seems like a known bug. Upgrade from 22.04 LTS to 24.04 LTS and the connection to internet is broken In my case, I upgraded to 24.04.1. The bug still is there. The fix I do is from this place. I have to do it almost every time I open the OS. sudo rm /etc/resolv.conf sudo dhcpcd Now as mentioned in the post internet is back but the icon on the taskbar is still broken.

The latest LTS release of Ubuntu, 24.04 is having a very unstable installer. I could install it from the installer in some machines without any problem. However, the installer simply is a UI only update. On the UX side it fails completely. Seems there is no error handling done. On simplest of things, the installer just shuts down. On one of my laptops, I find it is very difficult to go forword with installation.

React Native still is and better than ever the toolchain for crossplatform application development. As usual the new version React Native toolchain keeps on changing. The documentation of the toolchain also keeps on changing(they call it evolving, not me). Starting a new project is now done as this npx @react-native-community/cli init MyNewReactNativeApp For a particular version of React Native, the command is like this. npx @react-native-community/cli init MyApp --version "0.75" This is basically using the community cli

In package.json there is a script section. From here one can run NPM Scripts. "scripts": { "one": "scriptOne.js", "two": "scriptTwo.js" } These can be run like this. npm run one This particular line will run scriptOne.js. This is powerful as we could take Node’s power and run any automated task for ourselves. At first this seemed simple to me. Soon I came across cross-platform bugs. Since we are writing this in JS, it could be run anywhere Node is available.