You can have the best tool in the world and still find people just hitting their own face with it.
Meme is funny, but that exception used as flow control hurts.
Since witches are generally agreed upon to be nasty bitches, I'd argue they don't care.
That's why he's not worried about stuff running out
He cs_assaulted the counter
In an upcoming post: "Why can't anyone just make a button that automatically hacks facebook???!!!"
It's really interesting how differently you see technology as a professional compared to "normies". So much stuff is easily solved by following instructions or reading error messages.
Well done, here's your price: ๐
You may redeem it for a star on a GitHub repo of your choice.
It all gets put into the main method though in this version ๐
Recently switched jobs from maintaining a 15 year old Windows Forms .NET Framework legacy codebase.
At the new job we stick to Clean Architecture, use unit and integration tests, have a code generation tool, actually make nice use of generics and use dependency injection. Also agile processes, automatic build tools, whatever. The difference is night and day and I'm so glad my ex boss fired me because I told him he's an asshole and his codebase is shit.
Ha! I'm partially looking at this issue in my bachelor's thesis.
It's not at all necessary to embed a browser, but it's really easy to transfer your web app to a "near native" experience with stuff like electron, ionic, cordova, react native or whatever other web stuff is out there. The issue is mostly that native APIs are complicated and relying on web views or just providing your own "browser" is a relatively easy approach.
Stuff like Flutter, Xamarin or .NET MAUI compile depending on the platform to native or are interpreted by a runtime. There's a study I use that compares Flutter to React Native, native Java and Ionic on Android and finds that unsurprisingly the native implementation is best, but is closely followed by Flutter (with a few hiccups), with the remainder being significantly slower.
The thing is. I don't think these compiled frameworks lag behind in any way. But when you have a dev team, that's competent in web development, you won't make them learn C#, Xaml, Dart or C++, just to get native API access - you'll just let a framework handle that for you because it's cheaper and easier.
Edit: To add some further reading. This paper and this one explore the different approaches out there and suggest which one might be "the best". I don't feel like they're good papers, but there's almost no other write up of cross-platform dev approaches out there.
Edit2: I also believe that the approach "we are web devs that want access to native APIs" may be turned around in the future, since Flutter and now also .NET offer ways to deploy cross-platforn apps as web apps. I'll get back to writing the thesis now and stop editing.
Reasonable
It's active users, not total users. I'm not sure on the exact metric, but users need to post, comment, vote or whatever to be counted for this statistic.
So, judging by the wizard frog being clothed. The wizard just told this dude to get naked for what reason? ๐คญ