6 ms·
You literally just run: > npx create-next-app@latest Press Enter a few times for default settings and voila, you have a hello world app up and ready to run.
by M4v3R 3y ago
You literally just run:
> npx create-next-app@latest
Press Enter a few times for default settings and voila, you have a hello world app up and ready to run.
- christophilus 3y agoJust because it’s a one liner to install something doesn’t mean you aren’t installing a big, complex, over-engineered thing.
- tail_exchange 3y agoSure, but if you want to use React to build a Hello World app, the framework is not the one I would blame for overengineering.
- uxp8u61q 3y agoLook at your computer. Are all its parts and pieces strictly necessary to display the text "Hello world" on your screen? No. Why don't you throw it away and buy something simpler, then?
- laputan_machine 3y ago[flagged]
- bentlegen 3y agoReact is a general purpose web framework, and is routinely used to do more than serving static documents. I would argue it was never even designed (originally) for that use case. And yet because it can, we have to have this tiring endless debate.
- uxp8u61q 3y ago> Because they are called "libraries" for a reason, it can do much more than "Hello, World", and they are routinely used for much more than that. There you go.
- laputan_machine 3y ago> When you're writing a specific program, e.g. it's never going to be anything more than "Hello, world!", why would you use the fattest framework when you can write it in plain HTML? Emphasised the parts I think you should re-read
- uxp8u61q 3y agoSorry, I guess I disregarded it because I figured we were talking about serious programming, not literally "Hello world". And if you're writing a single "Hello world", HTML is overkill. Make a free website on a random platform and literally just write "Hello world" in their WYSIWIG editor. Or hell, just serve plain text with "Hello world" inside, browsers will render it just fine.
- satvikpendem 3y ago> why would you use the fattest framework when you can write it in plain HTML? I mean, don't use "the fattest framework" then, who is forcing you to use it for writing hello world?
- laputan_machine 3y agoAs you get more experienced in programming you'll inevitably inherit projects that you didn't have any say over, when that time comes come back to this comment, I'd be interested to hear if you still feel the same way.
- satvikpendem 3y agoI have inherited such projects. But it seems like you're talking about code that is no more complex than hello world, as you've quoted, so it wouldn't be too complex to do in any language or framework. Now if you do inherit a larger project that you don't like, well, you either work on it or you switch jobs.
- 3y ago
- butlike 3y agoAs someone who can juxtapose OS X 10.5 to the latest Ventura release... believe me, I wish I could.
- Merad 3y agoI find it curious that we always see these opinions expressed about front end frameworks, but no one seems to have much problem with all of the complexity in back end frameworks like node, Python, Java, .Net... I have a sneaking suspicion that people are just more used to having complexity hidden from them behind a framework install, whereas front end puts everything front and center since it's all delivered to your project via npm.
- zepolen 3y ago- npx create-next-app@latest - npx: command not found - install node / npx - npx create-next-app@latest - realise your node is too old - install nvm / node - npx create-next-app@latest - answer a bunch of questions - npm start - get an error: Error: ENOENT: no such file or directory, open '/tmp/my-app/.next/BUILD_ID' - npm run dev - hello world in browser
- mavamaarten 3y agoThis is why web development (and python, don't get me started on the pain that is python) is not for me.
- satvikpendem 3y agoWhat do you code in? For any language if you don't have the toolchain set up, obviously it'll seem laborious to install it, it's not a knock on the framework used on top of the toolchain.
- bombolo 3y agoBut python is already installed on most linux systems
- satvikpendem 3y agoWhich Python, 2 or 3? How will you handle local versus global dependencies? Will you use pip, conda, virtualenv or something else? How will you package up the code and/or executable? It's not as simple as shipping code to the user.
- bombolo 3y ago[dead]
- mavamaarten 3y agoJava/Kotlin. You define where to get the dependencies in a simple script, you define the version of the build tools, a wrapper script fetches the build tools (gradle) for you and that's it. Everything is neatly cached system-wide where possible and on a project-level otherwise. No conflicts, no shenanigans.
- renegade-otter 3y agoWith 700 dependencies, 200MB, and a massive security surface.
- mickael-kerjean 3y agothat's still better than CRA, to make the point a few weeks ago at work, I counted > 800 dependencies and 6 high security vulnerabilities warnings. If facebook can't get their shit together, who can?
- satvikpendem 3y agoNone of that gets to the browser.
- renegade-otter 3y agoThe whole point is to have JS on front-end and beck-end, right? What is serving the JS? Isn't the server Node? And large security surface means just one compromised package is required to get on the server side. If an npm update gives you security warnings after a few weeks of a vanilla project just sitting there, something is very wrong.
- satvikpendem 3y agoSure, you could say the same about any language too though. I've used static site generators in Rust too, or Python, it's the same problem. People still use them because the benefits outweigh the minute risk of being compromised.