Re: [Thought experiment] Bringing swift into an experimental branch?

what problem are we solving here? people write code. fix the code if bug is found. work around it with redundancy. avionics hw/sw dev is good example how. if that level is needed

i'm not buying the don't insure the c code either. i mean i don't write that. but i have like concepts how buffer overflows work. maybe just don't do that? unsure if language should attempt to think for yourself and handcuff the coder. or attempt to

also trump doesn't do anything good to anything, so attempts to do sw dev in methods like piss everyone off, smash everything, perhaps build a new house eventually, meanwhile sleep under a tree doesn't work

also i've been here for like since 1999. languages woozh past like crazy, people hopping on and off. and then there's a c. why do we still use c?

also what's fun is that even with those "safe" languages, there's still way to bust that

also, does anyone recall the still ongoing huge mess of having libxo in base that was supposedly really good idea

whole import language is like trying to argue with people who keep telling you that "brawndo's got what plants crave, brawndo has electrolytes" without even knowing what they say

btw, yes, you can argue that maybe we need better code. now that code runs everything. like regulations, etc, like civil engineering. "certified" engineers, etc. but this isn't the way to fix it either. btw they still make a mistakes

it's all people making mistakes. the point where people stop making mistakes is called technological singularity. and i bet then the mistakes will be still made, just by computers

until then, maybe we could just take all this effort to just fix existing code

also, what about other things like aslr that also help and sound much better idea, are easier to do and we already have that

anyway what's the actual issue here anyway. and, yes anyone can take a code. it's called a forking and it often happens. new fork can either give ideas back, die off, continue separately, replace original, and so on. no need to piss people in original project off. you have full source. the bsd license pretty much gives you full freedom. just requires you to tell where it came from. i bet telling that is not an issue if you just want to port it from c to any popular language. it seems like noone here wants it. and it's ok. just like i plan to probably keep on using fbsd on some 32bit i386 or armv7 should that time come. people do it now for mips. it's always option to take code and walk off. i almost never want to piss into someone else's cup. just have own cup. iirc ianal but i don't think one even need permission to fork fbsd. this is not a war over some territory. do not fight for getting swift into fbsd. just make a witbsd or so!