Live data from Hacker News

Bashblog – a single bash script to create blogs

github.com

51–60 of 93 posts

Re: Bashblog – a single bash script to create blogs

#51
post #49
post #45

Earlier quoted context omitted.

Weird footguns don't matter if you stick to using shell for control flow, composition, and interpolation, and don't use all the weird things you have to look up every time. It's also very easy to do something in the commandline then just tail -n 8 $HISTFILE > script.sh and very little to no editing is needed to make that useful. Shell is not a programming language, it's an interface to the OS, and thinking about it l…

> Shell is not a programming language, it's an interface to the OS, and thinking about it like a programming language is just asking for frustration. I guess this just isn’t obvious to me. Where do you see the boundary between “interface to the os” and “programming language”?

Shell exists to give users a way to run programs. It was the user interface for UNIX, C was the programming interface. Yes, it's technically a programming language by any reasonable definition, but it's not meant to be used in the same way at all so that's not helpful.

Re: Bashblog – a single bash script to create blogs

#52
post #7

Earlier quoted context omitted.

Awful old Bash. I hate it. Seriously I don't know why you'd do this in Bash. Crazy choice.

Known system dependency that's (almost) always on the system you're on. I remember somebody once telling me that they had learned vi because "it was always installed". Well, no, technically, the only editor you can be sure is there is ed. So, you know, learn that. I was surprised that they actually did. Bash is syntactically not perfect, I agree. However it's a well known, mature, stable environment. LLMs can write i…

> technically... you can be sure there's ed

Unfortunately, ed has been omitted from the default installation of recent debians, at least. I had to install it manually.

Re: Bashblog – a single bash script to create blogs

#53

Earlier quoted context omitted.

This reads like parody! In a sane world (and I believe the HN community rules are fairly sane) we should be upvoting things that are interesting , or insightful , or informative , or otherwise tickle our curiosity . Not just because we agree with them! After all, who cares that I agree with something? Everyone has an opinion on everything, opinions in themselves are cheap and uninteresting.

It's not interesting or insightful to take potshots at a project because it's hosted on GitHub.

So one cannot have or express an opinion on hosting as it is a priori and uncontestably lacking in insight and universally uninteresting?

And HNN requires either or both: opinions must be insightful or interesting.

And what is either of those is objective, self-evident, and not even slightly subjective.

Right? How is this not merely a blanket way to assert opinions that are themselves boring and un-insightful ("hosting opinions are forbidden" is the de facto claim)?

Hosting on Github has been an up voted story several HNN times. Yet here its not interesting or insightful.

If the point is "potshots" why not ask or suggest more developed opinions instead of potshotting the potshots? Why not clearly note that "potshot comments on any topic are not optimal" instead of making this seem to be about hosting or what is insightful?

A down vote is not meaningful feedback and clarity tends to work better.

Re: Bashblog – a single bash script to create blogs

#55
post #52

Earlier quoted context omitted.

Known system dependency that's (almost) always on the system you're on. I remember somebody once telling me that they had learned vi because "it was always installed". Well, no, technically, the only editor you can be sure is there is ed. So, you know, learn that. I was surprised that they actually did. Bash is syntactically not perfect, I agree. However it's a well known, mature, stable environment. LLMs can write i…

> technically... you can be sure there's ed Unfortunately, ed has been omitted from the default installation of recent debians, at least. I had to install it manually.

WTF?! RIP Debian.

If I wanted an OS without a text editor, I'd use emacs.

Re: Bashblog – a single bash script to create blogs

#56
It's so interesting to me how people consider writing bash scripts to be some sort of absurdist gimmick. I've made some scripts like this for blogging, as well as many other things.

It's often not the best choice. There are situations where, I'd argue, it is. One of the main reasons, in my experience, is for very lightweight servers. I don't want python or node or anything. I want to run a web server with 128mb of ram and a 1gb disk. Somewhat niche, but it's useful to just use the base system.

The other useful thing about it is knowing your shell in general. Even if you're not on the infrastructure team, being comfortable knowing how to navigate a system is both fun and sometimes critical. You never know when you'll need it, and it's an interesting look into your tools.

It's akin to saying "why know how to use a saw when you can use a chainsaw" or "why know how to make a fire when you can use lighter fluid and a lighter?" Sometimes things come up. And it's fun to know how we got to where we are today.

Re: Bashblog – a single bash script to create blogs

#57

This is a good example of a program I would like to use if it was distributed in the standard repo of my OS, rather than totally unvetted on the Microsoft Github page of a random developer. PS: I don't know why HN allows downvoting seeing how it is always so abused. Nothing I wrote here is factually false, and what remains is just my personal opinion as a principled user of FOSS. A bit of tolerance for others' viewpo…

> This is a good example of a program I would like to use if it was distributed in the standard repo of my OS So why are you waiting? Be the change you seek. Simply become a maintainer of a distro, and publish the package there. Repeat for all the major distros.

The response I was expecting and deserved. That still leaves the residual whine about Github.
Post reply on HN