@Alexander_Johannesen I think that there is no need to say “sorry (to be blunt)”, when this bluntness is just a response to plain rudeness. But by the way: I don’t care about people being rude (as long as they can, in turn, stand a bit of sarcasm), and after seeing some German words in the IDE screenshots, it could be appropriate to link to wie man in den Wald hineinruft, so schallt es heraus - Wiktionary
But still, I’m in the dilemma: On the one hand, even when ignoring the “rudeness”, the contents of the communication was not helpful or directed towards finding a solution. On the other hand, and as I mentioned earlier: This “rudeness” may largely have been “venting” of some accumulated frustration, and I can understand that a little bit too well. While investigating this issue, I stumbled over Does not copy files to actual output folder when webpack-dev-server is used · Issue #29 · webpack-contrib/copy-webpack-plugin · GitHub , and this is a prime example of what I perceive to be the source of frustration for many web developers:
Something (seemingly trivial) does not work as expected
The issue is filled with fourty-eight (!) comments saying…
This was fixed in version 4.3.5.1.4-alpha
This issue is now closed (aha…)
This was re-introduced in version 4.3.5.2.0
I have the same problem
This is how I solved it /*code*/.
I have the same problem, and the solution above ^ does not work for me
The solution is explained in the documentation here: [dead link]
You can downgrade to version 4.1.5.2.0-beta
This is how I solved it in version 4.3.2.1.23-c: /*code*/.
I have the same problem, and none of the suggested solutions works for me
You can solve it if you download, install and use the following bunch of libraries: ...
This ^ solved the original problem, but caused three new ones…
…
And this is spread over a time span of five years (!)
(Eventually, some people seem to have replaced “whatever this webpack thing should do” with a plain shell script that does cp source target. Yay )
Now, whose fault is it that things are so complicated, that they are so unreliable, and that they break so often in subtle ways? Someone has to be blamed. And who, if not the developers? But … every developer is standing on the shoulders of millions of other developers. And sometimes, the wrong ones are blamed. For example, the Cesium developers are blamed when somebody has a problem with WebPack, that was actually caused by someone who made a mistake when editing some config file.
Thank you for viewing my frustration with understanding. If I was rude, I apologize. Maybe it’s also because I don’t speak English very well. Frequently use the translator and therefore it may be that certain things have seemed “impolite” to you.
would like to be called an expert and professional here. If you are that professional, you should know that web development is divided into 2 groups. Once in frontend and in backend development. The latter (backend) is my area which I have delved into for over 15 years!
And here, what we have been trying to do for 3 months about the start of the CesiumJS, including Webpack or Gulp and what else belongs there, only concerns the frontend development. And you noticed, at the beginning I also indicated that I don’t have that much experience with frontend development. But, apparently you haven’t read any of it, so you haven’t been able to do anything productive here regarding help, other than just the 2-3 destructive contributions from you.
And hey @Alexander_Johannesen (as if she would like to be a professional), you have absolutely no right to question my developer knowledge! You don’t know me at all and you have no idea what my work is about! Do not question yourself again when it comes to my profession and my knowledge!
Simple things and then complex? Isn’t that a contradiction ?! If it’s that simple, how can it be complex at the same time?
Regarding the fact that CesiumJS is used by hundreds or thousands of apps it might well be possible. I have never said otherwise. It looks like you’re really not reading right. Instead of thousands of apps, it could also be millions of apps. I only talked about it! But you seem to look at things with a blinker. The criticism of this from me, should and was only a positive (constructive) criticism, so that CesiumJS gets a lot further than it is now. I don’t understand what’s wrong with this! Well …
It may be that the support here is excellent. I didn’t doubt that either. But what use is it to me if I don’t get any answers for 39 days?
No matter how you talk against the wall, it won’t answer you. Of course, if you do not read correctly as a helper and do not have a reasonable dialogue with the person asking, one or the other piece of information may be missing, which is not so clearly evident from my side as an initial user. If it were obvious, then I would have already been able to solve the problem myself and not have asked here at all. I think it’s much more that you are focused on how to push one in than on helping.
And again: please don’t compare apples with pears! I only criticized the incomplete and incorrect documentation. As for the forum, I said that it was much better than running it through Discord or other programs as there was better support there in every way. For a user, support is very important. The better the support, the better the whole framework!
We just talked about the pros and cons of why should be Discord and not a forum. It’s just a recommendation from me. The frustrating criticism ONLY goes to the documentation as it is sketchy and flawed. So the documentation is shit at the same time - from the user’s point of view. You can’t do anything for that.
The reason for this is as follows:
Step-by-step documentation leads to errors. Because it is out of date and incomplete. These were criticized in the 1st, 2nd and 3rd contributions. In the meantime, it has even been confirmed here several times that it is incomplete and out of date and therefore incorrect. Ultimately, this is for someone who’s using it for the first time = shit! No matter how good it is. It remains with a negative view!
Even the repository was faulty and you couldn’t start it right after cloning. This has also been confirmed several times here. So I don’t understand your problem at all ?!
Why forum is stupid on the part of users: Clearly and clearly, because you have to wait a long time for answers! See 2nd post over 15 days and again with the post from 23 September I waited for 7 days and again on 29 October with the post I waited 17 days for an answer. Well notice it is only about the launch of CesiumJS. That is a total of 39 days that were wasted unnecessarily. How can you say that the forum works great?
In the past, letters / messages were sent with the pigeons and the message might even have arrived in 3-4 months. Now imagine that the hut burns down and the fire brigade will be notified in time, but the help will only come in 1-2 months ?! Then there is nothing left of the hut … and that’s exactly how it is here with the forum. So please don’t tell me Driss just because you personally have a psychological problem getting used to newer technologies. You don’t have to talk bad for good and counteract it.
Yes, but ultimately a product is only valuable and usable if it is accepted and used by third parties. If something doesn’t work or has gaps, it cannot be accepted or used. The program / product can be worth billions of dollars. What use is it if we (third parties) do not use it?
Furthermore, a bug can be fixed by people who are familiar with it. So, if you or others can’t solve it, then it can only be solved by the professionals … Isn’t it understandable, isn’t it?
I am just wondering why we have these kindergarten discussions instead of engaging constructively on the topic. Really ridiculous.
What do you have any idea what I’m up to?
Maybe in the future I will get the Enterprise version and it will no longer be free! But let’s be honest, who will buy a cat in a poke? The free version has to work first so that I can try it out to make my decision for an enterprise.
To express your personal problems about the others and certainly not to criticize them for solutions from others is really poor. Why don’t you show us your skills yourself and help us with simple things and create a working basis for beginners like me? If you consider your previous contributions to have helped, you are wrong. Because you simply concealed the problem and commented it out too generalized. This is no help, but rather contributes to despair and frustration. Telling someone, yes, there could be a thousand reasons why the error comes up. Or examples similar to this one: “Whether during this time a lightning bolt strikes my room or during which I suddenly had to go to the toilet or whatever … and that is why the error arose” is definitely not helpful . Sorry but that’s how I felt your contributions.
@Marco13 was very exemplary here and was able to advance things by analyzing things by guiding me to the solution. Ultimately, on closer inspection, he has solved the problem on his own. For that I thank him with all my heart.
From this I can see that you hardly have a clue about frontend development. Sure, you can run Cesium without Webpack. But for certain applications Webpack or the like is paramount and in such cases Webpack serves as a foundation for CesiumJS. The Webpack configuration that I have here works wonderfully in other projects. It only had problems with the CesiumJS, as special parameters were necessary for this. As a beginner, I cannot conjure this up from heaven if it is not described in the documentation in a reasonable and clear manner. But you have to be able to think that far first …
I ask you, if the documentation is so perfect for you, why is there this forum and why do thousands of questions and threads have to be created here?
Kind of obvious, wasn’t it? …
And again, if I do - as you are accusing me of having insulted and insulted the community etc. - I would like to apologize. Because, as already mentioned above, I have only uttered the facts + my frustrating ones here without having any intention of insulting someone personally.
This is sometimes caused by people talking about people, and not the topic (and I see the irony in that statement…).
On the one hand, I have to admit that this specific problem was somewhat specific to CesiumJS. Arguing otherwise when that thing is called CESIUM_BASE_URL could be hard. On the other hand, this is documented in the Quickstart, and even though I have no clue about web development, I noticed that the files that it is looking for are not in the Assets directory, but in the Assets/js directory - as it was explicitly set in the config file - and then concluded that this js was missing somewhere. Or to put it that way: How should CesiumJS know whether these files are in Assets or in Assets/thisIsMyFavoriteNonStupidDirectoryName?
However, the problem is “solved” now, let’s leave it at that.
Thank you for your comments and contributions. We’re closing this topic as some of the messages have violated Cesium’s Code of Conduct and are no longer in the community’s best interest.
)
… Isn’t it understandable, isn’t it?