I don't think there has been huge issues with incompatible ISAs on ARM. If you'd use NEON extensions, for example, you might have a C-implementation that does the same if the extensions are not available. Most people don't handwrite such code, but those that do usually go the extra mile. ARM SoCs usually have closed source drivers that cause headaches. As well as no standardized way of booting.
I haven't delved super-deep into RISC-V just yet, but as I understand these systems will do UEFI, solving the bootloader headache. And yes, there are optional extensions and you can even make your own. But the architecture takes height for implementing an those extensions in software. If you don't have the gates for your fancy vector instruction, you can provide instructions to replicate the same. It'll be slower on your hardware, but it'll be compatible if done right.
The assistant used to be able to translate any app on the fly. It was great when living in a foreign country and trying to figure out what those text messages I got meant.
It was truly the only thing I used assistant for. I've had it disabled since they dropped that feature.
The internet was just starting to get interesting. Windows had software to browse and do e-mail.
Linux had the stuff to power the whole internet. It was just a whole lot more interesting if you wanted to be more than a consumer of the information super-highway.
I wouldn't say I hate Windows. I've had Windows 2.0 through NT 4.0 installed, but it was more of an application that I rarely started because it usually just interfered with my MS-DOS programs. DESQview was a much preferable option, as it had true multitasking (yes, so did NT 4.0 - but it broke a lot of things).
I dual booted DOS and Linux for a couple of years, but DOS box was good enough in 1997 that I rarely had to boot DOS, so I've been Linux only for a couple of decades.
Slackware and Red Hat were the two distros in use in the mid 90s.
My local city used proper UNIX, and my university had IRIXworkstations SPARCstations and SunOS servers. We used Linux at my ISP to handle modem pools and web/mail/news servers. In the early 2000s we had Linux labs, and Linux clusters to work on.
Linux on the desktop was a bit painful.
There were no modules. Kernels had to fit into main memory. So you'd roll your own kernel with just the drivers you needed.
XFree86 was tricky to configure with timings for your CRT monitors. If done wrong, you could break your monitor.
I used FVWM2 and Enlightenment for many years. I miss Enlightenment.
This cleared out a flea infestation in our dog. We use it preventatively because ticks, as well.
Fleas tend to linger because their eggs shed all over the place. As I recall, frontline had some double action going on by both killing fleas and causing their eggs to hatch into nymphs that never evolve into breeding maturity.
Fleas don't really like biting humans, so any occurrence is a one+off.
zram is only suitable if you have no swap. I'd you have swap, zswap does a better job. It also compresses pages in memory, but swaps the least recently used pages to disk when pressured.
Sounds s lot more fair than the experience I had at home!
Three kids crammed in front of one computer. One on keyboard, one on mouse and one on joystick. The one on joystick was at the worst disadvantage. A small nudge was a good way to sabotage rebuilding your fortress.
Start with getting some experience before considering buying a boat. Not only can you lose your investment, but your life. Job a club, take lessons, make friends at the local yacht club, volunteer as crew.
Requirements for being a skipper vary quite a bit between countries. Some let anyone go up to a certain size, others require certifications even for small dinghies.
The bigger the boat, the harder it is too both manoeuvre and maintain.
Do you want something small that you can roll into the water on a ramp when you use it?
Do you want something big enough that requires a crane to get in the water? Prepare to spend a week cleaning, sanding, polishing, waxing and applying new anti-foul yearly.
HarriPotero @ HarriPotero @lemmy.world Posts 0Comments 193Joined 2 yr. ago
I don't think there has been huge issues with incompatible ISAs on ARM. If you'd use NEON extensions, for example, you might have a C-implementation that does the same if the extensions are not available. Most people don't handwrite such code, but those that do usually go the extra mile. ARM SoCs usually have closed source drivers that cause headaches. As well as no standardized way of booting.
I haven't delved super-deep into RISC-V just yet, but as I understand these systems will do UEFI, solving the bootloader headache. And yes, there are optional extensions and you can even make your own. But the architecture takes height for implementing an those extensions in software. If you don't have the gates for your fancy vector instruction, you can provide instructions to replicate the same. It'll be slower on your hardware, but it'll be compatible if done right.