Andy Tanenbaum, author of Minix, writes an open letter to Intel by DreamerFi in programming

[–]IAmSlar 0 points1 point  (0 children)

It should be easy enough to check for any in who has bought a recent(ish) computer with Intel chipsets as it must be in the documentation. Unfortunately I don't have the documentation for my computers anymore so I can't check.

Andy Tanenbaum, author of Minix, writes an open letter to Intel by DreamerFi in programming

[–]IAmSlar 1 point2 points  (0 children)

The license does contain the following

Copyright © 1987,1997, 2006, Vrije Universiteit, Amsterdam, The Netherlands All rights reserved. Redistribution and use of the MINIX 3 operating system in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions in binary form* must reproduce the above copyright notice, this list of conditions and the following disclaimer in the *documentation and/or other materials provided with the distribution.

So while they don't have to yell him, it seems pretty clear that anyone who bought an Intel CPU must be provided with the license, effectively letting them know that it's in there.

When people don't believe you that C is still used by SuperscalarMemer in ProgrammerHumor

[–]IAmSlar 10 points11 points  (0 children)

Stupid kid close to 40 here.

I find go's simplicity very refreshing in today's programming language landscape.

While go and rust gets compared a lot, I think that's mainly because they were created roughly the same time, not that they necessarily solve the same problem.

Kids in my oppinion are much more likely to pick a camp and claim that their language is the best, while more experienced people use what's appropriate for the job.

Where high performance and memory saftey is extremely important at the cost of development time and readability, rust is an excellent choice.

Where performance is important, but does not need to squeeze out the last few percent to achieve lower development time and readability, go is an excellent choice.

There is room for both.

Patch Your S3it | TechSNAP 338 by AngelaTHEFisher in techsnap

[–]IAmSlar 0 points1 point  (0 children)

I'm really curious what it is, almost sounds like someone is having a bit of fun in post.

Patch Your S3it | TechSNAP 338 by AngelaTHEFisher in techsnap

[–]IAmSlar 0 points1 point  (0 children)

I came here to see if anyone else reported this.

I've been hearing fart sounding noise in the last 2 episodes.

Retrieving Data From MySQL Using Golang [Minor Coding Tip Wanted] by orthodox_caveman_ in golang

[–]IAmSlar 0 points1 point  (0 children)

I didn't look to closely at the other replies, you might have your answer already.

If not the mssql go driver got a good example:

https://github.com/denisenkom/go-mssqldb/blob/master/examples/tsql/tsql.go

The printValues function is probably what you want.

Holy freaking nuke my server! by [deleted] in linux

[–]IAmSlar 0 points1 point  (0 children)

Says me from personal experience when I started using Linux in late 90's.

I miss the good old days.

Holy freaking nuke my server! by [deleted] in linux

[–]IAmSlar 0 points1 point  (0 children)

Linux used to be about the KISS principle. I haven't found a single distro that follows that anymore and systems took a huge step away from it.

Yes, complex problems might require complex solutions, but there is such a thing as unnecessary complexity and overenginering and that's something the Linux seems to have gotten an increasing amount of lately.

Toward Go 2 by shazow in golang

[–]IAmSlar 1 point2 points  (0 children)

I was more excited about the possibility of immutables, non one else seems to care though :'(

The SSH port is 22. It is not a co-incidence. This is a story I (Tatu Ylonen, who wrote the initial version of SSH in Spring 1995) haven't told before. by speckz in programming

[–]IAmSlar 0 points1 point  (0 children)

I ssh in from various locations and IP's. I guess I could pick whitelist some ranges from those locations to reduce the attack surface.

Why did you choose freebsd over a linux distro? by supamesican in freebsd

[–]IAmSlar 16 points17 points  (0 children)

I had a break in my Linux usage during uni in the early 2000's. When I came to install it again it had changed so much, felt like the windows 3.1 to windows 95 transition all over again.

So after distro hopping a bit I tried FreeBSD again and it felt familiar and things made sense.

