Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MI
Posts
0
Comments
376
Joined
1 yr. ago

  • I don't think those are the problem, but rather how they are used. And in case of managed languages like C#, it's almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷‍♂️

  • I'd really like to see this. However I don't have high hopes when looking at the current state in Slovenia, where Microsoft is deeply rooted in all public and non public sectors, starting from schools. Most know only Windows and Word while they don't distinguish between the two and schools system doesn't give a shit about teaching anything about computers let alone non Microsoft. One of the reasons is, of course, teachers being computer illiterate or ... know only Microsoft. And so on and so forth.

  • Yes, there should be sanctions against any country doing that and worse. But there aren't. Why not? I see a lot of downvotes and no explanations. As per Europe, aren't we talking mostly about US, since Linux is trying to follow their sanctions? Also even Europe is divided about who the enemy is, like pesky Hungary.

  • Western tanks are built to protect the crew, while Soviet/Russian are built to advance regardless of anything without much consideration about crew safety (typical Soviet mentality). The turret throw is due to the shells being stored right under the crew, beneath the turret, and when those detonate (which is quite easy with modern anti tank weapons), everything is thrown magnificently into the air. Crew has no way to survive. It's different with western tanks, where shells are stored more safely and such a hit usually doesn't evaporate the crew.

  • They might work, but then one is bound to be online. Also different computers might have different configurations and that is something to pay attention to as well. Alternative is a synchronisation to source (nextcloud sounds a good fit) but then you might bump to synchronisation conflicts and such. Both ways will produce a lot of traffic unless you redirect creation of build artifacts to a local directory. Which might not be always possible.

  • A remote machine might not be always possible, such as when you develop mobile apps or when you have more than one monitor available. Sadly all options have problems. And (auto) pushing is not an option when you work on a team project where pushing non compilable code is not a welcome option.