"secure" is relative. They may not be e2e encrypted, but they are still encrypted via TLS, like any HTTPS traffic. It's the same encryption used for online banking. If you care about your instance admin being able to read your messages, you should use Signal or a Matrix client though.
But remember that only a few years ago, almost nobody used e2e encryption, and it wasn't much of an issue.
Whenever possible, it’s recommended to work in a common Git repository and use branching strategies to manage your work. However, if you do not have write access for the repository you want to contribute to, you can create a fork.
A fork is a personal copy of the repository and all its branches, which you create in a namespace of your choice. Make changes in your own fork and submit them through a merge request to the repository you don’t have access to.
https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html
How is this different from GitHub?
Just to make sure there's no misunderstanding: When I want to contribute to a project I'm not involved in, like inkscape, I'm not allowed to create a branch in their repo, so I have to fork it, which creates a copy of the repo, and sets the original repo as a remote.
Note that git is a distributed VCS that doesn't distinguish between servers and clients. Forking and cloning are the same operation from a technical perspective, except when you git clone, the copy ends up on your local machine, and when you press the "fork" button, the copy is on a GitHub/GitLab server.
Over the years people have developed an unbelievable number of coding languages. They all do pretty much the same job in pretty much the same way.
That's one way to say that you don't know a lot about programming languages.
Personally I have coded in Mercury Autocode, COBOL, FORTRAN, PL/1, LISP, Assembler, PERL, basic, C, C++ and JavaScript plus probably some others I have forgotten.
Sadly, there's no functional language in this list except LISP.
JavaScript’s longevity is assured for one reason. Browsers only support JavaScript.
Incorrect, browsers also support WebAssembly, which allows many languages (including C, C++, Rust, zig, Go, and many more) to run in the browser. And even without WebAssembly, languages can be transpiled to JavaScript, so you don't need to code in JavaScript to run your code in the browser. Languages that can be transpiled to JavaScript include TypeScript, CoffeeScript, Reason, Elm, PureScript, Dart, Kotlin, Scala, Nim, ...
However JavaScript has a flaw.
Not just one. Every programming language is flawed. Some languages have no type safety, some have no memory safety, some have no thread safety (or no multithreading to begin with), some are too slow for certain applications, some have an incomprehensible or verbose syntax, most support only one (sometimes two) paradigms (functional / imperative / object-oriented / logical), some have no proper module system, or no control over mutability, or visibility, or memory allocation, or side effects... some lack ergonomic error handling, or cooperative multitasking facilities such as coroutines, or generators, or macros, or reflexion...
If you don't appreciate the vast design space that is programming languages, of course you won't understand why there are so many of them.
Unfortunately, this quote is often taken out of context to argue that optimization is not important. Here's the full quote:
Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%.
In other words, you should optimize your code after you have profiled your program to find out which sections are most performance-sensitive, and you should use benchmarks to verify that the optimizations you have applied are beneficial.
The name "pull request" is actually more accurate, because you ask the upstream repository to git pull the changes from the downstream repo.
Thank you, too!
I started another, even bigger flag at (960, 830). Feel free to help!
P.S. I also started an ace flag, a non-binary flag, with more to come :)
Even if this was true in 2013, when this article was written, the more accurate answer today would be "it depends".
In Rust, there are multi-threaded async executors implementing M:N threading (e.g. tokio), where M asynchronous tasks are mapped to N operating system threads. So when you await, the rest of the function may very well run in a different OS thread.
Swift also has async/await, and like tokio it uses multiple threads to run concurrent tasks in parallel (therefore using multiple OS threads).
Scala's equivalent to asynchronous tasks are Promises, which can also run in parallel, as I understand it.
Kotlin doesn't have async/await, but it has a similar concept, coroutines, which are basically a superset of asynchronous tasks. While Kotlin's coroutines are single-threaded by default, there is a multi-threaded implementation, enabling truly parallel coroutines.
Go also uses coroutines (which it calls "goroutines"), which can use multiple threads.
C++ will soon get coroutines as well, which support multithreading to run coroutines in parallel.
My Fairphone is 4 years old, it has been dropped on the floor (even hard surfaces like rocks and asphalt) countless times. It still works and looks like new. It has a protective cover that covers the edges, but not the screen or the back. It still survived all these years without a scratch.
You can hire a pilot to fly your privately owned plane or helicopter. If it crashes, the pilot dies doing their job, even though it's not a commercial flight.
To be funny, a joke requires a grain of truth. Absurdity alone doesn't make a good joke.
I've been using Manjaro with KDE for a few years now. It works smoothly, I never ran into any issues with it.
The
pacmanpackage manager is pretty nice, too, I found it faster and easier to use thanapt-get, and the provided packages are always kept up-to-date. Updating the system (even installing a newer Linux kernel) is very simple and works reliably. So you always have the latest version of your apps, the kernel, and the DE.In the rare occasion that a program is not available in the official repositories or the community-maintained AUR, you can also install
snaporflatpakpackages.And since Manjaro is derived from Arch, you can use the Arch Wiki, which is very useful when you want to set up a database, use the android debug bridge, install another package manager, or do anything else less than trivial.