Re:Integrating “safe” languages into OpenBSD?
by drb91 on Monday December 04, 2017 @03:07PM
(#15846932)
How do you even find an i386 processor these days?
[ Parent
| on HN ]
Re:Integrating “safe” languages into OpenBSD?
by avhon1 on Sunday December 10, 2017 @12:50AM
(#15890176)
AMD still sells Opteron CPUs [0]. You can buy new servers with them [1].
[0] https://www.amd.com/en-us/products/server/opteron
[1] https://www.thinkmate.com/systems/servers/rax/amd#browse
Re:Integrating “safe” languages into OpenBSD?
by 2trill2spill on Monday December 04, 2017 @04:49PM
(#15847869)
In the OpenBSD world i386 == x86. And it's pretty easy to find an x86 processor now a days.
Re:Integrating “safe” languages into OpenBSD?
by deathanatos on Monday December 04, 2017 @08:56PM
(#15849200)
… such as? You're merely restating the claim, without providing any proof.
Consumer machines, AFAICT, are all amd64 (or x86_64, if you prefer that name). I understood the original post to mean i386 == x86, and I agree — where do you even find an x86 today (for sale, in a non-niche use case, i.e., "pretty easy")?
Re:Integrating “safe” languages into OpenBSD?
by kelnos on Monday December 04, 2017 @09:37PM
(#15849336)
OpenBSD has as a goal to run on much more than just standard currently-sold consumer hardware. You can certainly disagree with that goal, but that doesn't make it go away.
Re:Integrating “safe” languages into OpenBSD?
by drb91 on Tuesday December 05, 2017 @06:05PM
(#15856956)
Oh I totally get this—but what is this hardware that people are still using OpenBSD with that they haven't upgraded in 30 years? Targeting i386 as opposed to, say, i486 or i686 seems like an exercise in idealistic masochism.
Re:Integrating “safe” languages into OpenBSD?
by kelnos on Thursday December 07, 2017 @04:40PM
(#15874578)
I think you're misunderstanding: "i386" is just shorthand for "32-bit Intel". They're not specifically talking about the 80386 chip. The same problem exists when you consider newer 32-bit chip families in that ISA.