Maybe for developers, but I can't imagine most people going back to the terminal. The smartphones won and has the largest market. It would be especially awkward to use a terminal on a touch display. Maybe with voice this will be easier, but I doubt people want to go around in public talking and giving instructions to their phone. UIs are here to stay.
I got it last year, as a man in my early 30s. My doctor didn't believe me but his eyes widened as I showed him the rash. It took him one second to say that is shingles, with no doubt. If you get it you have to get to the doctor ASAP to get the antiviral medicine before it spreads. It is the most painful thing I have gone through.
I'm pretty sure I got is because of stress. I quit my job, sold my home and all my stuff to travel for a year. I was awarded shingles the week after handing in my resignation.
I’ve self medicated with OTC acyclovir before getting a stronger prescription and it worked quite well. The trick was to diagnose quickly, the tell was the itching wouldn’t stop even while scratching.
Pro tip: keep some cold sore oral medicine at hand.
Until there's a common, well-supported, and sufficiently performant family of RISC-V SoCs or CPUs with support for existing well-supported GPUs, RISC-V support will be a massive pain in the ass of a moving/fragmented target.
This has held back Arm for years, even today the state of poor GPU drivers for otherwise good Arm SoCs. There is essentially a tiny handful of Arm systems with good GPU support.
The way Microsoft are ruining Windows makes it seem like enterprise users are the tech debt they want to get rid off. Like making their servers non-deterministic by serving random ads or leaking secret content to their AI. It makes sense that they would rather have their customers run Linux on Azure, so they don't have to do R&D for their own OS.
It's actually not that thinner (1.9mm compared to 12 mini) so I doubt it will. And it definitely can't make for the huge size difference (134mm of extra width).
Ditto. This adds 10.5mm of width, but shaves 4mm of depth (2mm on each side, as measured when holding in one hand). So the net increase is only 6mm. I won't be pre-ordering one of these, since I want to feel it in-store prior to purchasing.
The weight is also significantly (in percentage terms) greater.
All or nothing mentally wont get you very far. You're digital device is probably made in China, but that doesn't mean you'll want to store your personal data in a Chinese data center. I try to choose European whenever possible and avoid or limit the use of American, Chinese, and Russian tech.
I don't see the need for Lit anymore. Lately I have just been raw dogging web components without any libraries. Having a nice templating system like JSX on the server makes it a breeze.
Part of using web components, for me, is that it is just javascript. There is no upgrades or deprecations to think about. Of course those things still exist on the server though, but it is easier to maintain it there.
The great thing about web components is that you can build them however works best for you.
Native web component APIs don't have the DX that many people expect though, because they are so low-level. Lit provides just that declarative reactivity on top.
Personally I find that lit abstracts quite well some pieces of functionality that you're going to implement yourself anyway to not have to write manual <template> all over your code plus the plumbing to add it to the DOM.
I find that there is little practical difference between "html" tagged template literal and writing JSX. Not to mention there is a compilation step in JSX.
I mean sure, as long as it runs on the server. Personally I feel JSX is way more expressive. The JSX I write runs on server side rendering to HTML. That way there will be no flash of unstyled content, cumulative layout shift, or any other jank. It looks correct even before the javascript has been downloaded, except it isn't interactive yet.
reply