Earlier quoted context omitted.
I hate the fact that Ruby doesn’t get more love. It’s a great language on its own. It doesn’t need Rails.
I like Ruby, I hate Rails. But Sinatra is awesome.
[deleted]
Why Is Front-End Development So Unstable?
141–150 of 366 posts
Re: Why Is Front-End Development So Unstable?
#142Earlier quoted context omitted.
I like Ruby, I hate Rails. But Sinatra is awesome.
Personally I'd rather use Grape over Sinatra. I also wrote Modern[0] to provide a really nice, functionally-oriented OpenAPI server for Ruby that is very much Not Rails. (Looking at porting it to TypeScript soon to provide a similar-feeling API.) [0]: https://github.com/modern-project/modern-ruby
Will take a look, thanks.
Re: Why Is Front-End Development So Unstable?
#143React is only 3 years old?!?!
It's 5.
Re: Why Is Front-End Development So Unstable?
#144React is only 3 years old?!?!
No... It was release in March of 2013, making it more than 5 years old.
Re: Why Is Front-End Development So Unstable?
#145Is there a difference between "Medium" and "Self Promotion"?
I tried barking up that tree a year or 2 ago when Medium took over HN.
Re: Why Is Front-End Development So Unstable?
#146It's also very unstable and young because requirements keep moving, and developers keep figuring out more 'auto-magic' and simply better ways of implementing UIs. UI used to be simple, a page, a few links, click through to other pages. Then we needed templated pages, because we had a lot of pages. Then full blown 'applications' were ported to the web, and life was a nightmare of double-headed dragons and dark holes w…
To expand on your point, somewhere along the line, the web went from a content delivery mechanism to a full GUI + content delivery mehanism.
The allure and advantages to developing a full GUI on the web are many, including portability and availability.
But the downside is that you are suddenly developing to the lowest common denominator - the browser - which not only has to support the "old" web but complicated GUIs (something it was never designed for), which in turn means all sorts of "magic", as you put it, to make it work (i.e. crazy DOM manipulations).
And because browsers were never designed for this, there is no One True Way to develop a simple user action. Search for "drag and drop in javascript" for example. So what happens is, everyone invents their own way of doing stuff, which turned into a race of who is more popular/clever, resulting in a gajillion ways to do the same thing.
Re: Why Is Front-End Development So Unstable?
#147At some point, when modules get "micro" enough, the effort of managing them and learning their usage outweighs the effort of implementing the thing yourself. Most JavaScript projects seem to walk that line quite closely. I'm a React developer at work, but I recently gave Vue a try at home. This is one of the things that most stood out to me about it. React makes a selling point out of the fact that it's "just renderi…
The script tag approach is nice and lowers the threshold for the curious, but looking back, I'd recommend starting with vue-cli right away, because as your app grows you'll run into limitations of that setup, esp. with more advanced babel features, runtime transforms, ... The warning about using the cli in the vue docs is imo a bit exaggerated, you get some nice prompts and an equally smooth experience :)
Re: Why Is Front-End Development So Unstable?
#148This is a really well-written and well-thought out piece. The author touches on a number of points but never gets polemical. This piece resonated with me particularly well: > Be wary of self-promotion > Over the last few years I’ve seen much more aggressive self-marketing in the JavaScript world, possibly due to the rise of paid online training materials and the employment/consulting advantage of being a Github ‘cele…
It's a problem for other communities, like Python. I read a blog post recently from a well known python dev where he talks about explicitly cultivating "fame" around his open source tools. My experience, as one who has tried to promote my own tools, is that literally nothing good will come of it for the community as a whole. It's a bad practice in my opinion. For example: https://github.com/pypa/pipenv/issues/2228
What incentives would a someone have to invest a considerable amount of time in releasing and maintaining an open source project if they can't even use that to promote themselves?
Re: Why Is Front-End Development So Unstable?
#149Web frameworks are churn-y because they are incredibly leaky abstractions covering really awkward impedance mismatches. This means that they are never quite satisfactory - and that just to use one, you need to be capable of building a new one yourself. Think of a typical web app. Your data exists: 1. As rows in a database, accessed via SQL 2. As model objects on the server, accessed via method calls and attributes 3.…
(B) Nails it.
I'd guess that a large portion of new frameworks start simply because everyone who spent enough time with the old one gets sick of the bad or non-existent documentation for edge cases, etc.
Rinse and repeat.
Vue is no better, after reading the rest of the comments. In many ways worse.
Re: Why Is Front-End Development So Unstable?
#150It's unstable because there are millions of developers working with front end technologies and that community is rapidly finding better ways of doing things.
And when better ways are found, because development is so time consuming and difficult, people move to embrace those new and better ways.
I'm glad of the rapid change because there is alot more improvement needed at the front end.
Consider for example the vast amount of crushingly complex configuration that is required for many front end development tasks - this is yet to be addressed, although giant leaps have been made - such as create-react-app - thank god.
JavaScript has to become "zero configuration" to the greatest extent practical, and JavaScript programmer should dump configuration heavy tools as soon as they possibly can for zero configuration tools.