GooieJS VS ASP.NET Core

There have been a couple posts discussing PWA's. This Github Repository has every file you need to make your own Progressive Web App. Simply clone the repo (or download zip) and replace the in index.html with your own.

Problem: Anyone should be able to easily make and host a website. Solution: When you're finished coding, use your browser's save-as function and select webpage-complete to save to a single index.html file. The GitHub Repository includes everything you need for a PWA, meaning an application that users can install to their mobile/desktop homescreen. Simply clone the repository, swap in your index.html file, and host on GitHub Pages for free.

Comments: you can take a look at the code here

Snowden is a legend free Assange yo! The sites only been live for a day and there’s no real documentation yet, I don’t think anyone would understand just by looking at it. You can read the repo but I’ll give you a little run through. If you click the leftmost icon labeled “Soul” it should open a window with some text in it. That text is just JavaScript, you can change the part that says “GooieJS” to something like “Snowden Fan Page” and the home page will change its header to say so as you type. You can use it to build complete websites using just JavaScript, live from your browser, while using default browser functions like dev tools. I have a background in print, so it’s also a useful tool for print applications. This app let’s you make and print a business card and it was written in the same manner. If you click “save as pdf” instead of print, you can open the page you were working on in a program like Adobe Illustrator. If you’re making an app, the repo has all the files you need for a progressive web app, meaning something someone can save to the home screen of their phone. Just plug your processed code and you have a web app 🤗

Haven’t worked on the mobile version yet, it should look like this on desktop check out the docs at the github repository but it’s all still a WIP

> Just .GetAwaiter().GetResult() it.

That won’t work with various synchronization contexts, where doing this would cause a deadlock. There’s not much fun in trying to debug such issues.

And now that various libraries only provide async api, or worse an non-async version wrapping the async one with . GetAwaiter().GetResult(), you’ll be in for a treat updating your dependencies.

Async all the way is the answer, although various frameworks still don’t offer async hooks. Recently I ran into this for example trying to write an async validator in blazor, but that’s not possible and you have to work around it [1].

C# 5 introduced async/await almost 12 years ago. And we’re still not “async all the way”.

[1]: https://github.com/dotnet/aspnetcore/issues/40244

This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.