Hacker News new | past | comments | ask | show | jobs | submit | Bino's comments login

Why would anyone use split/join?


Maybe that’s what some people use. For example deepcloning objects in JS is faster with json.parse(json.stringify())


I actually think the old keyword is quite clever. I'm sure it could make sense in some places.



Thanks, we've gone with this instead of http://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/11.2/.


It's really bad when you need a tl:dr on a security vulnerabilities release, it was a lot more bugs than I expected, I wonder if GitHub enterprises is just as bad?


If only there were a solution I could buy... ;) No, I do believe you should use Google Authenticator, it’s free, easy to implement and adds a lot of security over just passswords.


I feel they try to turn it into a feature... facepalm


I would say it all depends on why the do it, if there is a clear motive (like if they depend on it...then it makes sense for me and them and builds trustworthiness). But just sponsor something out of the blue - no. I don’t believe in random goodness when money is involved.


Agreed. There definitely should be a transparent explanation behind the move. In business money speaks.


I say go for it, if you are not a key employee (there is no risk imho), you may just be a better fit in their other company.


Like it, as a runner and European citizen I always get confused if someone refers to American miles or not, but 5k is always 5000meters regardless? Do Americans who run ever talk about miles?


American runners use miles. Speed is "mile pace" (minutes per mile). Daily runs are measured in miles and so on.

A marathon is the "26.2" (i.e. miles).

Interestingly, (continental) European runners do in fact use miles. It seems to be not unheard of, at least. I've seen miles used by Germans in online forums. E.g. citing daily mileage or minutes per mile pace.

Because many popular distances are metric, North American runners who use miles may still be mentally tuned to the metric side of things. For instance, someone mostly focused on miles in a marathon might take a note of their 10 km split time, checking whether it's properly below their 10 km race pace.


5K is 5K for Americans as well, as per Wikipedia https://en.m.wikipedia.org/wiki/5K_run


If you can, you should consider updating to 11.1 instead.


Why?


At least partially because you only have another year of support for FreeBSD 10.x, whereas FreeBSD 11.x is expected to be supported until 2021. This includes security fixes.


11.x may supported until 2021, but 11.1 itself will only be supported up until 11.2 is released + 3 months. So if 11.2 is released before the end of July 2018, then 10.4 which has an EOL of October 31st, 2017 would actually be supported for longer.

Generally speaking, more conservative users will wait at least until the xx.1 point release before switching to that major version, but if you're on the very conservative side you may want to wait until xx.2. However, there are numerous updates even between minor point releases which you could apply if any errata are discovered if you don't mind.


Yes, but the point of point-releases is that they're largely about maintenance and hardware support - so moving from 10.x to 11.x might take some testing, maybe rewriting some management scripts, etc, but 11.1 to 11.2 should be easier since nothing major changes about the system. Having a year's buffer to migrate means that if there are issues, you can fix them or get them fixed before 10.x EOLs and you're stuck running an unsupported OS.


You're supposed to upgrade to point releases pretty much immediately.


One reason could be built in IPSEC (11) and NAT_T (11.1) but I see cases where people would like to stay on 10.x.

I couldn't find anything about those extensions being enabled by default in 10.4.


This is my number one reason for moving to FreeBSD 11.1. FreeBSD 11.0 was weird because they enabled IPSEC, but did not enable NAT_T in the GENERIC kernel.


I guess that's kind of obvious.


Nothing about FreeBSD release versioning is obvious.


If we use Windows Versioning Perspective.

10.4 = Versoin 10, Services Pack 4

11.1 = Version 11, Services Pack 1

At least that is how i think of it. Am I missing something? What isn't obvious about it?


> At least that is how i think of it. Am I missing something? What isn't obvious about it?

I think the number of times I've witnessed discussions over the decades regarding "which version of FreeBSD should I use?" numbers in the hundreds.


As far as I understand it, that is nothing more than an urban legend based on the fact that 5.0 was a terrible, rushed release and not meant for production (it was also marked as such). That mistake has not been repeated since, to my knowledge.


The official answer to this is to use latest stable version for any new server. That means 11.1 right now.

10.4 is intended for individuals who are still running 10.x


Historically, it wasn't always obvious which "service pack" one wanted to jump in at, or whether the .0 release was any good, etc.


The 10 and 11 kernel ABIs differ


Seriously? this makes more sense to you than much more human-centric release names like Fuzzy Slippers and Spicy Chicken Sandwich?

sheesh.

:D


I mean it's obvious that you'd want the latest release, and there's no release numerically higher than that one. But I understand, for some, laconic and prejudicious snarks are more pleasing than trying to understand what the interlocutor is trying to communicate.


Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: