Will JavaScript type annotations kill TypeScript?
The creators of Svelte and Turbo 8 both dropped TS recently saying that "it's not worth it".
Yes: If JavaScript gets type annotations then there's no reason for TypeScript to exist.
No: TypeScript remains the best language for structuring large enterprise applications.
TBD: The existing user base and its corpensource owner means that TypeScript isn’t likely to reach EOL without a putting up a fight.
I hope they both die. I mean, if you really need strong types in the browser then you could leverage WASM and use a real programming language.
I don’t know and I don’t care.

Tutorial: Customize Your Terminal OG Style — No Libraries or Plugins!

Mar 16th, 2018 1:00pm by
Featued image for: Tutorial: Customize Your Terminal OG Style — No Libraries or Plugins!

Coders live in the command line. We use terminal all day, every day, no matter Which Of The Things we are building, or fixing, or banging our foreheads on our ergonomic desks over. So it makes absolute sense to tweak the terminal environment to make it comfy and liveable. Consider how, for example, running brew install (whatever) delivers its results in color-keyed message and instructional text. This not only renders the text physically easier to read, but also makes it much quicker for us to grasp the meaning and act on it.

Of course there are all kinds of libraries and plug-ins out there designed to let us redecorate the terminal to our hearts’ content, but — ultimately — how much fun really is there to be had by installing someone else’s pre-packaged design choices? With a few simple exercises in command-line-fu, our next bash script can be colorfully formatted and way more user-friendly — all with zero config, and installing exactly zero plug-ins.

Note: I’m assuming bash, here. I’m so not getting into any zsh-vs-bash-vs whatever debate. Bash is the default shell on virtually every UNIX system, meaning it is highly portable and that, once you get used to it, you can use it practically everywhere. It all comes down to personal preference, and bash is mine. Also, bash is the default shell on Mac and most Linux systems; if you’re a Windows user, I got nothin’ — try checking out Cygwin for creating that beautiful bash experience on your box.

Say My Name

Your prompt — the text that appears before your cursor in bash, like Leons-Macbook-Pro:~LeonJenkins$  — is actually defined by a variable called PS1. You can inspect the current value of this variable by simply typing ‘echo $PS1’ into your terminal prompt (‘echo’ tells the terminal to simply print out whatever follows). Be warned: you’re going to get back some chicken-scratch looking escaped characters, similar to Regex. (Wanna learn regular expressions, which is a universal shortcut language for text all its own? Sweet! Check out this TNS regex tutorial)

If you’ve never before messed with your prompt, PS1 is most likely going to return ‘\h:\W \u\$’ — a string of escaped characters representing hostname (\h),  working directory (\W), and username (\u). Not exactly pretty, is it?

One of the very first useful pieces of coding advice I ever received, upon venturing into the previously uncharted waters of the vi command line text editor, was to change my bash prompt to something brief and memorable. So we are starting by simply getting rid of hostname — most of us know darn well which host we’re using, thanks.

  1. Locate ‘.bash_profile’ file — you may have to create one from the command line in your username filepath
  2. Open it in your favorite text editor. If it’s blank, that’s ok.
  3. Find wherever ‘PS1’ is, if there are values in .bash_profile and change them to the following.  If there are not, simply type the text entirely.
  4. Save the changes and inspect terminal (you may need to restart terminal for changes to take effect).

Having set your prompt to current working directory and your username, then an arrow (instead of the classic ‘$’, just for fun!), you should see:

From here, you can play around with changing username to something truly short and sweet — for example, turn “LeonJenkins” into simply “Leon”. (Obviously, you should substitute your own username and variation here, unless you happen to be THE Leon Jenkins. In which case, please PM me).

Serious prompt customization is outside the scope of this guide, but you can learn plenty by simply messing around with it. If you’re serious about rolling your own, the Bash Reference Manual’s Controlling the Prompt is a primer for escape sequences.

Color Me Beautiful

By default, terminal is a no-nonsense monochrome environment.

Fortunately, bash got built-in color codes!  For example, ‘\e[1;31m’ is the code for red, which can be combined with other text or commands in terminal:

Unfortunately, once you’ve told terminal to go red, it stays red. You can type “reset” to revert to the default monochrome… which clears the color, but also the entire screen.  Or, you can add ‘\e[0m’ — the color code for white — to the end:

Yes, this is cumbersome. So, remembering that bash is a place we can write scripts to do stuff, let’s bring in some variables. There are all kinds of choices you can assign: font color, background highlight color, bold, italic, underlined — even blinking text, if you want to get obnoxious with it. However, to stay with our simple example, assign a variable with the name of your choice, then the equal sign with no spaces (important), and then $’code name here’ — codename must be inside single quotes — to apply styles to terminal text. Mix and match!





This is an extremely basic example, obviously, with the point being you can drop these variables into any shell scripts you write and go to town. The easiest way is to copy a standard cheat sheet of color and font style codes into your .bash_profile as variables, and you can call on them from then on to your creative, colorful heart’s content.

Second that Emoticon

Or, as we call ‘em now, emojis. (When I was a kid, we made our OWN emojis from ASCII characters, and we LIKED it).

This is a bit trickier, in that it depends on your operating system, but couldn’t be easier in practice: just copy/paste the emojis directly into terminal. (You can also assign your faves to variables in your .bash_profile, for fast shorthand access).

Completely Option-al

Ok, so these aren’t actually visual effects, but rather a couple super-handy command line shortcuts I’ve come to really love. These are ways to alter the Readline capabilities built into bash, that somehow nobody ever mentions when you first start traversing the terminal. Maybe because they’re so useful and obvious that we immediately internalize and take them for granted? In any case, if you are new to all this, get thee immediately to that Readline link above and see all the other sweet CLI tools.

There is $set show-all-if-ambiguous. You know how you can start typing a filepath name and tab to autocomplete, right? Or at least attempt to, but tabbing too early rings the Dreaded Ding of Shame. This is called the completion function. Terminal default for this show-all-if-ambiguous option is “off”; switching it to “on” (i.e.just simply open terminal and type it in if you’re totally new to this) means that words with more than one possible completion will list all matches immediately, instead of ringing the bell.

Also, try: $set completion-ignore-case on. The default is “off” for this. Setting it to “on” allows filename matching and completion while ignoring upper or lower case. Meaning that camelCase is no longer going to cause camelCursing. At least as much.

Photo by Ash Edmonds on Unsplash.

Group Created with Sketch.
THE NEW STACK UPDATE A newsletter digest of the week’s most important stories & analyses.