CSharpRepl: C# REPL with syntax highlighting and intellisense
fuqua.io
fuqua.io
If any other REPL can get to a point where it can rival LinqPad in functionality then it'll be an absolute winner.
The key features linqpad has that I'd need from any replacement:
* Securely store secrets
Util.GetPassword prompts the user for the password if it's not in it's store. Leverages the windows user credential store.
* Keeps the process running
This is absolutely key, it keeps alive the process even after the script has finished, so you can easily attach a debugger / profiler to it when the script isn't running, then start the script again. It also means you can use AppDomain.CurrentDomain.SetData to cache expensive setup if you're trying to profile something.
* Quickly switch between expression / statements / program mode
It'll intelligently work out if you've written a single expression vs multi-line statements, and you can switch to "program" and it'll wrap what you've done so far in a Main stub.
* Easily define default App.Config files, default namespaces, default nuget packages.
After finally getting a fiddly setup working, there's a "Use as default for new queries" button which is very convenient. Also the "clone query" functionality is similarly useful for copying not just the C# text but all the background namespace declarations, references, config, etc.
And that's about it. I barely use the database connection and exploration side, but I do use it daily for hooking into DLLs to quickly test changes to our internal projects.
Made this video to show LINQPad and getting OAuth tokens from the Spotify api.
C# is my favorite language because is relatively easy to write something without having to write a lot and there's relatively little boiler plate and ceremony.
On top of its imperative foundations there were added some functional capabilities that are integrated very well.
What is als likeable is there are a ton of learning materials for those who are interested, a ton of libraries and frameworks and the community being helpful.
Also, C# can be used in about every domain, web backend, web fronted, desktop, small utilities, games, mobile and even microcontrollers.
What I dislike about C# is that every file is also an object and I rather like a less OOP approach.
Also, there are features the community asked for years, like algebraic types and even though people working on the language implementation recognized their importance, they still didn't find their way in the language.
My favorite update to C# would be if it doesn't force so much object oriented workflow. Even C++ lets you work in a procedural way.
Another.NET language I like is F# but I didn't invest much time in it because I don't have where to use it for work.
F# mostly replaced bash/powershell for me.
It's a really nice language to use, I'm quite surprised.
Because I had to check this myself: Monogame is not tied to mono! It claims to support dotnet 8, so it looks suitably current and maintained.
It is annoying that Microsoft had their own perfectly adequate game framework which they binned at one of the transitions https://en.wikipedia.org/wiki/Microsoft_XNA
There is another framework called FNA that I've not used personally but I've heard it tries to match XNA exactly while monogame is a bit more forward looking. So FNA is good for porting forward your older XNA games.
I want to branch out to native stuff like C++ & Rust for memory management stuff, but they don't seem to come close in terms of the reflection abilities or probably the function is there, but just a nightmare to work with.
Anybody have any thoughts/opinions?
Let me write a function without 50 tokens of boilerplate!
public static implicit operator ClassA(ClassB b)
As for the implicit cast, two extra tokens in an uncommon case doesn't seem so bad when you consider all the nice common things like var, the lambda syntax, initializers, pattern matching, LINQ, delegates, etc. etc.
Defining implicit cast operators frequently (especially ClassA -> ClassB) might be a sign that a better implementation is required. In practice, it's not done often.
Agree on unncessary Async suffix. It is a common mistake (it is one) to add it for methods that cannot or will not offer non-async variants.
Note: I’m ignoring <InternalsVisibleTo> csproj property.
2. It encourages everyone to think about nouns rather verbs.
It's not as extreme as java but the smell is there.
I don't really know how else to enunciate it anymore than how I don't like Taylor swift music or whatever.
There a time when class hierarchies are ugly but fine, completely fine, and genuinely a bit dangerous: C# doesn't seem to have an option for the latter
https://github.com/waf/CSharpRepl?tab=readme-ov-file#compari...
Even though it's not as feature-rich as linqpad's Dump() method, personally I find the ability to pretty print any object ("detailed view"[1]) by pressing ctrl+enter really convenient. E.g. try typing in
new Uri("https://news.ycombinator.com")[1] https://github.com/waf/CSharpRepl?tab=readme-ov-file#:~:text...
That might be all you need to fix the F# REPL too.
https://github.com/waf/CSharpRepl/issues/318#issuecomment-21...