|
|
|
"His BMI was higher than average ..."
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Or the Garfield approach: "I'm not overweight, I am undertall".
|
|
|
|
|
PC is idiots trying to impose their views on others.
One can be sensitive to others, without being PC.
Ed the Barbarian.
|
|
|
|
|
#Worldle #395 3/6 (100%)
🟩🟩🟩⬜⬜⬇️
🟩🟩🟩🟩⬜⬅️
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
Knew where but Had to use map to get name
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I used to be indecisive. Now I'm not so sure.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I'm trying to understand my procrastination, I'll start first thing in the morning!
|
|
|
|
|
I used to have a really bad mental health problem - I was absolutely convinced my superiority complex was smaller that everyone else's . .
Where's the door - I seldom bring a coat . .
A few are great.
I am small.
Together we are the Universe.
|
|
|
|
|
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Using a Java-based IDE for writing C++ code.
(rant of the day)
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Which one?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
I can hear the Gods of C++ sobbing...
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Is using a C++-based IDE to write Java code OK? If so, why not the reverse?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Writing Java code would be frustrating per se.
Java-based IDE are slooooooooooow.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Eclipse will compile 25,000 java files in minutes and build a comprehensive database of the code during the compilation.
Maybe it is just slow dealing with C++? You might check for linting/ validation options that can be disabled.
|
|
|
|
|
Eclipse was fairly new when I tried to use it, maybe 15 years ago. Maybe the build speed was high even then, but the interactive response was extremely slow. Unless you were running the fastest PC on the market, you were typing blindfolded; you saw no echo from your keystrokes, and for all supplementary functions you might as well take a walk to the coffee machine to refill your cup while waiting.
We suspected - and I still do - that the extremely sluggish interactive response was a result of a bad porting to the MS Windows environment, done by developers who had not learned how to build Windows applications (if this is correct, Eclipse is certainly not alone with such problems!), because Eclipse had a good reputation in *nix environments - that's why we thought it would be the best tool for us. But none of us had sufficiently powerful machines to run it; it was thrown out.
If the problem was a poor port to MS Windows, the problems may have been cured within a release or two. I don't know. To us, Eclipse was so extremely bad, performance wise, that we said: Never more Eclipse. Today, that may be wrong, yet I will be very reluctant to give it a new try, even after that many years. It was that bad. (Besides, I haven't been coding Java for years, and have no plans for picking it up.)
|
|
|
|
|
trønderen wrote: because Eclipse had a good reputation in *nix environments
Sadly it is the best IDE on *nix environments, but not due to its merits.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
den2k88 wrote: it is the best IDE on *nix environments Nah, Emacs was always the best.
|
|
|
|
|
Emacs is a good OS, but it could use a decent editor.
|
|
|
|
|
Quote: We suspected - and I still do - that the extremely sluggish interactive response was a result of a bad porting to the MS Windows environment, done by developers who had not learned how to build Windows applications
Some things were (maybe still are) difficult to port to Windows.
I had a bad experience and dug into it with a benchmark that: Opened multiple small files, read them, wrote them, then closed them.
The time do do this on a Windows machine on NTFS with the set of test files I had was around 1m30s. On the same Windows machine, running a virtualbox Linux, with the same files on an ext4 filesystem the benchmark took around 12s.
The reason? On Windows, various applications can (and do) hook into the "open", "write" and "close" filesystem calls. If you're running just 1 AV and a filesystem indexer like Everything, each time an application opens a file, it's three times the overhead of doing the same on some other OS.
For applications that may open lots of small files, I don't know how you'd "port" it to Windows other than by rewriting it to not use multiple small files. For something eclipse, I'd imagine that simply referencing other java projects via maven or similar is going to result in many thousands of files being downloaded.
|
|
|
|
|
On the other hand : I'm using a very old java based tool to search for text in files in windows directory structure. And it is the only one I trust on the results old furt me
|
|
|
|
|
I just use VS Code. It's got a few wrinkles, like intellisense just randomly dying on certain files, but honestly I'm surprised it can autocomplete my layered C++ template constructions at all.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
Considering that the dodo may be on the way back Gene editing company hopes to bring dodo ‘back to life’ | Extinct wildlife | The Guardian that may not be a good example, anymore.
But no, bug reports will still need to be made. Bugs will still occur, some of them will be potentially catastrophic (what do you mean, the plane tried to land 2 meters below the runway???). So bug reporting will still be needed. AI might be able help narrow down the nature and/or location of the bug, maybe even one day correct the bug, but for now, as others here and in other locations have noted AI is very poor AI at writing code. I can't imagine it would do any better at fixing bugs. And companies producing software will still be liable.
Keep Calm and Carry On
|
|
|
|