If you type a lot for a work, spending the time and money for better tooling is not only healthy but should be encouraged. Unhealthy, is when you try to track down an after market Key Cult for $2,000 and spend $500 on switches because you feel like you have to try them all.
Readit Newschoiway commented on My Unhealthy Relationship with Keyboards jackevansevo.github.io/my... · Posted by u/jandeboevrie
choiway commented on Elixir – Why the dot when calling anonymous functions? dashbit.co/blog/why-the-d... · Posted by u/weatherlight
For those of you who are interested by Elixir but find the lack of static typing an issue here are somethings to be aware of:
1. Static Typing is planned and currently the top priority of the team
https://elixir-lang.org/blog/2022/10/05/my-future-with-elixi...
2. There is a type checking tool
https://github.com/jeremyjh/dialyxir
3. You can go a long way with pattern matching and guides in the meantime and have alot more guarantees that a typical dynamic typed language.
I do like me some static typing but it took me a while to realize that the guards and pattern matching provides runtime guarantees and not just compile time guarantees.
choiway commented on Apple reveals Vision Pro, a AR/VR headset unlike any other arstechnica.com/gadgets/2... · Posted by u/thx-2718
Feels more like a Lisa moment than an IPhone moment.
You're not missing anything if you can and don't mind building a framework of tools that run long running processes, handle the start up, failure and state of those processes and be able to introspect the status and internal state of those processes in a standard way.
The way isolated processes can be created and managed allows for the "let it crash" ideology in Erlang. For example, when you visit a Phoenix Framework site, you have your own process. If I was visiting the same site and encountered a state that crashed my process your process would be unaffected. The "exception" would only affect me until you ran into the same state that caused the crashed.
If I reported the crash to the developer, the developer could fix the bug and soft start the entire application without affecting your process. This isn't possible because of the language per se but really because of the entire Erlang ecosystem around fault tolerance.
*edited for more stuff
choiway commented on Reasons the banking crisis isn’t a repeat of 2008 chase.com/personal/invest... · Posted by u/s-xyz
Just because a cookie doesn't crumble the same way doesn't mean the cookie isn't crumbling.
Unix Mercenary, LLC is brazenly on the nose.
choiway commented on Clever uses of pass, the Unix password manager vitalyparnas.com/guides/p... · Posted by u/smartmic
I got stuck at init
1. Install the .NET 6 SDK: https://dotnet.microsoft.com/en-us/download/dotnet/6.0
2. Terminal ,pick a folder, `dotnet new wpf`
3. `dotnet run` and you have an (admittedly empty) hello world app
It's telling me it took 1.5s to build the app.
Want to publish the app?
`dotnet publish -o ./publish -r win-x64` which takes a bit longer as it has to download some runtimes (60 seconds max, then cached). Zip up the resulting folder and ta-da you have an application. Just unzip and run the .exe.
If you want a single-file exe (as in completely statically compiled without self-extraction) that's a bit more advanced and requires a few properties in the csproj to configure how to handle native assemblies that expect to exist on disk. If you want it to have no runtime dependencies, add `--self-contained`
This is the best response I've seen to the question: "What's the easiest way to get started developing a native Windows app". Better than anything Microsoft has put out.
Isn't WPF getting phased out tho?
#1 is the #1 complaint. In 2021, I still don't know what Windows framework I should invest my time in if I want to develop a native Windows app.
choiway commented on Our journey in dropping the ORM in Go alanilling.medium.com/exi... · Posted by u/henvic
Took me a while to realize that ORMs are fine as long as you don't use them for the "R".