grepgeek's comments

Did they try to ask for donation? Linux Journal has a huge reader base most of who probably grew up in the 90s and early 2000s. Most of these readers are now probably working professionals and earning well enough to donate a small amount to Linux Journal on a monthly or yearly basis to keep this journal running.

I have travelled to India often but I don't understand Indian politics enough. So if someone here can help me with these questions, I'll appreciate it!

* What does it mean for Lakadh to not have a legislature? Does it mean that this province cannot have elected local leaders?

* Why are the prominent politicians under house arrest? What is their offence?

* Why were these two articles repealed?

This is cool. I wonder how outline.com manages to get past the sign-up wall.

> Register to read this article in full: Sign up

I don't want to create a new account to read an article? Is there any other option to read this article?

I know one could say that if I don't want to create an account like the website wants, then I have no right to read the article. Yes, I understand that. I respect the website's owners' right to enforce access to the article however they please and I am okay to not read the article if there is truly no other way to read it without creating an account.

I like the way Creative Commons licenses do it. First there is a simple bullet-point-wise summary for layman like this: https://creativecommons.org/licenses/by-sa/4.0/ . Then there is the entire legal code for lawyers: https://creativecommons.org/licenses/by-sa/4.0/legalcode .

I think all contracts should be written like this. If any clause of the legal code contradicts the summary for layman, then the summary for layman should take precedence during its interpretation in the court.

This practice is not unusual. Books often start with a preface or foreword. Very dense technical or research papers start with an abstract and introduction. But for some reason contracts do not follow this practice.

This does not look like the description of "10x engineer" at all. An "immature engineer"? Yes. But "10x engineer? No.

A true "10x engineer" would also care a great deal about documenting stuff, communicating that to the team, and be wise to ensure that a good technology system should not have a single point of failure (either technical or human). The fact this so-called 10x engineer made himself a single point of failure goes against the basic principles of engineering.

I am honestly unable to decide whether the original tweets by @skirani were said in seriousness or as sarcasm!

Which websites do you still find using Flash? I ask because I am genuinely interested to know. I think it has been years since I came across a website that used Flash. I uninstalled Flash the day I found that YouTube does not require Flash anymore.

It was discussed here: https://news.ycombinator.com/item?id=20454966

Anyone knows what theme is used in this blog?

The swift-http-import README is great. Can you describe what do you see especially nice in the castellum README? Honest question because it looks like a regular README (which is not to say that a regular README can't be great) but I just want to know what you find good in the castellum README.

You could have still kept the massive state in a dict or a list or a tuple and passed that dict around from one function to another, could you not? Why did it become necessary to implement classes?

Only if there are major contributing developers who do not work for Google. Is that the case with Go?

If there are no major non-Google contributors to Go, then the fork may not be successful due to lack of familiarity with the code base.

Can you elaborate? In what ways, is modern Java a more pleasant experience compared to Go?

The community of free and open source software developers.

Really, with the kind of license proliferation that was going on due to every Tom and Harry that wanted to publish their own license, it was difficult to understand which license was really safe to use and which wasn't. FSF and OSI stepped in to bring some sanity to this situation by categorizing all the free and open source licenses by their permissiveness and restrictions. The majority of the open source development community adopted these licenses.

Any license that restricts making money would neither be considered a free license by FSF nor an open source license by OSI. The license could discourage making money without contributing back to the community and the GPL family of licenses do achieve that to some extent but they cannot outright restrict making money.

The OSD has its roots in Debian Free Software Guidelines which for a long time has been the community standard for what guarantees free software must provide. FSF's four freedoms of free software are also similar. OSD adopted Debian's guidelines to create the open source definition.

If a license does not allow us to run a software how we wish we lose freedom 0 to run the software how we wish. We lose the right to use the software for any field of endeavor. You might want to consider it "open source" because you can still see the source but widely accepted terms like "open source" do not get redefined so easily based on how some people feel about the term. The term's meaning still remains intact due to the meaning it holds for the vast majority of open source software developers.

You might be aware that in Google not every application team works together with the security teams. They are supposed to work with them. That is the best practice and that helps with security compliance and review. They often do. But it is also sometimes easy to forget doing so if the team is not doing their due diligence.

It is possible that this team did not work with the security team even if it is a highly unlikely scenario. The likely scenario is that this team did work with a security team and they were aware they were supposed to hash the passwords but they made a mistake during the implementation.

I think what is being underappreciated here is that very very smart application developers can have little to no idea about security best practices. I can say this confidently from my direct experience of working with Googlers.