FPC on Web3

[VisualLab]

At first I was going to respond to this "text chaff", but it's a waste of my time. The content gives the impression that it was generated by some AI bot powered by a (parameterized) script into which someone added a list of keywords that should be included in the resulting text. It's a waste of time to spend on this garbage. People visiting the forum may get the impression that there are more such rubbish threads, so this may negatively affect the perception of the forum by people who visit the forum less often. I suggest deleting this thread, it's a waste of space for garbage.

It must be genuine and incisive, Joanna hasn't accused OP of being a troll or a "Pascal hater"...

 

[VisualLab]

So, assume all you say it is true (since blockchain etc discussions are not on topic here, only Pascal programming is), what are your plans?

Will you port FPC to web3, and when do you expect to have something running?

Large work and course changes must be done by the people with a large stake in the subject matter, and you seem to be passionate about it.

Expecting the current developers to drop what they are doing is not likely to happen, so not very productive, since they might not be in the security field (in that way)

If he responds with a long tirade full of pompous phrases without any specific content, it may indicate that the text was probably generated by a bot.

[Blacha]

So, assume all you say it is true (since blockchain etc discussions are not on topic here, only Pascal programming is), what are your plans?

Will you port FPC to web3, and when do you expect to have something running?

Large work and course changes must be done by the people with a large stake in the subject matter, and you seem to be passionate about it.

Expecting the current developers to drop what they are doing is not likely to happen, so not very productive, since they might not be in the security field (in that way)

Thank you for this point of view.
I apologize, but I will ignore the irrelevant suggestions of the participants of this discussion, because I want to avoid verbal jostling, and besides... please do not take offense at what I am about to write, but I am at a stage in my life where the line of people willing to kiss my ass is getting longer and longer. Thanks to this, I can focus on nice and pleasant things, e.g. my passion for FPC/Lazarus and Web3. I do not have time for "jostling".
Where would I start? By reviewing several important tools for creating ICP projects. One of them is "dfx" - is the primary tool for creating, deploying, and managing the dapps for the Internet Computer platform.
If we use dfx to create a new project ("dfx new project1"), the structure of the dapp project will be created. Before the structure is created, dfx gives you a choice of tools - various backend programming languages ​​and several frameworks for the frontend (can be skipped).
And here it is begging to enable the possibility of building everything based on FPC. Building the frontend? No problem with pas2js. The final effect (html and js) can be embedded in the frontend structure.
It's worse with the backend. Here it's worth analyzing the libraries available for different programming languages ​​(on-chain and off-chain) and I agree that this is work for the team. A huge advantage of the FPC/Lazarus environment is the ability to create WebAssembly code.
dfx gives you the ability to run SC in a locally available canister (node.js) or send it to the ICP mainnet (dfx deploy).
Unfortunately, I don't have the knowledge to assess the scope of work, but from my initial analysis it appears that the entire code for the dapp could be prepared in Pascal.
Smart contract written in Pascal... wow! how does that sound!

[VisualLab]

I apologize, but I will ignore the irrelevant suggestions of the participants of this discussion, because I want to avoid verbal jostling, and besides...

Ooo, so it's not a bot after all Either way, the participants' suggestions were not only important, they were crucial. Because only after that did the OP start writing content that resembles a human's statements and not a bot's!

please do not take offense at what I am about to write, but I am at a stage in my life where the line of people willing to kiss my ass is getting longer and longer.

So what if the OP didn't turn out to be a bot when something's wrong with his head. He fancies himself as some kind of God Are Alzheimer's and Parkinson's gentlemen trying to visit him or did he smoke too much "weed"? And in addition he has "sophisticated" fantasies with cheap sexual overtones

Where would I start? By reviewing several important tools for creating ICP projects. One of them is "dfx" - is the primary tool for creating, deploying, and managing the dapps for the Internet Computer platform.
If we use dfx to create a new project ("dfx new project1"), the structure of the dapp project will be created. Before the structure is created, dfx gives you a choice of tools - various backend programming languages ​​and several frameworks for the frontend (can be skipped).
And here it is begging to enable the possibility of building everything based on FPC. Building the frontend? No problem with pas2js. The final effect (html and js) can be embedded in the frontend structure.
It's worse with the backend. Here it's worth analyzing the libraries available for different programming languages ​​(on-chain and off-chain) and I agree that this is work for the team. A huge advantage of the FPC/Lazarus environment is the ability to create WebAssembly code.
dfx gives you the ability to run SC in a locally available canister (node.js) or send it to the ICP mainnet (dfx deploy).

Well, there is not as much "sawdust" in this text as in the previous "essays". So it really isn't a bot

Unfortunately, I don't have the knowledge to assess the scope of work, but from my initial analysis it appears that the entire code for the dapp could be prepared in Pascal.

Wow, what an insightful analysis! And with a delicate note of "ingratiating"

Smart contract written in Pascal... wow! how does that sound!

And at the end, toadying to the point of nausea Who's trying to kiss whose a...?

[Khrys]

