← Back to context

Comment by bilekas

16 hours ago

Am I just getting more grumpy in my old age or is every new framework just complete bloat ?

I wanted to give it a try, but I need to install bun, a new js runtime, okay fine, why not. Javascript needs more runtimes after all.

Then I need to install `nuekit`.. globally.. Okay...

Now I need to run an obscure command 'nue; which I didn't know I installed. `nue create simple-blog`

Then it tells me to follow the tutorial docs, great. But I need to start writing YAML.. Losing patience now.

My relief comes when I see :

> Nue is not currently tested or developed under Windows, so use it at your own risk.

Well I guess as a Windows user I can't have a 'Standards First Web Framework'.

Think I'll stick to what actually works instead.

10 comments

bilekas

Reply
ezfe  14 hours ago

I had you until the last line.

Windows causes so many problems for me in a full stack development role because people come in and have trouble installing things, etc. and nothing works properly.

I'm not surprised this app doesn't support Windows, I certainly wouldn't bother putting that time in myself. You can have a cross-env but everything else should just work or it's not my problem.

  • WorldMaker  12 hours ago

    Node, Deno, and Bun are all great on Windows and all work the same way on Windows they do anywhere else.

    Python is tiny bit more challenging to install. .NET is lot less challenging for the most part but has a few Windows install "quirks" now due to the frozen version bundled with Windows. Both are generally great on Windows once properly installed.

    Plenty of developers do full stack development on Windows. It's often extra work to break Windows development than to support it.

    (Also yes, Ruby is terrible on Windows, Swift is getting better, try to use task runners that aren't (Ba)sh scripts.)

    • andrewmcwatters  11 hours ago

      It's fundamentally extra work to support Windows when the rest of us are writing software for POSIX environments. Whatever extra work you think it takes to break Windows development is because others before already ported first POSIX-supported work to Windows.

      Node, Deno, and Bun, and all their contemporaries in other programming language ecosystems are targeting POSIX first, and then often times forcing those same APIs to behave the same way on Windows.

      That's why. Most full stack web developers are not doing things in a Windows environment.

      2 replies →

mossTechnician  15 hours ago

I think this is completely valid. From the title ("standards-first") I'd assume it would stuck to minimal third-party addons and use standards-compliant JavaScript as much as possible. Why not JavaScript for configuration, for example?

As a side note, and not to excuse lack of Windows support, but: I've switched to WSL (Linux) for development on Windows. Coupled with Visual Studio Code, the results are much faster than when I used the Windows terminal directly.

smt88  13 hours ago

> Well I guess as a Windows user I can't have a 'Standards First Web Framework'.

Windows has had a Linux subsystem for years. This should not be an obstacle for you anymore.

andrewmcwatters  15 hours ago

My big fat stink test is if I need tooling at all.

Do I need npm or another utility? It probably stinks. Do I need to build something? It definitely stinks.

    # Create a website
    nue create simple-blog

Stinks all around.