skysight-inc/HackerNews huggingface dataset:
...and it's down. Google Cache: https://webcache.googleusercontent.com/search?q=cache:IQfOUB...

"All fisheries that take place in federal waters require regulatory action to open and close season, set catch limits, modify conservation and management measures, or adjust participation eligibility requirements... In many cases, multiple regulations must be enacted each year for a single fishery and that is a good thing – American fishermen depend on active, science-based management to ensure that their individual operations and their industry are economically and environmentally sustainable."
The apps you listed (+ other similar apps) are exactly what I use DO for. To me they are the KISS cloud provider. Nothing super fancy but the flip side to that is that they are easy to use and interface with.
When I want an MVP or a non-enterprise type app I go to DO. If I want something more complex or something that needs more PaaS-like services (databases, app hosting, etc) I turn to the big three.

EDIT: This is coming from someone who works at MSFT and gets a bit of Azure for free. To me it's all about using the right tool for the job.
How is this different from, my personal favorite, Fossil. http://fossil-scm.org/index.html/doc/trunk/www/index.wiki
But does KDE work well on a low resource machine?
I am more the MongoDB bandwagon. Shemaless makes prototyping so much easier. And no migrations!
I don't find Go simple at all, actually. Any individual line of Go might be simpler than many individual lines of Scala. But understanding how the whole system works can actually get complicated, particularly in code where the lack of generics forces type information to be lost.

Consider a pipeline:

source ~> retryQueue.firstInput ~> requestAttempter
requestAttempter.successOutput ~> finalizeResult
requestAttempter.failureOutput ~> retryQueue.failureInput

This is basically logic to process a stream of messages, successes get finalized, and failures go into a retry queue until they succeed. I've got a large system doing this right now with Akka streams.

In Scala, type signatures ensure that everything lines up or else you've got a compile error. In a similar Go system, I lacked stream abstraction (I think Cloudflare has a beta library that does this now) and the lack of generics mean that streams are untyped.

For example, what if I pass a `Message` object to `retryQueue.failureInput` rather than a `MessageWithRetryMetadata`?

So I don't agree at all that Go code is easier to understand and maintain than Scala.
No. Sanskrit is not derived from Indo-European family. There is absolutely no evidence for that. Nor do South Indian languages appear linguistically distinct. I'm a Kannadiga and many Kannada words are directly derived from Sanskrit. My mother is a Tamilian and a lot of Tamil words are also derived from Sanskrit. This falsehood was spread by the British.

> In any case, Iranians today identify as Aryans (Iran effectively means the land of Aryans in old Persian, as I understand) and the general western consensus these days seems to deem Indo-Iranians as Aryans especially due to obvious recent historical connotations during which many in the west dissociated from the term.

It doesn't matter because India was also called Āryāvarta (Abode of the Aryans) in the Ancient days. This was way before Iran got it's name (possibly in the 3rd century A.D). Iran was called Persia in the olden days.

The word Aryan itself has multiple meanings. The definition of Proto-European Aryan is different from Indo-Aryans of India.
For counts of things you have in memory, 32 bits is usually enough -- even if each thing is just 8 bytes, 2^32 of those objects would require 32 GB.
Oops, it's duplicate, I didn't see that post before, Thanks for info
"It can also cause Google to ban sites from Adsense."

If you object to ads, is that a bad thing?
You could always say

if (flag) while (1);
I used darcs for a while a few years back, it was ok. But definitely less polished than git.

Also the only vcs I've ever used where the repo managed to corrupt itself to the point I lost committed but unpushed changes
I should have clarified that I didn't mean general tech, but specific tech products that are hyped.

You're right about the serial entrepreneur aspect. But we're still talking about staggering sums.
I agree that the heuristic is far from complete. I've been tempted to add to it many times, but for me, it starts to diminish its usefulness.

I'll use "my test" to indicate areas that might have less consideration. For example, solution design tends to get the most attention from founders. You have an idea and start to run with vision and possibilities.

