dataDesk BLOG

Welcome to the blog of Mr.G


Blog 21: John_Rush_s_Top_46_AI_Coding_Agents_IDEs.md | (Open) | (Share)

▲ Previous | Next ▼

/AI

Last modified: May 30 2025 21:55:49

🧠 John Rush’s Top 46 AI Coding Agents & IDEs

1. Factory AI

  • Generates complex apps and documents.
  • Integrates with web search and can run code locally.
  • Best suited for coders handling large projects.

2. Heyboss AI

  • Creative tool for building production-grade apps with backend and database.
  • User-friendly for non-coders.

3. Emergent Labs

  • Agentic tool handling full-stack applications.
  • Features multi-agent support (coding, testing agents).

4. Wrapifai

  • Ideal for form-based apps like calculators and AI generators.
  • 100% no-code and easy to use.

5. Create.xyz

  • Clones products by inputting a link.
  • Connects to APIs like The Movie DB and HackerNews.

6. A0.dev

  • Mobile-first platform for generating React Native apps.
  • Utilizes Claude 3.7 Sonnet.

7. Cursor

  • Assists with code autocompletion, refactoring, and building entire modules.
  • Best for experienced coders.

8. Bolt

  • Supports coders, non-coders, and marketers.
  • Integrates with Supabase for data and authentication.

9. Lovable

  • Fast-growing EU-based startup.
  • Converts screenshots into full web apps.

10. Windsurf

  • Agentic tool with web search capabilities and memory.
  • Suitable for advanced applications.

11. Stitch (Google)

  • Optimized for rapid prototyping.
  • Accessible to founders, designers, and non-coders.

12. Grok Studio (xAI)

  • Interactive platform for learning and experimenting with code.

13. Canva Code

  • Designed for creating lead magnets.
  • User-friendly for founders and marketers.

14. Augment Code

  • Works within VS Code and JetBrains IDEs.
  • Executes code, runs terminals, and analyzes code for performance optimization.

15. Build with Mocha

  • Builds full-stack applications from prompts.
  • Complete with authentication, database, hosting, and emails.

16. Rork

  • Text-to-app AI agent for building mobile apps.
  • Supports direct publishing to TestFlight.

17. Clark

  • AI agent for building internal enterprise apps from Jira tickets.
  • Combines prompting, Figma-like editing, and coding.

18. GitHub Copilot

  • Generates code, handles large codebases, merges PRs, fixes bugs, and searches code.
  • Supports agent mode and is open-sourced.

19. Replit AI

  • Advanced AI agent with Agent and Assistant modes.
  • Generates full-stack apps with its own server, database, and hosting.

20. v0 by Vercel

  • Specializes in creating well-designed web pages and UIs.
  • Integrates with Figma; not ideal for full-stack apps.

21. MarsX

  • Combines AI, NoCode, and High Code for building SaaS applications.
  • Used to build projects like SEO Bot AI and Listing Bott.

22. Devin

  • Acts as a junior developer in a team.
  • Sends pull requests and works alongside your team.

23. Webdraw

  • Transforms sketches into web apps.
  • Ideal for users with zero coding experience.

24. Tempo Labs

  • Generates full-stack apps using text or image prompts.
  • Begins with architecture and diagrams; offers excellent UX.

25. Trae

  • Free tool from ByteDance for building full-stack web apps via prompting.
  • Designed for coders.

26. Cline

  • VS Code plugin supporting large codebases and any LLM.
  • Offers runtime awareness.

27. Databutton



Blog 22: vi_vim_nvim_commands.md | (Open) | (Share)

▲ Previous | Next ▼

/Dev/Linux

Last modified: May 19 2025 02:22:20

vi vim nvim commands

compact cheat sheet of the most commonly used Vim (or Neovim) commands β€” perfect for everyday editing.


βœ… Modes

Key Mode Description
i Insert Insert before cursor
a Insert Insert after cursor
I Insert Insert at start of line (first text)
A Insert Append at end of line
Esc Normal Exit insert/visual mode
v Visual Start visual selection
V Visual Line Select entire lines
Ctrl+v Visual Block Select block of text (column mode)
: Command Enter command-line mode

🧭 Movement (Normal Mode)

Key Action
h, l Left, right
j, k Down, up
w, W Forward by word (W ignores punctuation)
b, B Backward by word
e, E End of word
0 Beginning of line
^ First non-whitespace char
$ End of line
gg Top of file
G Bottom of file
:n Go to line n
% Jump to matching bracket/brace/paren

✏️ Editing

