7 ms·
I am not badmouthing JavaScript or bandwagoning on the "Electron is the devil. Long live native apps!" But I've been wondering more and more, especially throug
by Waterluvian 9y ago
I am not badmouthing JavaScript or bandwagoning on the "Electron is the devil. Long live native apps!" But I've been wondering more and more, especially through my own experienced biases at work: how much of the, "we chose x because y and z" is retroactive justification for the simple truth: "I wanted to use the technologies that make me enjoy my job."
I often have to fight with myself to pick the right tool for the job, not the tool that makes my job the most fun to do.
- joshmarlow 9y agoFirstly, I agree with you! I like the philosophy that "Production should be as boring as possible." That being said, using tech that makes you enjoy your job will help you be more productive and potentially attract enthusiastic developers. I feel there's probably a balance (as in all things) between boring production/exciting development - but I don't feel I hear that discussed often enough.
- beckler 9y agoI heard once that if you're doing something boring to pick an exciting technology. If you're doing something exciting, pick a boring technology. Not sure what you would consider exciting or boring, but I thought it was decent advice.
- jkmcf 9y agoThat advice is good when you only report to yourself. If you report to a company and your decisions affect $$$$, directly or indirectly, then it's probably the worst advice.
- vog 9y agoDo you care to elaborate? That doesn't make any sense to me, as the advice given above is exactly what you should do in a company, if I understood it correctly. (Higher risk on a simple project, because that's the only opportunity to learn new stuff, as in the worst case you can start over. Lower risk for a complex project, because there's already enough risk in the project itself.)
- shakna 9y agoProcessing transactions at a bank is "boring". It's simple, apart from scale, and the spec is usually insanely well documented. But if you reach for that new language that hasn't been battle-tested yet, you're probably screwing the bank over.
- ExactoKnight 9y agoI'm in banking at a startup level and I'd have to disagree with this. There is tremendous fear in the industry right now over being seen as outdated or dinosaur, especially with all the blockchain hype. You can make simple technology choices like moving from a stateful SQL database over to a blockchain ledger like Sequence, and in doing so, you will attract a way higher calibre level of talent. You will also have way more people interested in working for you, and the skillsets and knowledge learned within the company for doing it will future proof you far better than going the boring old route.
- shakna 9y agoI'm one of the contractors that rolled out instant transactions at CBA. The feature is absolutely hype, and a selling point, or was til the RBA required everyone else to follow suit. But it doesn't change the fact that fundamental things that cannot be allowed to fail should not be built on twigs. CBA worked with Wells-Fargo to build a blockchain ledger, running atop skuchain, which itself Go and JS. That's a lot of hype and new in one place. But it wasn't in a simple systems-critical place, it was done for one contract, with one customer first, with regulatory approval for the experiment, to see if blockchain technology was feasible. It was also not proof that this can scale, that needs more experimentation. Lots of simple things are fundamental, and you do not mess with those. Simple/complex isn't enough to say whether you should experiment, because experiments should be as far from impacting your bottomline as possible. R&D should stay in R&D, until it is proven stable. You can't afford to build a house of cards.
- jkmcf 9y agoThe main gist is whatever you add to the company stack, the company is now responsible to maintain, possibly forever. My current situation is basically this times 10 since the people who did exciting tech left. If the team and managers agree, by all means use the exciting tech, but it isn't a decision to make in isolation. The canonical link on choosing boring technology is http://mcfunley.com/choose-boring-technology http://mcfunley.com/choose-boring-technology. A relevant example is microservices which are all the rage right now. But, you have to be this tall to use them[0]. You cannot effectively just say you are going to do microservices, especially if you don't know how to do microservices. Alternatively, consider the potential problems for your company if you had introduced React on your own in a core business element, and your company had a patent beef with Facebook, and FB hadn't switched to the MIT license. [0]: https://martinfowler.com/bliki/MicroservicePrerequisites.html https://martinfowler.com/bliki/MicroservicePrerequisites.htm...
- nnq 9y ago> If you're doing something exciting, pick a boring technology. Not being exceedingly serious here but... you pretty much summed up why Python is so successful in AI/ML and science ;)
- espadrine 9y agoHow does that follow? The boring technology in AI/ML is C++. Which is why TensorFlow etc. have a boring & hard C++ core, and a lovely & easy Python layer that transmits the computational graph to the core. Electron is similar: a boring & hard Chromium C++ core, and a lovely & easy JS layer. What pains me is that there is no reason to include libraries we don't use. Each Electron embeds a large amount of memory-consuming libraries that do things that are way out of scope for most apps: screen recording, sound editing, GPU graphics libraries…
- nnq 9y agoPython is a boring technology. It's a 10+ years old language, like ~20 years behind cutting edge programming language research and implementation. Also, as for the programming style it encourages, it strongly nudges you against any "cool" way of programming: even the most basic kinds of functional programming is something you end up avoiding in P and "dumbing down" your code to more procedural idioms, and OOP over-over-over-architecting is something you just don't do because of the performance penalty and the lack of serious refactoring tools for large codebases. The side effect is that all code is more readable and understandble to anyone, including self-taught devs. JS itself is a boring language at its core too, except that it evolves faster than anything else. And the ecosystem is anything but boring (and also anything but sane...). Cooler and more advanced (in terms of language features) languages are Julia (it has real macros, advanced type inference etc.) and even R (yeah, it's a mess, but as a language it's more advanced and "cooler" than Python). On the "web backend" scene Ruby is a way more "not boring" language, but the ML and science communities avoided it almost completely (I have a few theories as to why...). And then there's the "truly cool" and "0% boring" languages like: Scala, Rust, Elixir, Clojure, Haskell, Elm, Crystal, Pony etc. But don't get me wrong, I like Python for being what it is: an incredibly boring scripting language, that encourages a "stone age level" style of dumbed-down programming. With slightly awkward but stable libs (on which people agree almost unanimously of which to use). Because with Python I can focus on the product instead.
- dchuk 9y agoMost engineers have this bias. Feigned justification for biased decisions in the past rather than challenging original assumptions in the first place.
- smacktoward 9y agoI would phrase the problem slightly differently: not "I want to use the technologies that make me enjoy my job," but "I want to use the technologies that I already know." Electron is popular because it lets you write desktop apps in JavaScript, and there are a lot of developers out there who know JavaScript. By going with Electron, those developers can build desktop apps without having to learn anything new. They can extend their existing skills into a new arena, without having to learn any new ones. Developers are always asked to turn products around as fast as they possibly can (and, um, also people are lazy), so this is a very powerful appeal. This "I don't have to learn anything new" factor is literally the only thing Electron has going for it. Using any other alternative will result in applications that perform better, fit into their host environments more naturally, and generally work better than an Electron app will. But there are a lot of JavaScript developers out there, and any other alternative would require all those folks to learn a whole bunch of new stuff to get started -- new languages (C/C++, C#, Java, Python, etc.), new toolkits (UWP/Win32/Cocoa/whatever, Qt, WxWidgets, etc.), new programming paradigms, etc. etc. etc. Whereas with Electron they can pick it up and be productive in a couple of hours, which is a hugely appealing prospect. Tools that let people leverage what they already know will always do better than those that require a whole bunch of learning up-front to use. Electron is just the latest example.
- Waterluvian 9y agoI don't disagree with your analysis, but I disagree that it's a simple rephrase. They are two separate issues: 1. Pros/cons of using tools we already know 2. Pros/cons of using tools we enjoy using I am awful at Docker because I started using it yesterday. But upon using it, I'm suddenly so attracted to it and am thinking about what fun personal projects I can apply it to. It's a beautiful technology. I am very strong in JavaScript but love avoiding it like the plague unless it is the appropriate technology. Edit: okay I'm skeptical of a part of your analysis. Please show me a detailed example of building a desktop app that runs on Mac/Windows/Linux, looks reasonable, and takes the same or less time from a competent developer. I am genuinely starving for an alternative to Electron that doesn't come with a significantly heavier dev/support cost.
- stupidcar 9y ago
- brlewis 9y agoFree software is obliged to use technologies that make contributors enjoy their job, especially for a project like Atom where you can't expect an individual or small group to do all of it.
- redwall_hp 9y agoIs it really bandwagonning to be annoyed that so many bits of software, which many people run simultaneously, use a tool where a Hello World is over 100MB in memory? At least the Electrino idea is more reasonable. Using a framework already loaded into memory by the OS and sharing it would go a long way toward reducing the bloat...though not toward the horrible battery problems it introduces. Seriously, people are still brushing aside issues with something where a blinking cursor caused CPUs to crank up to the max...
- styfle 9y agoElectrino was a great idea, but the project was more of a POC and I haven’t seen any new development. So until someone can build a production ready, cross platform, JS desktop experience....Electron will live on.
- jopsen 9y agoOn android I think both Chrome and Firefox supports installing a website as an icon on the home screen. It might already hide the address bar when opened in this mode. I personally expect that it's just a matter of time before this becomes an install mode for desktop apps as well.
- flukus 9y agoWhen I check where my battery life is disappearing will these apps appear under Firefox/chrome or the app name? It sounds like a promising avenue for bitcoin mining.
- c909 9y agohttp://fluidapp.com/ http://fluidapp.com/
- styfle 9y agoYou fail to realize the purpose of Electron. It’s not to wrap a website, it’s to add features that the web doesn’t offer. For example, how could Atom exist and be able to show your files in the explorer pane as a web app? It can’t. Electron adds the missing pieces/permissions that desktop apps have had since the beginning.
- zimbatm 9y agoHere are some more reasons to pick a technology: Familiarity, knowledge transfer is a big drive for technology adoption. The bad bit is when the decision maker leaves the team and the rest are unfamiliar with the tech. I think this applies to Electron pretty well as web developers can now contribute. The "it would look good on my CV". I'm thinking about Kubernetes where it doesn't make sense to use most of the time but everybody wants to be doing it because it's hot.
- pjmlp 9y agoThanks to Docker and Kubernetes, everyone that cares about DevOps needs to brush up their Go skills, regardless how we might think about it. However this is a part of being professional, using the required tools for the job.
- rolypolypup 9y agoI wish engineers and computer scientists would pay attention to that gut reaction more often. Programming really at some level is as much about translating human ideas into physical computations as anything. In this regard, it is a fundamentally psychological process, as much about the programmer as the computer. There's a sort of psychological-cognitive -> math -> physics process, and I often feel as if the emphasis is on the second two steps, and not so much on the first two. There's good reasons for this, but it's resulted in a sort of blind spot that often comes out as people just preferring languages like python or javascript or whatever, and not wanting to acknowledge that those fuzzy, poorly understood preference processes are driving development as much as the choice of algorithm or hardware constraints. I think it's poor ergonomics, really, and effects things as much as memory management models, etc. We're at a stage, though, where languages like Nim, etc. offer some promise of ergonomics and performance, and I hope people will pay attention to it carefully, so we don't end up in the same situation as the one Atom exemplifies. I like Atom, and don't have any particular attachment to Nim, but do think there's something we shouldn't be ignoring anymore. Often when a language is difficult to intuit, the reaction is to shame the programmer, to characterize them as not smart enough to understand the language. Sometimes there's some truth to that, but sometimes I think it reflects deficits in the language, whose sole purpose, really, is to translate human thoughts into computational events.
- jimbokun 9y ago"There's good reasons for this, but it's resulted in a sort of blind spot that often comes out as people just preferring languages like python or javascript or whatever, and not wanting to acknowledge that those fuzzy, poorly understood preference processes are driving development as much as the choice of algorithm or hardware constraints." One language that openly acknowledges it is designed first and foremost with psychological factors and ergonomics in mind is Ruby: "For me the purpose of life is partly to have joy. Programmers often feel joy when they can concentrate on the creative side of programming, So Ruby is designed to make programmers happy." https://github.com/alexch/ruby_notes/blob/master/ruby-intro.md https://github.com/alexch/ruby_notes/blob/master/ruby-intro....