Skip to main content

Cat de puternic trebuie sa fie un framework sau o tehnologie ca sa schimbe ceva?

Problema se pune in felul următor: ce trebuie sa contina un framework sau o tehnologie ca sa schimbe ceva si sa fie folosit la scara mare?
Pornim de la cazuri reale:
  • MEF nu a avut un impact foarte mare - este greu sa convingi lumea sa folosesca recomandările tale, mai ales ca in fiecare firma exista deja un framework ajutator;
  • EF nu a avut nici un impact major, NHibernate inca exista( NHibernate este deja un produs matur care a trecut de problema: ce a fost prima data. EF inca nu este un produs matur in totalitate, unele funcționalități inca lipsesc);
  • ASP.NET MVC a batut tot, proiecte de gen MonoRail au fost rase;
  • Prism - o aplicatie care a ajuns la o masa critica si incepe sa fie integrata de catre M$;

Exista proiecte care au nevoie de o masa critica pentru a reuși. De exemplu Oslo Project( cu limbaj M). Un proiect indraznet, in care M$ a investit foarte mult, dar din pacate a fost oprit. Acesta concureaza direct cu EF si nu a ajuns sa fie folosit atat de mult incat sa supraviețuiască.
Un lucru important este ca in ultimul timp M$ face parte din puținele firme care investesc bani in cercetare si vor sa aduca ceva nou pe piata( totul e marketing, dar avem si noi de castigat).

De ce am scris acest articol? Am fost implicat anul trecut într-un proiect care urma sa folosească limbajul M la baza unui DSL si am avut o mare dezamăgire sa aflu ca proiectul Oslo de la M$ a fost întrerupt. Daca s-ar fi ajuns sa se faca o implementare completa a limbajului M, s-ar fi ajuns intr-un moment critic, deoarece acest proiect are in momentul de fata cateva buguri destul de grele.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...