I am at a stage in my life where the line of people willing to kiss my ass is getting longer and longer. Thanks to this, I can focus on nice and pleasant things, e.g. my passion for FPC/Lazarus and Web3.
[...]
Unfortunately, I don't have the knowledge to assess the scope of work, but from my initial analysis it appears that the entire code for the dapp could be prepared in Pascal.
Smart contract written in Pascal... wow! how does that sound!

Well, then why don't you go ask your countless ass-kissers to help you get off your ass and start actually focusing on your FPC on Web3 project instead of going "please FPC developers can I have this thank you in advance"? If anyone is kissing asses, it's you asking other people to do your work for free so you can make money off it more easily.

Crypto and smart contracts are an interesting technology. I'm not ruling out widespread adoption somewhere in the future. But the sheer arrogance and sense of entitlement many cryptobros put on display makes my blood boil.

This will be my last reply in this thread; I got baited.
Enjoy your moisturized butt and your centralized VC shitcoin.

[MarkMLl]

Ooo, so it's not a bot after all Either way, the participants' suggestions were not only important, they were crucial. Because only after that did the OP start writing content that resembles a human's statements and not a bot's!

In fairness, he's posted a couple of coherent comments elsewhere.

However this thread definitely isn't.

MarkMLl

[Blacha]

Good MAE,
I will try to ask the question from the first post again - what do you see as potential obstacles to building Web3 solutions with WebAssembly in the FPC/Lazarus environment?

[Marc]

Hi,
The problem is that most of us (I think) have little to zero experience with this "web3". If I read this, I think what's in it for me. How can it help my product. What are the benefits for my customers. Except that it is the next "hype thing".
What I do want to know is how it works. How will a regular app look like. What needs to be done behind the scenes. Having only a description of tool like 'dxf'  is for me something like black magic. Everything is in a black box, and the command "MakeIt" does it all... what... how... help...

So if you want something to happen in the next X years, explain in normal understandable words

Marc

Thank you for this point of view.
I apologize, but I will ignore the irrelevant suggestions of the participants of this discussion, because I want to avoid verbal jostling, and besides... please do not take offense at what I am about to write, but I am at a stage in my life where the line of people willing to kiss my ass is getting longer and longer. Thanks to this, I can focus on nice and pleasant things, e.g. my passion for FPC/Lazarus and Web3. I do not have time for "jostling".
Where would I start? By reviewing several important tools for creating ICP projects. One of them is "dfx" - is the primary tool for creating, deploying, and managing the dapps for the Internet Computer platform.
If we use dfx to create a new project ("dfx new project1"), the structure of the dapp project will be created. Before the structure is created, dfx gives you a choice of tools - various backend programming languages ​​and several frameworks for the frontend (can be skipped).
And here it is begging to enable the possibility of building everything based on FPC. Building the frontend? No problem with pas2js. The final effect (html and js) can be embedded in the frontend structure.
It's worse with the backend. Here it's worth analyzing the libraries available for different programming languages ​​(on-chain and off-chain) and I agree that this is work for the team. A huge advantage of the FPC/Lazarus environment is the ability to create WebAssembly code.
dfx gives you the ability to run SC in a locally available canister (node.js) or send it to the ICP mainnet (dfx deploy).
Unfortunately, I don't have the knowledge to assess the scope of work, but from my initial analysis it appears that the entire code for the dapp could be prepared in Pascal.
Smart contract written in Pascal... wow! how does that sound!

[VisualLab]

Good MAE,
I will try to ask the question from the first post again...

Quite a nice marketing graphic. I can do that too. I would just add more green to make it seem more ecological

what do you see as potential obstacles to building Web3 solutions with WebAssembly in the FPC/Lazarus environment?

The main obstacle is the vision of no benefits from devoting time and effort to dealing with something that you are trying to present in in bright colors here.

As Khrys mentioned earlier, everything related to cryptocurrencies has all sorts of serious flaws.

1. So far, it has only brought benefits to small groups of various bandits, fraudsters and slysters:

• drug manufacturers and dealers,
• arms dealers (like But or Kashoggi),
• burglars encrypting files on users' computers and promising to decrypt them in exchange for paying a ransom,
• burglars and fences stealing data (personal, financial, source code) from companies and institutions and offering this data on the DarkNet,
• scammers/fraudsters who extort real money from naive people in exchange for virtual currency.

2. All this infrastructure requires hardware with a lot of computing power and is terribly energy-intensive.

3. Cryptocurrencies are subject to huge exchange rate fluctuations, much larger and much more often than traditional currencies. It is possible that these fluctuations are caused by people who, however, have some control over this software and manipulate it in order to gain benefits at the expense of other participants.

Cryptocurrencies have been around for quite a long time and their serious drawbacks have still not been eliminated. So far, there are no benefits for the average Joe. Conclusion: cryptocurrencies are a dead end. In the past, people had many different ideas that turned out to be useless after years due to their flaws.

[Blacha]

So if you want something to happen in the next X years, explain in normal understandable words

Thank you.

I will try to outline a few of the most significant features of this technology:

• dApp is launched in the browser regardless of the operating system and processor (I think the world of technology is definitely heading in that direction);
• decentralization - in ICP both the frontend and backend are decentralized in the so-called distributed ledger. What are the advantages of this? Our application is always and everywhere available until the last node of the blockchain network is turned off.
• infrastructure security - dApp and data processed by dApp are resistant to attacks that we know from web2. Apart from the fact of encryption, a potential attacker has no possibility of focusing on a single server, IP address, domain;
• data security - data processed in web3 is natively encrypted and distributed. There is no possibility of browsing without the keys of the owner of this data;
• built-in identification systems (Internet Identity) based on a certificate delegated by blockchain to the browser signed with our key (in very simple terms). There is no need to create complicated and multi-component login and authentication systems. The backend checks the permissions to call (who is caller) a function or access data based on the so-called PrincipalID. I emphasize - this is the native functionality of this technology ready to use. All you need is a hardware key (e.g. an independent or built-in encryption module in a smartphone or computer);
• implementation costs - until recently this was a significant obstacle, but with the development of ICP this has changed dramatically. In ICP, the so-called "reverse gas" operates, i.e. the implementation costs are negligible at the beginning and may (but do not have to) increase with the growing popularity of the dapp. From a business point of view, it is a win-win. For some time now, we have been hosting the frontend in ICP and observing the costs. The conclusions are satisfactory enough that we are slowly preparing to host websites in parallel in web2 and web3 and eventually completely switch to web3 (especially since there is no SEO problem in web3 ICP);
• 4Gb canisters, in which we embed both the dApp and the data (WebAssembly). Canisters can be connected, created from the backend or managed depending on your needs. A cool example is the decentralized OpenChat messenger I mentioned earlier - there, each user/group/community functions in the canister space.

The development of various dApps on ICP can be observed here.

[MarkMLl]

So if I'm reading that correctly: it's a distributed botnet for cryptocurrency transaction processing.

MarkMLl

[Blacha]

Let me give you a practical example - I once created a system for a certain healthcare entity that consisted of an element supporting patient registration and office software for doctors (yes, I created the key elements of the system in FPC/Lazarus). During COVID-19, online sessions dominated, so there was a need to create tests for remote execution (e.g. MMPI II). I will skip the organizational details, but considering art. 9 GDPR (Processing of special categories of personal data), it was a big challenge to do it safely. Fortunately, there were no mishaps...
Creating similar software in Web3 would eliminate about 80% of the undertakings and problems related to the security of such a system. Sensitive data (medical records and specialists' notes) would be available only to authorized medical personnel, bypassing the services of the entity authorized to process data based on the contract (ISPs, IT specialists operating the system on the server side, cloud service providers and others).

And finally - please, let's not bring cryptocurrencies into this, because that's not what we're talking about!

[MarkMLl]

And finally - please, let's not bring cryptocurrencies into this, because that's not what we're talking about!

Well, you were the one who started off with the "word salad" so what do you expect us to think?

So you're talking about a distributed ledger. Where is the bulk data kept? /Surely/ you aren't relying on peoples' desktop PCs for that, particularly after it's been running for a while and has accumulated a few petabytes of state? /Surely/ that will need facilities rented in server farms, which aren't going to be browser-based (or even browser-capable) making things like Webasm far less relevant? /Surely/, for the limited number of target types, native code or an established intermediary like Java bytecode will make more sense, particularly since some types of server will already have Java accelerators?

MarkMLl

[Blacha]

I have not used the word "cryptocurrencies" in any of my statements. Just to be clear.

I have to admit to one thing - I am measuring this discussion by my own standards, so it may indeed sound like a marketing message.
So I am catching up.

Why ICP (Internet Computer Protocol)?

Well, because it is the only protocol that allows dApps to function in their purest decentralized form with reasonable maintenance costs. Unfortunately, other solutions require the use of hybrid models (I wrote about this in the first post), i.e. frontend-web2 <-> some intermediary solution or the so-called oracle <-> backend-web3. Why am I not interested in such a solution? Because it is not very secure and susceptible to penetration. If you look at the costs of maintaining a dApp in different environments, you will understand why I chose ICP.

As for the IC network topology, I suggest you familiarize yourself with this data: https://wiki.internetcomputer.org/wiki/Decentralization The hardware requirements of the network are quite a challenge (despite the division of requirements into acceptable generations), but there are more and more nodes willing to participate in the ICP consensus mechanism.

The basic format of the ICP smart contract code is WebAssembly (WASM). Of course, it must meet the restrictive requirements for the protocol, but it is for this reason (also because of pas2js, CSS-based controls) that I see FPC/Lazarus with great potential for building dApps in this environment.
Instead of creating a tirade, let me direct your attention to ready-made explanations for self-education: https://internetcomputer.org/how-it-works

[MarkMLl]

Just How many times are you all going to get tricked by the same entity that keeps making new accounts? 
...
Hi , while you are all busy interacting with this reincarnated poster from  previous equally ridiculous threads, I was trying to build a community for pascal programmers.

Joanna, that is not your call. The rest of us are gradually teaching him to write English, so don't just jump in accusing him of being a troll.

I'm tacking your other comment into a different thread to avoid polluting this one.

MarkMLl