sdk VS TypeScript

Some issues that don't make the @protected annotation as useful as it could be are that @protected elements are not hidden the in tab completion outside their scope and protected is not being inherited (and can thus be called from outside the library on those subclasses).

If you're willing to pick up another language, I actually think Dart is the best overall programming language for young beginners. It's very streamlined and well thought-out. It doesn't have all of the complexities of languages like C# and Java, but it still has everything you'd want for application development.

Google's Flutter UI framework and Dart programming language are the best way to do desktop development right now. It supports desktop app development for Windows, MacOS, and Linux. You can also compile the same app for mobile on Android and iOS.

Flutter is a mobile app development framework based on the Dart programming language, developed by Google. One can develop Android apps, iOS apps, web apps, and desktop apps using the same code with the Flutter Framework. Flutter has a large community, which is why it is the fastest-growing app development framework ever.

Dart isn't showing up yet? I thought C# would be bigger.

Flutter arrived in 2017 as a Google project promising scalable cross-platform mobile development. It offers a batteries-included approach and comes with a comprehensive set of Material UI-themed components for building your interface. It uses declarative rendering, like React Native, but relies on the Dart programming language instead of JavaScript.

Dart is a client-optimized language for fast apps on any platform.

You are likely hitting some variation of https://github.com/dart-lang/sdk/issues/51226 or https://github.com/dart-lang/sdk/issues/50082.

Hehe, someone already proposed optional chaining on unknown, and it was rejected. https://github.com/microsoft/TypeScript/issues/37700

In this article, an application will be created using the Node.js with TypeScript and Express.js where a serverless API will be implemented and deployed on the AWS Lambda service.

Finally, a big reason is TypeScript trips up on unbound generics for an arrow function - it thinks it's a JSX tag. It does not have the same issue with named functions.

ECMAScript/JavaScript import modules by import/dependency specifiers and every plattform I know will convert the dependency specifier to some path or an url it can fetch. If the direct location cannot easily be defined, must the platform perform some kind of traversal (visit many files before it "knowns"). This process is slow, but remarkable slow if it is done over a network. This can be fixed if the developer provide more specific dependency specifiers, for example adding the file-extension. But there is a problem: TypeScript do not support if you add the .ts extension. It does not rename dependency specifiers. Its extremely weird actually:

Except that we have a full page of API breaks and new errors about options that are going away shortly.

"bundler" is definitely not going to be the right resolution mode for using Deno; you may be better served by using ESNext or Node16/NodeNext. The "who should use this mode" section here I believe is still accurate: https://github.com/microsoft/TypeScript/pull/51669

From the PR (https://github.com/microsoft/TypeScript/pull/51669):

> New compiler options

> - allowImportingTsExtensions: Allow imports to include TypeScript file extensions. Requires '--moduleResolution bundler' and either '--noEmit' or '--emitDeclarationOnly' to be set.

To be clear, I'm not using tsc to build code for Deno. I've got module X which imports module Y, neither of which have any platform-specific dependencies. Right now if module X imports Y with the .ts extension, Deno can import X but tsc can't. If module X imports Y without the .ts extension, tsc can import X but Deno can't. With this compiler option, I should be able to include the .ts extension and allow both to (independently) import the same code