skysight-inc/HackerNews huggingface dataset:
I agree that Kubernetes for personal projects is likely going to be totally overkill for many, but I disagree that containers themselves are overkill, which this author also suggests. These are arguably two separate issues entirely, and lumping them together is extremely misleading. I happily run all my (very small) side projects in containers without Kubernetes and it's really pretty simple to do so.

As soon as this author mentioned he was happy with using Ansible, Systemd etc instead (which are all reasonable tools for what they are) he lost me - this is collectively much more work for me as the sole developer than a simple Docker container setup for virtually all web app projects in my experience. If you understand these relatively complex tools, you can likely learn Docker well enough in about an hour or two, the payoff in time savings in the future will make this time well spent.

In my experience "Dockerising" a web app is much, much less time consuming than trying to script it in Ansible (or Chef, Puppet, <name your automation tool>) and of course much less error prone too. I've yet to meet an Ansible setup that didn't become brittle or require maintenance eventually. If you are using straight forward technologies (Ruby, Java, Node, Whatever) your Dockerfile is often just a handful of lines at most. You can even configure it as a "service" without having to bother with Systemd service definitions and the like at all.
> So basically, ignore 1/2 of the reasonable problems that are solved in the first article and then look, no need to learn anything!!!

I think the point is... do you actually have those problems? A lot of people jump immediately to worrying about having thousands of requests per second when it doesn't make any sense.
Depends on what's inside app.yaml, no?

At minimum it requires good-enough health checks so that k8s can detect if the new config doesn't work, and automatically rollback, otherwise you're looking at "no downtime except when there's a mistake" situation.

...and to really check that the health check and everything else in your .yaml file actually works, you will probably have to spin up another instance just so that you can verify your config, unless you like debugging broken configs on live. Well, of course you can always fix your mistake and go "kubectl reaplce -f", but that kinda goes against the requirement of "no downtime".

I grant that k8s makes it easier to spin up a new instance for testing.
Apple Further Refutes Bloomberg Report Suggesting Spies Tampered with Servers
If anyone is looking for apis for mysql : xmysql will be really helpful.

https://github.com/o1lab/xmysql/

Xmysql is just one command to generate REST APIs for any mysql database.
Go green, go HaikuOS
Deno – A secure TypeScript runtime on V8
Fun fact: Heat generated by quantum tunneling's leakage current inside your processor's transistors is the main limiting factor for cramming more transistors into a smaller space.

https://spectrum.ieee.org/semiconductors/devices/the-tunneli...
Maybe the opposite? The repeats make speakers of non-tonal languages notice the tones that they normally filter out from speech, and to them it sounds odd.
There's a huge diff between "your web management software is buggy" (pretty much every web management software is kinda crappy and significant number probably would dissolve like wet paper under a serious security audit) and "your motherboard has extra chip which grants full hw level access to outside parties". The former is completely routine and happens nearly every time anybody bothers to do a security audit. The latter, if true, is one of the biggest stories of the decade.
At this point I’m left questioning his sanity, or his intelligence, and the latter seems relatively sound. What is wrong with this guy, that he can’t just stfu and help his many endeavors succeed?! Shut up Elon! Shut. Up. SpaceX matters too much to be at risk because you have the self control of a toddler.
This is a moving target; I haven't been in school for a while. Here's two:

The complicity of US corporations in the holocaust.

The way the US protected people who committed atrocities to gain a scientific advantage after WW2.
It's too late for me to edit this comment, but I was wrong to dismiss Sans Forgetica based on the review. I checked the paper and it notes:

> Although the more general prevalence of “desirable difficulties” (Bjork, 1994) is beyond the scope of this article, several research groups have found that disfluent fonts improve performance on memory tasks (Cotton et al, 2014, Diemand-Yauman, Oppenheimer, & Vaughan, 2011; French et al., 2013; Lee, 2013; Sungkhasettee, Friedman, & Castel, 2011; Weltman & Eakin, 2014). Though some have also failed to replicate these effects (Eitel, Kühl, Scheiter, & Gerjets, 2014; Yue, Castel, & Bjork, 2013), the balance of evidence suggests that disfluent fonts may aid memory but not reasoning—presumably because reading words more slowly benefits memory, but not reasoning.

