Paradoxical, but true. We, the 1C programmers, do not like 1C, which creates work. Why do we bite the hand that feeds us? I will try to clarify.
Closedness and non-publicity 1C
1C is not interested in feedback from developers. I don't even know where to write to register a wish for the platform. But even if they are registered, it will not be done for five, ten years, and possibly never. There is no discussion of "wishlist" and is not planned, the necessity is determined by "a giraffe, which is big and knows better".
Resources in 1C, where developers communicate, are fenced off as much as possible. For example, you can only get to the developer's partner forum if you have passed the "1C: Specialist" exam. But this is not enough - you need to work in 1C: Franchisee or buy a development kit (about $ 50).
There was a funny case about this kit - during quarantine 1C sold it three times cheaper than usual. But such a "discount kit" did not give the right to access the partner forum.
The same goes for privacy from users. An error in the configuration can be sent not by a button in the program, but only to the mail, indicating the registration number of the program, which few users know. It is impossible for a developer to send an error message without specifying a specific client where this error occurred, and for this you need to ask the client's permission.
Given such closeness, somehow it is not surprising that the 1C company is not public, which in the 2021 century seems generally bad manners. 1C does not have evangelists and preachers, 1C does not have social networks, there is not even a website with news from the life of the company and its office.
By the way, 1C tried to create resources to attract developers. There was such a project "Our 1C", an analogue of Infostart, has now died happily. Those. it seems that someone in 1C took the budget for it, mastered it and closed it safely. Or maybe 1C was disappointed in connection with the developers? In any case, the death of the project was not explained in any way to those developers who put their efforts and resources into it.
Lack of publicity and openness leads to another disgusting side of the coin - arrogance. They say we are here 1C, and you are a bug. You buy it anyway and use it, cry, shoot up, but eat a cactus.
1
1 . . , 1 . ?
, 1 PERFECT () . 77 , . , , . , .
, - . 1 .
, . 1 ERP . , . , , , . ERP 1 .
. , , , . , " ".
, 1 . " ", . , .
, 1 , , , ? , ?
1 , " ". ? ? , . .
, , .
, . 1 . , . 1 . , , .
1
1. , 1 , . , , .
, 1 . .
- . , , ? ?
1
, 1, -. , 1 -, .
, , , , . ""?
. .
, , - .
- Navision. , Navision , . 1 . .
, , - . , , , . , - , .
1 ( ).
, .
ERP 1 .
, ERP - , , , . , 1 . ( ) ERP. (), (), (), () . - .
1
1 . , Fresh - -middle. - .
, "". . 1 . , -, .
, , Goto, " " ..
- . - , 1 "" .
1 . , . -, . , .
1
1 . 1 - , . 1.
- 30$, , 180$.
1 30$, , 1: 10$.
, , 1 . , . 1, , . , , .
1 , " 3.0" .
1 , 2021 , , SQL-, , - My-SQL . , , , , .
, . 1 . . , .
, open-source. , , ? , - .
, - 1 . ( ), , , . .. 1 ().
1 , - , , .
. 1 "" 1:. 1: . , .
1: "" , . 1: " ", - .. , , .
. "" - . , , , , . "" , , , , , - .
.. 1 - .
1
1 1 . , . .
1 . . , , 2, 3 . .
1 1. , , . :
, . "". - .
1 , . .
. , . 1 , .
1
1 , , . 1, - , . , .
, 1 No-code .
1. Java, , .
A paradoxical situation arises - a 1C programmer needs to know and be able to do more, but they pay less for it. Moreover, the experience gained in 1C is not quoted in the West. This is reminiscent of how our doctors and engineers who emigrated to the United States worked as cleaners and loaders.
Miracles do not happen, and over time, 1C programmers will become an expensive curiosity. There will remain a small class that will do the settings for reports, printed forms, exchanges. Otherwise, 1C will only use consultants who should not be able to program.
Disclaimer : everything described in the article is only the personal opinion of the author and may not correspond to reality.
