191–200 of 243 posts
Microservices are the new hype with related tech. It's DDD with a new jacket, requires a devops team and it has some interesting concepts though. Almost no one has a decent implementation for micro-frontends. Although ING bank released a nice framework related to this - https://medium.com/ing-blog/ing-open-sources-lion-a-library-...
The first rule of DevOps is that if you have a DevOps team then you're not doing DevOps.
Earlier quoted context omitted.
> language of choice for the working class dev What an incredibly strange framing.
That was my initial reaction too, but then I found it hard to disagree with (in the general case of course) and instead thought maybe it's an astute and interesting observation. The more familiar slight is that it's 'the language of choice for script kiddies', but I suppose they've grown up and gotten apprenticeships.
Earlier quoted context omitted.
I am a Python / Django guy given the choice. Python may be a slow language, but I haven't seen many places where python is the cause of the bottleneck. Rewrite stuff so that the database is doing the heavy lifting, and add the appropriate indexes and you shouldn't have any problems. SPA's are a pain in the arse. Usually close to twice the amount of code to avoid page refreshes. Usually the apps are way slower than a…
I disagree. I think SPA's are fantastic. Sure, they can be misused, but so can most things. I'm an intermediate level web developer. I enjoy working with ReactJS-- I like that it's a framework and way of doing things. 1. manages to accomplish everything that I need to get done 2. has a huge community & huge amount of open source reactjs components available 3. is highly customizable If one isn't going to use a modern…
> ReactJS in my experience makes development faster, easier, better organized and more enjoyable.
Maybe it makes development faster, but in my experience it makes debugging someone else's code a whole lot more difficult. CSS for example. It seems nice to define the style in the same file as the component code and it makes development a little bit faster. But when you have to debug, it's far easier to have styles defined in classic stylesheets in a different file rather than trying to track down the location of some dynamically generated CSS class. (I know as I have been degugging code that was written by an agency, and the CSS styles are defined in a mix of both React files and normal CSS).
From your list of benefits I don't see anything that couldn't be achieved with sever side rendering and a bit of jQuery. If your front end needs to have a lot of user interaction, then SPA's will be the correct tool for the job. For most web apps they are overkill.
The React frontend we have at my current workplace is incredibly bloated compared to a similar complexity website I created using Django and Jquery. Doing certain simple tasks is like pulling teeth.
Earlier quoted context omitted.
I disagree. I think SPA's are fantastic. Sure, they can be misused, but so can most things. I'm an intermediate level web developer. I enjoy working with ReactJS-- I like that it's a framework and way of doing things. 1. manages to accomplish everything that I need to get done 2. has a huge community & huge amount of open source reactjs components available 3. is highly customizable If one isn't going to use a modern…
What about the server-side of things? If you only have to the UI sure, but if you have to write the whole thing, rails/django is going to be way less work. No need for an intermediate network JSON API with all the encoding/decoding that it entails, just routing on one side instead of two and many more.
Why do we need frontend routing?
Earlier quoted context omitted.
>"AWS has started to take on third-party, open source components e.g. Cassandra, ElasticSearch, MongoDB as they run out of things to build." I'm aware of their Elasticsearch and MoongoDB offerings but what is their Cassandra offering?
Dynamodb
Earlier quoted context omitted.
We moved from one big box to Kubernetes. Now we have a load of kubernetes related problems to fix.
Learning pains? It is more complex, but the efforts will return value. Email me if you'd like some help debugging and stabilizing
So far I have seen little benefit.
I think React is "winning" the framework competition, if we're judging from number of jobs. It seems like a business decision for many people - React can make websites and apps, and it's probably easier. I haven't had enough experience to say, but it seems like Java; not necessarily the best tool, but something easy to hire for. Flutter is also coming in hard on mobile. Also not something I've had enough experience t…
React + TypeScript seems to be to frontend JS as JEE was to Java.
Earlier quoted context omitted.
React + TypeScript seems to be to frontend JS as JEE was to Java.
What is Ruby on Rails in this analogy?(the thing that replaced JEE monstrosity)
Personal biases are involved I'm sure. Ruby is fine, Rails is great, I just don't see it used very often.
On the other hand, I still see a ton of JEE being heavily utilized in a number of sectors. Ruby might have in the past taken over Java for small shops that basically create a frontend to a database, but I'd argue that was never true for the enterprise sector.
Earlier quoted context omitted.
That was my initial reaction too, but then I found it hard to disagree with (in the general case of course) and instead thought maybe it's an astute and interesting observation. The more familiar slight is that it's 'the language of choice for script kiddies', but I suppose they've grown up and gotten apprenticeships.
I just don't know what separates the working class developers from the "other" kinds of developers. I'm a 9-to-5 working developer, and I don't use PHP.