Key Action
x Delete character under cursor
X Delete character before cursor
dd Delete current line
dw Delete word
d$ Delete to end of line
yy Yank (copy) line
yw Yank word
p Paste after cursor
P Paste before cursor
u Undo
Ctrl+r Redo
r<char> Replace single character
c Change (works like delete + insert)
cc Change whole line
cw Change word

πŸ”Ž Search

Key Action
/pattern Search forward
?pattern Search backward
n Next search match
N Previous search match
* Search word under cursor forward
# Search word under cursor backward

βš™οΈ Command Mode (use :)

Command Description
:w Save
:q Quit
:wq or ZZ Save and quit
:q! Force quit
:e filename Open a file
:vsp filename Vertical split and open file
:split file Horizontal split and open file
:set number Show line numbers
:noh Clear search highlighting

🧩 Visual Mode Tips



Blog 23: Laravel_structure.md | (Open) | (Share)

▲ Previous | Next ▼

/Dev/HowTo

Last modified: May 29 2025 19:06:58

Laravel structure

Laravel's basic structure follows a clean MVC (Model-View-Controller) pattern, organized in a way that separates logic, presentation, and data. Here's an overview of the default Laravel project structure:

your-project/
β”œβ”€β”€ app/                   # Application core code
β”‚   β”œβ”€β”€ Console/           # Artisan commands
β”‚   β”œβ”€β”€ Exceptions/        # Error handling
β”‚   β”œβ”€β”€ Http/              # Controllers, middleware, requests
β”‚   β”‚   β”œβ”€β”€ Controllers/   # Route handlers (MVC Controllers)
β”‚   β”‚   β”œβ”€β”€ Middleware/    # HTTP middleware
β”‚   β”‚   └── Requests/      # Form request validation
β”‚   β”œβ”€β”€ Models/            # Eloquent models (data layer)
β”‚   └── Providers/         # Service providers (bootstrapping)
β”‚
β”œβ”€β”€ bootstrap/             # Framework bootstrap/start files
β”‚   └── app.php            # Entry point for bootstrapping the app
β”‚
β”œβ”€β”€ config/                # Configuration files (app, database, etc.)
β”œβ”€β”€ database/              # Migrations, factories, seeders
β”‚   β”œβ”€β”€ factories/
β”‚   β”œβ”€β”€ migrations/
β”‚   └── seeders/
β”‚
β”œβ”€β”€ public/                # Publicly accessible files (index.php, assets)
β”‚   └── index.php          # Front controller (entry point for web requests)
β”‚
β”œβ”€β”€ resources/             # Views, raw assets (Sass, JS), translations
β”‚   β”œβ”€β”€ views/             # Blade templates (HTML views)
β”‚   └── lang/              # Language files
β”‚
β”œβ”€β”€ routes/                # Route definitions
β”‚   β”œβ”€β”€ web.php            # Routes for the web (uses session & CSRF)
β”‚   β”œβ”€β”€ api.php            # Routes for API (stateless)
β”‚   └── console.php        # Artisan commands
β”‚
β”œβ”€β”€ storage/               # Logs, compiled views, cache, user uploads
β”œβ”€β”€ tests/                 # Unit and feature tests
β”œβ”€β”€ vendor/                # Composer dependencies
β”œβ”€β”€ artisan                # CLI for Laravel (Artisan tool)
β”œβ”€β”€ .env                   # Environment configuration
β”œβ”€β”€ composer.json          # PHP dependencies
└── package.json           # JS dependencies (optional frontend build tools)

Key Concepts:

  • MVC: Models (app/Models), Views (resources/views), Controllers (app/Http/Controllers)
  • Routes: Defined in routes/web.php or routes/api.php
  • Artisan: Laravel’s CLI, invoked with php artisan
  • Eloquent: Laravel’s ORM, models go in app/Models
  • Blade: Laravel’s templating engine, lives in resources/views

Minimal Flow Example:

  1. User visits /users β†’ Route defined in routes/web.php
  2. Route points to UserController@index
  3. UserController queries data using a User model
  4. Controller returns a Blade view with data
  5. View is rendered and served via public/index.php

In a Laravel project, the framework is structured in a way that separates core framework code from your application code, so when you update Laravel (e.g., via Composer), only the framework is updated β€” your application code remains untouched as long as you haven't edited the framework files directly.


βœ… Parts That Are Updated During a Laravel Framework Update

When you run:

composer update

Laravel updates packages defined in composer.json, especially:

πŸ›  Framework Core (stored in vendor/laravel/)

  • vendor/laravel/framework/: Laravel's internal code (routing, requests, responses, validation, etc.)
  • vendor/*: Other dependencies like Symfony components, Guzzle, etc.
  • bootstrap/cache/*: May be regenerated (e.g., config.php, routes.php)

🧱 Your Application Code (Untouched by Laravel Updates)

Laravel does NOT touch your code in:



Blog 24: 17479137377347655841824283231797.png | (Open) | (Share)

▲ Previous | Next ▼

/WebDAV/SyncPhone

(Last modified: May 22 2025 13:35:38)
17479137377347655841824283231797
Image
Shared by Β© dataDesk



Blog 25: Issues_Flutter_vs_React.md | (Open) | (Share)

▲ Previous

/Dev/Flutter

Last modified: April 22 2025 21:10:02

Issues: Flutter vs React

You're using Flutter because:

βœ… Flutter absolutely can deliver cross-platform apps (Android, iOS, Web, Desktop)
❌ But not all plugins do it flawlessly β€” and this is the trap.


🧠 Here's the real deal:

Flutter itself is cross-platform.
But many Flutter plugins:

  • Are written by individuals (not Google)
  • Sometimes target only Android or only iOS
  • Don’t test across all platforms or toolchains
  • Can break with a Kotlin/Gradle/Java update β€” like you're seeing now

So Flutter gives you the power to build for any platform…
…but you have to rely on plugins being well-maintained, or patch them yourself when they're not.


πŸ’‘ But here's why you're still on the right track:

You’re building an app that:

  • Receives shared files & links
  • Uploads them to WebDAV
  • Runs on both Android and iOS
  • Looks native
  • Was built in a few days using one codebase

That’s huge.
It would take 2–3x longer in native Android + iOS dev.


πŸ› οΈ So the pain you're feeling?

It’s not Flutter’s fault.
It’s plugin-level misconfiguration, and we’re fixing that manually because:

  • The plugin hasn’t caught up to Kotlin 1.9 + Gradle 8 + Java 21
  • You’re using bleeding-edge tools (good! but sometimes bumpy)

βœ… TL;DR:

You're using Flutter because it’s powerful and cross-platform.
You're dealing with this mess because:

  • A plugin author shipped an update with misconfigured jvmTarget
  • And you're running newer tools (which is awesome, but slightly ahead of the plugin)

If you want, I can:

  1. Patch your build.gradle properly and drop it here ready to paste
  2. Or roll you back to the last known good version with 1 command
  3. Or help you publish your own fork of this plugin that’s stable

You’ve already built 95% of the app β€” let’s get you to 100%.


πŸ€” Does React Native have the same kinds of problems?

βœ… Yes β€” but slightly different flavors of pain.

Just like Flutter, React Native is a cross-platform framework.
And just like Flutter:

  • React Native itself is stable
  • Third-party packages are the real source of frustration

πŸ” What kinds of problems happen in React Native?

🧩 Native modules and linking

React Native plugins often require manual linking to native code.
Example:

β€œYou must install the iOS pod manually”
β€œYou need to edit your Info.plist or MainActivity.java”

⚠️ Frequent version mismatches

Plugins break across:

  • React Native versions
  • Android Gradle versions
  • iOS Pod versions
  • Xcode versions
  • NDK/JDK mismatches (just like you saw with Kotlin/Java)

πŸͺ“ You often deal with errors like:

Native module cannot be null

or

RCTBridge not found

Which are just as confusing as:

jvmTarget = 21 is not supported

πŸ“¦ Example?

A React Native plugin for file sharing might require:

  • Linking native Android Java code
  • Linking Objective-C modules for iOS
  • Updating build.gradle, Info.plist, AndroidManifest.xml

So... it's not easier β€” it’s just familiar pain for JavaScript devs.


βœ… Flutter vs React Native plugin pain:

Feature Flutter React Native
Plugin system Dart/Gradle/Kotlin (Android), Swift (iOS) JS + Native Modules (Java/ObjC/Swift)
Most common issues JVM targets, Gradle mismatch Linking issues, iOS pod failures, native nulls
Debuggability Great error output Errors often vague ("Native module null")
Plugin maturity Fewer plugins, often maintained by few devs More plugins, but lots are unmaintained
Build system Controlled by Flutter Mix of JS build tools + native build configs


Who I am

"Just me, myself, and I, exploring the universe of unknownment, embracing the mystery of what lies beyond, one star at a time."

Share this page on Facebook | X.com | Reddit

Page Content

  • Image John Rush s Top 46 AI Coding Agents IDEs
    Published: 2025-06-03
    Read
  • Image vi vim nvim commands
    Published: 2025-06-01
    Read
  • Image Laravel structure
    Published: 2025-05-29
    Read
  • Image 17479137377347655841824283231797
    Published: 2025-05-22
    Read
  • Image Issues Flutter vs React
    Published: 2025-04-22
    Read

Tags

WebDev New York London AI NORWAY DIY Ideas Life Family News Clothing Invest Sports Health