Credit to kradroy for noting the discrepancy and prompting me to check. I regret the error :(
There are a lot of fully professional, large-scale shops not using Kubernetes, so the analogy seems unfortunate, to me. But I guess that shows you how successful the marketing for this stuff has been, if you think that anyone not using it is acting like a "shade tree mechanic."
"generally absolutely ridiculous"

Did you look at the map? It's nearly all things with a place name in the product name. For example, "Welsh Beef". Why is it reasonable for a consumer to buy Welsh Beef and for it to possibly have come from somewhere other than Wales?

It seems to me, more like generalising the concept of trademarks to place names rather than just company names and brand name.
There's also a zero chance of working with anything that's better than mainstream.
It's also not simple... at all.
There's too much jargon here for me to follow what you're saying. I'm not sure what you mean by "box operator" or "modern modal versions of the ontological argument", nor do I know what Kant's objection is.
That's my point. We don't need "the island"; when we've worked out the genetic issues with cloning, we'll already know how to just grow organs on-demand. The whole clone thing doesn't make that much sense when you look at it that way; it would cost a fortune to raise a human to adulthood just for organ harvesting, plus garner all kinds of ethical problems and controversy and protesters etc. No one's going to protest organ-growing or 3D-organ-printing except maybe a few religious nuts.

And with the clone, what happens when you harvest its heart (killing it), and now you need a lung? Or you harvest one thing, and then get injured and need that same part, but you didn't have multiple clones lined up? With organ-printing, you just make the organ you need when you need it.

We still don't have truly 100% working clones; we tried with a sheep a while ago and it wasn't 100% and died early. However, we're already experimenting with 3D-printing organs.
It's very hard for people to envision what would happen, outside of "i'd have to pay more money". except... a lot of society would change overall:

* predatory lending would drop (people not having to go to payday lenders to get money for medicine, for example)

* fewer sick days from people (either for themselves or their kids)

* FAR FAR FAR more mobility in the labor force, as so many people feel locked in to their job because "insurance". Employer-provided insurance is one of the biggest things holding down our innovation and progress in society, IMO. I know dozens of talented people who are afraid to move jobs, move cities, or make any change at all because "current job = health insurance". They'll never be able to go work for newer small company X, because "insurance". Big companies may bitch about costs, but employer-provided insurance is a huge moat - financially and emotionally - that keeps the status quo humming to the detriment of many on the lower end.
Key word there being "on-prem".

The hard part of Kubernetes is setting up the cluster. If you are using an existing k8s master, it should be fairly easy.

One day of course seems like a bit of an exaggeration to me :)
You’re welcome! It’s been... confusing. Such is life on the edge!
Jellynote | CTO | Paris (visa sponsorship possible) | Full-Time | 80kEUR + equity

Every month 1 million musicians come to Jellynote looking for new songs to learn and play on their instrument. We are the marketplace where music teachers and pros share their resources (sheet music, video tutorials) and meet the people who want to experience the joy of making music.

This is the perfect moment to join as we’ll be scaling the team with the newly raised money.

Technologies used in our stack include Python, Django, C++ (viewer), Rest, CSS3, ES6, CoffeeScript, React, Node, Vue, MongoDB.

You'll need to be very hands-on, as well as demonstrate an ability to lead and make strategic decisions impacting the product and the users.

Your responsibilities:

- Transition current platform into a two-sided marketplace with content creators on one side and music learners on the other

- Recruit 1 front end and 1 back end engineer, later on iOS and Android engineers

- Evaluate technology choices, and potentially lead refactoring work

- Improve apps latency

- Implement agile methods and rigorous testing & deployment processes

- Participate in R&D efforts to improve the interactive score viewer, and imagine algorithms to automate the transcription of a score

- Always keep financial and human cost of decisions in mind

Email flore@jellynote.com.
I've been told quantum chemistry and physics simulation. For example drug discovery via simulation.
I step up the challenge: To use the relational model everywhere. I'm working on it:

http://tablam.org

Eventually, if this project move forward, I pretend to provide a nicer version of sql on top of it, so get possible to do:

from customers
where id=1

instead of

select *
from customers
where id=1
Thanks for the response :)

I have read the news about the YES Bank CEO. I was hoping that they would be more relaxed with payment banks.

I'll drop in a mail over the weekend. I saw you guys when I was in my third-fourth year of University. I think the other startup that was doing something similar was Finomena but I see that your target market is different.
Oral tradition part is important because otherwise I don't think "people a few millennia ago thought that the maximum human lifespan was in the ballpark of 120yr" follows. You can say "the authors of Bible thought that the maximum human lifespan was in the ballpark of 120yr" or that they're influenced from the public, but that needs further evidence.
It's interesting that the numerous sources all decided to confine in Bloomberg. How did they all know to go to the same paper? And if some of them went to other papers then we should hear about it tomorrow, I guess.
The intro paragraph to the wikipedia article about MBTI is nothing but citations about how bad it is.

Aside from that, the standard sources of psuedoscience woo debunking all have long articles

https://rationalwiki.org/wiki/Myers-Briggs_Type_Indicator
https://skeptoid.com/episodes/4221

and finally https://www.spectator.co.uk/2018/09/the-personality-test-tha... has a brief bio on Katharine Cook Briggs
Let me hand you some binoculars, it might be hard to see the details from the vantage point of giants' shoulders:

* A lot of things "missed" is what further research proved to be "obvious" conclusions of exactly the groundwork laid by these games.

* Between 80h/week, personal life and the permanent question whether your game will sell at all, considerations what you should do in case your game becomes a cultural heritage are moot.

I have been part of this circus 15 years ago and while I definitely am proud of what I did, I do not think any lessons I learned are directly relevant today. Not only that, but I can not imagine to revisit my old code for any amount of money. Yes, my build system increased build speed by a factor of 200 over industry standards, but no, I am not going through those 2.5k loc gnu-make ever again. Or to even document the tricks we used to deliver a 80k jar, including assets.

A lot of the stuff was done to deal with hardware limitations that are irrelevant today. Why go through a lot of pain when the resources today are sufficient to play 100 instances of an unoptimized rewrite in an emulator?
I have had the idea of looking at other countries before but I haven't put in time to figure out what countries I should be looking at. Will look into this.
Posted above at https://news.ycombinator.com/item?id=18143595
I think respectable MSM rarely lie about having sources and sources having said what they claim they said. However, sources can be chosen, and sources can lie, so the question is how deep your trust goes. This is why anonymous sources are always very problematic - you can trust that the paper accurately reported that somebody said something, but you have no idea if that somebody was lying or not.
HDF5 or How I Learned to Love Data Compression and Partial I/O
:( with the particular project I've been looking through, trying to debug via running the entry point was a non-starter. The part of the system I needed to trace would only be able to run if I had 4 other services running (all started seperately from the same main file) and a full dataset loaded.

Once I finally discovered a hint about which files governed the behaviour I was investigating I was finally able to isolate the tests to begin the debug cycle.

Sometimes it's just complicated.
Ask HN: What is a problem you're shocked hasn't been solved yet?
It's entirely plausible as long as no one is inspecting the final product. The hard part isn't connecting the traces, it's doing so without immediately arousing suspicion when a tech open the server and sees a ghetto engineered chip hanging off the PCB at a weird angle.

I hadn't read the detail about the second flash chip. Obviously, if they're just putting compromised flash into a footprint left empty by the manufacturer on purpose for recovery, it's much easier, cleaner, and can be done with a small group.
People really don't care. It's not so much a callous -- "I could see this guy die in front of me without batting an eye." It's more that all the stuff you mentioned: injuries, an incident being your fault, court dates, etc. legitimately never enters their head. They do not picture that someone might be on a bicycle in their blind spot until someone is.

I think it probably changes when people have children, because they can imagine their child being hit, which helps to make that connection. For most drivers without children, yes really, they do not think of that stuff.
mdncomp 2.5 Released - Mozilla Browser Compatibility Data on the Command Line
How to Decrease the Tech Gap in a Team?
Another unique suggestion that I couldn't possibly think of. I'm really overwhelmed by the response I got to this thread. I'll look into this.
You failed to provide evidence that fruit exhibits no laxative effect. That study didn't report a laxative effect because it wasn't testing for a laxative effect.
not sure that is even worth pursuing; Part of Kosher principles is even the appearance of not being kosher (ie eating Kosher bacon, which looks like 'non-kosher' bacon) is frowned upon
Yes I agree. But in the context of this article, we're talking about small projects. So I wouldn't expect the need for an on-prem setup.

In fact I've used Kubespray[1] to setup a cluster with Ansible before with mild success. Nothing production ready, but it's actually a good tool for that job. At the end of the day you can't run Kubernetes on Kubernetes :D

[1]: https://github.com/kubernetes-incubator/kubespray
No, that's why I said most; and that's also what makes it more appropriate for APIs -- you don't want uncontrolled performance hitting you like this; if you wish to allow for aggregates, you expose them as properties.
Maybe I am a little biased, but once you define what SQL interface you want to provide to your users (so the schema of the tables) you have basically decoupled your internal data structure from the view of the client.

At this point the only thing you need to do is to update the user facing database whenever necessary and keep it consistent with your view of the world.

Yes, you have a new problem since you had to maintain the costumer view consistent with your view, but it may be a price worth paying.

The way I would test this implementation is with RediSQL (https://RediSQL.com) that I wrote (so I am definitely biased) but it may be worthed to test it.
I think webkik is saying, Open Source is better because if you DO spend money on security it can be spent by the community in aggregate / across successive efforts to pay experts to AUDIT the open source project.
>I'm willing to believe it's true that drivers are not often penalized for injuring them, but are most drivers really that bad?

Most drivers? I'm guessing not. Many drivers, however? I believe so. It doesn't take that large a percentage of the driving population for uncaring/bad drivers to cause havoc, and make it very unsafe for you to be around them. For instance, if you're a bicyclist on a busy highway, many hundreds of cars could pass you on one trip. It only takes one of those who hates cyclists to run you off the road (yes, this actually happens sometimes, in some places).
> Not really familliar with PCI DSS but it might be that the card-readers/terminals aren't PCI-compliant if opened? So not the manufacturer's issue but the customer's.

I think that's the case. The EEV Blog guy did a teardown of and old one once and pointed out the numerous tamper-detection features that would clear the device if opened.

However, if I were the customer here, I'd tell the supplier that from that point forward they need to supply me free extra product with my orders, so I can do my own random destructive testing to look for implants. I order 100, they send me 105 for the price of 100.
Oh, it is so nice to see this again.

This is the tool that introduced me to the notions of recursion and fractals when I was 11.

I remember spending two weeks cobbling up a Logo program to draw the dragon curve on my Apple IIe

https://en.wikipedia.org/wiki/Dragon_curve
I was big on artificial sweeteners (I refuse to eat any sugar), mainly erythritol and monkfruit, but some science(1) says that just their taste profile can trick your body into thinking it's consuming a real sugar with the associated glucose/insulin response and this could be one reason as to why non-nutritive sweeteners can throw your blood and insulin response profiles out of whack, which may be a reason as to why individuals who consume artificial sweeteners suffer the same maladies as those who consume high levels of sugar.

If the science on this issue becomes conclusively affirmative, then it's sort of the nail in the coffin for artificial sweeteners, because it doesn't matter what the compositional makeup of the sweetener is, it's our own bodies own responses to the taste/smell that are giving us the ill effects.

I would definitely like to be dissuaded as to believing this is not the case, though, as it's caused my to ignore my sweet tooth for far too long! :)

For those who are interested in and/or consume artificial sweeteners, I think this link is definitely worth a read:

[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4661066/
> Ocaml has no concurrency options worth mentioning

LWT is a thing.

As for being dynamic, my experience has shown that beyond prototyping, most dynamic languages don't scale with the teams.

You apparently never seen enterprise JavaScript, specially in projects with multiple consultancy companies being part of the mix.
I don't see what's "douchey" about it, but it's certainly a pointless affectation with no sound basis in modern usage. The New York journalism establishment seems to be into those for some reason.

My favorite is when the NYT -- uh, make that N.Y.T. -- writes acronyms like F.B.I. and I.B.M. with periods that even the institutions themselves don't use. Some kind of obscure orthographical virtue signal, I guess.
True, but I think that the "mainstream-ness" of Go (debatable as it is) was of secondary importance to the article, which didn't even mention that there are other languages out there which solve the concurrency problem in other/better ways. Whether or not a language is mainstream is more or less a matter of opinion, in any case. Certainly Haskell, Rust or Erlang (to name a few) are probably less widely used than Go, but none of them are obscure, so to not mention them at all suggests that the author is either being disingenuous, is not aware of those languages' capabilities, or simply forgot.
Co-founder here. If you want to check out the automated scheduling, click the link for the demo. Both of the sample projects are being scheduled using the scheduler. Edit the tasks to change the duration or other restrictions and the schedules will all be automatically updated.

Happy to answer any questions about how we built it, our tech stack, or what it's like doing a startup with your wife :)
No, it plays way better than that.

Our eyes do not see. Our brains do. And the upscalimg from limited data is amazing!
So how did these top secret, "undetectable" chips communicate with various components of the server? You can't exactly stick a chip on a motherboard, secure it with a dollop of gorilla glue and say "YAY, i kan haz."
> Modern fMRI technologies can tell if people are fabricating stories. There's actual science behind them

I think there was some actual science behind the polygraph too, but just having actual science on poorly informed/motivated participants isn't really enough for tech that will have long term adversaries.

I can't recall if 1/3 or 2/3 of myth busters staff could beat the fMRI once prepared and motivated.

Initial experiments on disinterested subjects given no information about past experiments may have legitimately been about the same for both fMRI and polygraph (at the respective times when participants could have had no information)..
Content Cookbook: Upload Files with Node
Felt legit to me. Sites can, should, and do take steps to mitigate brute force attacks, his approach showed some shortcomings in those steps, e.g. they already only allow 3 bad PINs per call, but he showed that by hanging up immediately after the 3rd bad PIN they make it relatively trivial for the attacker to detect the failure. He also demonstrated that due to the partial phone number masking in the UI the attack could be done from an apparently trusted phone number.
I thought GP comment was replying to this in GGP comment:

>IMO running your own Kubernetes cluster for a company is insanity unless you have a very good reason to do so.

To me, "running your own" means "on-prem", and it did seem to me that the response of "I can create production ready in a day" was directed at that, which I whole-heartedly disagree with.