skysight-inc/HackerNews huggingface dataset:
Indeed, but they do have policies, high level approaches and big decisions too.

The problem with this kind of direct democracy is the same as with all diplomacy - astroturfing, focus groups, demagoguery and unintended consequences.

Focus groups make diffuse votes matter less despite being more prevalent. (Overwhelming majority in some cases.) Astroturfing is a kind of diffuse bribery. Unintended consequences is most often when people are presented with a package deal and do not dig deeply enough to figure out results. Finally demagoguery is usually by presenting a palatable but highly inferior option or by going for short term bandaid solutions.

The latter two are less relevant to a programming language project.
1-1 is good time to talk about personal growth , promotions , salary increments , inter-personal issues etc. be prepared for it (at least few hours) and have clear-cut actionable items to follow up or put the agenda in meeting invite itself, otherwise it will be just a random talk.
Responsive Tables – How to scale your site beautifully
Just a inane tangent, but I rather think Disneyland is Disneyland for adults.

Or maybe I don't adult well.
So it wasn't only me. The whole parallel with Trump is ridiculous. With all the reasons to bash the administration, this sounds like a 12yo rant, for the sake of bashing.
Thank you for the amazing works.

There is a type in the copyright footer on your website, it states (c) 1066 - 2019
They still have a significant presence in Silicon Valley.
Why the downvote? It is not like the organization form was thrown onto the project by an external force?

Or does self organizing mean something different from what it says?
It is already for a year or so. We have not met any limitations (for our use cases) there.
I've watched a youtube video about the chances to survive a fall from/or with airplane parts (sorry forgot the channel but it was some physics channel) and the reason seems to be that airplanes tend to break in the middle while the rear of the plane tends to stay in one piece. So you still have some protective shell around you if the plane has a crash that is at least to some degree survivable.
I took an inventory of which apps my parents use: email, solitaire, Youtube, and some web browsing. That was it. Linux is good at doing those things, so I put them on Xubuntu (my preferred distro) about 8 years ago. Once my mom understood that the UI was similar enough to Windows, she didn't mind. Its been remarkably stable (and usable) ever since.
Knowledge from small number of debates outperforms wisdom of large crowds (2017)
Out of that list, I only feel comfortable talking about personal growth but that also gets tiring. My personal growth goals don't change every week.

Promotions & salary increments, maybe when the time come but it's a once a year talk?

And inter-personal issues, I get along fine with my coworkers. Should I complain about them more often?
First, about accessing private fields on members of the same class: the spec will allow this via `other.#foo`.

The reason I said that the difference between `object.foo` and `object.#foo` is not purely syntax is because they are two completely different actions. The first is a lookup in the object's property map/prototype chain. The second is a private field lookup.

`object.foo`:

1. Check to see if there's a property named "foo" in `object`'s property map.
1a. If yes, return the value.
1b. If no, continue.
2. Does this object have a prototype?
2a. If no, return undefined.
2b. If yes, repeat these steps starting from 1 using this object's prototype.

`object.#foo`:

1. Test to see if you're in a class.
1a. If no, throw a Syntax Error.
1b. If yes, continue.
2. Test to see if `object` is an instance of this class.
2a. If no, throw a Syntax Error.
2b. If yes, continue.
3. Test to see if the class defines a private field *#foo*.
3a. If no, throw a Syntax Error ? (Not positive on this one, it might just return undefined).
3b. If yes, continue.
4. Look up this class' private fields for `object`.
5. Get the value for *#foo*.

In case it wasn't clear: the private field `object.#foo` is NOT a property on `object` named `foo` and marked private. It is a field which exists in a namespace only accessible to the class definition. Without the # sigil, there'd be two issues. See [0] for a pseudo example of how private fields really behave.

The first issue comes from a decision made in the spec by the committee: private fields must not interfere with object properties. This essentially means that an object can have the private field #foo AND the object property "foo" (as I described here [1]). Without the #, the fields would have to exist in the same namespace as the object's properties. If you error out when `object.foo` is accessed outside of the class definition, it would not fit the spec's definition of "private". [2] [3]

