Sadie  Cassin

Sadie Cassin

1622082498

Announcing Vendure v1.0

Vendure is an open-source e-commerce framework built on Node.js, TypeScript & GraphQL. After three years of development, we are incredibly excited and proud to announce the first stable release!

Why Vendure?

Just over three years ago, I found myself researching the e-commerce ecosystem. My family runs a successful art materials retailer with a website I had built from scratch well over a decade ago, having taught myself PHP and MySQL from one of those 5-inch-thick books that come with a CD-ROM in the back cover. Foolish? Perhaps! Back then there were few alternatives anyway.

But the time had come to find a better solution. In the intervening years, the choice of e-commerce frameworks has improved in both number and quality. We have the established, mature players like Magento, WooCommerce, Spree Commerce & Shopware as well as newer challengers list Sylius & Saleor. All worthy solutions - but here’s what was missing:

  • TypeScript / Node.js
  • The majority of solutions are PHP-based. There was very little out there for the huge community of JavaScript/TypeScript/Node.js developers. A massive pool of expertise untapped.
  • Headless
  • “Headless” means “API-driven”. I had spent the prior three years working on a headless CMS project, and I was sold on the benefits of this architecture.
  • Great developer experience
  • Hours were spent attempting to set up a dev environment to test out these frameworks. I wanted something simple to set up, and simple to extend. I don’t want to dig through layers of config and abstractions in order to add a new attribute to my product model.

So once again, I foolishly decided to build my own.

#vendure #node #typescript #graphql

What is GEEK

Buddha Community

Announcing Vendure v1.0
Sadie  Cassin

Sadie Cassin

1622082498

Announcing Vendure v1.0

Vendure is an open-source e-commerce framework built on Node.js, TypeScript & GraphQL. After three years of development, we are incredibly excited and proud to announce the first stable release!

Why Vendure?

Just over three years ago, I found myself researching the e-commerce ecosystem. My family runs a successful art materials retailer with a website I had built from scratch well over a decade ago, having taught myself PHP and MySQL from one of those 5-inch-thick books that come with a CD-ROM in the back cover. Foolish? Perhaps! Back then there were few alternatives anyway.

But the time had come to find a better solution. In the intervening years, the choice of e-commerce frameworks has improved in both number and quality. We have the established, mature players like Magento, WooCommerce, Spree Commerce & Shopware as well as newer challengers list Sylius & Saleor. All worthy solutions - but here’s what was missing:

  • TypeScript / Node.js
  • The majority of solutions are PHP-based. There was very little out there for the huge community of JavaScript/TypeScript/Node.js developers. A massive pool of expertise untapped.
  • Headless
  • “Headless” means “API-driven”. I had spent the prior three years working on a headless CMS project, and I was sold on the benefits of this architecture.
  • Great developer experience
  • Hours were spent attempting to set up a dev environment to test out these frameworks. I wanted something simple to set up, and simple to extend. I don’t want to dig through layers of config and abstractions in order to add a new attribute to my product model.

So once again, I foolishly decided to build my own.

#vendure #node #typescript #graphql

Eric  Bukenya

Eric Bukenya

1620906720

C# Coding Guidelines And Best Practices v1.0

This document describes the rule and recommendations for developing software application and class libraries in .NET using C## as a language. The main purpose is to define the general guidelines to enforce consistent coding styles and formatting that can be useful for developers to avoid common mistakes they do while development of software applications using C#. This document covers naming conventions, coding styles and some architecture level suggestions.

Purpose of coding standard and best practices to do it

Coding standards are a set of guidelines used for programming language that recommends programming style and best practices to achieve it.

The coding standards generally covers indentation, comments, naming conventions, programming practices, file structure within project, architectural best practices etc. Software developers are highly recommended to follow these guidelines. The coding guidelines have following advantages.

  • Increases the readability of source code written.
  • Will contain fewer bugs and work more efficiently.
  • Requires less maintenance.
  • Easier for old and new developers to maintain and modify the code.
  • Leads to increase in productivity of developers.
  • Reduces the overall cost for software development.
  • Make the difference between a successful project and a project that is, at worst, dead on delivery.

#c# #v1.0

Uriah  Dietrich

Uriah Dietrich

1617812820

Google Announces TensorFlow Quantum 0.5.0: Expected Features & Updates

Google is celebrating the first anniversary of TensorFlow Quantum (TFQ), a library for rapid prototyping of hybrid quantum-classical ML models. TFQ is regarded as a tipping point for developments in hybrid quantum and classic machine learning models the company has been pushing for years.

#developers corner #google tensorflow quantum #tensorflow quantum #tensorflow quantum 0.5.0

What is Industry 4.0?Latest Trends, Technologies & Examples

https://www.mobinius.com/blogs/what-is-industry-4-0-trends-technologies-examples

#industrial revolution 4.0 #digital transformation companies #industry 4.0 services #industry 4. 0 technologies #internet of things #iot applications

Aketch  Rachel

Aketch Rachel

1621014600

.NET 5.0 and C# 9.0 for Xamarin Developers

NET 5 has finally arrived and is one of the biggest releases on the history of .NET platform!

As the first phase on the unified view that Microsoft unveiled last year, we finally have a single platform for our entire application stack.

But what does this means for Xamarin developers?

Last may Microsoft announced .NET Multi-platform App UI (or MAUI for short); the future of Xamarin and Xamarin.Forms that makes Xamarin a first-class member of .NET. But, as this is such a big a change that it would not be able to be ready in time for .NET 5.0, so its postponed to version 6.0, expected to be released next year.

While we wait for MAUI and .NET 6.0, we have Xamarin.Forms 5.0 to look forward to in the immediate future. Including brushes/shapes support, swipe view, drag+drop, templating and much more!

The .NET team is also focusing its unification effort by bringing most of the .NET Core BCL implementation to Mono. This is exciting as we can take advantage of the optimizations in .NET 5 in the most recent versions of Xamarin.Android and Xamarin.iOS. This source code unification should be ready by .NET 6, when they will be named .NET for iOS and .NET for Android (and the Xamarin brand will be dropped 😬).

Well, for now I’ve talked about the invisible part, but there’s an important last piece that we can start using right now: C## 9.0! 🎉

C## 9.0

The latest installment of the language is not automatically enabled for Xamarin projects, but James Montemagno has done a great post explaining how to enable it while explaining the rationals behind language selection and availability.

But what’s good about C## 9.0? Well, there are lots of new features, some postponed from previous versions and finally made available. One of these new features is Record Types. This is a language construct that allows us to declare data objects that can easily be made immutable, like:

The example above declares a FeedEntry class that represent a blog post on a site feed. Notice the use of the init in place of set. This ensures that the property can only be set once on object creation. Records declaration also have a simplified syntax:

public record EntryAuthor(string Name, string Email);

This will declare an EntryAuthor record with the properties Name and Email. Then when creating new instances we can using the Target-typed new expressions:

Some developers prefers to have type annotation before the variable itself but like the conciseness of the var declarations. This new syntax allows for both and can also be used to initialize class fields and properties:

Last, but not least, suppose we need to set the published date on the instance we have created? Immutability is a concept from Functional Programming where we never mutate values on a object, but create copies with new values and we’re covered here:

Our initial record hadn’t declared the Summary property. By using the with expression on the previous record we could create a new instance with all the existing values and adding the summary.

#.net 5.0 #c# 9.0 #xamarin