skysight-inc/HackerNews huggingface dataset:
Currently we are running ES on big iron in production.

There are both advantages and disadvantages.
On plus side:

- easier to manage several big machines than shitload of small instances potentially on top of virtualization solution (debugging overlay network etc. at night is not fun)

- nodes are more resilient to big requests (both big bulk indexing and resource-heavy searches). Your risk of hitting sudden OOM is practically zero (although ES does have circuit-breakers that try to prevent processing requests that would cause OOM)

- while not having compressed oops is sad, not having multiple copies of JIT and compiled code cache etc. is a plus

- using a modern concurrent GC is more sensible on bigger heaps. G1 is actually fine on 64g. Some of us are running Shenandoah on Java 13 in production, I’m looking forward to apply it on my clusters (or get back to testing ZGC).

Disadvantages:

- NUMA. Try to pick more recent Java as it’s tuned to run better on NUMA machines, still not all of JVM is NUMA-aware

- fault domain is larger and getting hot node up to speed (in-sync) after restart can easily take about an hour. Getting it up from empty storage going to take a bloody while

- elastic.co folks seem to have recommended settings for lots of small nodes not big ones, so you are on your own to discover proper limits for every setting
I love how python enables these kinds of solutions so easily. Great read!
How do we keep our dependencies updated over this outbreaks?
I dont know if is just a impression of mine, but people are getting more realistic and less romantic about this stuff, really understanding the limits and the use-cases, letting Python do what it does best but leaving some parts of the system to be managed in a AOT-compiled platform like C.

I think a lot of people got burn when they adhered to the "i want to use just this thing for everything" mantra, which is pure illusion. And as with all illusions we tend to nurture, it will lead to a crash with the status-quo of reality.

This was also what happened with Javascript. If you used it as the script language that it is meant to be, everything will be fine.

The problem, as i understand it, is trying to follow the misguided and over-hyped steps of Java.
Mars will have a 420 day since it has a 668 days a year
Rails is still the best way to create server-side-rendered HTML web apps IMO, but besides the effects of SPAs on Rails, Rails is also declining fast because Ruby became a too niche language.
I never really thought about that, or put 2 and 2 together on taxes.

Why don't we have annual dynamic taxes? I'm sure there is a lot of nuance that would have to be worked out, but it seems like an excellent method for smoothing volatility.
Because those certificates are much well guarded (HSMs), rather than an unencrypted .pem file sitting on a server or someone's computer.
So true on useless questions in turbo tax. I used credit karma this year and it was way easier than turbo tax simply because i didn't have to answer a million questions.
The 1918 flu particularly affected 20-40 year old healthy people.

https://www.smithsonianmag.com/history/why-did-1918-flu-kill...
The Case for Lowercase
> You need an environment that runs on production settings but isn't production.

Why?

> Setting up an environment that ideally has read-only access to production data has saved a huge number of bugs from reaching customers, at least IME.

That's an anecdote, not a reason. Also, just because you've done it that way doesn't mean it has to be done that way, like you asserted.

> There's just so many classes of bugs that are easily caught by some sort of pre-prod environment

Also does not support the claim that you need a pre-prod env.

> Development environments

Whoa, there! You're sneaking yet another kind of environment into the conversation? Maybe not. This is unclear, given the many different ways that people do work.

> not the same as production obviously, but it's a LOT closer

You seem to want something like production. There is nothing more like production than production.

If you're set up to do A/B tests or deploys with canaries or give potential customers test accounts you're probably able to start testing in production in a sane, contained way.
While I agree that it is better from a security perspective not to issue long lived certificate and that automation would be best, I dislike the fact that the subdomain of any certificate I issue becomes public due to Google's certificate transparency project.

By making every subdomain public, it makes the job easier for any attacker wanting to try and find smaller servers to target. It's not that I believe in security through obscurity but besides making sure all servers are as secure as they can be, I do believe in not making the job easier for adversaries.

