Microsoft's own machine learning repo "Project azua" ( https://github.com/microsoft/project-azua ) runs on JAX. Let that sink in.
Windows is the afterthought.
Let that sink in...
121–130 of 349 posts
Microsoft's own machine learning repo "Project azua" ( https://github.com/microsoft/project-azua ) runs on JAX. Let that sink in.
Windows is the afterthought.
Let that sink in...
Are symlinks on Windows really such a big issue? I’ve never heard of projects using symlinks in their tree. If Windows developers are complaining about you doing something unusual, why is it their fault?
Windows is horribly hard to learn. In a day, i learned how to create file, directories, change the stats on those, execute diff and patch, an do weird string modifications with grep and cut (and learn to commit and push with git). First day on an UNIX machine. First work week on a windows machine (at that time, i had already built a LFS): we have those two project with two different version of (proprietary JS front framework) and (weird php framework). Those don't use the same version of mycrypt.dll (and others, but this one i will remember for at least two dozen year). With the support of non-intern engineers including a windows DBA, it took us a week to manage to install the two different versions.
A week prior, i was linking to a previous version of Ruby for my RoR app (it was around 2013).
But since, i really respect windows sysadmin, they are the best of us. I will just never, ever want to work on a windows server again. I like learning, but putting that much effort for this little rewards? not worth.
Typical UNIX FOSS rant, not taking into account all the development workflows on Windows.
It is. I generate the Windows executables for a program by cross-compiling Rust on Linux. Then test with Wine. The Rust crates are cross-platform enough that I don't have to special case platforms. This is easier than having a Windows machine. The only current headache is that there's no pure Rust bundler, to make ".msi" or ".msix" installer files. If you dump the legacy OS stuff, it gets easier.
I tried doing that, and then found that my test suite passes on real Windows but fails on Wine, because it uses APIs which Wine doesn't implement correctly (or at all).
Earlier quoted context omitted.
Good news is winget will soon support single binaries so that is one option.
Can you link to info about this? I can't find much in a quick Google search
I agree that symlinks cause more trouble then is needed on any platform. Sadly, only Node really likes to use them to optimise the store of packages Personally, I don't have major issues compiling things on Windows for other platforms (macOs, Win32, Android, Linux). Only awkward thing is designing UIs
Microsoft's own machine learning repo "Project azua" ( https://github.com/microsoft/project-azua ) runs on JAX. Let that sink in.
At this point Windows as a primary development platform is essentially dead. With a few exceptions (DX) nearly everyone writes code for Unix/Linux and then cross-compiles for Windows. Windows is the afterthought. Let that sink in...
Now try building a "portable" binary that runs on a version of Linux older than yours.
Use ‘zig cc’ and target the appropriate glibc.
Microsoft's own machine learning repo "Project azua" ( https://github.com/microsoft/project-azua ) runs on JAX. Let that sink in.
At this point Windows as a primary development platform is essentially dead. With a few exceptions (DX) nearly everyone writes code for Unix/Linux and then cross-compiles for Windows. Windows is the afterthought. Let that sink in...
That's a very bold statement that I suspect is far from true.