Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked.

Lets invent circumstances where it would be a problem to run your own car, but lets not invent circumstances where we can allow home brew MMI interfaces. Such as 99% of cars where the MMI interface has nothing to do with wipers. Furthermore, you drive on the road every day with people who have shitty wipers, that barely work, or who don't run their wipers 'fast enough' to effectively clear their windsheild. Is there a enforced speed?

And my CPAP machine, my blood pressure monitor, my scale, my O2 monitor (I stocked up during covid), all have some sort of external web interface that call home to proprietary places, which I trust I am in control of. I'd love to flash my own software onto those, put them all in one place, under my control. Where I can have my own logging without fearing my records are accessible via some fly-by-night 3rd party company that may be selling or leaking data.

I bet you think that Microwaves, stoves etc should never have web interfaces? Well, if you are disabled, say you have low vision and/or blind, microwaves, modern toasters, and other home appliances are extremely difficult or impossible to operate. If you are skeptical, I would love for you to have been next to me when I was demoing the "Alexa powered Microwave" to people who are blind.

There are a lot of a11y university programs hacking these and providing a central UX for home appliances for people with cognitive and vision disabilities.

But please, lets just wait until we're allowed to use them.

Then you go to list all the problems with just the car. And your problem is putting your own AI on a car to self-drive.(Linux isn't AI btw). What about putting your own linux on the multi-media interface of the car? What about a CPAP machine? heart monitor? Microwave? I think you mistook the parent's post entirely.

My point, since I was replying to a poster who said the above, was if you are making $300 a year, you don't have a laptop. So, if you read my assumption, that you don't have a laptop, android phone or laptop, and you are making < $1000 USD a year, the Flea-Scope will cost more than a decent one with a built in display and much more than a ~2mhz toy intro oscilloscope ($11 on Aliexpress) [1]

I could also very well reply with just the quote above.

https://www.aliexpress.us/w/wholesale-oscilloscope-.html?spm...

The problem is, with a toy scope, you aren't really gonna know if what you're measuring is real. This might be useful as a kit to build to learn how to program microcontrollers, or measure audio signals (the $11 one, or the mic on your phone can do this), but a bad scope will generally cause more problems for the hobbyist. When you get near the limit of a scope's bandwidth, the signals get really messy and full of artifacts. Arduinos run at 8-16Mhz, so you're gonna hit a wall really quickly and once you can't rely on the output, the investment will be lost.

tldr; VGA always looked like crap on most LCDs, imho they were almost unusable until DVI.

TSUNAMI THREAT FORECAST...UPDATED ---------------------------------

  * THERE IS NO LONGER A TSUNAMI THREAT FROM THIS EARTHQUAKE.

compiled on my laptop on WSL.

sudo apt install x11-common libx11-dev

make

ran with

cat horizon.sc pittsburgh.sc | ./banks

If Tor was ubiquitous obviously not, but its very niche, and looking at a chart of use, its pretty much only used for drugs and CP. There are privacy use cases, but just like using crypto as a currency and not a speculative gambling investment, its in the small minority of uses.

I've seen many custom JIRA workflows, where you define specific states that can progress to other states. Nearly all of them, over time, were modified so that any state can move to any other state.

And if you engineers don't use the tool you provide, the data in it is useless. Engineers are typically very smart and will just twist any tool they don't like.

Declaration: In order to have accurate state between projects and bugs, everything needs to be tracked in JIRA.

Result: 70% of your Jira stories are now "This JIRA tracks an issue stored in the Github repo, see the repo for current status"

[1]https://www.crowdstrike.com/blog/statement-on-falcon-content...

I haven't seen a NRA rate enforced at Facebook, however 6% is the target at Amazon.