macOS deprecating scripting language runtimes, including Python, Ruby, and Perl

Post by snazz » Thu, Jun 06, 2019, 12:04 PM UTC

skohan wrote: post #314

saagarjha wrote: post #287

Earlier quoted context omitted.

If you have a command that doesn't print a new line, the prompt normally ends up on the same line as the output of the last command. iTerm can "fix" this.

See this is where I would rather have my terminal obey the program rather than imposing its own behavior. IMO a good terminal should be extremely minimal, and anything extra should be opt-in.

Post by zwily » Thu, Jun 06, 2019, 12:13 PM UTC

hestefisk wrote: post #304

cynwoody wrote: post #223

Earlier quoted context omitted.

Mac OS versions prior to OS X used ':'. Mac OS X, initially released on 24 March 2001, uses '/', like other Unix-derived systems. Also, like other unices, OS X uses '\n' as the line ending. Prior Mac OSs used '\r' as the line ending. Windows uses '\r\n'.

Similar, HFS+ used to provide the option for case insensitivity. Both things were built in for legacy support reasons during the transition from OS 9 to X, as with Carbon.

Post by Sean1708 » Thu, Jun 06, 2019, 12:17 PM UTC

toyg wrote: post #351

Fnoord wrote: post #293

Earlier quoted context omitted.

> Sure, it’s not a hard engineering challenge. However, installation instructions right now are as simple as “run this one-liner on your terminal”. That’ll have to materially change. It could just as well still remain a one-liner. Every system Homebrew is installed on has Bash installed (not the latest, but still). Instead of > /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/i…

> Every system Homebrew is installed on has Bash installed Ironically, they are also moving from bash to zsh for default shell. Again not an unsurmontable challenge (just make sure the bang is correct in your scripts, bash will likely still be around somewhere in macOS for the foreseeable future) but another little hurdle to mind.

Post by Longhanks » Thu, Jun 06, 2019, 12:23 PM UTC

toyg wrote: post #357

alerighi wrote: post #324

Good thing, python2.7 is deprecated and no longer receives security updates, and a lot of Linux distributions (Arch and Fedora for example) plans to remove it from the main repositories at the end of this year, so having it installed doesn't make sense. Even the perl and ruby version installed is old, and nearly nobody uses perl or ruby at this day. Maybe perl is still used by some programs and scripts, for example T…

> python2.7 is deprecated and no longer receives security updates Let's not go overboard - 2.7 will get security updates and patches until the end of December. > nearly nobody uses perl or ruby at this day. Well, except for homebrew of course, the Ruby-based package manager nearly "everybody" uses...

Post by smashedtoatoms » Thu, Jun 06, 2019, 12:28 PM UTC

nailer wrote: post #336

paulcarroty wrote: post #214

Earlier quoted context omitted.

You can use it, yep, but devtools aren't enough. You'll meet a lot of issues sooner or later. Windows is second-class citizen for Node, Linux or macOS are much better - just share my experience.

Personally I moved to Windows about 2 years ago, have been developing node all day during that time and deploying on Linux. It's been great since about node 8. What have your issues been?