skysight-inc/HackerNews huggingface dataset:
I've done some thinking on this over the years. I'm not convinced it is "ADHD" per se, based on reading the symptom list and observing family members who do clearly have the symptoms. Of course it is always tricky to self-diagnose.

For me it is more akin to an addiction mechanism : consider someone who is overweight because they eat too much and exercise too little. This situation is crystal clear to everyone, including the person themselves. Yet, almost nobody improves their weight situation just because they "realize" that they should be eating less and exercising more (two things that from a practical perspective are pretty easy to do). We don't say that they lack focus to stop eating -- we think of their behavior more in terms of an addiction.

So what's going on? Obviously it's complicated but on some level the person's brain has decided that eating is actually what it would prefer to do vs not eating, even though it "knows" this isn't going to achieve the desired outcome.

Similarly with "getting st done" I suspect. Although your brain knows that it should be cutting code or writing blog articles, it actually prefers to read HN and research the security measures used in triggering mechanisms for the primary stages in thermonuclear weapons.

That being the case it sounds like you are already taking all the typical countermeasures : don't have food in the fridge; count food points; try to keep the long term goal in mind..

One other thing I'd say in the context of freelancing and remote work is that you may be unfairly judging yourself, or rather comparing yourself to a mythical perfect version of yourself, due to the lack of available other people with which to compare your achievements.
And dont even bother mentioning golang aps that use mongodb, immeadiate hue and cry, definatly a haters stack.
I thought Tesla was Musk's company until now. Apparently they actually reached a settlement with Eberhard to officially call Musk (and another two people) "founders" even though they actually weren't. https://www.cnet.com/news/tesla-motors-founders-now-there-ar...
No Strings Attached: The Behavioral Effects of U.S. Unconditional Cash Transfer
Since November WASM is enabled by default in the major browsers now:

https://caniuse.com/#feat=wasm
Nested ternary
Thanks for sharing this, Sam!
Found the thread: https://news.ycombinator.com/item?id=5570013

The "unknown HN user" is bambax
Or maybe it’s because we’ve tried golang repeatedly, been frustrated the entire way, and are desperately hoping that someone will help us understand what people actually see in the language.

I work and live in SF. Of people I talk to in real life who’ve used golang for non-Google, non-toy projects, sentiment is at least 4-to-1 against it, and in my anecdata that ratio generally increases as people use it for longer.

The one consistent praise I’ve heard that seems genuine (and that I don’t entirely disagree with) is that it’s easy for a new team member to jump on board and be productive. Which sounds great, but if this is what you’re optimizing for at (in my opinion) the expense of nearly everything else, then it seems like a self-fulfilling prophecy of high turnover.
I can help you with proofreading & editing any text. My email is victomlinson@proofpapers.com.
I’m inexpensive.
Ternary operators can be abused. E. g. somebody can write code with nested ternary operator and long expressions. If/else will be more readable in this case. Go is a nanny language - Go authors give to coders on Go as little foredoom as possible.
It should be mentioned that none of that should ever make its way into a Git repo in the first place. If a secret is committed to Git, it's compromised, period. Suck it up and generate a new secret.
A comment upthread did the math:

> The author is able to achieve a speed-up of ~4x which is close to the 5.89x achieved by the Rust implementation.
Best Free App for Domestic and International Phone Calls
It seems there's an attempt to quell customer discussion via locking such a thread on their forum[0]. A particularly upset customer's remarks[1].

[0] https://forums.flightsimlabs.com/index.php?/topic/16236-furt...

[1] https://forums.flightsimlabs.com/index.php?/topic/16236-furt...
Yes! Certainly on the source code, and hopefully on CASP13 too.
I tryied to read it- but in the second sentence the well rounded argument i expected, became a syntactic sugar and base library bitching about round not being part of the base.

