7 ms·
My field is web development, and, to be honest, the most exciting thing going on is that more people are starting to complain about the complexity of developmen
by onion2k 10y ago
My field is web development, and, to be honest, the most exciting thing going on is that more people are starting to complain about the complexity of development. Hopefully this will lead to people slowing down and learning how to write better web software.
As an example, one survey (https://ashleynolan.co.uk/blog/frontend-tooling-survey-2016-results#js-testing https://ashleynolan.co.uk/blog/frontend-tooling-survey-2016-...) put the number of developers who don't use any test tools at almost 50%. In the same survey about 80% of people stated their level of JS knowledge was Intermediate, Advanced or Expert.
- Illniyar 10y agoTo me as a web developer, the most exciting new development is react native (not react itself) - it's redefining the border between web and native apps in a way that cordova and xamarin never did.
- subpixel 10y agoAs a web dev, the most exciting development I see is the rise of progressive web apps and a shift away from native apps in situations where web-like experince is more appropriate. That said, I'll be thrilled if React Native gives rise to higher quality apps in situations where a native app is unavoidable (e.g. my bank's app).
- pg_is_a_butt 10y agouh... why is a native bank app unavoidable? you're all idiots.
- swyman 10y agoWhat kinds of situations do you think are more appropriate for web or web-like apps?
- subpixel 10y agoI'm actually hard-pressed to think of any non-gaming interface that is better suited by a native app than a web app in 2017. Five years ago native apps made a level of UX possible that was unheard of on the web, to say nothing of mobile. But today not only has HTML/js closed the gap, but whiz-bang native animations aren't impressive just on account of being novel anymore.
- amelius 10y agoI'm feeling that React Native is just another artificial constraint we developers have to deal with. I would have preferred it if Facebook (and/or Apple, Google) would have pushed WebApps more instead. A web browser, with the right amount of love, would be more than capable of doing the stuff that React Native can do.
- jdormit 10y agoGoogle still is! Progressive web apps now have the ability to be installed "natively" on Android devices [0], meaning they show up in the app drawer like any other app rather than being limited to a home screen icon. I think these are the future. Once they catch on with mainstream consumers, native apps won't stand a chance against the convenience of simply visiting a website to install/use. Plus, on the developer end, we finally have a true "write once, run anywhere" situation that doesn't involve any complex toolchains or hacky wrappers. [0] http://www.androidpolice.com/2017/02/02/progressive-web-apps-will-soon-act-like-native-applications/ http://www.androidpolice.com/2017/02/02/progressive-web-apps...
- amelius 10y agoThat sounds absolutely fabulous! But do you think that Apple would embrace this technology, given that e.g. their app-store is generating lots of revenue?
- arvinsim 10y agoAsking the right question. And that's not sarcasm.
- thunderrabbit 10y agoThey won't, but they eventually won't have a choice. If the experience is simply better on other devices, consumers will move.
- jdormit 10y agoNot at first. But if the tide turns enough, Apple with have to jump on board to avoid losing market share.
- pwython 10y agoI've been interviewing junior/intermediate frontend candidates for the past few months now. 90% don't use any test tools, and their biggest complaint is their current employer forcing a new framework/library for the sake of being bleeding edge. While interesting to them, it turns out most of them really just want to see what they can do with vanilla JS.
- lisivka 10y agoWhy you expect that junior developer (someone with very little or no development experience) will use a test tool or any other development technique? I expect that junior developer in software field should be able to program only.
- devwastaken 10y ago>Why you expect that junior developer (someone with very little or no development experience) I don't think thats the definition of a junior developer. Test tools are apart of building software, you should be hiring devs that have created projects that use tests of some sort, if not with the technology you're using. >I expect that junior developer in software field should be able to program only. I don't know how you can have little to no dev experience and know how to program.
- lisivka 10y agoDevelopment and programming require different skills. Developer need to know development cycle, automated testing, continuous integration, software life cycle, ticketing systems, source control systems, branching and merging, cooperating, etc. Programmer need to know programming languages, patterns, algorithms, computer internals, effectiveness, profiling, debugging, etc. Junior developer (in software filed)) has no or little experience in development, so junior developer is almost equal to a programmer, which causes lot of confusion.
- blablabla123 10y agoI think this distinction is a bit ancient...
- donaltroddyn 10y agoYeah, this is one area where webdev is way behind other fields, and i think we're going to see lots of new tooling in this area soon. We're currently working on a way to help devs test web app functionality and complete user journeys without having to actually write tests in Selenium or whatever. The idea to is let devs write down what they want to test in English ("load the page", "search for a flight", "fill the form", "pay with a credit card", etc), then we'll use NLP to discern intent, and we have ML-trained models to actually execute the test a browser. You can give us arbitrary assertions, but we also have built-in tests for the page actually loading, the advertising tags you use, page performance, some security stuff (insecure content, malware links). At the end we hand you back your test results, along with video and perf stats. It’s massively faster than writing Selenium, and our tests won’t break every time an XPATH or ID changes.
- onion2k 10y agoSounds intriguing. There are a few tools for recording interactions with a webpage in order to replay the actions as a test (Ghost Inspector, Selenium IDE, etc) but they tend to be pretty horrible. I've been working on my own as a Chrome extension for a little while. What you're building sounds really interesting though, especially if it can deal with complex Javascript apps. Anything that can make developers more inclined to test things is a good thing.
- donaltroddyn 10y agoYeah, I've looked at all the current tools and there's basically two types (other then just writing straight Selenium): - Test recorders that aren't a great experience and output incomprehensible, brittle tests. - Test composers that I can best describe as 90's SQL query builders for Selenium. Complex JS apps are still a challenge for us (especially with some of the WTF code we come across in the wild), but we have a strategy in the works for them. We're still pre-release though. If you're interested, send me an email (donal@unravel.io) and I'll add you to our alpha list.
- retreatguru 10y agoWe are using ghostinspector mainly for it ability to compare screenshots between runs. I think the future of testing will be apps like this that don't require you to specify every little div but just record your actions and play them back and catch differences. Right now ghostinspector only takes a screenshot at the very end but they are adding a feature where you can take a shot anytime. As these apps get better at knowing what matters and what to ignore - all the better.
- amelius 10y agoThen, considering that if people don't spend sufficient time/money on proper testing, how much time/money do they spend on security? Probably even less.
- moron4hire 10y agoIf you are counting on people slowing down, you're in the wrong business. You're asking the wrong question. It shouldn't be "how do we get people to slow down?" It should be, "how do we make rapid software development better?"
- vram22 10y ago>the complexity of development Huge and seemingly often unacknowledged issue these days. And many attempted solutions seem to be adding fuel to the fire (or salt to the wound) by creating more tools (to fix problems with previous tools) ... Red (red-lang.org) is one different sort of attempt at tackling modern software development complexity. Its like an improved version of REBOL, but aims to be a lot more - like a single language (two actually, RED/System and RED itself) for writing (close to) the full stack of development work, from low level to high level. Early days though, and they might not have anything much for web dev yet (though REBOL had/has plenty of Internet protocol and handling support).
- pault 10y agoI think the most exciting trend in web development is the rise in popularity of functional programming styles in front-end frameworks. This makes the complexity problem much easier to solve, as the code is (should be) less likely to cause an unanticipated mutated state which can't be easily tested for.
- allanmacgregor 10y agoIs not only the front end the backend is also getting a fair bit of traction.
- swyman 10y agoWould you mind sharing an example or pointing me to a good guide that explains this concept? How does functional programming make a problem less complex than OO or imperative? I've heard this a couple of times, but the intuition has never quite clicked for me.
- morenoh149 10y agoIts state. Functional programs tend to have less state as their output is the same for some given input. With things like jquery you quickly introduce state, say is some dropdown open, which your next function will have to check is true or false before proceeding. And so on.
- pault 10y agoI'll give it a shot; functional programming style--some languages enforce it, some languages merely have features that allow for it if the author is disciplined enough to do so (JavaScript is in the latter camp)--generally eschews mutable state and side effects, i.e. a variable `foo` that is declared outside of the function cannot be altered by the function. Some "pure" functional languages restrict all functions to a single argument. This may feel like an unnecessary constraint (and opinions vary), but one thing that can't be denied is that it keeps your methods small and simple; in any case, it can be worked around by applying a technique called "Currying"[1], which is named after the mathematician & logician Haskell Curry, not the dish (also the namesake of the eponymous functional programming language [the mathematician, not the dish]). Because nothing outside of the function can be changed, and dependencies are always provided as function arguments, the resulting code is extremely predictable and easy to test, and in some cases your program can be mathematically proven correct (albeit with a lot of extra work). Dependency injection, mocks, etc are trivial to implement since they are passed directly to the function, instead of requiring long and convoluted "helper" classes to change the environment to test a function with many side effects and global dependencies. This can lead to functions with an excessively long list of parameters, but it's still a net win in my opinion (this can also be mitigated by Currying). A side-effect (hah) of this ruleset is that your code will tend to have many small, simple, and easy to test methods with a single responsibility; contrast this with long and monolithic methods with many responsibilities, lots of unpredictable side effects that change the behavior of the function depending on the state of the program in its entirety, and which span dozens or hundreds of lines. Which would you rather debug and write tests for? Tangentially, this is why I hate Wordpress; the entire codebase is structured around the use of side-effects and global variables that are impossible to predict ahead of runtime. There is much, much more to functional programming (see Monads[2] and Combinators[3]), but if you don't take away anything else, at least try to enforce the no-side-effects rule. A function without side-effects is deterministic; i.e. it will always give you the same output for any given set of inputs (idempotence comes for free). Because everything is a function, functions are first-class citizens, and there are only a few simple data structures, it becomes easy to chain transformations and combine them by applying some of the arguments ahead of time. Generally you will end up with many generalized functions which can be composed to do anything you require without writing a new function for a specific task, thus keeping your codebase small and efficient. It's possible to write ugly functional code, and it's possible to write beautiful and efficient object-oriented code, but the stricter rules of functional style theoretically make the codebase less likely to devolve into incomprehensible spaghetti. Manning Publications has a book[4] on functional programming in javascript, which I own but haven't gotten around to reading yet, so I can't vouch for it. However, it does seem highly applicable. [1] https://en.wikipedia.org/wiki/Currying https://en.wikipedia.org/wiki/Currying [2] https://en.wikipedia.org/wiki/Monad_(functional_programming) https://en.wikipedia.org/wiki/Monad_(functional_programming) [3] https://en.wikipedia.org/wiki/Combinatory_logic https://en.wikipedia.org/wiki/Combinatory_logic [4] https://www.manning.com/books/functional-programming-in-javascript https://www.manning.com/books/functional-programming-in-java...
- PicoCreator 10y agoIt's probably just a matter of time. Because all software ecosystems goes through its phases of "maturity" regarding testing. Not too long ago (in human-years, not internet-years). Most node packages weren't built with unit testing. Now its quite common in the popular packages. Website UI is probably the same thing. After all, it took us a really long time till we got the whole HTML5 spec finally stabilised. So you will probably see the tipping point occur over the next 10 human years, or less. And just like you I been really frustrated with the inadequacy of UI testing tools, especially with Selenium. So like @donaltroddyn, I set out to develop my own UI testing tool (https://uilicious.com/ https://uilicious.com/), to simplify the test flow and experience. So wait around, you will see new tools, and watch them learn from one another. And if you want to dive right into it, we are currently running close beta.
- greggman 10y agoThere's a market imo for a full solution that includes front end and entire backend including deployment, seemless scaling, seemless upgrading, seemless backups, seemless local dev, seemless staging, etc. 99% of web apps need the same features but most of this is still up to manually rolling your own. I should be able to clone some repo, enter some DO/AWS/GOOG keys and push.
- jfindley 10y agoI admit I'm not terribly familiar with it, so I might be misunderstanding, but isn't this more or less what AppEngine is?
- megalodon 10y agoThis solution is the opposite of "slowing down and learning how to write better web software".
- acid__ 10y agoI've been using and loving Zappa[1] lately. Basically it lets you seamlessly deploy a flask app to AWS Lambda -- that solves your deployment, scaling, upgrading, staging, backups, etc. And local dev is just running the flask app locally. [1] https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa
- romanovcode 10y agoThe problem is that every developer creates his own way of doing these things and you have a complete mess without any standard way of doing things.