The second issue is that without the #, the compiler would need to determine at the call site which lookup method to use, and they decided this would incur too much overhead on every single lookup in the already complicated property lookup logic.

0: https://news.ycombinator.com/item?id=18707421
1: https://news.ycombinator.com/item?id=18706363
2: https://github.com/tc39/proposal-class-fields/blob/master/PR...
3: https://github.com/tc39/proposal-class-fields/blob/master/PR...
Lyft shuttles are better buses. Better times, flexible routing, less road damage, and more comfortable rides. And they relieve pressure off the municipal system. It's a win-win, except for people who blame Lyft for public transit's flaws.
What's the use for these kinds of wireless networks? I've seen wireless networks in big campuses before and it's just a bunch of APs that sit on their own VLAN that talk back to a controller sitting a telco closet somewhere else. They just plug into the wall so the only wireless part is the connection between the user and the AP but these kinds of things seem like they are meant for a different use case.
Probably the companies they use to actually collect money from members.
Depends what your interests are.
Can My Business Leverage Data from Enterprise Apps by Connecting BI Tools?
https://imgur.com/a/hgBdkJJ

This one looks a bit dodgy
The boogie man about serverless is overrated.

In the grand scheme of things, at least for AWS, the only thing you do to make your app “serverless” is add a function with two parameters as your entry point. If you’re following standard software engineering principals of keeping your interface and your business logic separate, it’s not that hard.

On the other hand, the fear of “vendor lock in” is overrated. You’re always “locked in” to your infrastructure. Companies hardly ever change their infrastructure wholescale. The risk of regressions are too high and it’s usually not worth it.

Besides, if you rely on AWS services and are letting AWS do the “undifferentiated heavy lifting”, converting lambdas is the least of your issues.

If you are just using AWS to host a bunch of VMs, congratulations, you now have the worse of all worlds. You’re spending more than baremetal and you still have all of the management overhead.
This is great marketing but suggesting some symbiosis between serverless and startups is odd. Startups for the most part dont have scaling issues that are experienced on the server. They’re usually people, process, and financial issues.

I see posts like this and wonder how many people will use some new paradigm because people say “its fast” when they still have no traction (not suggesting the author doesnt) or they dont even understand the scaling properties of their software or business.
It's a little hard to cite now - most of the user-level permissions are gone, or are behind a "This permission is restricted to a limited set of partners and usage requires prior approval by Facebook" restriction.

They've clamped down repeatedly on how much data comes out of the API - you used to get full info on friends, then just their names and IDs, then that list wound up filtered to just other friends who'd authorized the same app.

It used to be extremely wide-open.
You just defined the value and utility of it thus it is valuable whether he dies or not.

Your argument is like saying that understanding cold fusion has no value because no one has communicated a valuable understanding of cold fusion.

It might not be possible but if you by your own definition figure out how to do cold fusion then that is a valuable insight, whether or not it comes to fruition or the person dies.

Insights cannot not be valuable, they don't have to be implemented to be valuable which is easily demonstrated by a simple thought experiment.

If you had a time machine and could go back in time on that submarine right after he gets the idea on how to do it, extract that information and leave before he dies, would that be valuable? Of course it would.

Getting an insight in the shower or getting an insight on drugs/mushrooms doesn't change the value of the insight whether it gets implemented or not.
The spec (and the committee) has defined "private fields" to mean that anything outside of the defining class (including subclasses) should have no knowledge of them. If your subclass needs to know about the property, make it "soft private" by prefixing it with _.
Dirty dealing in the $175B Amazon Marketplace
Rural broadband, primarily. Places where there is no DOCSIS3/3.1 coax cable, beyond any reasonable copper loop length for ADSL2+ or VDSL2 over old POTS phone wiring, and the only other option is a small satellite terminal. There's hundreds of WISPs all over the US operating in their own little pockets of service area. Rural parts of eastern Oregon and nothern Idaho for instance.

High degree of venn diagram overlap with the same customer market for the SpaceX Starlink system if it does become a concrete reality.
Go Develop – Docker and Makefile based setup for bootstrapping a Golang project
Hmm, it depends.

Elsewhere someone bemoans that landing pages don't answer "what is it?".

Some (most!) sellers couldn't care less if it's right for you, just if you buy it. Spelling out what a product is can lose customers.

Example: Back in the day I bought a minidisc player-recorder as you could easily put/remove tracks digitally. Turned out you couldn't do that properly, only from computer, not to computer, making it terrible for live recording (my need). If they'd told me properly "what is it" then I would instead have bought an mp3 player.

Yup, still bitter - cost me many hours that mistake.

A corollary to this though, they made the sale, but I've never bought from the company (Sony) again.
I thought it was a great idea at first but in reality I only use it for the calendar and get annoyed by requests on every other site.
In fairness to the other side, I think the glitter-in-the-eye part is where an issue might arise. I don't agree that the privacy thing would hold up for shit, but courts have ruled against folks setting up booby traps on their property in the past.
The question is if the explicit ones replace the implicit ones or are in addition to them.

I don't know python well, so this all might work very well for them. But if, for instance, there was a very core developer or two, then no amount of structure will take away from their sway. If a major point of contention arose between the "paper" structure and the core developers, there will be a problem.
I would never work for a company that wants to save a few bucks by having as part of their process “manual failovers” that might cause me to wake up in the middle of the night when they could have just allowed me to properly architect the thing in the first place.
All dictatorships have bureaucracies; are they going to rule alone? The question is whether those power structures are visible and explicitly negotiable.
But then what happens if you have `private myVar` and you need to access the public `myVar` from within the class?

That's not an extreme hypothetical, it was a real example from someone trying to use this feature. They had tried to emulate private fields with an underscore before, people started using the private variables, and now they want to refactor while keeping the current "private-turned-public" variable working the same.

I'm sure you can come up with answers for most of those things, but will they really be easier to understand than the current proposal? I'd hate if I have to look around in the class any time `this.anything` happens to see if it's private, public, shadowed, a getter/setter, etc...

`this.#myVar` is explicit, it's obvious, and even if it's ugly as a sin, you know it's not doing something "normal" right away.
I'm currently involved in automation processes, which has always been a thing but now 'RPA' is a fashionable term.

Peddlers of the term are also peddlers of ambiguity for what their tools do. Those that I meet that have seemingly been evangalised by these solutions describe 'only low level coding needed'. Assembly? Or not wanting/knowing/needing/trusting to multiskil a team?

There are good RPA tools. The authors of which are straightforward about what they do.

That's just an example of an audience (me) having trouble understanding something smoke and mirrors is often painted around.
Show HN: Atari – Solving Games with AI (Part 2: Neuroevolution)
I think my point was that is you're not covering "what is it?" when you're answering "what's in it for me?" you're not actually covering "what's in it for me?" (if that makes sense).

To successfully demonstrate the value, you need to convey how that value's delivered in my view.
How is “architecting for lambda” harder than traditional architecture?
Ironic that the site hosting this article does not give a real opt out to intrusive tracking (their privacy policy refers you to your browsers help menu to learn how to block their cookies!).

Is this GDPR compliant?
What if your not near the entrance to the tunnel - how do you get to the subway?
Linux has never purged any of those. It is more like it got "conquered" by money and resources allocating developer time. For that matter, so will any truly important and developed FOSS.

Not sure what do you expect, Mozilla model with an NGO, who can still be pushed by competition and wealth into irrelevancy?

