Blazorise VS llvm-project

I made a Blazor component library for one of my personal projects that failed, but the component library lived on as an open-source project called Blazorise [1].

In late 2019, I got a well-paid job in a large local company because of the project reference. Unfortunately, COVID happened, and I lost that same job after a few months. So again, because of Blazorise, I got several other gigs as a freelancer.

But after a while, it was hard to do all the work on the projects and do freelance jobs at the same time. Not to mention that family time was also very limited.

So I decided to commercially license Blazorise to companies, and keep it free for individuals. Hopefully, the decision paid off. Today I run a small company and continue to work on Blazorise full time. We're still fully bootstraped without any external funds.

[1] https://blazorise.com/

https://blazorise.com is fully done on Blazor. Also the support forum https://blazorise.com/support

Da, vidi https://blazorise.com/

I am working on form that run dynamic sql query in database and populates the results in datagrid. I don't know how many columns will return by the query. So I populate my resuts in DataTable, but unable to display on datagrid. Relevant issue [Feature] Full featured work with DataTable in DataGrid · Issue #701 · Megabit/Blazorise (github.com) . Does anyone know workaround for this.

Making Blazor run on Linux was a lot of hard work. Mainly because there is no official support from Microsoft (but even that doesn't always help, as you will see in the next section about macOS). I tried to make it work with 3 different community driven projects: Electron.NET, Chromely and Photino. Electron is very bloated and very slow - it takes for ever to start debugging from Visual Studio. I also hated that it first opens a console window and then the Blazor window. I don't want to see 2 windows open. Chromely also first opens a console window and then the Blazor window. I couldn't make it work in Linux. That leaves Photino. It comes with a Blazor sample that works in Linux without a problem. But my project didn't work in Linux with Photino. I found out that the problem was loading content for https://github.com/Megabit/Blazorise from the \wwwroot\_content folder. I sumbitted a GitHub issue and the problem was fixed in Photino.Blazor v2.5.0

I did something similar with Blazorise, a personal project of mine, https://blazorise.com/. It started as a hobby project. After some time it grew too large that it took most of my time, not to mention the time I could spend with my wife and son. Things changed during the Covid when I was laid off. Then I started freelancing for a while, and last year I finally took a big step and went full-time with Blazorise. Switched to dual licensing, where larger enterprises must purchase a commercial license. It is working, and hopefully, it will continue to work. Or otherwise, my wife will rage on me :/

My guess is that they're using component libraries (like Blazorise) rather than write components themselves.

'Computer Architeture: A Quantitative Apporach" and/or more specific design types (mips, arm, etc) can be found under the Morgan Kaufmann Series in Computer Architeture and Design.

"Getting Started with LLVM Core Libraries: Get to Grips With Llvm Essentials and Use the Core Libraries to Build Advanced Tools "

"The Architecture of Open Source Applications (Volume 1) : LLVM" https://aosabook.org/en/v1/llvm.html

"Tourist Guide to LLVM source code" : https://blog.regehr.org/archives/1453

llvm home page : https://llvm.org/

llvm tutorial : https://llvm.org/docs/tutorial/

llvm reference : https://llvm.org/docs/LangRef.html

learn by examples : C source code to 'llvm' bitcode : https://stackoverflow.com/questions/9148890/how-to-make-clan...

See

https://github.com/llvm/llvm-project/issues/88344

https://fortran-lang.discourse.group/t/flang-new-how-to-forc...

You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.

> There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.

Actually, it's implemented in LLVM for years :) https://github.com/llvm/llvm-project/commit/a98546ebcd2a692e...

> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.

Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.

Case in point, this was fixed in both major C++ libraries:

https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...

https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...

So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?

For everyone else looking for the magic in this almost 7k lines monster, look at line 6610 [1].

[1] https://github.com/llvm/llvm-project/blob/8ec28af8eaff5acd0d...

Through value tracking. It's actually LLVM that does this, GCC probably does it as well, so in theory explicit bounds checks in regular C code would also be removed by the compiler.

How it works exactly I don't know, and apparently it's so complex that it requires over 9000 lines of C++ to express:

https://github.com/llvm/llvm-project/blob/main/llvm/lib/Anal...

https://github.com/llvm/llvm-project/blob/main/flang/docs/F2...