Ravi S. Iyer: Software Development

Note: This post is in-progress. However, as the extension is available, I thought of publishing the in-progress post having the extension repo link and some other details. Quick-Info The VSCode Extension repo:  https://github.com/ravisiyer/html-auto-header-ids  . Its Readme explains how to use it. Details Blogger does not have a way to support automatically adding an id attribute to section headers in a post. An id attribute enables the section header to be used as the target of a 'jump link,' which can be used to create internal links within a Contents section of the post, or even as a link from an external webpage. ... ****To be updated**** Background Info including AI chat extracts Creating internal links in Blogger blog posts involves switching from Compose to HTML view, searching for the required section's HTML and adding an id to its HTML element. This is the part that is quite time consuming. Creating a link to such an internal lin...

Recently Blogger has changed its blog backup procedure such that the XML files that would get created by default when we chose backup, is now part of a Google Takeout which has default of .atom for the blog content files.  Later I checked again that the Google Takeout options shown for Blogger backup do not seem to provide an option to limit the backup to one blog and to exclude media from it. Specifically, I tried clicking on 'Multiple formats' button in the Google Takeout page. That opens up a 'Blogger formats' modal but which shows dropdowns for Blog feed, photos etc. but which only show current value and do not allow it to be changed. Next I tried going directly to https://takeout.google.com/ . In 'Select data to include', I deselected all and then chose only Blogger. It now was the same like above. It had the same 'Multiple formats' button which behaved the same way as above. So, as far as I could make out, even Google Takeout does not allow me to ...

Last updated on 3 Sep. 2025 Now I have completed code-along for over half of a tutorial on a cross-platform (mobile and web) Edu app using React Native and Expo for web: (YT video) Simon Grimm: Build Your Own MASTERCLASS clone in React Native , 4 hrs. 42 mins, Mar. 2025. My blog post with notes for that tutorial . In the process, I am now getting more comfortable with using React Native and Expo for Web as a cross-platform mobile and web (Android/iOS/Web) solution for small to medium sized apps. Note that in such a tech stack approach, there will be some amount of platform-specific (Android/iOS/Web) code but large part of the code will be shared across platforms and all the code will be in one project. But a question popped up in my mind: Progressive Web App (PWA) using React also claims to provide a mobile and web app solution. PWA React app seems to be easier to do than React Native and Expo for Web for such cross platform apps. While I knew that React Native app on mobile would ...

Last updated on 2 Sep. 2025 Sections in post 1. Advantages of MPA (ASP.NET MVC/Razor, PHP, Django, Rails, etc.) over SPA 2. MPA, SPA, Hybrid (SSR/SSG + SPA) - Trends in Popularity (2025) 3. React does not support pure MPA; JS Ecosystem Options for Pure MPA Not Mainstream 4. Mature MPA stacks are Tied to non-JS Languages (C#/VB.NET, PHP, Ruby, Java, Python) 5. Next.js + React + React Native Preferred Today for Small–Medium apps 6. Classic MPA stacks (ASP.NET, PHP, Rails) - Limited/No Migration Path to Mobile Front-Ends 7. Origins and Timeline of ASP.NET, PHP, Rails, React/Next.js and React Native stacks 8. ASP.NET (classic, pre-Core) vs ASP.NET Core (2016 → now default ASP.NET) 9. Timeline of Popular Web Frameworks [Note: As of now, I felt that I may not need the section summaries much in this post and so have not done that.] ========================================================= ========================================================= Details Copy-paste followed by editing of part ...