261–270 of 553 posts
Yosys and open source FPGA toolchains. I think FPGA are vastly underrated and hard to use because of tooling and this is promising in changing it.
soil science influenced agriculture, watch 'kiss the ground' on netflix.
Heat pumps and better insulation. It's magic how heat pumps pull heat out of thin air. I honestly think part of the reason they are not adopted as much is people can't understand them and don't trust them because of their ignorance. Insulation seems pretty boring until you start to realize how much energy can be saved by modern insulation.
Almost all new houses are built with heat pumps where I live because it's kind of a no-brainer in those situations. And I see one old house after the other being wrapped in new thick isolation. But heat pumps in old homes just aren't a thing because it's expensive and a lot of work to adapt the house's existing heating. People do understand it, they just don't want to bother with that.
Earlier quoted context omitted.
They are good. But not in very cold environments. I have one and when there is more than two degrees of frost it struggles. So for a lot of continental areas they are almost useless since they do not function when you really need them. For temperate climates and coastal regions they are wonderful.
I think you’ve stumbled on the REAL reason there’s hesitation with heat pumps. There’s a massive difference in capability and efficiency and usability of heat pumps. The crappy ones don’t even work below freezing. The good ones can operate even down to -20F efficiently, even air source. And ground source ones don’t have a hard limit at all (although they face a similar wide difference in capability). Low effort cheap…
Earlier quoted context omitted.
It's because the bare TLD isn't setup to accept requests, but the `www` subdomain is (it's DNSed to a different IP): $ curl -v --head https://nushell.sh/ * Trying 162.255.119.254... * TCP_NODELAY set * Connection failed * connect to 162.255.119.254 port 443 failed: Connection refused $ curl -v --head https://www.nushell.sh/ * Trying 185.199.108.153... * TCP_NODELAY set * Connected to www.nushell.sh (185.199.108.153)…
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…
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 above - maybe someone can comment on additional use cases or reasons for sticking to the www convention, which aren't covered in the linked page.
When i last asked the question to a company who only had their website available with wwww but didn't without, i got an unsatisfactory and non-specific answer where spam was mentioned. I'm not sure whether there's any truth to that.
- Native File System support coming to the browser: https://web.dev/file-system-access/ - jamstack.wtf - federation-based networks - CRDTs: https://josephg.com/blog/crdts-are-the-future/ - data-oriented programming paradigm ( https://rugpullindex.com/ shameless plug) - web components: https://docs.ficusjs.org/index.html
e.g. lemmy.ml
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…
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 provided user name, helpfully overwrite the first 1,000 users instead because... admins don't need weekends, am I right? Who doesn't enjoy a disaster recovery instead of going to the beach?
I'm what you'd categorise as a power user of PS 5.1, having written many PS1 modules and several C# modules for customers to use at scale. I've barely touched PowerShell Core because support for it within Microsoft is more miss than hit.
For example, .NET Core has caused serious issues. PowerShell needs dynamic DLL loading to work, but .NET Core hasn't prioritised that, because web apps don't need it. The runtime introduced EXE-level flags that should have been DLL-level, making certain categories of PowerShell modules impossible to develop. I gave up. I no longer develop for PowerShell at all. It's just too hard.
It's nice that Out-GridView and Show-Command are back, but they launch under the shell window, which makes them hard to find at the best of times and very irritating when the shell is embedded (E.g.: in VS Code)
The Azure commandlets are generally a pain to work with, so I've switched to ARM Templates for most things because PowerShell resource provisioning scripts cannot be re-run, unlike scripts based on the "az" command line or templates. Graph is a monstrosity, and most of my customers are still using MSOnline and are firmly tied to PS 5.1 for the foreseeable future.
Heaven help you if you need to manage a full suite of Hybrid Office 365 backoffice applications. The connection time alone is a solid 2 minutes. Commands fail regularly due to network or throttling reasons, and scripts in general aren't retry-able as mentioned above. This is a usability disaster.
Last, but not least: Who thought it was a good idea to strip the help content out and force users to jump through hoops to install it? There ought to be a guild of programmers so people like him can be summarily ejected from it!
Heat pumps and better insulation. It's magic how heat pumps pull heat out of thin air. I honestly think part of the reason they are not adopted as much is people can't understand them and don't trust them because of their ignorance. Insulation seems pretty boring until you start to realize how much energy can be saved by modern insulation.
Along the same line of thinking, tankless water heating [1] seems like a no-brainer. It surprises me that places like the US have not used it as the default from the start. [1]: https://en.wikipedia.org/wiki/Tankless_water_heating