Date: Mon, 17 Apr 2023 08:50:47 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Docker Message-ID: <c6723269-be74-9aef-a369-9cc97992832e@tundraware.com> In-Reply-To: <1047709965.4366598.1681704641048@mail.yahoo.com> References: <20230329053443.6ADA6B6AFED5@dhcp-8e64.meeting.ietf.org> <CA%2B1FSihVrJ8cZ4ZU6mMr0sKJsZ98V4fh2vpDLugw7MGj-%2BEBPg@mail.gmail.com> <CA%2B1FSijL50mQ-HveBA4HZeNkSoaORv=aty-15nNLzn9amzY_nw@mail.gmail.com> <6002f636-310b-a9fd-b82f-346618976983@timpreston.net> <CA%2B1FSigV_pPwVW%2BDd8WZYGcNQVt7%2BYOcsnJFoRhS6jL5A636pg@mail.gmail.com> <20230412150350.12f97eb2c9dd566b8c8702d2@sohara.org> <CA%2B1FSihVPCQ6tp8u=aqnLyyOPpCMrnhYGcC8bCUgRbFHTdY5sA@mail.gmail.com> <1535315680.2770963.1681309684072@mail.yahoo.com> <20230412155252.5e38ea4728bd52dc798852fc@sohara.org> <1d0a7ed1-9330-49df-9b66-9ee4387de511@app.fastmail.com> <78F4160A-2D26-4A22-9139-A9 132FC42688@ellael.org> <8f3a86806377c2c92039eaf2765f5b85862de178.camel@riseup.net> <CA%2B1FSij0N-CRhMRXVUK81BWPTn0vDVcbQSF2Q11Zz%2BgJdL_Ddw@mail.gmail.com> <858859542.4652196.1681696294734@mail.yahoo.com> <92f6a9df-fd1e-9411-6093-fc8a145a dd17@tundraware.com> <1047709965.4366598.1681704641048@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/16/23 23:10, Paul Pathiakis wrote: > Believe it or not Tim, I do agree with you on a lot your points. > > However, in the hey-day of BSD based derivatives, I saw a lot of the issues. I laughed on the Hotmail transition. A 10x transition to NT4 machines... You and me both > > Well, I've been in hundreds and seen more than just one. > AWS does have FreeBSD as does Azure. > Yeah, someone else pointed that out as well. I stand - well, sit - corrected. > And you're right, I know what the reality is. I live the delusion that some day.... we'll go back to code optimization and proper methodologies instead of throwing hardware at it. I am so on your side about this particular point. Agile, Scrum, and driving product teams is a fine way to do new feature exploration and/or get fast user feedback on the UX experience. It's a terrible way to engineer complex server and platform systems. The cool kids seem to think you can avoid waterfall specification entirely and just inch their way into solutions. They end up reimplementing things over and over to get it right and usually end up missing non-functional requirements like speed, scale, security, and recoverability. The result is code bloat and people hacking their way through complex systems rather than planning their way.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c6723269-be74-9aef-a369-9cc97992832e>