But, as you noted, the attention given to economics may be lacking. This can help remind you to try to balance your planning.
> Which fans without a lot of money?

If you have more fans than seats, some people will be unable to attend. That's unavoidable. But the constraint you're replying to says "ensure that fans without a lot of money can see me", not "ensure that all fans get to see me". So your criticism is a little off target. Yes, those fans willing to show the most dedication might have an advantage.

But we can solve the majority of the "disproportionate power to the wealthy" by the simple expedient of only allowing one or two tickets per person, and matching ID to purchasers of the ticket at the door.
That 'almost no one' is growing steadily.

https://linux.slashdot.org/story/16/07/02/184229/linux-grabs...
> If you shut off JavaScript a lot of sites won't work

If a site requires JavaScript, it already doesn't work. If a site requires JavaScript, its owner clearly doesn't care about either your security or your privacy.

Why use a site which requires JavaScript?

JavaScript delenda est.
Hire the foreign worker obviously. That's just business and economics 101.
I doubt that Go network libraries and crypto libraries are so well battle tested as Java ones, which Scala can take advantage of, specially taking into account the amount of JVM and library vendors.
They are a very large EU-wide integrator, and have partnerships with pretty much all the boxbuilders. The whole saga with Sun hardware was likely just another profit opportunity.
>For some reason, SRV records are not in wide spread use.

No legacy tooling supports it. Poor support on the products already there. Huge numbers of firewalls are hard coded to 80:443 so alternate ports would be blocked.

When you make a poor choice on the internet, it lasts forever.
The HN headline was changed by a moderator, I suppose to comply with the guideline that the submitted headline should match the article's title.

I originally submitted it with a headline describing the 14nm AMD Zen core being 10% smaller than the 14nm Intel current-gen core (and I accidentally linked to page 1 of the article instead of page 2.)
https://www.youtube.com/watch?v=n5yt67uZdgQ is fairly decent talk.
I know you're making an analogy but comparing AdNauseum to ambulance drivers is a bit of a stretch. One of these is saving lives. The other has no purpose except to inflict damage on ad networks. Aside from damaging ad networks, it also actively harms site owners by increasing the risk of them getting blocked from the ad networks that fund their work.

I don't see a lot of merit in AdNauseum. It feels to me like a petty "fuck you" response from people who don't like ads.
DO is cheap, you can achieve scaling and failover for a lower fee than with AWS. Their new load balancing solution is nice but lacks features and its price is 3x higher than what we provide at https://pikacloud.com.
This is probably too much to ask, but is there any chance you have React bindings on the roadmap?
Is customer development still worth anything if a third party does it?
Thanks for this. I was baffled to see so many comments explaining how to "fix your grip strength".

It's not a bad thing to do, as a climber I care a lot about grip strength, but it's not a significant total-health goal. Grip strength is highly predictive partly because people don't train it, and so it represents overall fitness and muscle development. Working hand strength in isolation just breaks that predictive relationship without producing the overall health improvements that come from an active life and whole-body fitness.
Linode's load balancers have clearly defined support for 10,000 concurrent connections. Am I missing where the limits are on DO's?
No affiliation, but I really like http://gmb.io. I'm a black belt in Brazilian Jiu Jitsu, so I find dynamic body weight movements more engaging than weight lifting or yoga. The progressions on the site are fantastic - some of the best movement pedagogy I've seen.
> It's wonderful to not have null. Except that you do anyway!

If you hit a NPE in Scala, you're doing something objectively wrong. You should be wrapping any calls to Java libraries that may return null with Option().
Are you 10x though? Gotta be 10x or more.
You don't need to specify a return type in scala. In this case the return type is inferred as Option[Long].

You are correct about the exception if the cookie's value can't be parsed as a Long. You might instead write the code as:

def getUserId()(implicit request: RequestHeader): Option[Long] = {
request.cookies.get("uid")
.flatMap(cookie => Try(cookie.value.toLong).toOption)
.filter(_ > 0)
}

or, equivalently:

