An interesting thing about this is that even for jets the direction is high bypass ratio turbofans as they are more efficient. Meaning even there props are more efficient.

And presumably debugging is a lot more work as AI is just a fancy template lookup and has no idea what it is doing.

Basically quickly generate crap code then hope you can debug it into something acceptable.

I always thought writing and debugging code on VS was fine. Where I never liked Visual Studio was building especially cross-platform building or just using special tools etc. Fankly just give me an editor and Make, but make sucks on Windows due to slow process startup. But I do like the VS debugger.

• Security Now.
• The Register
• Sashdot
• Lxer

I also subscribe to the Debian Security Announce email list.

Also using RSS with Youtube now. Muxh better way to follow Youtube channels.

Me, not a purist, but heavily prefer FOSS. My wife does use a proprietary Linux scanner app but that is it. On Android about 14% of my apps are proprietary.

Actually, it was not obvious. CSS is not a term I have heard for proprietary software. Cascading Style Sheets … yes.

Low blood pressure can cause this too especially if your on meds that can lower blood pressure. For me a cup of coffee, working out in the morning, and being careful when I take those meds helps.

NoScript browser extension is one example. DNS filtering is another.

In college, one of the best courses I took was Programming Languages. It covered a smattering of languages illustrating different approaches and methods. Maybe a week or so on each plus you had to write some code in each.

Android is Linux using SELinux for user confinement plus users do not have root access and it uses verified boot to enforce all that.

Keep in mind the system meaning root can do anything it wants. User apps cannot though they can ask the system to do certain things for example by SUID executables for example or other methods. Not sure how android actually does it.

What is different about Android is owner, user, work profiles, and the new private space structure. Not sure low level how that is done but presumably combination of different users, SELinix, and different encryption keys.

I think they said Pandoc. I have used that too some.

Bluefish.

By the way. The only files you mentioned I am less sure about are configs. Specifically if these configs are system specific, probaby only examples or templates should be included but the configs should be built by the build process on the target system.

Edit: It should contain tests. Running some equivalent to ‘make check’ on the target system is pretty standard.

Edit: Not sure what .github folder tree file contains so cannot say.

If your talking about a source distribution archive, generally it is the project in the ‘distclean’ state. This is decribed in GNU documentation. I think for GNU Make. Not sure if the git specific files should technically be included but maybe these days they should. The ‘distclean’ state is generally the same code as from the VCS tree but with hard to build files pre-built but probably not platform specific files. The ‘maintainerclean’ state is basically the clean VCS snapshot nothing pre-built.

Edit: The reason to prebuild some not platform specific files is to minimize the tools needed for installing from source.

Keep in mind that this is probably very instance dependend. I use Beehaw which generally does not tolerate this sort of thing and this expectation is stated very clearly. For us down voting is not even possible. We also do not federate with nodes that cause the biggest issues. So there are things that can be done but it is not perfect and has consequences.

Just mentioning.

Edit: Even with that, there has been discussion of Beehaw leaving the threadiverse due to these issues and lack of mature moderation tools. Not sure where that stands.

Keep in mind that you actually do have control over what you and your reports use for software and their license compliance. Otherwise not your problem. Beyond that, it is an issue for legal anyway and management.

deleted by creator

Sorry, the most important thing about a language is readability and maintainability. Also speed writing bug free secure code is next. Speed of execution and sometimes memory use is next.

The order may vary depending on project.

By the way, I would not consider logging in via ssh and running a bash script to be insecure in general.

However taking uncontrolled data from outside of that session and injecting it could well be insecure as the data is probably crossing an important security boundary.

I was more thinking of the CGI script vunerability that showed up a few years ago. In that case data came from the web into the shell environment uncontrolled. So uncontrolled data processing where the input data crosses security boundaries is an issue kind of like a lot of the SQL injection attacks.

Another issue with the shell is that all proccesses on the system typically see all command line arguments. This includes any commands the shell script runs. So never specify things like keys or PII etc as command line arguments.

Then there is the general robustness issue. Shell scripts easy to write to run in a known environment and known inputs. Difficult to make general. So for fixed environment and known and controlled inputs that do not cross security boundaries probaby fine. Not that, probablay a big issue.

By the way, I love bash and shell scripts.