11–20 of 61 posts
it's pretty crazy that this article only mention hyper or the built in vs code terminal as it's two recommendations, when excellent terminals like alacritty, kitty and terminator exist and aren't written in javascript
I have been enjoying Foot Terminal of late - minimal, fast, Wayland-first. Not sure about complete feature-parity, but I personally did not miss any feature of Alacritty. https://codeberg.org/dnkl/foot
> 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.
> It takes years of practice to become a terminal guru, but here's the good news: we can take a shortcut. We don't really need to know 98% of the stuff you can do with a terminal. If we focus on the most-important critical fundamentals, we should be able to become comfortable with the command line in a remarkably short amount of time.
There's very little in here that is _unique_ to front end developers. This is more of an introduction to the terminal article. You have a web background and so perhaps wanted to frame this with that context but I think this is better off with a title of something more akin to `Introduction to the Terminal`. The only thing in here related to web is the `npm` command. Everything else, git, terminal tabs, meaning of `$`…
POSIX-1.2017, man7, where Ubuntu man pages are online and other distro manual pages, macOS man page differences, understanding shell built-ins vs commands, etc. Yeah. I don’t think I have ever once seen a blog article point to primary sources. MDN, for example for web developers, not a primary source. Sometimes I wonder if people ever ask themselves how people answering questions on Stack Overflow or people writing M…
I just read MDN and W3 for like a month while making slides, then played around for a bit with all I learned on an example app. No one had taken the time to do that before I guess?
> 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.
it's pretty crazy that this article only mention hyper or the built in vs code terminal as it's two recommendations, when excellent terminals like alacritty, kitty and terminator exist and aren't written in javascript
There's very little in here that is _unique_ to front end developers. This is more of an introduction to the terminal article. You have a web background and so perhaps wanted to frame this with that context but I think this is better off with a title of something more akin to `Introduction to the Terminal`. The only thing in here related to web is the `npm` command. Everything else, git, terminal tabs, meaning of `$`…
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"?
Then learn CSS.
Then learn Javascript, and realize that Javascript can be used to write HTML and CSS at runtime. The console is just Javascript in interactive mode.
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"?
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 in the dev console?