@ostream Long story short, stable, zfs built in and up to date packages.

Longer story:

I was running slackware from 1999 to 2022.

I got a PowerPC Mac and was running OSX for a few years.

Once I got a PC again Ubuntu was a thing and I tried that for a while but was annoyed how out of date the repo was.

I did try arch for a while to get up to date packages but I just didn't have time and the willpower to fix issues caused by system breaking updates.

New PC and Linux did not get spousal approval so it was windows for a few years, but at that time life and work was so busy that there wasn't much time for dealing with computers at home anyway.

I tried FreeBSD 9 in 2013 and really liked zfs, stable base system and up to date packages. My server install of FreeBSD 10 has now been incrementally upgraded up to the latest 13.2 over the last 8 years and has been very hassle free.

I'm now very comfortable and know my away around FreeBSD so I've got no interest in moving back to Linux.

Hi arch user, I use FreeBSD :)

Do you have any documented code guidelines?
We (try) to resolve unnecessary code review comments by documenting mandated style as well as things that are optional. So you can't comment if an optional thing missing just because it's your personal preference.

If comments show up that aren't covered by the guidelines, we discuss them, make a call if they are mandatory or optional and document the decision.

Personally I think a lot of ideas from rust will become mainstream, but I doubt that rust will survive long term.

Whatever clang-format does, I'm so past formatting my code manually.

Now if I get to setup my own .clang-format it it would be int& foo()

You are absolutely correct and my assumption that zfs compression was doing most of the work here was completely incorrect. The compression ratio of this dataset is still 1, it's just a sparse file.

It would have been quicker just to run truncate 2E...

@NoOneCares yes, that's the one. I wouldn't be too quick to blame Baloo though, this is from a failing disk after all.

zpool status doesn't show any corruption on this file though and the disk started failing at the time I installed and tried to start the plasma desktop. It's very possible that other disk issues causes Baloo to fill this file with 0's or something repeating, hence the insane compression.

@IntrusionCM I took a video of me checking the size of the file this morning (sorry about the tiktok, it's the easiest I could think of at the moment)

https://vm.tiktok.com/ZSe8cdWbh/

*laughs in FreeBSD*

Non-sysyem files, I including third party packages goes in /usr/local.

Ever since trying FreeBSD i never understood why Linux distro a still mix system and third party packages in /usr/bin et alt.

It's build 2020 you should skip, it's got a virus...

In my case we use gotomypc with any filesharing features including copy paste is disabled. Round trip latency is around 200-300ms. It works but it's not very pleasant.

I use k for key.

Works very well for maps as well when you do for k(ey),v(alue) in map

That is probably the case @orhun, might be more of a community/library creator issue than pip issue.

The BSD's are waiting for you :)

I went from S.U.S.E 5.3 -> Slackware 7 -> distro hopping -> mac OSX panther, tiger -> distro hopping -> FreeBSD.

Spent the last 5-6 years in FreeBSD and I feel at home.

Is the mouse held together with black duct tape?

WhatsApp?

It did that to me, I wasn't too interested to transfer my history to my new phone, but I wanted to export all my messages for archiving.

But no, as soon as I had logged in to my new phone it would not let me get them anymore.

I tried to get around it but after 2 attempts it seemed to reset itself and wanted to setup a new account instead.

@dder, paranteses around the condition and a semicolon.

Not GO :(

If by "my room" you mean bedroom, then 0.

In the whole house:

1 hp microserver
1 hp workstation
1 working hp laptop
1 broken dell laptop
1 raspberry pi
1 onion omega 1.

@HelloBaze

The simplicity of C with a modern standard library and easy concurrency. I'm also in love with Go :)

7: C++, SQL

7: trading systems dev?

@stop, those are all stored in an unsigned data type right?

And there would be random stack traces due to typos happening every now and then.

Now learn C++ and search for std list...

As a C++ dev, s/python/go/

I could not get used to indentation instead of curly braces.

Traditionally it's been written as:

People run Linux because they hate windows.

People run BSD because they love UNIX.

For the record I love UNIX and I tolerate wimdows.

I think I use vim too much to be able to tolerate a non-physical ESC key.

@jonii

Wikipedia explicitly says:
"There are no precise dates for when this cohort starts or ends"

In the date and age range section they reference many sources where researches use any of 1977, 1980, 1981 and "late 1970's to early 1980's"

End dates of 1995, 1996, 2000 and "mid 1990 to early 2000"

So I can correct myself that it can be as wide as 1977 to 2000, making millenials depending on who you ask anywhere between 18-41 years old.

Personally I don't think someone born 2000 should be considered millenial as they did not come of age around the millenium. Similarly, someone who is 23 at the millenium shift is probably a bit too old to be considered coming of age in 2000.

Personally I think the 1980-1995 age range which most seems to use is sensible.

37 year old millennial here, had a sort of mid life crisis around 34-35 years old.

Mid life crisis isn't just for 40+year Olds. Mid to late 30's is alao mid life crisis is prime time.

The age range for millenials vary depending ding on who you ask. It can be as wide as from 1977 to 1995, making the youngest millennial 22 and the oldest 41.

Previous employer, all editing do in vim on Solaris, c++, makefiles, commit messages etc.

Current employer, C++ in visual studio, with vim plugin, all other misc files in gvim.

Alt home desktop, visual studio code in Linux, with vim plugin.

Home server, all editing, including remote login coding on my phone (I wish I was joking) in vim on FreeBSD.

Last week my team lead said that I'm stuck in the 70's. I'm a millennial though so I wasn't even born then.

Applications with input fields that close the window when you press ESC are the bane if my existence (I'm looking at you beyond compare), I can not untrain pressing ESC before saving.

:wq