skysight-inc/HackerNews huggingface dataset:
True, but irrelevant for Linus. It's not a good way to get ahead[1], but if you're already far enough ahead...

Personally, I think I'm on "your" side -- as it were -- on the side of civility, but sometimes you've just got to get shit done. Properly, which sometimes means shouting the right things at the right people[2].

I do think it's unreasonable of you to say that Linus is not "being reasonable", as you've clearly implied in your comment. To my mind he's being entirely reasonable, just not very "polite" or "civil" or whatever you want to call it.

[1] As in: Rise up the corporate ladder.

[2] Sorkin's "Too Big To Fail" was a big eye-opener in this regard, FWIW.
> ... he distinguished himself enough from the rest of the field ...

...by not being a plumber?
> He really talks in extremes.

Easiest way to herd cats on a mailing list.

> I see all his points but it doesn't make these things pure garbage.

Well.. you see his points and his opinion. People are always in a hurry to take affront to this, but really, he's just putting the argument where it's ultimately going to end up anyways, and in the process, he gets to avoid the dozens of follow-up emails that fruitlessly attempt to convince him out of this opinion.

You're really only left with two options, disagree and move on, or fix the problems he has with it and try to get him to use it again later.
57 is lightning fast. Like, almost uncomfortably so on my machine.

Broay this is because quantum is much further along in nightly than on the other channels. Specifically, they're more aggressive with multithreaded settings, multiprocess is enabled, and the quantum css component is turned on, too.

Is also helps that we compare to chrome. On Linux chrome doesn't even do GPU rendering. So the HN crowd probably has a disproportionately bad experience with it
Setting it up, looks great. I have a question though.. what's the difference between server api and client(s) api(s) JSON config?
> Ever tried to have 60fps on a tableview with constraint-based layout cells

Yes. I've found AutoLayout to be acceptable in this case, provided you're not doing something awful.
If those guys are traveling seasonally or between jobs, it's because they're following the work or out of work. They are not choosing this lifestyle, they are entrapped in it. Yes, if they end up driving by the beach or a national park on the way to the next job they will stop and enjoy but, not the same thing at all. The term lifestyle business does imply something different, more like the folks in the article, or Tim Ferris, or something whether you like the term or not.
I prefer my bikeshed already painted. It lets me get down to the assembly, and maybe even storing the bikes.
> You are still creating objects, be they heap or stack based. You are still choosing data structures and designing systems that will have an impact on object lifetime.

As you do in any language.