So, instead I use wildcard certificates, and for this automation gets much more annoying, you need to use DNS to validate it (route 53 or similar does provide an api that can be used) and then I'm not sure if I'm confortable having each server generate their own wildcard certificate, leading to 100s of wildcard certificates...

This is why I currently use old style 1 year wildcard certificate which gets updated through chef but I'm really not sure if this is the best solution or not.
Could you expand more on why you disagree with this? Do you believe the opposite - that "Build Almost Always Beats Buy"?

I've made the build-vs-buy decision many times in my career. I don't necessarily regret /all/ of those times, but the general lesson I've learned time and time again is that you're going to end up investing WAY too much time maintaining your special version of X when you should have spent that time solving problems unique to your business model.
Look more closely; we've had these for years. These bloody things are now sold in nearly all party shops, variety stores, and supermarkets in the Netherlands, because US media (like films and music videos) and social media from America feature these as the cups you use for a party.

Your local Jumbo sells them. Your local Action probably too. They seem to be bought by teenagers mainly.

For the non-Dutch: the stereotypical plastic cup in the Netherlands is white and much smaller than these solo-cups. The trend is towards more environmentally friendly paper cups though.
"We are all multiple personalities, they just have imperfect amnesia and the same name."

~R. Bandler
IMHO, expiration dates on certificates are and have always been the Wrong Thing. The Right Thing is to have the certificate contain a time stamp of when it was issued. The client should decide whether the certificate is still trustworthy. The cert can contain a recommended expiration date, but the dispositive information should be the issue date.
Philip Leder, Who Helped Decipher the Genetic Code, Dies at 85
Well, that's gonna be of limited use for (terrestrial) seismology. :D
If you start a side project with the goal to make money then you are making an error of definition. A side project should have the goal of teaching you something or being useful in some other way. If it doesn't then it has failed. If it makes money that's gravy but it should definitely not be the first factor in deciding whether or not it has failed.
Yep, I can confirm the GC part. We start with that before touching anything else to get the most out of the system. G1GC is pretty tunable.
I agree but there is a significant tradeoff. You are forced to use lower level expressions, meaning you reinvent algorithms and more importantly their names.

For example splitting a collection with a predicate in FP jargon would be „partition“. The function name is descriptive and universal (to those who know it). In Go it is another for loop, which is more verbose, can be implemented in different ways and doesn’t show intent until read and understood.

This rather small example shows how Go programming (read: reading/writing code) doesn’t scale as well with better understanding and experience, as programming in more expressive languages.

Note that I‘m not saying that this is absolutely good/bad. There are obvious merits to Go‘s approach.
How did you find a part time seng job? I’ve never seen one in my life. It’s all full time and contract work
Any of those frameworks that you endorse particularly?
I prefer Meccano. I'd rate Lego second.
No it's not.

The news this week is that the UK is looking to not honour the terms of the withdrawal agreement in order to avoid a Northern Ireland-UK border. This sort of behaviour is eroding trust not just with EU but Japan. Lack of a transition FTA for either would send the UK into recession.

Also look at UK's recent immigration policy announcement where they announced a move to a points based system. There is no low skilled visa for people who work in agriculture. That industry has already said they will see a significant decline over the long term.
I agree that calling a very successful language "garbage" is a childish move. I also think that we shouldn't tie our egos to the tools we are using. Nothing good arises from that.
If you don’t mind me asking, how could one get into this field if they’re already an experienced software engineer in the more “vanilla” stuff (web services, etc.)?
ICQ and AOL basically died.
While Microsoft bought Skype and basically morphed it into new-MSN.
So Microsoft's slow growth, long-term strategy succeeded, while it shouldn't have (?).
This is better than nothing but they really need to step up their handling of files in a general way.

Even on the Mac it is ridiculous that for decades the Unix “file” command (installed on the Mac!!) knows more about files than the graphical OSes do when opening them. Why is it so hard to recognize text as something openable and previewable without a specific file extension, for instance?

