258 karma · joined May 7, 2018
Then, I started mounting it to my dirt bike helmet, just for video evidence if I were to wreck and die. What I didn't realize was just how painfully slow it feels to watch a video of me (barely an amateur rider) on a track. The silver lining being, watching that video has helped me improve quite a bit.
I'm surprised GoPro hasn't formed partnerships for success in other markets. High school sports, and even younger, are often filming competitions and performing automated or manual analysis to rank players and provide feedback. Schools and Boosters are paying crazy amounts of money for these services, but it could be so much better aggregating videos of ~10 mounted GoPros together to get "on the field" perspectives. Then there's the whole professional sports media market. People LOVE hearing audio from NFL quarterbacks, imagine a first person view.
There must be a line though. I certainly wouldn't want laws in my country to force Wikipedia to alter facts based on my location. I suppose it's possible that's already happening.
Autopilot -> Automatic Pilot. Automatic: working by itself with little or no direct human control. Pilot: one qualified to control a vehicle. I'd argue if autopilot requires intervention it is hardly automatic and definitely not qualified to operate a vehicle.
Further, consider other automatic devices in most cars, such as the automatic transmission. How do people expect to intervene with a gear shift during normal operation? Never.
I don't fully understand this opinion. Learning "new" things can be difficult, but there's little "new" in dart compared to other languages. Maybe you can elaborate?
Installing required tools, setting up a project, including debugger, is just damn easy (VSCode extension FTW). Also, any prior experience in mobile using Kotlin, Swift, or JS, translates well to Flutter and therefore Dart. Bonus knowledge bridge for people with MVVM experience due to first class async Streams API and third party RxDart (following ReactiveX spec).
I've had, to my surprise, the most success with Flutter. (I've built multiple React web apps and spent way longer attempting React Native.)
I try to re-evaluate my opinion of the mobile ecosystem monthly, and would love to know how people agree / disagree with my rankings:
1. Just make a web page
2. Native iOS & Android
3. Flutter
4. Some ordering of remaining cross-platform tools depending on requirements. (React Native, Vue Native, Xamarin, Ionic, Titanium, PhoneGap, Kony...)
It is my belief that the Apple iOS docs are just another barrier to developer entry; similar to their $100 yearly license, expensive hardware combined with their WYSINWYG simulator, and woeful iTunesConnect experience.
These barriers to entry, including the poor documentation, definitely have some interesting affects on the ecosystem. I've seen examples of all of these in the real world.
* Experienced iOS devs have a shared trial by fire experience.
* iOS salaries are slightly higher on average compared to Android.
* Skilled iOS devs tend to be excellent developers in general.
* Average iOS devs can be more arrogant and less likely, or less capable, of helping out in other languages and projects. (Apple framework specialist pigeonhole principle)
* There is almost zero culture or standards regarding application architecture or documenting iOS apps.
* Underlying "older" concepts like memory management have been masked, forgotten, and / or ignored.In the early 2000's, CVS started treating patients at their MinuteClinics in the pharmacy. It became directly comparable to an actual doctors office, where cigarettes haven't been sold since the 1950's.
Anecdotally, and ironically, most of the people that are aware CVS made this move are inconvenienced smokers. I'd expect a huge continued marketing campaign around this endeavor in the US, but it hasn't been as strong as many other less impressive campaigns.
Maybe a bad example, but it's basically mandatory to include a manpage for a cli utility, but do you always include drag & drop for a file uploader?
There aren't many reasons an engineer would want to jump into the political fray besides altruism. It's like choosing to join the largest, most corrupt, bureaucratic, change-averse, and valueless company that ever existed. For lawyers, that probably sounds like a dream come true.
My perspective as an engineer: Yes, there are huge important problems I would like to help solve. No, I don't think I'm willing or capable of solving that class of problems in a system like that.