Live data from Hacker News

2048 in sed

github.com

11–20 of 39 posts

Re: 2048 in sed

#11

> Note for OS X users: The version of sed installed has different options than the Linux one. Notably, it does not have the extended-regex option -r. I recommend building the latest version from here: http://sed.sourceforge.net/ The option is there, just different: -E (the same as grep)

Why doesn't Apple just ship with standard GNU utils?

They are the de facto standard. Having the need to compile all these basic stuff for any scripting to be portable is a nightmare.

Re: 2048 in sed

#13
post #8

Have someone made Emacs version? Isn't it more easy to write it in elisp compared to sed.

I'm sure Emacs has a "unix mode" hidden in there somewhere. Inside it, I bet there's a full complement of GNU utils. Sed should be in there somewhere.

Re: 2048 in sed

#14
post #3

Sed awesome. Also, disappointed no one has blatantly embedded https://github.com/progranism/Bitcoin-JavaScript-Miner to put all this time wasting to good u$e.

Sadly that javascript miner is stupidly slow. You could have a top Hacker News post and still only make pennies.

Re: 2048 in sed

#15

> Note for OS X users: The version of sed installed has different options than the Linux one. Notably, it does not have the extended-regex option -r. I recommend building the latest version from here: http://sed.sourceforge.net/ The option is there, just different: -E (the same as grep)

GNU sed 4.2.0 and up also support -E for compatibility with BSD sed (though this is undocumented).

Re: 2048 in sed

#16

> Note for OS X users: The version of sed installed has different options than the Linux one. Notably, it does not have the extended-regex option -r. I recommend building the latest version from here: http://sed.sourceforge.net/ The option is there, just different: -E (the same as grep)

Why doesn't Apple just ship with standard GNU utils? They are the de facto standard. Having the need to compile all these basic stuff for any scripting to be portable is a nightmare.

I believe it's a licensing issue, could be completely wrong though.

Re: 2048 in sed

#17
post #3

Sed awesome. Also, disappointed no one has blatantly embedded https://github.com/progranism/Bitcoin-JavaScript-Miner to put all this time wasting to good u$e.

Sadly that javascript miner is stupidly slow. You could have a top Hacker News post and still only make pennies.

Not even that really. You might get a single difficulty 1 share or two, worth literally less than the maximum precision BTC allows.

Re: 2048 in sed

#18

> Note for OS X users: The version of sed installed has different options than the Linux one. Notably, it does not have the extended-regex option -r. I recommend building the latest version from here: http://sed.sourceforge.net/ The option is there, just different: -E (the same as grep)

Why doesn't Apple just ship with standard GNU utils? They are the de facto standard. Having the need to compile all these basic stuff for any scripting to be portable is a nightmare.

Apple has chosen not to ship any GPLv3 code.

Re: 2048 in sed

#19

> Note for OS X users: The version of sed installed has different options than the Linux one. Notably, it does not have the extended-regex option -r. I recommend building the latest version from here: http://sed.sourceforge.net/ The option is there, just different: -E (the same as grep)

Why doesn't Apple just ship with standard GNU utils? They are the de facto standard. Having the need to compile all these basic stuff for any scripting to be portable is a nightmare.

If your well-beloved GNU coreutils did not breach every POSIX standard and add new flags to every program, no such problem would exist. Seriously, I do not know whether Mac OS is using a custom implementation of UNIX utilities, or distributin BSD coreutils, but I know that it is a licensed, certified UNIX.

Re: 2048 in sed

#20
post #19

Earlier quoted context omitted.

Why doesn't Apple just ship with standard GNU utils? They are the de facto standard. Having the need to compile all these basic stuff for any scripting to be portable is a nightmare.

If your well-beloved GNU coreutils did not breach every POSIX standard and add new flags to every program, no such problem would exist. Seriously, I do not know whether Mac OS is using a custom implementation of UNIX utilities, or distributin BSD coreutils, but I know that it is a licensed, certified UNIX.

UNIX certification means nothing if the utils are intentionally outdated and incompatible with the de facto UNIX-like implementation due to petty licensing concerns.

At the end of the day, whether some script works is the issue, not a UNIX branding.

Post reply on HN