def getUserId()(implicit request: RequestHeader): Option[Long] = for {
cookie <- request.cookies.get("uid")
value <- Try(cookie.value.toLong).toOption if value > 0
} yield value
Off the top of my head, we should stop fetishizing science and technology. STEM is not automatically better than the humanities and the current effort to try to get more and more people to enter those fields is not helping the problem.
Because of "single responsibility principle" it's better if classes and methods do one thing. That usually leads to lots of small classes and small methods.
Amazon's delivery drones may drop packages via parachute
What will of the merchant here is being thwarted? The question was how to fulfil the merchant's desires, and I gave several possible answers.

As long as there's more demand than supply, some mechanism will allocate the scarce supply to the buyers who want it most in the sense of being willing to pay the most for it. Any other system cannot be pareto-optimal.
.NET is the only serious rival regarding such tooling.
Paying someone 10$ an hour to do a quick look at a game for 2 hours * 30 new games a day ~= 220k/year, double that to pay for games and your looking at ~450k/year which is not free, but that expensive either.

Really this could stand on it's own as a product either as a review site or an industry group that supports several review sites.

PS: An yes that seems like a high estimate the average is less than 20$/game and most of this junk does not need 2 hours.
4 Key Findings on the Retirement Prospects of Generation X
> why should a reader care what is the total space occupied by 450 ditched enclosures?

Sense of scale.
i'd argue the opposite.. i mean, i think you're referring to malloc when you cite premature optimisation, but this seems more of an issue of failing to optimise for the future or generalise beyond the initial needs of the developer
So start a mailing list when you're a small band. Email your oldest fans a promo code with priority booking and/or first tranche auction option.
Give people with an academic email address early options. Give people who like you on social media early options.
Include a promo code in sales of online merchandise for future gigs.
There are lots of potential ways to do it, while undermining the scalpers.

Also gigs seem pretty unaffordable already.
For a local government a preference of local business is not only ok. It should be the first choice, the second choice and also the third one.
In this case, as there is totally different tax flow involved as the article nicely explains, local business is the only responsible choice for an elected government, IMHO.
That is true. CPUs are catching up to GPUs in some ways. Intel is doing its best to take this market from NVidia. The future will tell.
I was under the impression that Digital Ocean was mostly lower end i.e the $5.00 or $10.00 a month instances. Can someone say what is the use case for a load balancer in front of small instances?

Is Digital Ocean now targeting larger customers now?
The creator of Android doesn't agree with you https://www.theatlantic.com/technology/archive/2013/12/the-d...
Authentication in GraphQL
Robert Caro, the Art of Biography No. 5 (2016)
> Also, apparently uint8_t may not be a character type.

I think that goes hand-in-hand with the fact that `char` is not guaranteed to be 8-bits wide in C, so by that fact `uint8_t` may not be a `char`. In practice I highly doubt this distinction really matters: Platforms without an 8-bit `char` are basically guaranteed to not support (a standards compliant) `uint8_t` anyway, and it is reasonable to target 8-bit `char` systems in which case it's safe to assume `uint8_t` and `char` are the same thing. (Well, `unsigned char`)
I haven't yet finished this book, but this is very good book imo. Can recommend.
> where many artists may really want to maximize audience size and not earnings from tickets.

Then get a bigger venue or how about stay in a location doing shows each night until they do not sell out. The artist can absolutely change the supply to meet the demand if they so chose.
"...There is no fairer way to decide..."

Now, this seems unimaginative. Surely, especially given all the feedback and critique on this thread, you can come up with other factors besides price that should influence fairness in this transaction?

We may decide that introducing other factors (like band loyalty or degree of enthusiasm for the show) is difficult, impractical, or threatens entrenched interests, but that's another issue.

We can't let enthusiasm for the allocation properties of markets ("it's Pareto optimal!") bleed over into value judgements about the outcome ("...so we all agree it's most fair!").
That's a better solution imo, but that assumes a perfectly flexible supply of venue space that often isn't there in practice. When it is, I also imagine the price is free to scale exponentially with venue size.