Ask about RedHat and their push for dominance in both init system, package management, GUI and audio server, conquering even Debian and Arch in the end, making Gentoo less relevant, making BSD compatibility hard.
Countered only somewhat by Android and its practices, Google's money and software market.
Playback or rendering ? I know my browser has performance issues because it doesn't have hardware-accelerated playback for VP9, I don't know if FF is in the same basket (sounds like it might be). Having an addon that only enables h264 solves that.
I think this is good feedback. I'm surprised that you got 2 negative responses to your suggestion. You never said that you disagree with the comment. You were requesting that 1 or 2 sentences could have been rewarded.
I'm doing ASP.NET Core on a Macbook Air using Visual Studio Code.
Chaos Engineering- Applied at Netflix, LinkedIn and More
Selling benefits you'd say "hear your music at it's freshest with our unrivalled audio fidelity" or somesuch, which of course is a lie; but that's marketing.
I think I fail to understand how Lambda works better for startups. I see primarily 2 arguments.

The first one is simplicity. You pack your Node.js application, upload to lambda and it works. But then in the article I see a chart with API Gateway, then Lambda, then SNS and then Lambda again. How is that simpler than deploying a single Node.js application on DigitalOcean?

The 2nd argument is scalability. I see how this is relevant, I'm wondering though how often it becomes really useful. How many products experience unpredictable spikes in traffic that cannot be handled by a single server costing $250/month? (that's one c5.2xlarge server on demand).

I believe FaaS and Lambda are very useful, but I think I miss the point why would people move their whole applications there.
BDFLs only work when they're the founder of the language, or a well-respected community member who is explicitly appointed by the prior BDFL. Without a clear line of succession, you get all the same destructive infighting and power struggles that real-world dictatorships experience.
This completely depends on what the startup is doing. For my use case (company name in profile) auto scaling is a god send due to individual users being able to influence how much work our jobs backend needs to do. This impossible to calculate and plan upfront so we totally rely on Lambda for this.
When that time comes, hopefully you have found product market fit and are capitalized well enough to make the move - see Dropbox.
> I recently had a German student explain to me that they understand hard (but dumb) work as what this phrase means.

Not quite.

It's a phrase derived from "Protestant Work Ethic":

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

Stripped of the religious connotations the phrase as commonly used (eg. "having a good work ethic") essentially means "feeling an obligation to consistently work hard for your employer".
Theoretical arguments are incredibly overrated for complex systems. Usually, they're just ways for academics to signal their ability to make these arguments, to show off how smart they are, and of little utility otherwise.

You need to see how things actually work out in practice. And in practice Swiss democracy works very well whereas most central bureaucracies are soul killers.
AIVA – Music Engine
Most Important Responsibility
It's weird because it's Rob Enderle.
You will get more problems like these if the largest advertising company develops browsers. No excuse for the other browsers though...
This is an early stage in the project but it looks like its intending to be a Chef or Puppet in python with a terraform-esque plan and apply stage.
I also use asp.net core both for personal project and company product. It works great especially with f# and giraffe. But in company we use oracle, the devart.data.oracle.efcore is not very good, actually a little bad.
A good benevolent dictator is often more efficient than a more decentralized and democratic system but you have a single point of failure and you need to be able to find said dictator in the first place. A bad or incompetent not-so-benevolent dictator can be absolutely terrible for a project and cause a lot of long-term damage.

For such an important project unfortunately I think a certain amount of bureaucracy and paperwork is not only unavoidable but actually necessary and important.
Yeah, I assumed that "sandbox" implied some smarter isolation technique closer to eg Linux namespaces instead of just app-v in a new shiny packaging. Nothing new for the malware-analysis use-case.
In retrospect, going serverless (using Serverless Framework) has been a terrible decision for us.

First, exposing an API served by AWS Lambda has the infamous cold start problem. It's not fun to wait a couple of seconds for a mobile app to respond just because the request hit in an unfortunate time. One solution we found is to use a Serverless Framework plugin to periodically ping lambdas to keep them hot. But each concurrent lambda execution is a separate container, so you have to anticipate a number of concurrent requests you will be receiving at peak, or want to handle without a ~1s latency. Ouch - what happened to effortless scaling? And Amazon API Gateway adds another 100-200ms of latency on top of Lambda.