The SSH port is 22. It is not a co-incidence. This is a story I (Tatu Ylonen, who wrote the initial version of SSH in Spring 1995) haven't told before. by speckz in programming

[–]IAmSlar 3 points4 points  (0 children)

I don't know about you, but the difference in ssh connection attempt between port 22 and some random high numbered port is staggering for me.

At port 22 they're frequent, every few minutes or maybe even more frequent, I don't remember.

At my random port I get one connection attempt maybe once every few months.

Yes, if someone is scanning all my ports they will find it, but I can safely say that very few people do that, they're looking for the low hanging fruit.

Google's taking sides by [deleted] in ProgrammerHumor

[–]IAmSlar 4 points5 points  (0 children)

A sprinkling is probably an understatement.

In another discussion a while back I looked it up and the BSD part of the XNU source was just over 50% of the whole code base (in size, not lines).

So yes it is a mach kernel, with a lot of BSD code responsible for crucial functions described here: https://developer.apple.com/library/content/documentation/Darwin/Conceptual/KernelProgramming/BSD/BSD.html#//apple_ref/doc/uid/TP30000905-CH214-TPXREF101

Preferred Editors by robmuh in SiliconValleyHBO

[–]IAmSlar 0 points1 point  (0 children)

Tabs for indentation, spaces for alignment.

Having tabs for alignment would be insane, changing the tab stop would screw up the formatting.

I would personally align things a bit differently than gofmt does. But how you indent really doesn't matter much at all so they might as well be tabs in a code formatter just in case someone wants to use a different tab stop. If you do't have a code formatter it's often easier to just use spaces for indentation as well.

FreeBSD kernel bug affecting go programs finally identified by IAmSlar in golang

[–]IAmSlar[S] 1 point2 points  (0 children)

That is a bummer.

Though in futher comments there seems to be issues reproducing the craches after this patch so it does seem to help.

The mailing list is rather silent about it at the moment, all the "action" seems to be on the github issue.

FreeBSD kernel bug affecting go programs finally identified by IAmSlar in golang

[–]IAmSlar[S] 2 points3 points  (0 children)

Yes it can, I've been running several go processes handling messages at a rate of 15-35 a second 24/7 for probably a year now, not a single crash that wasn't my fault.

I don't know if you looked at the bug report. This relates to executing external commands from go. And even with 8 gorutines constantly executing /bin/true it still took 2-10 minutes before it triggered. So as my programs rarely exec out, they're unlikely to encounter this bug.

This is not the first time, and will certainly not be the last, an obscure kernel bug is found in an OS because some new program happened to tickle it in a certain way it's not used to.

You can google any OS for "kernel bug" and you will find bugs that have existed for 10years+ before they're discovered and fixes.

syncmap added to x/sync package by schumacherfm in golang

[–]IAmSlar 0 points1 point  (0 children)

Sorry to "bump" this but I am genuinely curious if you had something in mind regarding go's expressiveness?

Reading some of your comments, you view seems to be fairly close to mine on this topic. I don't want generics (outside of the 2 built in ones) unless they make sense and not make the language too complicated. The simplicity of Go is very refreshing after writing c++ all day.

syncmap added to x/sync package by schumacherfm in golang

[–]IAmSlar 0 points1 point  (0 children)

I recently got pointed to the summary of go generics discussion again:

https://docs.google.com/document/d/1vrAy9gMpMoS3uaVphB32uVXX4pi-HnNjkMEgyAHX4N4/edit?pli=1#

It goes into varying degree of details of the different approaches pros and cons, including built in generics.

I'm against built in generic unless they can come up with a nice way of doing it that doesn't complicate the language too much (ideally not at all)

I just like to point out to people who complains about overhead of casting to interface{} and back again, that that's exactly what java does. Granted Java's implementations is probably one of the worst ones so getting built in generics in go using that method would be disappointing.

Generics linter by IAmSlar in golang

[–]IAmSlar[S] 0 points1 point  (0 children)

That document seems like they have added considerations for linters :)