Also, say there simply aren't enough teenagers to make it reach an equilibrium point on price alone. This method still ignores the fact that the artist might want to optimize for something other than ticket revenue. A sold out venue of trendy twenty-something's is can be worth much more than a handful of rich die hard fans willing to pay tenfold.

Finally, it requires a really good handle on what that expected audience is going to be, not just what they can pay, which is hard to do.
The Internet Archive wants to host PACER records from U.S. courts
Even if devices weren't ultrathin they'd need to be in protective cases. Cases can be damaged and easily replaced. A damaged device is more expensive and less convenient to repair or replace.

As for battery packs, I have multiple devices, but I carry one battery pack that can charge all of them as needed. My phone is much lighter in my pocket for not having to have a larger battery (that I don't usually need), my ipad is easier to handle, etc.
Um… production environments?

Early on you probably don't need it for the load but for handling recovery if an application server goes down.

Prior to now if you wanted to run a passable production environment for a small application you'd probably do something like a single persistent store behind 2 application servers fronted by an nginx to balance load across the two.

Doing that requires nginx config and finding an off the shelf package for handling healthchecks and automated removal of failed items from the nginx load balance rotation. Now DO will do that for you at slightly above the cost of you rolling it yourself but with the benefit of being (probably) more reliable and requiring near-zero time investment.

Edit: Other threads have pointed out that keepalive on the VM works for recovery on single compute instances. Seems likely that this is for DO's larger client who need recovery and multiple computes with load balanced across said compute surface.
Do you still have to stripe over multiple volumes to get good performance?
>> "patches welcome"

Here we are in a topic that actually documents the hostility people encounter when participating in Wikipedia, a topic that provides overwhelming anecdotal evidence among the comments that people are being actively discouraged from contributing to Wikipedia by hostile admins and topic campers (something I have personally experienced) and you pretend the actual problem is lazyness.

You deserved your downmod.
"No ops needed". Every time I see such piece of PR I cry a little inside. Sure, spread such things even more, so that everyone around, devs, managers, business take it even more seriously and build more horrible, unsustainable, overpriced, insecure and failing infrastructures and services. No ops needed in the serverless lambda cloud! ;)
Packet size is important. If your ports are strings, every packet gets that much bigger. Nobody wants slow internet for programming convenience.
Scala is a very complex languages, allowing tons of construct. And multiple ways to code anything. In any serious, bigger team project, you don't wanna use Scala imho. Not forgetting the super ugly stack traces.

If you really need functional programming, use a more functional language.

If you need speed, consistent code, and lots of developers. Use golang. Its simplifies software engineering.

Also if forced to use the JVM, i would chose Kotlin over Scala.
Care to elaborate? What doesn't work? Can't you use normal Skype?
The highest point in Denmark is ~170m high.
I recommend climbing on so many levels, and for some reason it seems to 'click' particularly well for a lot of programmers.

Most obviously, it offers some whole-body fitness that I don't find boring. But I've gotten a lot of secondary benefits that are hard to pass up. It's gotten me into normal weightlifting because "to climb better" is a clearer motivation than "to be healthier".

And it's a fantastic way to build strength comprehensively. As soon as one body part (bicep, wrist, hip flexor, whatever) taps out you'll struggle to keep going, so you tend to develop whatever is weakest. There's a lot of incentive to work flexibility, too, which can be dangerously ignorable for new weightlifters.
No real market can ever be built on the idea of guaranteed sale. The idea that someone wants something is not sufficient to mean they can have it. Concert tickets are limited in number by venue and artist.

I disagree with the assertion that result is good outcomes for the richest. Many concerts, store sales, and such, also have people camp out for access.

Online systems have no person to person interaction requirement which makes it ideal for automated systems. So the real result is, when up against a machine bidding for a service or item you want of limited supply you will lose.

