Live data from Hacker News

Curl Wttr.in

github.com

31–40 of 128 posts

Re: Curl Wttr.in

#31
post #27

Earlier quoted context omitted.

No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?

Maybe it's just me, but I find PowerShell to be so verbose. Why does every parameter have to have consist of a camelcased sentence? I'm a good typist, but I don't think what you wrote is better than curl wttr.in But that might just be (my) programming.

It's case insensitive and there are short aliases for commands. I live in Linux, but used it way back when. It's an object oriented shell that is kind of awesome and intuitive. Bash is great and you can get shit done, but i don't think it's as user friendly as powershell.

Re: Curl Wttr.in

#32
post #10

A good opportunity to remind everyone that we finally inboxed curl into Windows 10, so this works (with color output) from a stock Windows command prompt. Better late than never, I hope.

Glad to hear that, though I wasn't aware color output now works on windows command. I was under the impression the ansi.sys driver or similar was still necessary for color support.

My team shipped the next generation (after ANSI.SYS) of VT support with the first release of Windows 10 back in 2015. We keep adding things to it, trying to make sure we stay compatible with Xterm. It really is a different landscape now :)

The console subsystem is open-source at https://github.com/microsoft/terminal. Feel free to file bugs, complain, or what have you. That’s what we’re here for!

To quote GP, “better late than never, I hope”.

Re: Curl Wttr.in

#33
It's really nice but I started to use this a year ago and had to stop because they always ran out of resources. Hopefully this is fixed since it's such a nice and easy service!

Re: Curl Wttr.in

#34
post #12

Earlier quoted context omitted.

Isn't Windows 10 free?

there are ebay keys for a couple dollars

For the life of me I cannot understand why would anyone waste their money on such keys. Usually those are volume licenses being sold separately, which is not legal and does not provide you with a valid license. If one is intent on breaking the law anyway, one can save those two bucks and use of the many safe activation methods which do not require installing anything on your machine.

Re: Curl Wttr.in

#35
I use this all the time. I find this option pretty neat:

  curl wttr.in/Moon
Shows current lunar phase.

I use Termux[0] on my phone with curl installed. Pretty handy.

Also, check out rate.sx[1] from the same author:

  curl rate.sx
Shows information about current exchange rates of cryptocoins.

More similar console services: https://github.com/chubin/awesome-console-services

[0]: https://termux.com/

[1]: https://github.com/chubin/rate.sx

Re: Curl Wttr.in

#36

Earlier quoted context omitted.

No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?

Serious question -- not a flame war :) I honestly can't tell if this is sarcastic or not. I've been typing `curl -O http: ...` into command prompts for decades, and that Powershell incantation looks awfully unwieldy. In what way is it the happy path?

Can't speak for that person, but I'm certain it was sarcasm.

Re: Curl Wttr.in

#38
post #27

Earlier quoted context omitted.

No need for that. You can do this: (Invoke-WebRequest -Uri wttr.in).content from Powershell. Why not use the happy path?

Maybe it's just me, but I find PowerShell to be so verbose. Why does every parameter have to have consist of a camelcased sentence? I'm a good typist, but I don't think what you wrote is better than curl wttr.in But that might just be (my) programming.

PowerShell can be shorter by 1 character for this use case:

  irm wttr.in
irm is an alias for Invoke-RestMethod which is similar to Invoke-WebRequest but better for non-html responses like json or plain text.

Re: Curl Wttr.in

#39
post #10

A good opportunity to remind everyone that we finally inboxed curl into Windows 10, so this works (with color output) from a stock Windows command prompt. Better late than never, I hope.

Can you explain more about why you thought this was a good opportunity to interject an advertisement for your product?

Aw, come on. It was interesting and obviously well intentioned. Please don't be an asshole on HN; disincentivizing people from sharing things they've worked on is strictly negative for this site.

https://news.ycombinator.com/newsguidelines.html

Re: Curl Wttr.in

#40
This scared me the first time I tried it because the output was perfectly sized to my terminal. I couldn't fathom how it was possible for the server to know my terminal width.

It turns out my terminal was set at 125 characters wide and wttr.in outputs a 125 character width display.

Post reply on HN