administrative-scripting-with-julia
dotnet-script
administrative-scripting-with-julia | dotnet-script | |
---|---|---|
7 | 20 | |
160 | 2,592 | |
- | 0.6% | |
5.2 | 6.6 | |
7 months ago | 5 months ago | |
Jupyter Notebook | C# | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
administrative-scripting-with-julia
- GitHub - ninjaaron/administrative-scripting-with-julia: Guide for writing shell scripts in Julia
-
Administrative Scripting with Julia
I appreciate the "Why You Shouldn't Use Julia for Administrative Scripts" section[0] which asked exactly the questions I would have asked.
The choice of (non-Bash) language to write command line utilities is in a bit of odd spot right now. Python is basically almost everywhere installed but the dependency on runtime + venv oddities bring their own set of problems. Java has the same runtime need issues though things might improve with initiatives regarding native binary compilation (though including the runtime may not produce exactly lightweight executables). Perl used to be a hot favorite in this space but I don't think lot of people are writing new stuff in Perl even though it is still present by default almost everywhere. Go is almost perfect here except I don't want to deal with 3x the boilerplate. Personally I think Rust isn't a bad choice (libraries like clap hugely reduce the boilerplate) but the learning curve makes it a harder sell (even though for basic utilities, I don't think there would be too much wrestling with the borrow checker). Another choice that comes to mind is Nim; I think it is very well positioned except a lot of people don't know even about it so its a hard sell + even among those who know, everyone is looking at everyone else to take the initiative to adopt it in a corporate environment at a non-trivial scale.
[0]: https://github.com/ninjaaron/administrative-scripting-with-j...
-
Lisp or Julia
My question is actually not what everyone uses, but what is best suited for the task. Those two things are, of course, almost always different, because the average person is anything but smart. Here you see that Julia is indeed better suited for handling data than Bash: https://github.com/ninjaaron/administrative-scripting-with-julia And here you see that Lisp will be the best scripting language for certain persons: https://quotepark.com/quotes/1879617-larry-wall-is-lisp-a-candidate-for-a-scripting-language-whil/ Obviously, if you don't have in-depth experience with both languages, you don't have to answer my question.
dotnet-script
-
Google ZX – A tool for writing better scripts
Especially because these languages are only one package/install away and not two. I don‘t really get for which audience is targeted here. Usage in JS projects maybe, but then why not write it as npm tasks. ..
I‘m playing around with dotnet-scripts [1] at the moment (C# shop mainly) and this has the same issue imho. The reason why I looked into it was because we have developers not accustomed to bash etc. I still find it silly and would rather use ruby so…
[1] https://github.com/dotnet-script/dotnet-script
-
Simple PowerShell things allowing you to dig a bit deeper than usual
>making powershell actually enjoyable to use
My solution was to stop using it and instead use dotnet-script
https://github.com/dotnet-script/dotnet-script
Scripting with the full power of modern C# has been a huge win for me. And same/similar scripts will work on Windows/Linux/Mac. As my work language is C#, I don't have to context switch to another language for scripting.
-
REST API using C# .NET 7 with MySql
I usually create a container that has all database migrations and tool to execute those migrations. I name migrations as [yyyyMMdd-HHmm-migration-name.sql] but please feel free to use any naming scheme, keep in mind how the tool would order multiple files to run those migrations. I have also added a wait-for-db.csx file that I would use as the entry point for database migrations container. This is a dotnet-script file and would be run using dotnet-script. I have pinned the versions that are compatible with .net sdk 3.1 as this the version roundhouse is build against at the time of writing.
-
Is it possible to create executable from file instead of project, like java or go?
thanks, this is very good idea too, and with dotnet-script we can publish executable out of the script!
-
dotnet script script.cxs says no dotnet found
It sounds like this is feedback for the author of the dotnet script tool: https://github.com/dotnet-script/dotnet-script
- Administrative Scripting with Julia
-
C# vs Python
Yes, you can have single-file scripts too. There might be more options to achieve this, but the one that I use is running *.csx files via the dotnet-script (https://github.com/dotnet-script/dotnet-script).
-
Why Functional Programming Should Be the Future of Software
I do agree.
I think .Net has got it right. And dotnet-script [https://github.com/dotnet-script/dotnet-script] has been a game-changer for me with a REPL-like experience for unit testing and writing command-line utilities.
- Is PowerShell scripting worth learning?
- What is the/your current/popular choice for dotnet c# scripting ?