To prevent that might require limits based on some form of personally identifying the buyer and then restricting use to only that person. A bit privacy invading but it could be done. The only way it will get done is for the artist involved to force it.
I fail to see why the time it happened is relevant here. We're talking about generating capacity here, not draw. The wind blows around the clock, this could have happened at 4:30 PM.
> Is this properly null checking if required?

Yes, because if you're typing the word null in your Scala code you're doing something wrong. Any Java library that might return null should always be wrapped in an Option, so that you're dealing with Some or None, and you never get an NPE.

Option(myJavaLibraryFactoryMethodUsers()).flatMap(_.sortBy(- _.age).headOption)

...will get you an Option[User] of the oldest user. People who have written Scala for more than six months can immediately recognize what this line of code does, and it eliminates around 20 lines of equivalent Java (or Go?) code. This kind of thing rarely needs to be refactored.
Very similar to the c++ vs c debate.

C++ has tons of arguably useful features. But these features also in a way distract from the task at hand - solving a problem. You risk ending up discussing the meta problem too much - how to write and organize code.

C on the other hand is very basic, requires a lot of boilerplate and encourages re-implementation. But you are (subjectively) more likely to produce pragmatic code which will solve your problem.

Scala is the kitchen zink of languages, i could elaborate but I don't even know where to begin.

Go is very simplistic and architected to solve some recent problems. It's easy to write high concurrency, low latency apps with minimal startup costs. Perfect for microservices. And it explicitly avoids certain complicating features such as generics, while still catering for its use cases by supporting code generation and compile-time constant computation.

Go is the rise of New Jersey Style. All developers tormented by c++,ORMs,Java EE,Soap et al join ranks to show the world that "Worse Is Better".

A funny thing is that go is very similar in style to early Java, and I believe that Gosling et al did have the same mindset as Thompson and Pike. But somehow Java got overrun by the enterprise guys, and I don't know where they came from. Does anybody here know maybe?
The biggest advantage even for low-end services would be high-availability. If one server goes down you can automatically fail over to another without having to build that into your code.
"Unadulterated original x86" doesn't really exist, and hasn't mattered for decades at least.

Do you mean the 8086's instruction set? Many of those instructions are now implemented in microcode; sure, you can use them, but they're going to be dog slow. Turns out, nobody uses them.

Do you mean the i586 instruction set? Your system calls are going to be slow, since you have to trigger an interrupt.

Do you just mean 32-bit x86? That covers a large set of incompatible extensions among different vendors, and is of rapidly decreasing relevancy.

Do you just mean scaler instructions? That's really just hamstringing yourself: a lot of performance-sensitive applications involve manipulating vectors, and SIMD is a fairly easy and effective win.
Web Design: Everything You Need to Know About It
> Imagine how tedious it would be even to use a relatively simple discussion forum like HN if you had to wait for a full page reload every time you hit a voting button or expanded/contracted a thread.

You don't need a full page reload to implement voting; that's what the 204 No Content response is for: your browser sends the vote & doesn't refresh the page.
I have no idea where we're going with this.

You're original argument was that mathematics can model things that we might arrive at intuitively, without looking at the model - such as assuming commutativity in package manager installation order - correct?

I'm simply saying that mathematics can also describe things which are surprising; counter-intuitive even, so I agree with 'higher' comments in that being:

> based on a mathematical model of collaborative edition

is not sufficient for having that:

> behavior matches intution, [sic] every time

It just doesn't follow. Not least because one man's intuition differs from another's.
create a table with uuid and jsonb, collection_id columns and you've got a fully ACID compliant document store :).
We're focused on delivering a simplified cloud experience, if you want to run a bunch of $5 and $10 droplets then by all means go for it =]

But we're serious about building a feature rich cloud so that you can run all of your production systems from DO.

We run DO from DO itself, so as we continue to scale we will continue to release products and features that will make it easier to do so, both for ourselves and for our customers.
def doSomething():Unit = {...}
def doSomething:Unit = {...}
def doSomething() = {...}
def doSomething = {...}
def doSomething() {...}
def doSomething {...}