3,477 karma · joined January 9, 2020
The original cliparts were paper books. Designers would clip out the pictures they want, glue them to their master document, and then run it through a photocopier. Then later we had the big hero web templates and stock images. Even though every person involved has an excellent camera in their pocket, the thought of using it was unbearable compared to just downloading a stock image. Then we got canva which was basically the perfection of cliparts and stock images.
Now we have AI web design. It's just the newest step of the least exciting 'something needs to exist but its form is mostly without value' category of "content", which is itself a category so devoid of meaning that nobody doing it even bothers to give themselves the title of 'designer' or 'writer' or 'illustrator', instead self labeling as 'content creator'.
For what it's worth though, I find AI designs to be mostly okay? They aren't exciting but at least the ultra low contrast design era is finally over and I can finally have usable scrollbars and easily find the login button on most websites now.
Business: aruba instant-on. They cost more and updates are much less frequent. They are also more reliable and the support experience is far superior even though it is HP.
shield is still competitive. It has become a little laggy but apparently that can be fixed by swapping out the launcher.
no caldav support so I couldn't get my next appointment as a widget on my phone. Similarly, your contacts in proton are trapped there and cannot sync with any other system (such as your phone...)
limited quantity of aliases compared to fastmail. this is actually a really sticky feature with fm from what I've been seeing. I would have to rename a bunch of accounts or switch to using a catchall to transfer out.
The other problem is that I have a fancy throttle and stick with lots of extra buttons and switches. I know common functions by touch but if I wanna toggle exterior lights or something I have to look down and find a label.
For me choosing a screen + head tracking vs VR is like choosing to use speakers instead of headphones. The headphones sound way nicer and give much more immersive soundscapes but sometimes you want to have some tunes going and not have your ears get sweaty.
I don't run it anymore but my old server was a dual xeon (with two of those coolers crammed in) and I rarely heard a peep out of it.
1080px wide (aka on my vertical monitor) HN comments stop reflowing > 300%
At 1920px wide it never stops reflowing.
The speed limit display is great for simple highways and I appreciate the warning when I reach a speed zone, but not ready for anywhere complicated.
The user will say 'it lags' but does not mention if they have tearing enabled in wayland, what are their 1% lows, have they set an fps cap, what vsync settings have they chosen in-game. On top of that there is an ecosystem failure as not every game supports arbitrary caps and you have to configure some mangohud thing.
Linux is only a 'just click play' experience if you have no standards because I have never had this stuff be correct out of the box on a fresh install.
It is nice that you know what the law is but that isn't the same as the law being followed. Also the bank was PNC, not the biggest guy ever but not a small player either.
Someone would send you a document and it took over the entire Teams window. You had to exit it in order to chat with the person about the document. The concept of having more than one 'thing' on screen at the time was completely missing. My only explanation was that the developers had never used a computer before.
2. Buy a relevant dongle/antenna for the protocol you want to use. I recommend the ones from Sonoff or from the Home Assistant foundation (I started with the sonoff for zigbee, but added the ZBT-2 for matter/thread. they are both good)
3. install proxmox to the metal.
4. use tteck's install script to make the HAOS vm. Don't make the containers, make the HAOS VM specifically: https://tteck.github.io/Proxmox/#home-assistant-os-vm
5. Plug in your dongle(s) and don't forget to assign them to the new VM. You should now be able to start using home assistant. If you're using zigbee, choose zigbee2mqtt rather than ZHA, it's more reliable overall.
My setup is around 2 years old and I haven't had to administrate it at all.