OS stands for "Oh Shit!"
If your goal is developing Android apps, then start with mainstream official tutorials. Install the Android SDK and follow the tutorial. That's your intro.
Then, get the source code of a FOSS Android app that you use, and build and run that. Then make some changes to play around with it, to see how stuff is structured, relates, and changes.
On that project, with the change history cloned, or on their repository web interface, look at some changes that were implemented. A bug fix or new feature. How did they implement it? Where did they [have to] change what?
Then look if the, or a project you use, has some open tickets with labels for beginners or looking for contributors. Explore those. Try to resolve them.
Python’s major pro is its simple, straightforward syntax, which excels at data handling. This has made it popular with novices of all shades […]
For first-timer coders, Python is easier to learn, understand, and adapt than many low-level programming languages […]
Is python being easy to learn actually true? I can see it being easier than low-level programming. But there's other alternatives like C# and Java that certainly seem much better and easier to me. Especially when you consider the ecosystem around only writing code.
Plus, the Python language is a steadfast feature in the desktop Linux software landscape. It’s preinstalled on most Linux distributions, boasts extensive library support, and can be used to fashion very cool (as well as very basic) Qt, GTK, and other toolkit UIs.
It's certainly available, and more readily available on Linux. The whole v2 v3 mess was lackluster. But I guess preinstalled is convenient, and more accessible than installable Java or whatever.
I've never seen JavaScript or Python popularity as evidence or correlating with actual qualities. More with a self-promoting usage. Python was being used in science, then in AI, then AI became popular. To me, it seems like a natural propagation consequence more than simplicity or features over other frameworks and languages.
eeew (/s)
I have a dislike for both of them. Well, for JavaScript mainly the server-side part. I'm fine with it on web scripting, where it's the only native one.
Notably for CPU only. And on other platforms they already did.
Broadcom would like to clarify that while using KVM for the CPU virtualization, they will continue to rely on all of the existing VMware virtual devices for graphics and other functionality. Also on both macOS and Windows they have migrated to the native CPU virtualization frameworks.
Do you not have tools you use, or miss, in your normal PC use? I have so many things I would like to have and do or finish. Things come up naturally.
Outside of brainstorming with a friend what projects we could work on together, where I was able to make use of my backlog, ideas, and wishes anyway, I never had to think about what I want to make.
Can be tools and apps or libs you use, contribute to or implement an alternative that may or may not fit you better, or tools you're missing. I've made various stuff for data conversion, archiving, video cutting, hosting/config setup, checksum generating, hex viewer, …, exploring new tech, …
I found it hard to follow despite C# being my main driver.
Using ref, in the past, has been about modifiable variable references.
All these introductions, even when following C# changes across recent versions, were never something I actively used, apart from the occasional adding ref to structs so they can contain existing ref struct types. It never seems necessary.
Even without ref you use reference and struct types, where reference content can be modified elsewhere. And IDisposable for object lifetimes with cleanup.
Have you considered creating a ticket called "Can't ask questions without joining discord"?
Do you think it would have more answers if it were on GitHub discussions?
I'm not familiar with their products and product names, so I had to look them up, sharing that here, including the other two free non-comm mentioned in the blog post:
- Aqua: test automation IDE (various tech)
- Rider: .NET and game dev
- RustRover: Rust IDE
- WebStorm: JavaScript and TypeScript IDE
Release must be documented
It's not a must [unless you put it into a contract], it's a should or would be nice
Many, if not most, projects don't follow a good, obvious, transparent, documented release or change management.
I wish for it, too, but it's not the reality of projects. Most people don't seem to care about it as much as I do.
I agree blind acceptance/merging is problematic. But for some projects (small scope/size/personal-FOSS, trustworthy upstream) I see it as pragmatic rather than problematic.
The abstract:
Two critical and interrelated questions regarding the design and study of programming languages are:
- What does it mean to design a programming language? and
- Why does minimal demographic diversity persist in the programming language community?
In this paper, we present feminism as a philosophical lens for analyzing the programming languages field in order to help us understand and answer the motivating questions above. By using a feminist lens, we are able to explore how the dominant intellectual and cultural norms have both shaped and constrained programming languages.
A key contribution of this analysis is the explanation of how marginalization in the programming language community limits the intellectual and demographic makeup of the field.
We see this paper as an invitation to everyone in the programming languages field to deepen our collective understanding of the forces shaping our field. Our goal is to illustrate opportunities for more inclusive practices that will introduce greater diversity to the design of programming languages and the demographic makeup of the programming language community.
LOL
Even with a lot of buttons available, good videogame controls are simple and narrow. Natural combinations add depth without overcomplicating things.