So yes, please improve options for handling links but let’s not pretend they aren’t still years behind where they should be.
Certainly a problem with 100-s of nodes. One thing is that GC pauses in big clusters become more problematic as the chance to hit stop-the-world pause on at least one node for every request is getting higher.

Going beyond dozens takes a fair amount of tuning and trouble-shooting.
A crowdfunding site for product feature requests.

Stripe closed my account before I was able to launch as it was "unable to accept payments for crowdfunding"..... Their marketing doesn't match their policies.
> React can make websites and apps, and it's probably easier.

It was order-of-magnitudes easier than what existed when it was first released. IMO once CSS modules became common (around 2017 IIRC, so OP may not have known about it), that was when React won - we got fully-styled and functional web components for free.
> It’s interesting that it’s been common to see this exact same opinion (a lack of conscientiousness on the part of students) expressed in Germany about German education over the past 10+ years yet you cite German students as a good example.

That fits the Dunning-Kruger effect. They are better than others at what they've been paying attention to improving. Not sure how to square that with their perception of decline though; maybe others who haven't been paying attention to the issue have declined worse, or just started out worse.
It’s highly concurrent but not pauseless
Most production systems are barely on JDK 8. G1GC is the most used GC for high-performance production systems at many large companies (1B+ USD revenue) I have worked for.
> The verbosity of

if err != nil {
return err
}

> is outweighed by the value of deliberately handling each failure condition at the point at which they occur. Key to this is the cultural value of handling each and every error explicitly.

I've talked about this before, but it annoys me a lot that checking if an error exists and returning it is referred to as "handling the error". You are not handling anything - you're passing on responsibility up the stack just as clearly as if you had thrown an exception.

You're just doing it manually instead of letting the runtime do that for you. You're also making it much harder to tell the code that handles errors apart from the code which doesn't.
I wouldn't say that this is true for such "middle-class" "consumption" categories like college and healthcare ?
Selloutstraße
How to build a state of the art Sign Language Recognition model
You can buy a fireproof lipo charging bag today
Having seen too many times how throwaway code and proof of concepts went into production I try to always write decent code. You don’t need all the bells and whistles but just give things decent names, put repeated stuff into functions, avoid memory leaks, define constants and so on.

It also reduces cognitive overhead. A lot of people seem to spend a Lot of energy thinking about whether a project needs proper coding or not.
Is this an early April fool article?
Thanks for this comment, I didn't know about those details.

And yes if it wasn't him it would have been someone else.
^(.)'(.)'(.)$

I got a tooltip say:

Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Update:: Oh ^(.)"(.)"(.)$ works and fast.
He had the courage of his convictions. Though a bit of mathematical insight could have shown that if the world was flat then gravity would not diminish with height. Some people just prefer practical experiments to theoretical calculations.
I don't have anything to contribute, apart from a link to a comic which sums it up hilariously:

http://www.amazingsuperpowers.com/2013/03/business-men/
There are lots of different types of catalysts: Homogeneous (molecule, typically small, in solution), heterogeneous (solid or porous surface) and enzymes (biological molecules.) Many do work by bringing reactants together so that the relevant fragments can combine. Chemical reactions are usually described as going through an energetic transition state and many catalysts stabilize this state so that the reaction can "get over the hill" and become product. Of course, it also stabilizes it for the reverse reaction so the products can become reactants again. The overall equilibrium is not changed. Both reactions speed up. If, however, one extracts the product as it is formed, more product will be formed and hence catalysts are incredibly useful since, by definition, they are not consumed by the reaction - i.e. you get the catalyst back so it can continue to do its work.

Here's a good example of how enzymes catalyze reactions:
https://pdb101.rcsb.org/learn/videos/how-enzymes-work