That this bubbled up, sums up the true power of javascript. No good arguments, but lots and lots of people who know and use it. Lua should just attach itself via script converters to that ecosystem and convince via time and better syntax the unwashed masses.
2 additional reasons (of my own) which I don't typically see:

1. No default function parameter values.

2. You can't require struct fields. So, you can make a new struct, and then later try to access a field, you get a runtime error (that the compiler didn't catch).

The second can effectively be solved similarly to the first. If a struct could take a default value (like a class), then you wouldn't miss something like creating an empty slice.
Have you seen what atrocities people can do with nested ternaries?
I tried hard to like Golang but I couldn't. The only good thing about Golang is that's it's a high level compiled language that's suitable to replace Python in many use cases especially in the web, there's no other popular language in this category. However, the lack of features and forcing specific design patterns for a c-like language is totally annoying.
I think that's an uncharitable explanation. I'm very happy using the Google services I do and I pay them for my personal domain/email (have for the last decade or so). I think Kubernetes is a great idea and I run it in production. But it would be difficult to find a job that would pay me enough to deal with the frustration generated by having to deal with Golang.
The commenter isn’t trolling, you’re just being incredibly literal in your interpretation and responses, so much so that you’re being obtuse. He said “your feelings were hurt” because you said it’s rude - you don’t need to start a diatribe litigating the commenter for assuming your feelings were hurt. If you find something rude, you took offense to it in some sense, and if you take offense to something, reasonable people could say your feelings were hurt in some sense.

On a similar note, when the commenter said what you’re saying isn’t rational, you took the opportunity to point out that humans as a species aren’t rational. That feels like you’re deliberately missing the point, but in case you’re not, here’s that point restated: It doesn’t make sense for you to call an author rude when the author is matter of factly informing the reader of the necessary prerequisites.

For what it’s worth, it’s apparent that the other commenters who responded to you, myself included, agree with the substantive meaning you’re attacking so literally.
What we posted got shared in various other places (Designer News, Twitter, Reddit, etc), which might we why it was higher. But Hacker News was definitely the catalyst of it all.
The first 80 hours of a work week seem the hardest... the next 60 fly by in a daze of mania. It's hard to remember how to sleep and not think about work all the time, but your productivity is constantly falling. It works best for projects you can literally do in your sleep and anything requiring decision making, detail, or creativity should be done in the first day. If mistakes aren't very obvious when assembling the final blocks at the end, you'll miss them. Camaraderie is important too!
And so many people out there wonder why engineers are hesitant to work for startups now, and demand high salaries.

I do also feel that the founders in that story should be named and shamed. There is absolutely no excuse for that kind of behavior. They should never be able to do that to anyone ever again.
That's not a contrarian view. It is a widely-held view. Plenty of IT administrators would rather not think about security, which is largely an externality to their job.

If they're inconvenienced by the 90 day deadline, they have Microsoft to blame for it, not Google.
> Isn't it a dynamic analysis tool, i.e. a C interpreter that keeps an eye out for UB?

Indeed, I'm sorry, I had tis-analyzer in mind. tis-interpreter is indeed closer to Valgrind. It interprets the C code according to its semantics, without going down to assembly level nor executing the code.
Some other theories relevant to this:

https://en.wikipedia.org/wiki/Duverger%27s_law

https://en.wikipedia.org/wiki/Median_voter_theorem

https://en.wikipedia.org/wiki/Realigning_election (events where party political coalitions do fracture, despite efforts to keep them together)
I recall that there are regulations about cars that make it more likely that a wide variety of owners will be able to maintain them successfully.
I would agree, but then, the author names reasons to dislike Go (even if we all heard them before), does not say anything about Google and is not even exceptionally vulgar about it.

So after reading about golang over and over, it seems it is going the MongoDB way. A lot of excitement at the start because it's easy and fast to put something out but as soon as maintenance mode needs to kick in, people realize it is not the silver bullet and maybe not even a ok solution.

