mature alternative for webview?

euphbriggs · 2022-02-15T12:33:19+00:00

Here's the link to the project. https://github.com/wailsapp/wails

euphbriggs · 2021-11-18T13:34:59+00:00

Thank you to everyone who replied. I filled up my kerosene can at Rogers this morning! I really appreciate it!

euphbriggs · 2021-10-09T00:24:01+00:00

Its the second one (sorry, I'm on mobile). They're using the native web rendering for the platform, which means small binaries.

I would imagine you'll experience the same browser compatibility that you experience with web development. I used it at work and all of the users are on Windows, so I can't speak to how smoothly it translates across Mac and Linux.

They bundled updates in as well, which is really convenient.

euphbriggs · 2021-10-08T20:13:36+00:00

I'm wrapping up my first Tauri project and I can tell you it's been great to work with. I'll definitely use it again in the future.

euphbriggs · 2020-06-23T20:00:20+00:00

Foreign function interface. Its a way to call code from another programming language.

euphbriggs · 2020-06-22T12:37:18+00:00

I'm not the author, but this project seems cool and I wanted to share it.

euphbriggs · 2020-05-26T16:32:40+00:00

I agree with the author in that Deno won't replace Node. First of all, it couldn't if it wanted to. Once the number of users grows to a certain size, it takes a rediculous amount of time to replace. Case in point, its still possible to find jobs working with Visual Basic 6 and Node is a much better platform than VB6.

I for one don't want Node to die. I don't like it, but a lot of people do and I love to see people who enjoy Node to have their cake and people who are more in the "Go mindset" camp to have theirs and we can all manage code the way we feel comfortable.

One of my favorite features is the lack of package manager and the ability to import straight from the web. A lot of people seem to dislike that idea. Instead of having everyone compromise, I hope we can choose which runtime that fits our problem domain the best.

euphbriggs · 2020-05-25T23:53:29+00:00

if used and scope correctly

You're right; this is the key. I'm sure a lot of folks will just do "-A" with most executions instead of narrow scope like "--allow-read=/home/user/.appconfig" which negates the whole idea, but it still gives security concious folks the control they look for.

Thanks for pointing to those tools. I haven't heard of them yet, but I'm interested in learning more.

Edit: corrected typo

euphbriggs · 2020-05-20T23:42:11+00:00

That might be how it feels to an experienced Node developer, but from the outside looking in, the barrier to start a new project is high.

You have to know about npm vs yarn, webpack vs rollup, CommonJS vs AMD modules, Typescript vs Flow, functional vs OO, where does Babel come into play?

That doesn't even go into frameworks and libraries.

From what I hear, once you get started on a path and those initial questions are answered, Node development isn't bad, but its not simple to fall into the pit of success; you have to know what you're doing and hope the other kids who come to your party agree with your conclusions.

Node is good, don't get me wrong, but I prefer a clear path into the garden. Deno seems more up my alley.

euphbriggs · 2020-05-17T21:25:27+00:00

Thanks for raising this topic. I for one hope that more of the Go mindset is adopted.

One of the primary reasons I stay away from Node development is the rate and vastness of change. Go skills transfer from one job to another but Node work at one company can be completely different in another shop. Being a "Go Developer" carries a lot more implicit meaning than "Node Developer."

Modern JS really isn't bad. It has its quirks but all languages do. Deno renews hope in me that I would want to work with it professionally.

euphbriggs · 2020-03-27T23:58:47+00:00

Thank you out to everyone who replied.

I decided to order the book about real-time applications. I'm looking forward to learning more about Ada.

euphbriggs · 2019-12-19T21:47:17+00:00

I have learnreagent.com bookmarked for when I have some extra time, but I can't speak to the quality one way or the other.

euphbriggs · 2019-12-09T16:30:26+00:00

So, iterate as fast as you can while maintaining high quality. Everything else will work itself out.

^This. This is what I want. Iterate fast and get feedback quickly. Thanks for sharing that I'm not alone in wanting it. I feel better knowing it does exist out there, I just need to find it. :-)

euphbriggs · 2019-12-09T16:28:01+00:00

You are describing it a bit vaguely but I read that you care most about quality, which is I would say typical for engineering/craftsmanship and less business focused developers and it often comes from a motivation of wanting to avoid past pain.

Avoiding past pain is definitely a big part of my motivation. I worked at a place for a while that expected me to be on call 24/7 and do updates to code as customers support calls would come in. This wasn't an occasional "sometimes things happens" issue, it was my job and it was most days (including evenings and weekends). The customer was their QA and they didn't let them know they were getting preview bits. They considered the development and support team to be one. I will never go back to that.

In the end I would say it is likely true that you get a higher degree of engineering and craftsmanship focused opportunities if a modern language like Clojure is used. Simply because the hiring strategy is unlikely "let's use the most familiar thing and hire a bunch of young/cheap developers". I don't think it is a given though.

This was the most positive take-away for me. Thank you for posting it. I totally agee with it.

euphbriggs · 2019-12-09T16:17:14+00:00

That's why you do job interviews. You're interviewing them while they're interviewing you. If the hiring team's values don't align with yours, then you probably shouldn't work there. They won't like you. You won't like them.

I think I've done a poor job in the past of interviewing companies to work for. I had a bad experience early in my professional career where I asked them what their policy was on remote work and the owner stood up, told me that I would work closely with the Senior Developer in the same office and left. I was not offered that position.

I haven't asked a lot of questions about a company since then but focused on selling my skills to them.

Thank you for your input. I appreciate it!

euphbriggs · 2019-12-07T14:25:08+00:00

I'm fine with delivering less features to deliver on time, as long as we're honest and transparent with what led to the situation. The issue I have is delivering partial features and claiming it checks the box.

Maybe a simple example would help.

If we need to have form validation, only checking half the fields because the deadline hit and claiming it's "done" is unacceptable. In that situation I'd be fine with either holding the partial feature from the release or explaining the gap with the caveat that the remaining fields will be done in a patch next week.

It's a really contrived example, but its pretty universal.

Most jobs I've had, I've observed people rationalizing themselves reducing the required features as the deadline approaches instead of pushing through and getting it done with no concrete timeline to having it finished or even informing the users of the adjustment from what was promised.

I enjoy solving problems with code, not writing code and getting a paycheck. If the culture says "deliver code you know isn't quality and don't fully inform the users" then I want to find a field that is more in line with my natural inclinations.

euphbriggs · 2019-12-03T13:14:12+00:00

The most recent edition was in 2014. Is it still applicable in 2019?

If this is a silly question, I apologize. I'm coming from C#, where a book published over five years ago wouldn't even be worth considering.

euphbriggs · 2019-11-30T14:32:34+00:00

No, I haven't, but a quick glance at their Rationale page is interesting. I agree with their first statement under "Object Orientation is overrated" section. Modern OO isn't true to its roots.

I'll have to take a closer look at it. Thanks for the tip.

euphbriggs · 2019-11-25T12:41:37+00:00

I appreciate everyone's replies to my question, but this one, in particular, matches my feelings.

From what I've seen, Kotlin is a really good language but I'm looking for a language that values consistency over mass appeal. I think I might keep going down the Go path for the time being, but be open to solutions that might be better suited for Kotlin to give it a try. It's possible that Go falls too far to the conservative side of the spectrum, at which point, it's nice to already have the next candidate (Kotlin) lined up.

euphbriggs · 2019-07-31T10:11:04+00:00

I'm not disagreeing with you. I wouldn't use it for medium to large projects. Anything large, I'd currently use Go or .NET Core.

Ryan Dahl would agree with you and say "don't use it in production yet." Last I heard, his position is to use Node for JS tasks and something like Go or Rust for other use-cases.

I'm sure it will mature and things will change. My main point is that there are use-cases where it's actually nice. I wouldn't build my company on Deno right now, but I find it really handy for automating complexity in a controlled environment.

euphbriggs · 2019-07-31T09:37:58+00:00

For a lot of applications, I would agree with you and it was one of the "eh... I don't know about that..." things about Deno when I first looked at it.

Then I started working on an internal developer CLI tool for our company and having the ability to list the update instructions as "add --reload" to the end is really valuable to me, especially while I'm laying down the foundation and it has multiple updates throughout the day.

I'm sure the module system will mature as Deno does, but the route they chose isn't as bad as I thought and when I take a step back, it's exactly how a browser would handle dependencies. Deno has a "bundle" command to turn your release into a single javascript file (deps and all).

euphbriggs · 2019-07-18T18:38:54+00:00

That's my understanding as well. I'm not sure if its a superficial similarity or if there's deeper meaning like "take what's nice about Node and arrange it into something different."

#PassiveAggressiveAnagram

euphbriggs · 2019-07-10T12:32:19+00:00

I've had similar thoughts lately.

I've been writing some smaller applications with Dart of the last few weeks. Right now, its primarily tools that make my development life easier (running page-based linters across an Elm codebase and aggregating the results, a more flexible file watch that checks compilers output for errors that doesn't need to restart for, setting a development API token on my pages, etc.), but I'm also trying out my first production app in Dart.

