Accidental Tech Podcast avatar

Dexa/Accidental Tech Podcast

Learn more
Published Jan 20, 2024

353: Modern-Day Dialup

Dive into the future of technology with insights on Apple's advancements, as hosts weigh the pros and cons of laptops, especially the robust yet affordably priced 16-inch MacBook Pro, and examine the practicality of foldable phones. Uncover deep discussions on selecting the right programming language for server-side production, balancing innovation with tried-and-true reliability.
Episode Highlights
Accidental Tech Podcast logo

Topics covered

Popular Clips

Questions from this episode

Episode Highlights

  • Language Readiness

    Determining when a programming language is ready for server-side production involves more than just popularity or trends. explains that the decision should be based on the specific needs of the service, such as efficiency in CPU time and memory, rather than just following what big companies like Facebook or Amazon use 1. He emphasizes that sometimes, using a less common language can be beneficial if it offers significant advantages for a particular task 1. adds that being the biggest client of a technology is not ideal, as it can lead to unforeseen challenges 2.

    If you want to use go or erlang or yes, even swift for your real production server that does this one simple thing that you have a really good reason to use it for, it may actually be worth dealing with the immaturity, the lack of tools, lack of documentation, so on and so forth, as long as it is actually feasible.

    ---

    supports this view, suggesting that the choice of language should align with the developer's priorities and the nature of the project 2.

       

    Implementation Choices

    When considering server-side implementation, the decision-making process should focus on reliability and maintenance. prefers using established languages that offer stability and low maintenance, as server issues can arise unexpectedly and require immediate attention 3. He advises against using newer languages like Swift for critical server tasks due to their rapid changes and immaturity 3. echoes this sentiment, highlighting the importance of choosing technologies that have been tested by larger companies to avoid scalability issues 4.

    For me, I want my server stuff to be as low, needs, low maintenance, high reliability as possible for that set of priorities, which again may not be your priorities, but for that set of priorities where my server stuff is really just supporting low profile task that I don't want my server stuff to be exciting.

    ---

    Ultimately, the choice of server-side language should be guided by the specific needs and priorities of the project, balancing innovation with practicality 4.

Related Episodes