But isn't that a problem of the whole industry? First a hype gets build up and a lot of people jump on the band wagon. Then the real world kicks in and some complain overly loud and others chime in with "I told you so". Finally a lot of people change the tech stack silently because nobody likes to talk about their failures too much.

I can't say if it is the same with golang, I did not use it at all yet, but some design decisions are at least doubtful.
Zero rating violates net neutrality; you can't be in favor of zero-rating and opposed to net neutrality. I know there are people who disagree with that, or who think it's possible to "balance" zero-rating against net neutrality, including Erik Moeller of the WMF. Those people are entitled to their opinion, but it is wrong.

I think English Wikipedia didn't participate in the Day of Action because it's harder and harder to organize anything on WP, which of course is why WMF exists and why it isn't accountable to WP.
What are you implying about SpaceX and BlueOrigin...? What's really in that Roadster? :)
They could easily add more visibility levels (by using keywords like Java). They haven’t because it’s unnecessary and confusing.
it should be trivial to write a tool to stream a json file with proper newlines
While the guideline may be explicitly directed at comments, its purpose is to discourage people from defaulting to positions of bad faith. This is equally true for articles. With accusations such as this, it's particularly pernicious because they're hard to defend against: once you tread down the path of assuming bad faith, any argument against it is likewise assumed to be in bad faith: you've already dismissed them as untrustworthy. That's why the bar is so high with respect to comments: you need to have proof. I think it's perfectly acceptable to hold a similar standard when discussing submissions.
Then the correct approach is "you are likely not ready for this material, I recommend you do XYZ and come back".

There's no problem with telling a reader they are not ready for a text - in fact, it can save them time. The way in which you do it though can encourage or discourage a student.
I guess Banks need to follow some kind of compliance (like PCI), and there are at least, some guidelines or tested solutions for them.
Yes I don't get the authors argument. Now you need 4 lines of code instead of 1 in some cases. On the flip side it's easier to read for anyone looking at your code.

The weirdest part is that the author seems to prefer Java. Which is one of the more verbose languages out there.
In comparison, a Google Home gets an 8/10. Echo a 7/10.

Apple plain doesn't care about repairability.
Not sure what you're getting at -- my tools that generate json logfiles do trivially add newlines where I want them.

jq's "compact" mode will reformat files that don't have newlines where I want them.
Many of the deficiencies he noted are easily mitigated by tightly integrating the Go toolchain (and in particular the metalinter) with your development environment and CD workflow. I highly recommend vim-go for Vim users.

The flat namespacing is rough at times, but you get used to it. It also encourages you to be judicious in what you make global, which is imo a great thing. I haven't had a problem with capitalization. It's jarring at first, but you just get used to it.

There also isn't nearly as much magic as that cherry-picked example might lead you to believe. Then again, having worked with Ruby/RoR, I've seen just how gross magical behavior can get shudders and maybe my definition of 'magical' is a bit more forgiving. I'd like to see a more comprehensive list of such grievances.

It's possible that the Go ecosystem has improved considerably since the author wrote this (~1.66 years ago), so I'd love to hear his take on it in the present day. I do agree entirely about the horrific use of interfaces and lack of generics. I'll also throw in the lack of enums and poor default error convention/semantics as additional glaring issues.

This is all made that much more vexing by the fact that Go is so damn close to being a really great language.
Maybe I'm not following HN closely enough, but judging from this post, it seems that people are pointing out what they dislike about Go, instead of just heaping abuse on it. In my view, that's a positive and productive thing, for several reasons:

1) The discussion gives insight to people who have never used Go. The usual way of getting that kind of knowledge is to shoot yourself in the foot and learn from it.

2) The back-and-forth can provide useful advice on how to work around certain problems in Go.

3) Language designers can always use these discussions to guide and inform their decisions. "Hmmmm, haven't thought of that, better make sure my language doesn't do this; that other thing is an acceptable tradeoff, though."
I’m a proofreader & editor. I can do it for a reasonable price. See victomlinson@proofpapers.com.
Well yes!
You might not have that option to not use it (too late).

