r/dartlang

Hi, i am someone who knows programming fundamentals and object oriented programming basics from learning the java language. But now i am trying to learn dart and i have been having alot of trouble understanding it's concepts. I started reading the dart tutorial documentation on it's official dart.dev website and i am stuck on this page

https://dart.dev/learn/tutorial/object-oriented

for almost 2 days now i do understand what they are making but i don't not understand how they are doing it even after reading the doc i have no clue what's going on.

I am starting to question myself if i am miss some prerequisites or i do not have the programming skills to understand this yet.

Could anyone tell me if i should just drop the tutorial and learn from other source or what should i do.

Thank you

There's a polished SDK for talking to LLMs on the web (the Vercel AI SDK). On the Dart/Flutter side there was nothing equivalent — everyone re-wires the same plumbing (request shaping, SSE streaming, tool-call round-trips, multi-provider) by hand.

So I built llm_sdk: one interface, three brains behind it.

• 🔁 Multi-provider — Claude, OpenAI, Gemini. Swapping is literally one line.
• ⌨️ Streaming — streamText gives you a Stream<String>, word by word.
• 🛠️ Tool calling — declare a Tool, the SDK orchestrates the whole loop.
• 📋 Structured outputs — generateObject<T> fills a typed Dart object.

The whole design rests on a 2-method provider contract; all the logic (tool loop, streaming, structured outputs) lives once in the client. Adding a provider is pure dialect translation.

Pure Dart package (no Flutter dependency), MIT, fully tested (mocked request/response + SSE).

pub.dev: https://pub.dev/packages/llm_sdk GitHub: https://github.com/Geekles007/llm_sdk

Feedback very welcome — especially on the API ergonomics and which provider you'd want next (Mistral? Ollama? local?).

I’ve been working on dart_agent_core, a Dart package for running AI agents directly inside Flutter apps, without needing a Python or Node backend for the agent loop. The latest update adds a unified AgentHook pipeline plus observation-only AgentController events. This is useful if you are building agent loops or runtime/eval harnesses. Instead of only sending a prompt and waiting for a final answer, you can now intercept the loop as it runs:

• Use beforeModelCall to inject temporary context, change tools, adjust model config, or return a synthetic model response.
• Use afterModelCall to validate a response, retry, or replace the final model message.
• Use beforeToolCall to approve, deny, defer, or rewrite tool calls.
• Use afterToolCall to normalize tool results, inject follow-up context, or stop the loop.
• Use onTurnCompletion to continue the loop when the model stops too early.
• Use persistence hooks to decide when state should be saved.
• Use AgentController events for tracing, debugging, evals, and Flutter UI updates.

Pub.dev Github

This is one of the biggest ApolloVM releases so far, bringing two new languages, major WebAssembly advancements, and substantial runtime improvements.

https://pub.dev/packages/apollovm

🆕 Kotlin Support

ApolloVM now supports Kotlin parsing, execution, and translation, reaching feature parity with Java support.

• ✅ Parse Kotlin source
• ✅ Execute Kotlin code inside ApolloVM
• ✅ Translate Kotlin ↔ Dart ↔ Java
• ✅ Shared AST architecture with no AST changes required

Supported features include functions, classes, type inference, collections, control flow, and string templates.

🆕 Modern JavaScript Support

JavaScript is now a first-class ApolloVM language.

• ✅ Parse, execute, and translate JavaScript
• ✅ Classes, constructors, fields, methods
• ✅ let / const / var
• ✅ for, for...of, while
• ✅ Template literals
• ✅ Arrow functions
• ✅ Strict equality (===, !==)

JavaScript can now be translated to Dart and Java, and Dart/Java code can be translated back to JavaScript through the shared AST.

🌐 Massive WebAssembly Progress

Building on the work introduced in 0.1.27, ApolloVM now provides extensive Wasm generation support:

• ✅ Lists and Maps
• ✅ String handling and interpolation
• ✅ Loops and recursion
• ✅ Function calls
• ✅ Dynamic memory growth
• ✅ Map iteration (.keys / .values)
• ✅ Map parameters and return values
• ✅ Compound collection assignments (m[k] += 1)
• ✅ Browser validation on Chrome

The Wasm backend is rapidly moving toward full Dart feature parity.

⚡ Runtime Improvements

• Dynamic arithmetic now works correctly across all supported languages • for-each / for...of loops now operate on any iterable • JavaScript division follows JavaScript semantics (7 / 2 = 3.5) • Improved code generation correctness • Fixed CLI translation output issues

🧪 Quality & Testing

This release adds extensive coverage for Kotlin, JavaScript, WebAssembly, runtime behavior, translation round-trips, and cross-language execution.

ApolloVM now supports:

• 🔹 Dart
• 🔹 Java
• 🔹 Kotlin
• 🔹 JavaScript
• 🔹 WebAssembly (compilation/generation)

All powered by a single shared AST and runtime infrastructure.

GitHub: ApolloVM/apollovm_dart

The long-term goal remains unchanged: write once, parse anywhere, execute anywhere, translate anywhere.

#ApolloVM #DartLang #Java #Kotlin #JavaScript #WebAssembly #Wasm #Programming #OpenSource

Shipped mssql — a pure Dart TDS 7.4 driver for SQL Server. No FFI, no native extensions, just Dart and TCP.

Features: named params, connection pool, TLS, Azure AD auth, multiple result sets, streaming, transactions. 366 tests including concurrent pool stress tests and adversarial comparison against go-mssqldb and node-mssql.

dart pub add mssql

It works as a standalone driver today. The next step is switching knex_dart_mssql to use it as the underlying transport — which drops the C FFI dependency and makes the knex_dart MSSQL driver work on web.

github.com/kartikey321/mssql-dart | pub.dev/packages/mssql