21–30 of 61 posts
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?
It took me a bit to get the settings right to mimic zsh/oh my zsh but now it's fine. It's just slower than mac/linux.
> It takes years of practice to become a terminal guru And that's where I stopped reading. Point is, you absolutely need not become a terminal guru to use any of these web frameworks.
He said it was hard to learn everything. He didn't say you have to learn everything.
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?
Linux and free and open software is what gave birth to the web, and so quite naturally working with it evolves better and more naturally there.
Bill Gates and Windows famously absolutely missed the boat on the Internet nearly entirely. And yes, to this day they're still trying to catch up -- this is evident in their extremely late realization that they were never ever going to beat Linux at this. Hence WSL. (the Linux Subsystem for Windows :) )
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?
Meanwhile the internet was born and raised on Unix and had a competent (not perfect) design for terminals and shells.
The Windows terminal folks have done a bang-up job trying to make up the deficit, and mostly succeeded in the last few years. But it takes more than tools, it takes mindshare.
Was never interested in powershell, but there are other alternatives from WSL, like git-bash and the yori shell, both of which I recommend.
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?
NodeJs is not great on windows because the packages/modules model uses many tiny files and the Windows filesystem, NTFS, is extremely slow for this kind of load. Another problem is compiling C/C++ NodeJS dependencies on windows. It’s possible but few people cares about it and it’s often a source of issues. And the last issue are the windows specific bugs in various packages.
The community that write the nodejs packages kinda doesn’t care about windows, and has no reasons to since WSL.
I'm kind of trying to go the other way. I am amazed at how productive great front-end/js-first developers are with even just a browser console --- but I am totally flumoxed by this environment, and have trouble sinking my fingernails into the first ledge on that learning curve. Is there a "terminal developer's guide to front end"?
I use the browser's dev console to try out short JS snippets or for simple on-page scraping. (for longer JS as a scratchpad I use https://runjs.app ). The browser's dev console gives you access to the current page's DOM, plus anything you can do in JS. So stuff like `document.querySelectorAll(".foo")` works. Also `fetch()` works within the page's context. Apart from that, what are some other useful things one can do…
>> other useful things one can do in the dev console?
There just seems to be a suprising amount of built in stuff in the browser that does more than rendering text/layout.
I participated in some interesting work at a hackathon a while ago that used a web audio component to signal back and forth between various laptops and phones. It was mostly getting hacked together in the browser dev console.
(I'll come back with some code if I can find it...)
EDIT: OK, here it is: https://github.com/cantino/ultrastound
Honest question: Why is web development such a shitshow on Windows that that every single 'tutorial' like this doesn't even attempt to make it work, and instead just immediately directs Windows users to WSL?