Just like this guy you (or your colleges) might actually have been fooled by curiosity and hype to write some code and put it in production, and when you realize how bad it actually is (this was only a personal top 10). At least you should try to fight back against the hype and try to warn people.

Still think the general sentiment is quite go positive overall, go definitely needs more critique.
I met somebody who works for Target stores applying OR methods to optimize their supply chain.
The problem with these tricks is that they're dependant on V8 internals, which means that there's no guarantee that it will be fast on Firefox (or edge, or even Safari).

So now if google changes the back end, websites will slow down, which means that Google has to ossify implementation details, furthering this sort of black magic into CS lore forever.

This, honestly, is what I hate with modern dev. A few days back there was a discussion on how programming is hard nowadays.

Really, programming is more accessible than ever. What is hard is the "black magic" that's becoming more and more prevalent, most of which is implementation defined, that everyone is expected to know (and really, most don't really know anything. They just repeat rumors they read about online, often years out of date).
Selfhosted GitHub Pages for Cloudron
Yes Google allows longer for bigger issues. Meltdown and Spectre two great examples.

What surprises me is that so many of the really big ones seem to be found by Google.

Spectre and Meltdown by multiple poeple. But Shellshock, Broadpwn, Heartbleed, and Cloudbleed if memory serves all found by Google.

Off the top of my head can not think of a major one the last couple of years found by anyone but Google. Anyone else?
Whether google should disclose after 90 days or not is up for debate maybe, but i for one applaud the effort. Many many years, exploits have gone undetected/unpatched. If googles approach is to force people fix them, so be it.

Microsoft has no right to be angry - they should be thankful. This is peoples data, their business at risk. After being in the business for so long time, and with the resources they have, they can afford to put a small army of swes to fix security bugs.

Unlike a small company, the bugs in widely used software, by definition, affects a large set of people.

Disclaimer: google employee.
Has anything in it changed?
Wonder why the article isn't attributed? Had to click back to the author's home page on the site to find out who wrote it. Anyway, I think these are all good points but the one that really bothers me is no exception handling. Yeah, it makes a language more complicated to implement, but handling return values all the way up the stack is cumbersome and error prone. The vast majority of the time when something goes south deep in the stack I just want to clean up and send a signal back up to the entry point with whatever information I have. Having the language runtime handle unwinding the call stack is a big benefit in these cases. Much simpler to read and write correctly, imo.
Although I'm sure I encountered ASCII art years beforehand, my first time encountering it "in the media" was watching the film "Me and You and Everyone We Know" in theater.

Since then I've enjoyed the ASCII art I've encountered, from "hype trains" to "thumbs up". I find it fun to see.
As promised, Facebook traffic to news publishers declines again
If there was a way to collect on it, I'd bet good money there won't be space pirates in the next hundred years. Without some sort of fundamental (and I do mean fundamental) advance in propulsion technology, the notion of humans being a multi-planetary species is a joke.
Python does something similar with the _hidden __morehidden syntax. Some people will like the syntax, others won't. It doesn't really change anything about what you can achieve with Go.
I don't think it was well written.

It follows a bunch of cliches from HF notes (e.g., pointless references to classic mythology and random hand-wavy macro issues). They assert a bunch of things, surround it with some facts but the overall logic is loose. There are some reasonable points here and there which lend some sense of reasonableness. But that is all a DISTRACTION.

The general goal being to give the impression of big-picture thinking when the punchline is usually A TWEAK OF SOME LONG WORN OUT STRATEGY.

Lets cut through this.

The tweaky strategy here in this case is the chart at the very end showing 50/50 mix of SP500 + Eureka hedge long vol HF index. The combination of outperforms the SP500 significantly in overall return (and in risk adjusted space). I.e., you should buy some of our HF (or your own long vol) and then also buy SP500.

