Anonymous
and is large i guess?
Abde
it works pretty well
Anonymous
Mihail
Abde
Anonymous
Kdevelop
this one one of the companies i worked at uses
Anonymous
qt develop they used for STM32 programming
Anonymous
kdevelop was for the server and computer vision codes
Anonymous
Objects Should Be Immutable 🤫
In object-oriented programming, an object is immutable if its state can’t be modified after it is created. 🤞🏻
In Java/C#, a good example of an immutable object is String.✅
Once created, we can’t modify its state. We can request that it creates new strings, but its own state will never change. ❌
However, there are not so many immutable classes in JDK. Take, for example, class Date. It is possible to modify its state using setTime(). 🕒
This is an incomplete list of arguments in favor of immutability ⚡️:
• Immutable objects are simpler to construct, test, and use
• Truly immutable objects are always thread-safe
• They help to avoid temporal coupling
• Their usage is side-effect free (no defensive copies)
• Identity mutability problem is avoided
• They always have failure atomicity
• They are much easier to cache
• They prevent NULL references, which are bad
Let’s discuss the most important arguments one by one. 🌀
https://t.me/pgimg/178
[ Article ] : kutt.it/immtb
〰〰〰〰〰〰
#BestPractices #DesignPatterns
@ProgrammingTip
Anonymous
Objects Should Be Immutable 🤫
In object-oriented programming, an object is immutable if its state can’t be modified after it is created. 🤞🏻
In Java/C#, a good example of an immutable object is String.✅
Once created, we can’t modify its state. We can request that it creates new strings, but its own state will never change. ❌
However, there are not so many immutable classes in JDK. Take, for example, class Date. It is possible to modify its state using setTime(). 🕒
This is an incomplete list of arguments in favor of immutability ⚡️:
• Immutable objects are simpler to construct, test, and use
• Truly immutable objects are always thread-safe
• They help to avoid temporal coupling
• Their usage is side-effect free (no defensive copies)
• Identity mutability problem is avoided
• They always have failure atomicity
• They are much easier to cache
• They prevent NULL references, which are bad
Let’s discuss the most important arguments one by one. 🌀
https://t.me/pgimg/178
[ Article ] : kutt.it/immtb
〰〰〰〰〰〰
#BestPractices #DesignPatterns
@ProgrammingTip
ok this is not true that immutable is faster
Anonymous
Abde
Abde
but much more limited
Anonymous
immutablity has a point for high level codes, where you should probably not be using OO or imperative programming
Anonymous
but rather functional approaches
Anonymous
somehow
but i tried the C++ extension it's not IntelliSense at all
Roxifλsz 🇱🇹
Objects Should Be Immutable 🤫
In object-oriented programming, an object is immutable if its state can’t be modified after it is created. 🤞🏻
In Java/C#, a good example of an immutable object is String.✅
Once created, we can’t modify its state. We can request that it creates new strings, but its own state will never change. ❌
However, there are not so many immutable classes in JDK. Take, for example, class Date. It is possible to modify its state using setTime(). 🕒
This is an incomplete list of arguments in favor of immutability ⚡️:
• Immutable objects are simpler to construct, test, and use
• Truly immutable objects are always thread-safe
• They help to avoid temporal coupling
• Their usage is side-effect free (no defensive copies)
• Identity mutability problem is avoided
• They always have failure atomicity
• They are much easier to cache
• They prevent NULL references, which are bad
Let’s discuss the most important arguments one by one. 🌀
https://t.me/pgimg/178
[ Article ] : kutt.it/immtb
〰〰〰〰〰〰
#BestPractices #DesignPatterns
@ProgrammingTip
If you're making all your immutable, might as well go the functional route then, no?
Anonymous
one example is Haskell
Anonymous
now for low level robotics which things like OO and Imperative SHOULD BE USED
Abde
Anonymous
because of the smaller memory
Anonymous
ok
Anonymous
Abde
Not the same as VS intellisense but pretty decent
Anonymous
it is very easy to use
Anonymous
and actually is designed for C++/C
Abde
CLion is an other good option but you will have to €$
Anonymous
unlike qtcreator
Anonymous
you do not have to spend time reconfiguring
Anonymous
Anonymous
the other devs had it on unity
Anonymous
and i used it once on i3
Anonymous
oh and i use CMake for building
Anonymous
Anonymous
qt has qmake by default
Anonymous
Anonymous
which is a shitshow
Abde
Abde
you can pick whatever you want when you create a project
Abde
but kdevelop is also a good option
Anonymous
it is to the point that the people at those companies who used qtcreator were using qmake
Anonymous
instead of cmake
Anonymous
and they were not using any qt in their code at all
Anonymous
gonna switch almost entirely to linux, really tired of windows
Anonymous
and the only reason was "because it was too annoying to set up the cmake"
Anonymous
kdevelop and qt both work on both
Anonymous
Anonymous
Anonymous
Anonymous
no they were on windows
Anonymous
Anonymous
not why
Anonymous
they picked qmake instead of cmake
Anonymous
because cmake was too hard to properly set up on qtcreator
Anonymous
uhm
Anonymous
they were using custom compilers
Anonymous
to compile for stm32
Anonymous
well not too hard
Anonymous
too annoying
Anonymous
kdevelop has it's own issues but i found is much easier to fix those issues
Anonymous
there's also GNOME Builder 😁 that its icon is soo ugly that i won't ever try it.
Anonymous
vim was the easiest
Anonymous
there were no issues
Anonymous
vim just worked
Anonymous
and is my prefered editor
Anonymous
Anonymous
i use emacs as well
Anonymous
which i use for prototyping
Anonymous
then if it needs a speedup i move it into C/C++
Anonymous
and if it still needs a speed up i start bringing in ASM and Cuda into that
Anonymous
Anonymous
no highlighting
Anonymous
i don't do those low level things
Anonymous
Anonymous
it also does not have the best support for cuda