Live data from Hacker News

Ask HN: What under-the-radar technology are you excited about?

news.ycombinator.com

541–550 of 553 posts

Re: Ask HN: What under-the-radar technology are you excited about?

#541

Earlier quoted context omitted.

Steam's system survey shows Linux desktop usage at ~0.85% and general consumer surveys show less than 3% usage even after thirty years of development and that is in spite the fact that it costs nothing. Moreover, a $45 Raspberry Pi 4 costing a third as much will have vastly better performance as a desktop than any logic it's possible to fit on the DE10 board costing $150 that was mentioned. The examples provided ther…

1% of people would make the freedom over convenience trade off, just that there exists people who would and it would be important to them. I don’t see anywhere near 1% of people running a RISC-V softcore based computer on a de10-nano board but I would and many other hackers like me would.

I for one would love to.

Or to at least have a FPGA embedded in the machine Novena(*) laptop style.

(*) the open source laptop by Andrew Huang.

Re: Ask HN: What under-the-radar technology are you excited about?

#542

Allergy immunotherapy. I started a company on the backs of this treatment. The way we treat allergies today, with Zyrtec and Claritin, is medieval medicine. It doesn't solve the underlying problem; it just tries to cover it up. Allergy immunotherapy is the future. Most people don't realize that allergies are now a curable disease. In the future, taking Claritin for allergies is going to seem like taking Tylenol for a…

Won't ever work for most severe food allergies (e.g. peanuts) right? From what I understand, immunotherapy has not been found to be safe/effective for these allergies.

Interested to know as well. Does comment OP have an answer?

Re: Ask HN: What under-the-radar technology are you excited about?

#543

Earlier quoted context omitted.

My first IT gig, 25 (sigh) years ago, I tried to set up as an alias for www. . Seemed to work ok, but somehow I noticed that I had broken email delivery through our firewall, so I reverted the change. Couldn't figure out exactly what was going on, and set it aside. A few months after I left, I sent an email to a friend who still worked there, and it bounced exactly the same way. Called up my friend in a hurry, and su…

Why even have www. . in the first place then, if . is entirely sufficient on its own? It does appear that it's mostly done for historical reasons and sometimes you need CNAME records[1], but overall it feels like it probably introduces unnecessarily complexity, because the www. prefix doesn't really seem to be all that useful apart from the mentioned situation with CNAMEs. That's kind of why i asked the question abov…

It depends on the setup. Some cloud load balancers like AWS ELB require a CNAME, which DNS (RFC 1912) doesn't allow other records at that level if it has a CNAME.

So, can't put a CNAME on the apex, which probably also has MX records. I think in some cases like Exchange, if it sees a CNAME, it doesn't bother with looking at the MX.

Back in the day "CNAME flattening" or aliases (RFC draft draft-ietf-dnsop-aname) wasn't a common thing, so only real way was to redirect the domain apex to www, and then use a CNAME on the www. You'd probably need a separate service/servers to handle that redirect (at least DNS round robin would work in this case). So yea extra complexity in that case, due to the requirements. Or, give them DNS authority (eg, AWS Route 53).

Then there's the whole era of TV/radio commercials telling people "www dot " that a lot of people type it anyways. You can redirect www to apex, which some sites do for a "clean brand" but now browsers are dropping the www in the UI anyways.

I've also run into plenty situations where www worked but apex didn't. Relatedly, it's a little surprising that browsers didn't default to assuming typing the apex in the browser it would try www first. And recently, now we're getting SVCB and HTTPS DNS RRs along with A/AAAA (and maybe ANAME). Indeed lots of complexity.

Re: Ask HN: What under-the-radar technology are you excited about?

#544
post #116

Old tech. New software development is 99% aimless churn. We don’t need more new tech. We need better applications of old tech. There is so much software that works perfectly fine already. What’s missing is connecting it to real world problems.

Can you give some examples of where this is happening today?

Re: Ask HN: What under-the-radar technology are you excited about?

#545

1. GNU Name System to replace the DNS in a backwards-compatible manner, with delegation to cryptographic public keys (instead of IP addresses) and with strong guarantees against known attacks against the DNS (DNSSEC doesn't solve everything). https://gnunet.org/en/gns.html 2. Semantic sysadmin to declare your intent in regards to your infrastructure no matter how it is implemented (i.e. with a standard specification,…

PM lead for PowerShell here, thanks for the callout! I'll take "isn't the worst". ;) I'd love to get more of your thoughts around how PowerShell might be more useful for the kinds of scenarios you're thinking about. We see a lot of folks writing portable CI/CD build/test/deploy scripts for cross-platform apps (or to support cross-platform development), but we're always looking to lower the barrier of entry to get int…

The behaviour with UTF8 is still so strange to me. I get random behaviour during piping commands because utf8 still isn't the default for everything.

Re: Ask HN: What under-the-radar technology are you excited about?

#546
post #324

Earlier quoted context omitted.

Yeah. I remember looking at the Slack IPO and saying to myself, "Your F'ing kidding me. They went public for doing IRC channels in a web browser with emojis?!?!"

This isn't _as_ short-sighted as the famous "Dropbox comment"[1], but it's pretty close. a) Slack _clearly_ offers a lot of meaningful functionality over-and-above IRC channels. "Searching" - and, implicitly, persistence - is so fundamental to the offering that it's (apocryphally) part of the acronymic name. Threading, bot support, and channel discovery are all useful features. Sure, all of those things _can_ be impl…

I think you're both missing the point, though. And it surprises me how many people miss this point even on this incredibly smart forum. The idea doesn't matter as much as the execution. The business side matters as much or more than the technology side.

Re: Ask HN: What under-the-radar technology are you excited about?

#547