The last 1/3 of this old video from Shell describes how catalytic cracking, a crucial part of oil refining, works. It covers practical reactor considerations, including getting the products out so more are formed and 'poisoning' where a catalyst's efficiency is reduced by contamination and how that's dealt with in a continuous process.
https://www.youtube.com/watch?v=hC1PKRmiEvs
That sounds fascinating. Do you have a link or some more specific keywords I could search? I would like to learn more about that.
Also, go is an elitist language as well, in its own way. Its creators and many of the first proponets were big Unix/C/Bell Labs names. Quite opinionated people.
Next post from danfox - “how to get 3 job offers in 3 hours”.

Already has been publicly contacted by:

- GitHub CTO

- SerpApi CEO

- SourceGraph CEO

Search is hot right now!
> dreadful language to try to do concurrency in due to its global interpreter lock

don't take it too seriously. GIL has its issues and it would be nice to see it gone but "dreadful" is an overstatement. Python wouldn't be so widely used as a back-end language otherwise. Concurrency is not parallelism.

On "it [Go] will become a model for how concurrency is managed in future languages." -- it is not as clear cut as it appears at the first glance: "Notes on structured concurrency, or: Go statement considered harmful" https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
> "i want to use just this thing for everything" mantra

Is node.js dead yet?
> lenders use

i.e. when you take out a loan.

This is the key difference. So far none of the free credit scores I've been receiving match the number pulled when applying for a loan.
And how are the CAs supposed to squeeze you of money?
I'm sorry, but you still seem to be missing the point ? This isn't about bread varieties either, I would assume that most bread is bought within an order of magnitude of prices.
This would work for customer service ticket systems as well. Having been in that role, i definitely buried a few issues over the years that would have been better dealt with in the open.
How does the pay compare in game development? I have heard such mixed things
Except for the third party API dependency?
I hope your health is better now. Stay strong.
> ReactJS in my experience makes development faster, easier, better organized and more enjoyable.

Cool.

What's the worst thing about React?
That was an anomaly in many other ways too. Keep in mind that a good chunk of the world was still recovering from WWI. Being exposed to some other disease earlier in life can give a similar effect to vaccination.

This is one of the reasons why HIV spread was not as bad as it could have been in Western Europe where exposure to a disease still gave some benefits many centuries later:

https://www.nature.com/news/2005/050307/full/news050307-15.h...
Argh! Yes, ark of course.

That bit really drives the joke home, it's a shame if people missed that.
Property taxes sort of are dynamic (they can go up or down depending on property values), interest rates are definitely supposed to be dynamic. It would probably be a good thing to apply to income taxes, but they are already progressive and if you lose your job, well...you don’t have to pay them. Obama’s temporary payroll tax cut was a bit clever in this regard, as lower income people pay mostly payroll taxes anyways (directly or indirectly).
https://www.thechillypony.com

An email alert for horse owners/barn managers when the forecast will be colder than a configured threshold temperature. It's saved us a lot of mental energy this winter (having to check not just the forecast but also making sure to check the temp at 3 AM with windchill factored in, etc...). Got zero interest from various equestrian forums. shrug.

I taught myself Spring Boot through so that's a win!
Samsung E-FOTA on MDM integration explained
"The only Zen you can find on the tops of mountains is the Zen you bring up there."
Robert M. Pirsig
> The client should decide whether the certificate is still trustworthy.

Great, now you need to constantly go to some site like caniuse.com to see what % of browsers thinks your certificate is valid.
Kubernetes beat Mesos/Marathon, which is written on Scala. I don't think that's just a coincidence.
N95's not bad, but N99 (FFP3) is what you probably want for viruses. In theory these are designed to last a "shift" (8h). The manual should explain how to use it safely.

I'm not aware of the possibility of cleaning used masks. Just because the outside is clean, it doesn't mean the filter's still good.

If you want something cleanable get a full face mask with a cartridge filter. These look like (and actually can be) a gas mask. It also clearly communicates that you're serious about this, unlike the peons with those silly normal masks.
Yes, that's a good point. Especially valid because there is a very real limit on the number of test kits available. That's also a risk in case of asymptomatic spreading.
The beauty of a VAT is that there is nobody determining the difference between consumers and business, it's just transactions all the way down, with later ones verifying the earlier ones.

If you start adding rules, it will stop working.
A toss up between the Atari Portfolio and the Tandy 102.
It was an engineering team but we had a mix on the room of engineering, PMs, and senior leadership.

It was a very stressful project, we only had a tiny % of the resources we needed, and everyone had their belief as to the best way to navigate the maelstrom and come out the other side.

We were also all very invested in the product space (fitness) but in different aspects of it (e.g. running vs weight training) and we had no budget for market research. So for a long time (until BJ Fogg came along!) feature planning was "who is arguing the loudest for their point of view".

Then again this was classic Microsoft for the longest time, after all this is the company that had weekly "war room" meetings.
To be unattractive to people that feels that simplicity insults their intelligence might be Go's greatest feature.
Thanks for this info!

Doing a quick googling on elasticsearch and ZGC I just found this https://github.com/elastic/elasticsearch/issues/44321 where the official response from elastic is that only G1GC and CMS are tested and supported.

I still think that it will be worth trying Shenandoah or ZGC if/when we ever get down to do some experiments with larger heaps.
Put it on a private VLAN (eg guest Network that can't be reached from main network), pull the Sim card, uninstall all non-essential software, turn off all non-essential services.
Also Albert Heijn: https://www.ah.nl/producten/product/wi434996/ah-party-cups

Once you notice them, you'll see them everywhere.
I highly recommend trying out Java 11. G1 got quite a few improvements since 8.

In particular full GC is parallel since 10:
https://openjdk.java.net/jeps/307
FWIW success for my latest failed side project wasn't making money, it was having people use the tool/find it useful. It's free, no ads, etc... But I missed the mark on market fit.
Vespa.ai a good replacement for ES, right?
I think there are 2 cases in real world scenario:

1) either you have the habit, energy and time to systematically rewrite your code properly through iteration;

2) or you are so good that your average throwaway code is considered not that bad.

Because mostly either we are going through well known paths which leads to case 2) or we’re exploring new things and being “skilled & experienced developers” we manage to have the right habits, energy and time to build things iteratively ending up in case 1).

If in the end we still have trashy code, then we need to ask ourselves if we are lacking any of the following: skills, energy, time or good habits (or a proper context, but that’s a whole other universe of problems).
Show HN: A Webpack replacement written in Go
The optimist fell 10 storeys

And at each window bar

He shouted to the folks inside

'DOING ALRIGHT SO FAR!
Can someone chime in with the original intended purpose of the expiration date?

The one that I can imagine (without research) is that the issuer knows the quality of their own security practices, and if they says that a certificate will expire by X date, they are saying that they can't guarantee that they will still be the only person with the secret key after that point.

Any other explanation?
This is a really cool idea.

You could add a tag to feature request issues that it'd read from, maybe as a github app or something. I run an OS repo and it'd be really cool to be able to get through them all faster with a bit of money to pay a freelancer, for example. I imagine the users-paying side would be very hard to find though.

I'd also love to be able to attach a bounty to PRs with this money, although quality control would make me worry it'd be hard.

I imagine Patreon is never an enormous sum for people because the money is goodwill - it isn't tied to receiving anything back. You could make it like this.

I'm surprised there wasn't some other way of doing this - clearly other crowd funding sites exists, what do they use?
CAs are free to come up with more complicated schemes for customers that think they need them, including systems that include humans in the loop if that's what is requested. It's kind of embarrassing that hasn't happened yet, but apparently "just buy long-term certificates instead of bothering to improve things" wins out unless there is external pressure.

That said, many CA verification processes are just less-standardized variants of the things LE does. If you can get LE to give you a fraudulent cert, you will also find another CA you can fool.