xeonoex
I really don't know what they should do with the money other than make reddit more reliable. It was down last night. The value of reddit is the users/community. Technically, it's a modern message board/link aggregator. There are already many clones.
If you're a restaurant that is constantly smoking meat, you probably don't need a thermometer, but you probably have one. If you're an ordinary person, I would recommend a decent one at least. I have a thermapen. I don't regret buying it. If my fire dies and I don't feel like chopping more wood, or if I just put the brisket in the oven to finish overnight after it gets smoke, I can still know exactly when it's ready. I don't have to repeat the exact same process every time for a good result.
https://www.equities.com/news/robinhood-is-said-to-get-40-re...
https://twitter.com/justinkan/status/1354853920762253315
I'm no market expert, but I know that when cash is flowing between two companies, they generally have shared interests.
And there is no proof Melvin cut their losses. There is no way to know for sure. The shorts are still there, whether they're Melvin or anyone else.
And to add to that, a company (Citadel) that pays Robinhood a large amount of money for their data is one of those with the short positions. So Robinhood itself has a stake in this.
Disclaimer: I have no idea what I am talking about and this is only my opinion.
In simple CRUD cases yes. In many other scenarios, you might not. If your insert is a select statement, with joins and clauses, you can easily insert too much data, or no data at all.
I feel like encapsulation means that functions often should throw errors, because the small, one responsibility functions shouldn't have knowledge of control flow. For example, division. Anytime you divide, you might try to divide by 0. That's an exception. The / operator returns a number or throws an exception. Who would use a TryDivide function? What would it solve? The same error might be an exception in one scope, and expected in another.
I get that exceptions can be expensive, but they should be rare. Saving time on the pre-check for an exception might save more time than the rare exception. I would never throw an exception strictly for control flow, but avoid exceptions is a bad idea IMO.
But the line is very blurry.
RN has to keep the bridge up to date with best practices/deprecation, etc... so that seems like a bigger risk if support was lost. Xamarin did the same and had it's fair share of issues. I'd rather use something with it's own rendering engine. Way less 'magic' that can break.
I don't like coding React/HTML/JS/CSS. It's way easier to write UIs in Flutter IMO. And honestly, I don't even like the aesthetic of native iOS either. I prefer material. I see why web devs would prefer RN though, so there's obviously a huge need for it.
I don't think 'emulate' is the right word. It renders it's UI. I don't get 'how the fake is noticeable'. It might be a little bit different, but the average person won't pick it up.
To me, this is one of it's big upsides. It doesn't have to do all the translation to native. The performance is good. It's easy to write. No quirks of either OS. Though you do have to worry about the individual OS's if you're doing something lower level, but you have the power to do so, so that's still a plus.
Again, this is coming from someone who doesn't do web dev full time, so I'd probably resolve issues faster if I did, but for my side projects, it's too much maintenance. I just want to be productive if I have an hour or so a day. Flutter lets me do that. I write code, code runs on Android and iOS. It's easy. No react/vue/angular, webpack, bootstrap, scss, typescript definition files, or other 'magic' to worry about.
It's easy to setup, install, and it just works. I develop on Windows and Mac with a .NET Core backend and communicating via GRPC. Deploying the backend to a CentOS server. No issues running anything on Windows, Mac, or Linux, surprisingly. Whenever I have to use node, everything randomly breaks when switching environments. (Maybe I'm just bad with node/webpack and all that, but there is way too much I have to know to just build something).
I know web devs probably don't agree, but HTML and CSS weren't designed to build responsive, interactive applications, and all that has to be done to make it work makes it a pain in the ass to setup and develop. With stuff like WASM, Flutter, and Blazor, I'm hoping we have viable alternatives to traditional web development.
The funny thing is, I had to choose my child's age range (or enter the birth year or something) when setting up the app. Then, when I went to whitelist channel by channel, it had a bunch of recommended channels full of good/decent content. That should have been the default whitelist out of the box.
It isn't just about "being a parent". My daughter is very smart for her age. My wife used to be a teacher, but since we had kids, she stays at home with them. She has taught my kids a lot. She has learned a good amount from content on YouTube, Netflix, and Disney. I think it's good that she can use an iPad better than my parents (even though she can't read). She also can solve puzzle games on her own. Of course we guide her and limit her usage. My point is that an app marketed to kids should not be full of garbage content.
You have to whitelist a few channels, then it works ok. Though my daughter is only 3 now, and would be happy watching Blippi all day. Seems like it would be more complicated to whitelist channels as kids get older.
Check out this video: https://www.youtube.com/watch?v=3B4Y_aUBWTM
It's a very simple automation. It just gets text from a browser and inserts it into notepad. But it's a 3 minute video that does something. Check out Selenium tutorials and compare how much you would learn from a 3 minute video. You don't have to dive into the HTML, you just click on what you want to click/type into/scrape and it knows what you want.
But it still has all the power a developer would want. You can create custom activities using C# and VB. The product itself is not open source, but it is very extensible and flexible. The workflows it generates are text files, which work well in source control. It has source control integration built in, which a custom diff tool. It enables code sharing and encourages code reuse.
The only downside I would point out is that it only runs on Windows for now, which might be a problem for linux only shops.
Also, at large orgs, software updates can take _forever_. I know of some examples where updating to the newer version of a B2B software taking 7+ years.
And a lot of those automations will need things like OCR or NLP. Even just out of the box Excel integration is a huge time saver. UiPath has activities built in for that. It's more than just GUI interaction. There's a ton of partner technology with out of the box integrations, and you get frameworks to build your automations on, as well as all of the infrastructure and orchestration.
Disclaimer: I work at UiPath
This is a problem with almost any type of automation. I wouldn't say our software (I am only familiar with UiPath) is finicky. GUIs are finicky, but there are ways to deal with them. That's the stuff a good RPA dev can handle.
I was automating before I started at UiPath, and GUI interaction adds a new layer to automation, of course. But it is still maintainable when you implement them using best practices and CI/CD. I didn't have UiPath at my previous job but it would have made a lot of our automations more reliable and more maintainable. We're also making strides to address these types of problems easier.
I strongly believe that UiPath should a tool in any automation developer's toolbox, as well as GUI testing. UiPath is also pretty easy to use, so business users can automate simpler tasks on their own after going through the academy.
The industry is exploding, and good devs are in high demand. Salaries are high, and you can download Community edition and get certified for free.