Thanks, will check there.
Thanks, will check there.
I understand your attitude very well.
Let me demonstrate this technology to you; it is not magical in any way. Actually it's brutally simple.
It is centered around focusing on architectural structures. And it requires the reference implementation to be written (at least) once. But then after that, regardless of how complex the reference structure is, if it creates logically consistent part of software, it can and should be abstracted.
On the site is working example of trivializing Microsoft Office Add-in. While that does not even look like a lot of output code, the information hidden inside to get all the bits and pieces right is relatively large for the amount of code.
I am currently working on demonstrational videos of technology in action.
Meanwhile, if you take on the challenge; if you can link something in common Linux development, that has HOW-TO and example/reference solution available, I'll demonstrate the case abstracting it for you and making video out of it.
I just posted on a general "Software Development" forum about open technology that trivializes handling architecturally or otherwise structured code blocks dynamically.
I would like to understand the guidance challenges in critical Kernel sections as well as not-so-critical yet often modified portions of parametrized values to alter the kernel build.
This technology allows flexible use of recognizing and guiding about architectural structures (such as kernel-scheduler) that can be tailored independently even by the very novice Linuxians, who just happen to understand scheduling perfectly and know exactly what parameters or alterations the scheduler requires to suit for their embedded/real-time usage.
I hope I can get somewhat active dialogue around the subject, as while the technology is open and platform-agnostic, we have little understanding about Linux kernel development on our own. We understand operating systems and their architectural structures, but we need someone with experience on Linux Kernel, who can show the reference implementations that we can then together help to abstract out.
Hello Linux developers!
I hereby toss a challenge towards the community; I need your help to understand the HOW-TO and other common difficulties to understand Linux - development. They can all be abstracted away (from driver level development to complex-integrated-ERP-systems) so that the developer experience is as smooth as it can possibly be.
I am in a task of searching the community focus for enabling ISVs and single developers (or even users) to make enterprise-architecture-grade applications.
I was through Linux Foundation's Workgroups (relatively inactive), Linux Developer Network (relatively inactive) and now here (seems hopefully active).
Our organization discovered a technology that trivializes software development.
The technology is by-nature completely open, completely platform agnostic and it divides the problem and complexity so that it particularly well suits for open-source-community to challenge even the most complex enterprisewide systems.
Naturally it does much smaller miracles on the day-to-day software development, for mobile phone clients or for example Linux kernel or driver areas.
This technology is tool-supported in Microsoft / Visual Studio stack currently, which means that mobile device developers (that already use Visual Studio) can already make multi-platform targeting with it.
We can demonstrate and make Linux-specific examples over anything that requires to be structured or guided to be done in certain way. This applies to anything between driver implementations to multi-tier-architectural software.
Once the reference abstractions are made (which are also trivial to make - they take less time than writing that guidance on HOW-TO use something), only the custom code is handwritten. All the architectural ceremonial code is automated.
Now I understand the examples are slim, because the technology is best described with live-examples of something concrete. While all our current examples are for Microsoft development ecosystem, we simply need examples of Linux development challenges to start tackling them.