91–100 of 138 posts
Mentioning strace in an article titled "Learn just enough Linux to get things done" seems so out of place as to be absurd, even in an "Advanced" section. Anyone who needs the rest of this advice is going to be absolutely baffled by strace. Otherwise, decent little primer.
Earlier quoted context omitted.
Yeah, software development on Unix was so natural and enjoyable, even today half the time building a Linux library or app is typically spent in byzantine shell scripts trying to determine which particular occult incantation of incompatible or broken Unix you are not running and throwing various test programs at your compiler that last made sense in 1995. The true essence of delightful and plain right software develop…
>The true essence of delightful and plain right software development must be over in OpenBSD land, where they run the one and only gcc 4.2.1 Clang actually.
If it was only an exercise in self-flagellation, sure whatever, but no, their tears flow upstream when stuff 99% of the population uses on Linux inevitably breaks with their bastardized gcc.
(This is very obvious if you consider that no, they don't have an LLVM backend for the alpha)
Earlier quoted context omitted.
And git does work on Windows. There's even a windows logo on the official download page. https://www.git-scm.com/downloads
Git for Windows relies pretty heavily on MinGW, though. And it's best used from the included bash shell.
Great list for starters. But getting real work done requires much more. Having just walked through some basic steps with a novice, I can concur, modern linux is impossible without "recipes". Just setting up a hello world web app can involve: ssh login to running instance, using curl to download the gcloud sdk, tar to unpack, sudo to install, systemctl to start local processes, useradd dedicated www, chmod and chroot…
Disagree! I'm normally all for easier entry points, but ssh login to running instance using curl to download the gcloud sdk tar to unpack sudo to install systemctl to start local processes useradd dedicated www chmod and chroot to allow access rsync to tranfer files are absolute basics of system administration. People who cannot even handle those tasks should not use a root server for their project. There are alterna…
My concern would mostly be that the list above is unacceptable for learning, not for usability. That's ~8 different tools to learn from scratch, totally independent of the underlying project.
And sure, most devs will eventually know all of those tools (or equivalents) without much conscious effort. But there's a lot to be said for scripted introductions to complex systems.
Great list for starters. But getting real work done requires much more. Having just walked through some basic steps with a novice, I can concur, modern linux is impossible without "recipes". Just setting up a hello world web app can involve: ssh login to running instance, using curl to download the gcloud sdk, tar to unpack, sudo to install, systemctl to start local processes, useradd dedicated www, chmod and chroot…
>> For beginners, without a trusted hand to guide them, its beyond intimidating. These systems must become more accessible to the average human. I cringe at thinking about what a newbie has to go through. Install the right version of php/python etc on your platform Install a virtual environment Install a package manager Install a framework Install a database
Setting up novices to start their work with an arcane and difficult step is unfortunate even if it is unavoidable.
Mentioning strace in an article titled "Learn just enough Linux to get things done" seems so out of place as to be absurd, even in an "Advanced" section. Anyone who needs the rest of this advice is going to be absolutely baffled by strace. Otherwise, decent little primer.
I've been a linux user for almost eleven years now, and a professional software developer for four, and I wasn't even aware that strace existed until just now.
Earlier quoted context omitted.
Because people assume they should RTM and if memory serves me right it is a whole lot more confusing than your post :-)
Doesn't look any more complex than most man pages: https://linux.die.net/man/1/tar
It sounds like this project moved in the right direction and made the man page more efficient than googling, but many others haven't.
This is not a surprise - the Windows ecosystem simply wasn't designed with software development in mind. Aha? What is C# and Visual Studio? Or .NET? Was Linux designed for software development? This article is so bad, I'm really getting mad over here. Stop publishing such crap, you feed a lot of people's resentment against all those hipster developers who don't want to learn by RTFM, but want to have handled everythi…
Earlier quoted context omitted.
I've been a linux user for almost eleven years now, and a professional software developer for four, and I wasn't even aware that strace existed until just now.
I've been tinkering on Linux as a hobby for about 2 years now and was made aware of strace a couple of months after starting to dig a bit deeper. You make me hopeful of my future employment.
Mentioning strace in an article titled "Learn just enough Linux to get things done" seems so out of place as to be absurd, even in an "Advanced" section. Anyone who needs the rest of this advice is going to be absolutely baffled by strace. Otherwise, decent little primer.
I've been a linux user for almost eleven years now, and a professional software developer for four, and I wasn't even aware that strace existed until just now.
Because if you had, I don't know how you could not know that strace existed. Maybe you wouldn't know how to use it, but I don't see how you could be unaware of its existence if you are familiar at all with linux dev tools.