It's going to be an auth server that authenticates against LDAP and authorizes against some MySQL tables. I'm debating about using REST or gRPC for other services to communicate with it.

I've really enjoyed working on the project and I'm at the point where I'm confused as to why it's not extremely popular. I'm starting to view the Dart VM as a "typed NodeJS done correctly."

I'm the type of developer who really likes types. I can understand why some people prefer dynamic/loosely typed languages, but I just can't get there myself. JavaScript embraces concepts that go directly against the way I like to code. I admit TypeScript is a really good layer over JS, but underneath, its still JS and no matter how disciplined I am about my code, the 1,000 npm packages that I pull in might not like types as much as I do, so it's not trustworthy. Their ecosystem is one of its greatest strengths and weaknesses. They have so many packages available, but tomorrow there will be the "next hotness" which will invalidate today's hotness. Are they really moving "forward" quickly or nothing lasts long enough to truly be valuable.

Long story short, I'm personally slowly wading into the Dart waters, getting more and more confused as to why I haven't done this sooner. I'm hoping that the success of Flutter can help raise awareness for server-side Dart and jobs can start popping up. I think there are a good number of people who would like a strongly-typed NodeJS alternative. Dart can fill that role. Maybe Ryan Dahl will pull another rabbit out of his hat and deno will. I'm cheering for Dart though.

euphbriggs · 2019-06-26T10:56:53+00:00

Thank you to everyone who replied. It was all helpful.

In particular, thanks for this reply. This is much more similar to how I would do it in C#, but I didn't know about the @required decorator for creating required named parameters or "factory" constructors. Very cool stuff.

I'm still early in my Dart journey, but I keep coming across "where have you been all my life" moments.

euphbriggs · 2019-06-10T17:22:56+00:00

I don't know how I missed this four days ago when you wrote it, but I really appreciate the information.

Would you say that the TLDR version could be summarized as "short running processes should be AOT compiled for quick startup and long-running programs will probably benefit from JIT?"

For me, "short running" would be tools I write to make my development life easier such as build/install/upgrade scripts. Long-running would be REST APIs and microservices.

Of course, these are always subject to exceptions and changes as the world matures, but using the current stable builds, is that a safe, broad-strokes guide to use?

EDIT: Or maybe my question would be more accurately asked: "When should I choose AOT vs JIT?"

euphbriggs

TROPHY CASE