Earlier quoted context omitted.

PM lead for PowerShell here, thanks for the callout! I'll take "isn't the worst". ;) I'd love to get more of your thoughts around how PowerShell might be more useful for the kinds of scenarios you're thinking about. We see a lot of folks writing portable CI/CD build/test/deploy scripts for cross-platform apps (or to support cross-platform development), but we're always looking to lower the barrier of entry to get int…

Stop shipping your org chart! Microsoft has always had this problem, but with PowerShell -- which is supposed to be this unified interface to all things Microsoft -- it is glaringly obvious that teams at Microsoft do not talk to each other. To this day, the ActiveDirectory commands throw exceptions instead of returning Errors. Are you not allowed to talk to them? The Exchange "Set" commands, if failing to match the p…

Thanks for the thoughtful response! Many of these are totally legitimate: in particular, we're making steady progress to centralize module design, release, documentation, and modernization, or at least to bring many teams closer together. In many cases, we're at a transition point between moving from traditional PS remoting modules and filling out PS coverage for newer OAuth / REST API flows.

I don't know how recently you've tried PS7, but the back-compat (particularly on Windows) is much, much better[1]. And for those places where compatibility isn't there yet, if you're running on Windows, you can just `Import-Module -UseWindowsPowerShell FooModule` and it'll secretly load out-of-proc in Windows PS.

Unfortunately, the .NET problems are outside my area. I'm definitely not the expert, but I believe many of the decisions around the default assembly load context are integral to the refactoring of .NET Core/5+. We are looking into building a generalized assembly load context that allows for "module isolation", and I'd love to get a sense in the issue tracking that[2] whether or not fixing that would help solve some of the difficulties you're having in building modules.

For Azure, you should check out the PSArm[3] module that we just started shipping experimentally. It's basically a PS DSL around ARM templates, as someone who uses PS and writes the Azure JSON, you sound like the ideal target for it.

As for the help content, that's a very funny story for another time :D

[1]: https://aka.ms/psmodulecompat

[2]: https://github.com/PowerShell/PowerShell/issues/2083

[3]: https://github.com/powershell/psarm

Re: Ask HN: What under-the-radar technology are you excited about?

#548

Earlier quoted context omitted.

PM lead for PowerShell here, thanks for the callout! I'll take "isn't the worst". ;) I'd love to get more of your thoughts around how PowerShell might be more useful for the kinds of scenarios you're thinking about. We see a lot of folks writing portable CI/CD build/test/deploy scripts for cross-platform apps (or to support cross-platform development), but we're always looking to lower the barrier of entry to get int…

> we're always looking to lower the barrier of entry to get into PowerShell I’ve used powershell regularly since way back when (it was still called monad when I first tied it). I’m extremely comfortable in the Windows environment but even yesterday I found it easiest to shell out to cmd.exe to pipe the output of git fast-export to stop powershell from messing with stdout (line feeds) I really like the idea of a pipel…

We've fixed a ton of these in PowerShell 7 (pwsh.exe, as opposed to Windows PowerShell / powershell.exe), particularly because we needed to support Linux and more of its semantics.

If you're seeing issues within PowerShell 7, please file issues against us at github.com/powershell/powershell

Re: Ask HN: What under-the-radar technology are you excited about?

#549
post #224

Earlier quoted context omitted.

PM lead for PowerShell here, thanks for the callout! I'll take "isn't the worst". ;) I'd love to get more of your thoughts around how PowerShell might be more useful for the kinds of scenarios you're thinking about. We see a lot of folks writing portable CI/CD build/test/deploy scripts for cross-platform apps (or to support cross-platform development), but we're always looking to lower the barrier of entry to get int…

> we're always looking to lower the barrier of entry to get into PowerShell, as it can be quite jarring to someone who's used Bash their whole life (myself included). apt search powershell returns no meaningful result on Debian unstable. I think that's a big barrier to entry, at least for me and people who deploy using docker images based on Debian and Ubuntu.

Good to know! I've generally understood that the bar for package inclusion for both Debian and Ubuntu is fairly high (where Debian wants you to push to them and Ubuntu will pull from you).

Our setup today is simply to add an apt repo[1] (of which there is just one domain for all Microsoft Linux packages), and then you can `apt install`.

We also ship pretty minimal Ubuntu and Debian (and Alpine and a bunch of other) container images here.[2]

Oh, and we ship on the Snap Store if you're using Snapcraft stuff.

[1]: http://aka.ms/install-pslinux

[2]: https://hub.docker.com/_/microsoft-powershell

Re: Ask HN: What under-the-radar technology are you excited about?

#550
post #200

Earlier quoted context omitted.

PM lead for PowerShell here, thanks for the callout! I'll take "isn't the worst". ;) I'd love to get more of your thoughts around how PowerShell might be more useful for the kinds of scenarios you're thinking about. We see a lot of folks writing portable CI/CD build/test/deploy scripts for cross-platform apps (or to support cross-platform development), but we're always looking to lower the barrier of entry to get int…

Don't return everything, return what I specifically returned (yeah, I know about objects, talking about everywhere else). I know it will never happen, but one can dream. Painpoints aside, you and your team are doing excellent job. Thank you Edit: unless you are also responsible for DSC, than I'll take it back. It's terrible.

Unfortunately, we can't ever change that one, or the whole world of existing stuff will break.

It's intended as a shell semantic where anything bare on the command line just gets run, no matter your scope.

However when we introduced classes, we thought it was a more "dev-oriented" semantic, so we changed return there.

This will only return 'this will return':

  class foo {
    [string] ReturnTest() {
      'this will not return'
      return 'this will return'
    }
  }
  
  ([foo]::new()).ReturnTest()
Post reply on HN