The problem is long vol HF index has a ton of issues and is basically junk. It is not something you can practically replicate with long vol instruments and get anything similar in terms of performance. Additionally, a major part of the index is 2 Bridgewater funds which have fantastic performance over the period in question (especially the 3-4 years post crisis) and those Bridgewater funds are certainly NOT long volatility strategies. They are global macro. It is just constructed in a dumb way and is basically fiction. The firm that wrote the note didn't construct the index but they did select it for their comparison, so bad on them.

The classic problem with these long vol strategies is that you pay a ton of money month over month to get the return when vol picks up. And despite these strategies being generally diversifying, the performance drag kills you over time. People have looked at these strategies across many time periods, many geographies and they generally don't work. Likewise, many tail risk strategies that rely on buying options don't work well either (they can work OK under very particular conditions).
I don't think that's particularly surprising, and in fact that's the other half of the point: a 2K 'beginner program' in haskell or lisp could do all the work of a 50K C or java program, but because it's so much smaller, you have/need much less support structures and, yes, much fewer total defects.
I ended up removing my email account from my phone and removing my work slack channels from my phone. At around 3-3:30pm I close my laptop and I'm done for the day (outside of a problem gnawing at me that I think of a solution for at 10pm haha).

But generally just tune out from work and make sure you are disconnected.
OP please see: https://news.ycombinator.com/item?id=16181081
Please don't spam the forum with off-topic advertisements.
Anything can be abused. There is no technological or design measure that can prevent one from writing crappy code in Go or any other language. I'm certain of this as I had personally written some.

Except for esoteric languages, of course. I've yet to see someone claiming some code in Malbodge is crappy and offering a refactored version. ;) Just kidding.
Implicit interfaces are the single best part of Go. And the “too much magic” comment is so misguided - author complains it is bad for large codebases but it’s exactly the opposite. In the real world everyone uses conventions like those enforced by Go’s so called magic. Having these built into the language means you don’t have to figure them out every time you look at a different programmer / team’s code.
This is correct but sad. It's why better languages like Elm and Rust struggle to gain acceptance while inferior but well marketed efforts like Swift dominate.
> > The End of Men ... What if modern, postindustrial society is simply better suited to women?

> https://www.theatlantic.com/magazine/archive/2010/07/the-end....

It's a complete mischaracterization to call that celebrating the end of men. If anything it is worrying about it.
Here's a little doc Vice did behind the scenes of iFixit

https://www.youtube.com/watch?v=tx-9LkVIdz0
Lots of pros and cons, but those mostly reflect on myself. Coming out of college in '11, I had spent the past few years of my degree on HN constantly, very eager to work for a startup. Ended up working for a couple ones which went belly up pretty quickly, and quickly learned some life skills flavored cynicism. Tried my hand at cofounding a startup, got screwed over by my cofounder right as we were about to close our $1M seed, went into a spiral of depression. Realized that I was not the first or last person this happened to, and found the strength to ask for help, lawyer up, find a new job, etc. At that point, I was still only a year and a half out of college.

After that point, I began to work at funded, solvent mid sized firms for the past few years with increasingly higher amounts of salary and responsibility. It's now more than a couple years later, and although I've still got complaints with my current job situation, I've built up the skills to find a new job that will make me happier, the perspective to appreciate the journey I've been on in my past few, and savings to buffet some changes. At some point, I'm sure I'm going to try and take a side project full-time, but in the meantime, I'm pretty content making my career changes at my own pace, with my own agency, and with gradual results I'm happy with.

HN has provided a great forum to allow me to break through the reality distortion fields so common on the job (especially at startups) and make sane, levelheaded decisions. Lots of folks here have made the journey from student to engineer to founder, and I hope to one day join them! I'm beyond excited for when the right time comes for me to begin the next phase of my journey bootstrapping a lifestyle venture. It's one of the main things that keeps me going during shitty days at work, honestly.