> You are still worrying about taking references during captures of objects, and making sure it is the right type of reference, and that the object does eventually get released. Bonus points if this happens across threads (and with today's async programming models, it will happen across threads!)

In the case of modern C++, Swift, even ObjC–by “you”, you mean the runtime? Following relatively simple rules does not create a huge cognitive burden on developers, I think.

> And memory is still being fragmented, especially if the data model is complex.

Agreed, but then, we are speaking here of desktop-class applications, and fragmentation issues should be very rare in this day and age.

> In a GC language, that fragmentation goes away. Worrying about when an object is out of scope goes away. Capture as often as you want, toss objects between threads, no worries, it will get cleaned up eventually. There are pitfalls to avoid, accidentally keeping a reference around will leak memory, but that it true in C++ as well. GCs solve most of the issues.

Modern C++ makes it better, but there is still a quantifiable ease of use difference between modern C++ and a GC'd language.

There is also a quantifiable performance penalty to GC’d languages and defragmentation. And GC introduces a class of issues that are so subtle, only experienced developers with experience are able to properly debug or even know about.
I guess. It's just so horrendously counterproductive, even for Salesforce, if it really was was it's being reported as.
I've found that Postman doesn't always play very nicely with CORS because it's limited to what Chrome is willing to let it to, Insomnia doesn't have this problem at all so I've made the jump
puppet is not mentioned once in the article. It's called MEATPISTOL, which is a obviously a codename. Also this is Defcon.
Ok, I shall try to adopt a turn-the-other-cheek approach going forward.

I am somewhat curious why you've singled me out though, considering the specifics of the conversations I'm involved in.
This website is completely fucking unreadable on mobile. But hey, at least it's stylish or something.
Is there some similar reason why Debian doesn't use more convenient bug tracking system that would allow a Web frontend?

I don't mind periodically using reportbug, but using something like Bugzilla is way more convenient.
> Git comes with a nice pull-request generation module,

Can anybody explain a little more about this module? I thought 'pull request' is Github only.
I like this approach, not shying away from reexamining the fundamental problem. What do you define as a "weak market"?

Seeing as that's the problem, affording agents in the space more or better control to try and strengthen the market could be an approach - so I want to understand where/what the current weaknesses are.
True, but only in large organizations that can devote massive amounts of manpower and infrastructure and have extensive tooling to make it work.
To be fair marines and medivacs are amazing units in WoL. The same likely wouldn't apply with most other two unit combo. Roach ling maybe, maybe blink stalkers.
It is still ridiculous. Just because some lawyers take on clients over the internet doesn't mean that you need to say 'I am not a lawyer' every time you discuss a legal question online. I have never seen a case of someone being successfully (or even unsuccessfully) sued for pseudonymous, general online legal commentary.
I've noticed something pretty similar. I do appreciate video games and board games and speculative fiction and sushi and campy/punny humor and all the rest, but I've worked at companies where anyone who leaned more toward Agatha Christie and cake decorating (for example) might have felt pretty left out. The more pure-software a company is, the more everybody seems to assume that others share at least 70% of the standard obsessions - which now includes weight training, home brewing, and beard maintenance as well. It's pretty sad when people in advertising or even finance seem to have and accommodate more diverse interests. Wouldn't be surprised if undertakers do too, though I don't happen to know any personally. We are an extraordinarily fashion-driven folk, and that's not a good thing.
Most people at Defcon use a "burner phone" (a cheap supermarket feature-phone) while there. Nobody who is sane would turn on their work phone anywhere near the Defcon conference. I go there every year with a throwaway phone and laptop.

So nobody will see a text message in a timely manner, unless they knew the burner phone number.
Ask HN: Major Site gives bad results a lot. Flaws in stack/framework, or coding?
On a Major Commercial Site that shall remain unnamed, I run into a LOT of sloppy defects and malfunctions.

I mean, a LOT. Wrong results, duplicate data displayed, mis-sorting, fatal errors in loading pages (complete with annoying childish messages like "Ooops!" and "Uh-oh!"), the works.

Aside from the logic (coding) errors that I've learned to recognize and work around when possible, some of the other more bizarre/esoteric problems go away with a clear of cache and cookies (which is annoying, because I lose all my context in other apps/sites).

The problem is so pervasive in this company's apps and pages that pretty much any problem report garners the "clear your cookies and cache!" response, even when it is impossible that the problem could be cache-artifact-related. (Of course, I have to go ahead and demonstrate it on a new browser just to get them to proceed with actual diagnosis).

So, clearly, many of these problems are simply bad code... but do such problems result from problems in stacks/frameworks with any frequency, or are they more likely plain coder error? (I'm blissfully ignorant on the internals of modern web frontends.)

Or, put another way: when bad artifacts are picked up from the cache, it that the fault of the framework/stack or the fault of the programmer using them?
Also, should it really be called merge request? What exactly are they pulling during the merge?
How to Get a $20,000 Discount on an Electric Car
Since ES6/2015 the changes have been pretty minimal, so I disagree with your assertion. Since 2015 I find that async functions is probably the most alien addition... and the handful of others that are significant are mostly ignored or very natural extensions.

The shift from callbacks to promises is kind of alien, but frankly that was started well before 2015 even. The .babelrc I use for node projects is pretty simple as well, here's one I use for an AWS Lambda build...

{
"presets": [
[
"env",
{ "loose": true, "targets": { "node": "6.10.3" } }
]
],
"plugins": [
"syntax-dynamic-import",
"syntax-object-rest-spread",
"syntax-async-generators",
"transform-class-properties",
"transform-decorators-legacy",
"transform-object-rest-spread",
"transform-async-to-generator"
]
}

So that's literally 3 things that aren't in spec yet, and a couple that work around the runtime not having them. Most of what's going in is already in, or relatively well established and on the way.

Now, you do have to include a lot more if you want IE11 support, but hey, that's a different thing. I'm not sure what exactly you're having a trouble wrapping your head around.
> because there also can be a feedback effect from people preferring fields with more people of their own gender

No, that would mean that women in business, architecture, physical sciences, etc. would not have increased.

The fact that women in CS followed closely several other fields (business, architecture, etc.) means that % of women already on the field is not relevant.

The fact that other fields that use skills similar to CS (math, stats, physical sciences) have much higher women ratios, show that there is no inherent biological factor impacting it.
That's not proof. It's an observation that needs explaining. Scott Alexander's post[0], which was linked in TFA offers a plausible explanation.

> My impression is that there were lots of women in CS in 1980 for the same reason there were lots of Jews in banking in 1800: they were banned from doing anything else.

> Computer programming was originally considered sort of a natural outgrowth of being a secretary (remember, 77% of data entry specialists are still female today, probably because it’s also considered a natural outgrowth of being a secretary). Women had lots of opportunity in it, and a lot of women who couldn’t break into other professions naturally went into it.

> Then people let women become doctors and lawyers, so a bunch of the smart ones went off and did that instead.

> You can see the same thing going on with teachers. There’s been a huge decline in the percent of the most talented women who become teachers.

[0] https://slatestarcodex.com/2017/08/07/contra-grant-on-exagge...
I'd assume the increased life expectancy is more about the free healthcare than the earlier retirement.

Free treatment for everything. That does help a lot when you get old, starting with all the minor problems happening with an aging body, and concluding with the last few years where you could literally be kept alive despite a critical condition requiring constant care, all paid in full by the tax payer.
Are you absolutely sure you arent just convincing yourself?

As someone who does actually love all this stuff so much that work doesnt start and hobby doesnt really stop... We meet and work with people like you all the time. We like the diversity. There are many ways to contribute to the end result and any smart company hires both of us.

But your resentment is mean spirited. Get over yourself. We are not driving any one away. From operations to sales we are all needed to make the engine work. But if you come here arguing that those who love their job should be fired so there is place for you without you trying so hard, that just silly. Here is the thing: from all disciplines i know there are people who love and breathe their job. If thats not the case in engineering for you, then you likely want to find the field that does make you that happy.

That might just be a smarter plan than trying to convince yourself by convincing us that in a field dominated by people who love it, you can be competitive while considering it just a safe career path. You'll just end up miserable.
They seem to build it against a reasonable version of Qt, I haven't updated it in a while (because it's just a launcher), and when I do I'll just re-symlink against whatever Qt is currently installed (which I do keep updated)

I understand your argument, but in this particular case things aren't volatile enough that it causes any problems, and if it does it's just as easy to solve.
Despite all the snark in the comments here, this is actually a rather good article and analysis of overtly partisan websites and social media.
I recently tried out Lazarus, and besides looking a bit dated, it works REALLY well. I had no Pascal experience so it was also overwhelming for a hello world app. But after the basic Pascal "Hello World" command line app, a GUI app didn't even require a tutorial to get working. Really impressed and am considering Pascal for a project.
Decent podcast episode with Zach as a guest: https://theamphour.com/332-an-interview-with-zach-barth-of-z...
Ugh, makes me think of COM

https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...
If I create an app that delivers cup cakes and cakes to people having weddings - but only to people who have "straight" marriages, would this be a "narrow niche" and "business opportunity", or would I have the shit sued out of me?
> Ever tried to have 60fps on a tableview with constraint-based layout cells ?

Yes, even on a 4S.
App Annie's service is "VPN Defender", apparently:

https://techcrunch.com/2014/10/31/app-annie-fills-the-void-l...
Our projects' linting rules specify no semicolons, except when necessary; this means that we will _very rarely_ write something like this when we want to iterate over a small literal array:

;['foo', 'bar'].forEach(function (f) {
it(`has an ${f} field`, function () {
expect(......)
})
}

That said, we tend to use that construct extremely rarely, such as in a few test cases where we are doing the same kinds of things on two groups of items that need different descriptions.
I miss the glory days of RAD
> Diversity programs would at some point stop being ineffective.

I seriously doubt this will happen unless people criticize the failings of diversity programs, and diversity officer take this criticism seriously.
There's a good chance that those guys didn't even have their phones on. If something is that urgent you don't text, you call, and if the call doesn't go through you find someone else that you can call who can go to the people involved and so on until you have guaranteed timely delivery and if you can't achieve that then you're going to have to live with the consequences.

Doing a 'fire-and-forget' text message and then attaching grave consequences to the timing is ridiculous.
Well, if you're willing to be homeless you can retire any time you'd like.
“I want to learn how to fly a Cessna where should I start?”

“I’d recommend hang gliding. That way, you don’t have to worry about the complexities of piston engines. Since you already know how to fly a kite, you’re practically there already.”

While hang gliders and Cessnas are both flying, there are a lot of things Cessna can do that hang gliders can’t.

I will be glad when JavaScript stops being the answer to every question. iOS apps aren’t just webpages running on a phone. How, for example, does react handle pre-release Apple APIs? How does it work with ARKit or other iOS specific tech?

Why do we insist on building to quite literally the lowest common denominator rather than building to the strengths of iOS and Android?

React Native could be a prudent choice for certain kinds of apps, but I’d argue that the apps for which React Native excels probably don’t need to be apps in the first place.

Apps ought not be glorified web pages; they should take advantage of the hardware to the fullest extent.

If an actual Swift developer recommends React Native, I might listen, but generally it’s web developers who downplay the advantages of Swift because they themselves have been unwilling to learn how to get the most out of it and the iOS APIs.

This whole cross-platform obsession results in lower quality applications. Case in point: Slack for Mac OS. It’s decent, but it would be significantly better if it were actually native. This trend of wrapping a webpage and calling it an app is a disservice to your customers.

There’s a reason I have an iPhone. Yet, with this cross-platform nonsense, developers are essentially kneecapping our devices. This applies to Android as well.
Everyone complains about the build tools, but they simply haven't thought through the issues.

Let's say you were writing the web using Python. New browsers run v3.x, but old ones run 2.x or even 1.x. Further, features in newer versions of v3.x won't work on older versions of v3.x. New browsers could include all three runtimes, but old ones would be SOL.

How do you use v3 features and target v2 or v1? You must transpile knowing that newer browsers also have v2 and v1 engines included too.

You have hundreds of Python files in your system. Delivering hundreds of files is simply not practical on HTTP/2. You combine them and now you have webpack.

What about libraries? As big as the standard lib is for Python, it doesn't do everything. You use pip or conda and now have npm/yarn.

What about code consistency? The solution is pylint.

What about testing? Add that to your chain as well.

It's the unique issues of the web -- NOT Javascript -- that makes the build pipeline what it is. Until a few short years ago, these things weren't even possible. Today, if you know node/npm, webpack, babel, and eslint, you know the overwhelming majority of build processes.

I'd finally add that make, Jenkins, etc are far more complicated to learn than the JS systems.
It looks like github's pull requests and other features Linus had problems with have improved since 2012. Here is a pull request that Linus opened recently:

https://github.com/Subsurface-divelog/libdc/pull/7
> And nobody cares how much you produce if you're too unreasonable to sell them on your creation.

But Linus already has.
That explanation doesn't match the chart: There weren't a lot of women in CS. They were growing, just like other fields.

And then, suddenly, they stopped growing and started declining.
I don't believe he's being that nitpicky. Brood War had a lot of micro, including marine micro...

Boxer (SlayerS_Boxer is who I think you are referring to, as he also played starcraft 2) was well known for having really insane marine micro in the community before SC2 even came out. Starcraft 2 was just way bigger in the west so more people over here associate MarineKingPrime with micro than brood war pros.

e.g. https://www.youtube.com/watch?v=WJp0t9n8DWk
Off-topic:

Why does this blog need to be whitelisted with Adblock Plus? See data-adblockkey in HTML source. Are there any ads in this page? (Maybe owner wants revenue from domain parking?)

Why is this blog not working with simple user agents that do not process javascript (e.g., curl, etc.)?
"yes it's not as simple as calories in/calories out, but calories are still the most important" : http://physiqonomics.com/calories/

tl;dr: outrunning your fork is _prohibitively hard_.

In my personal experience, weight loss and fitness are not orthogonal, but they aren't the same vector, either. In agreement with the NYT link, I exercise because I want to be fit, because I want to prevent injuries, because I don't like being depressed, and because I want to do the previous items until I'm 90. Personal vanity is real, but secondary.
I have only been to the West Coast so far, which is very difficult for travel. I believe (but have no experience) Namibia, Kenya, Tanzania, Uganda are all spectacular are easy (er) for travel
I get the sense that you're trolling, rather than engaging in good-faith discussion.
> I would also note that saying "I wish more effort were being made" is a bit entitled when you're talking about an open source project. No one working on any open source project owes you anything.

no, "i wish" just means "i wish". it doesn't imply anything like "being owed".

being "open source" doesn't establish carte blanche to oblige everyone to labor on the project if they dared to have a thought or opinion.

> If you want the project to get better then find a way to contribute.

there are thousands of projects i'd like to see get better. not everyone has the time, ability, desire or capacity to implement everything they've ever wished for. this is just silly.
That's not a very good excuse for someone who's communicating with other people outside of his culture. He's had many many years to learn that his style of communication doesn't mesh with most people.
Words may be relative, but that's why we set up systametized math notation to appeal to when we need to start characterizing the precise nature of algorithms and systems.

To argue that this is act of pedantry is to argue that any form of canoncial notation to describe the essential nature of algorithms is itself pedantry. It's to suggest bigO notation itself is pedantry and by extension so is it's defense.

In the face of this, I'd say, "If you don't like it, don't use it. But many people do find it useful and it's corrosive in the extreme to demand the right to redefine it for what amounts to marketing purposes." Scala's got a bunch of actors in it's community that do this; and it's frustrating when you're trying to evaluate the ecosystem.

The asymptotic boundaries of algorithms ARE theoretical tools that can be misleading. For example, how many people incorrectly suggest that quicksort is asymptotically faster than merge sort? It's not.

But the response to this should not be to vaguely redefine the terms. The response to this should be to quantify the implementation's docs with real metrics.
Again, not trolling !

Your comment just make me thought of that, and how it makes me laugh each time I see that on a movie/show. And also realize that there is surely a (big) part of non-tech people that may think it's how it works.

If an encrypting method "tells" you you're getting close, it will be a bad one.

(and sorry if you took it personaly. Next time I'll check the poster profile first :)