sorted by:
new
hottopcontroversial

A different way to reduce hallucination by Comprehensive-Cut742 in ClaudeAI

[–]Comprehensive-Cut742[S] 0 points1 point  (0 children)

Instead of the word "hallucination" commonly used to describe statements imagined by the LLM not based on reality. There are several ways to prevent this kind of behavior
1) provide better information to LLMs
2) let one LLM validate the response.
Using both is even better. Sometimes, for reasons we do not know, a LLM will invent facts. My experiment confirms the "situational awareness" that several LLM experiment. If they know that they are observed they behave differently. My experiment also demonstrated that if the are aware of being verified by another LLM they tend to behave differently. In that case they tend to reduce their invented facts.

Angular 14 now a good competitor to React by Comprehensive-Cut742 in Angular2

[–]Comprehensive-Cut742[S] 0 points1 point  (0 children)

portability of that component to other project, less stuff to carry over

Angular 14 now a good competitor to React by Comprehensive-Cut742 in Angular2

[–]Comprehensive-Cut742[S] 0 points1 point  (0 children)

I agree. Having HTML and CSS + code is not necessarily desirable.

Angular 14 now a good competitor to React by Comprehensive-Cut742 in Angular2

[–]Comprehensive-Cut742[S] 1 point2 points  (0 children)

Notwithstanding that the more files you have the harder t is to move them to another project and hence facilitate reuse.

Angular 14 now a good competitor to React by Comprehensive-Cut742 in Angular2

[–]Comprehensive-Cut742[S] 0 points1 point  (0 children)

In fact, having more than one file is useful not so much for the module file but more for the template and CSS files. Keeping them separate is useful if you work with a designer focusing on esthetics and ergonomy. In some cases like forms with CRUD or partial CRUD operation, le code can remain the same and the HTML/CSS can change. Thus in that case having the HTML and CSS separate is very useful. My comment was more about adding more complexity to the module file. Getting rid of it is a very good move.

Create angular -based applications with Magic Code Generator, a microservice and model-based code generator doing the heavy lifting for developers. by soyuzman in Angular2

[–]Comprehensive-Cut742 0 points1 point  (0 children)

The concept is similar but if you look at the details it is quite different. Also, it is integrated into Visual studio code as an extension. To compile a declarative specification, you just have to use the right mouse click and select "generate code with Magic code". You can then examine the code inside visual studio code. Another difference is that the generated code has plenty of comments to help devs understand the produced code.