If you want to use an SQL database, you have to add your lambdas to a VPC, unless you want to expose your database to the Internet. But if you need to access the Internet from your lambdas, then you need a NAT (which you pay for). And you get another couple of seconds to cold starts while AWS attaches a network interface to your lambda. So, if you don't want this, you're stuck with e.g. DynamoDB. DynamoDB is optimized for scaling but it's a poor fit for relational data. Very basic support for indexes, no transactions, and data model migrations are very painful. There is also no spatial data story for DynamoDB, whereas if we had used Postgres, we'd be able to make use of PostGIS which is awesome.

The tooling is terrible. Serverless Framework is very rigid and riddled with bugs - we ended up maintaining our own fork of Serverless alongside forks of 3 plugins and another custom plugin we wrote to support our very simple workflow. There's no faithful offline reproduction of the API Gateway -> Lambda environment. We frequently ran into issues when the code is deployed that wouldn't show up when testing with a "simulation" plugin locally.

There's a lot of other problems we ran into, but these are the biggest ones I could think of. It didn't help that we didn't have much experience with this technology before deciding to serve our API using it (this was probably our biggest mistake). I guess we should have stuck with what we're faimiliar with - normal, "serverful" apps. And with the DyanmoDB provisioned capacity costs, I'm not sure we saved that much in the end.
I would say architecting for Lambda is easier and quicker than “traditional” by now. Was a bit flaky in the beginning, admittedly.
Feel free to represent yourself against a multi-hundred-million dollar (or larger) corporation and let me know how that goes.
> But they can at least be dismissed until the next feature update puts them back.

This is damning praise. If intentional it means users are't being offered permanent control of the software, only momentary changes. I dare say they aren't even 'options' at that point since the word implies lasting choice; at least for me.
Not a parent commenter, but I have some examples of upgradeability/repairability. Dell XPS line of laptops has upgradeable storage and screwed-in batteries. 15" variant has upgradeable RAM and wireless card. The keyboard is attached with screws instead of being permanently fixed to chassis and costs significantly less to order and replace yourself should you find a need for it. Similarly in the worst case scenario, there are replacement motherboards on eBay for $550 or sometimes less which you could again order and replace yourself (or upgrade your base CPU option with).

And both 13" and 15" Dells have a fingerprint sensor which is as snappy as Touch ID without being bundled with a thin strip of touchscreen and a $200 price hike.

That's because these laptops are designed to be serviced on-site by repairmen who are not always so bright. So I imagine, similar HP offerings are as robust.

Dell's and HP's phone support and warranty support are super awful, though, so this may be a factor for you. For me, the difference between a drink spill costing $600 (and I do it myself) on a $2500 Dell versus $1500 (and I have to lose my files/get a new system) on a $1600 MBP (both true stories) is significant and I'm not rich enough to go for latter.
Cheapest hotels and airline tickets
Introducing PyText Facebook’s New Framework for Better NLP Development
"Giving Spotify, Netflix, and the Royal Bank of Canada the ability to read users’ private Facebook messages."

Its RBC that is the interesting one here. Did anyone think we would live in a world where your bank has the ability to read your private messages between your friends?

EDIT:
Puer mentions below that this might just be a permissions issue and it doesnt mean that they actually read your private messages.
And funnily its from cznic while the op's router is from apnic.
Jamaica Crime: One U.S. tourist raped each month
Google looks for obscured ads, but there are new ways of tricking both the bot and the ads code coming out almost monthly.

What they look above all else are the organic clicks from clear IP ranges.
It's already started: https://medium.com/coryodaniel/from-erverless-to-elixir-4875...
The Founder’s Guide to Discipline: Lessons from Front’s Mathilde Collin
This looks really really nice, do you have any plan to add relational annotation support as well? Asking since a student is about to embark on a project that would require it. In hindsight, I regret that we did not get around to implementing Mechanical Turk support back when we made brat. [1]

[1]: http://brat.nlplab.org/