skysight-inc/HackerNews huggingface dataset:
For what it’s worth any decent IDE will warn you about that. But as a Java developer you know it’s wrong, Strings are objects and that’s not how you compare objects.

The tricky one is numbers.

Integer == int // fine

int == int // fine

numVarOne == numVarTwo // Uh-oh

In that third example you better make sure they aren’t both boxed objects or BigDecimals.

I’ve almost never seen the string one for some reason. It’s always boxed numbers.

Again, a good IDE is worth a ton.
Hey, I got a credit!

Diabolo is one of the more interesting BASIC compilers. It really does issue exceptionally fast code compared to others if you can make it work with the constrained subset it supports. It's about two or three times slower than handwritten assembly code, which considering it has barely token optimization passes (not really a thing on home computers in the 1980s) is notable.
Fighting Russia with computers, not rifles
it sounds like you dont make code changes unless they are required for function.
Just a heads up that different providers doesn't always mean different buildings. Different cities is more important for a physical disaster than different companies. For operational disasters (BGP/DNS/accounting error/abuse detection false positive/other customer DDoS, etc) different company is useful too, of course.
I'm not sure what point this addresses; maybe none. But I have to ask: who are the targets of these ads? Who are the people who would not have committed violence and genocide against the Rohingya until they saw a Facebook ad advocating it?
Who would want a 'middle skill' career? We can do better
>> A self-hosted Gitea instance my organization has been using had exactly zero downtime in the past year. None. Same with our CI system.

And when they do go down, how long will they be unavailable? When this happens (and it will happen) please post here so we can say "why are you running infrastructure yourself?"
I think it's so people realise it's not just them.
I agree. I've seen containerization mentioned by many vendors in the last year. It adds another layer of questions to vet like "do they possibly know what they're doing?"
You really seem shockingly self-unaware given the thread you're posting in.

https://en.wikipedia.org/wiki/Fan_death#South_Korean_governm...

> The Korea Consumer Protection Board (KCPB), a South Korean government-funded public agency, issued a consumer safety alert in 2006 warning that "asphyxiation from electric fans and air conditioners" was among South Korea's five most common summer accidents or injuries, according to data they collected. The KCPB published the following:

>> If bodies are exposed to electric fans or air conditioners for too long, it causes [the] bodies to lose water and [causes] hypothermia. If directly in contact with [air current from] a fan, this could lead to death from [an] increase of carbon dioxide saturation concentration and decrease of oxygen concentration. The risks are higher for the elderly and patients with respiratory problems. From 2003 [to] 2005, a total of 20 cases were reported through the CISS involving asphyxiations caused by leaving electric fans and air conditioners on while sleeping. To prevent asphyxiation, timers should be set, wind direction should be rotated, and doors should be left open.
I came here to write that. Me and my friends have a competition to get a (obviously CGI) picture of my living room filled with gold coins past those "is that photo real" platforms. So far, none has stood up to the test.

The worst one so far was TruePic, who even gave me a certificate of authenticity and then kept that certification PDF online on their website until they heard about us openly mocking them, and then they blocked the photo not because someone noticed that it's fake, but because "User has violated terms of service", which was me mocking them.
Yeah, Medium has always been recommending clickbait and sensationalist posts, yet after using it for nearly six years, it has become unbearable. Now you often come across plagiarism of poor articles from other sites and straight-up advertising. Some even actively recommended by Medium.

Personally, I hardly ever read posts and stopped checking Medium altogether shortly after learning that I'm no longer eligible to be part of their Partner Program, although I believe some of my posts still are pay-walled (Medium did miss their first deadline to implement the new requirements in January, as far as I know). I made very few bucks, one month nothing and the other more than $2 for old posts I published years ago that barely attracted reads. The algorithm is comically random and I can't say that being a member brought me any benefits, despite the better search result rankings on Google. It wouldn't have opted for a membership if it wouldn't be a de-facto requirement to reach anybody, as non-membership does not attract any readers anymore. It really isn't worth all the hassle and I'm more satisfied with a minimal blog on WriteFreely.

And considering that even the people behind Medium don't seem to know what they really want - they re-brand their site every two years - and cba to keep a minimal UI minimal, I doubt that Medium will ever improve. Poor content just seems to sell better.
Eh, I'll take that over <https://dorey.github.io/JavaScript-Equality-Table/> any day.

Boolean.getBoolean, however, now that is a proper Java land mine.
Heh, these aren't just hot terms that are willy-nilly thrown around like "cloud" or "serverless".

> The unit meets stringent MIL-STD / DO-160 environmental standards (MIL-STD-704F, MIL-STD-1275D, MIL-STD-461F, and RTCA/DO-160 for civil and military use)

These are legitimate standards that have strict specifications.
Could have been resolved with a "unsubscribe from this email" link included on the first email.
Identity + AuthN != AuthZ
A migration of that scale is difficult to execute on. I wouldn't be so quick to blame the whole Azure platform, unless it really is something in Azure that's responsible for these outages.
I think one could argue that hn comments are a core feature which is designed to draw in new users and have them use/interact with the platform. No direct monetary transaction, but I assume the hope is for growing the hn brand and ultimately getting a small percentage of users to apply to yc. Also, undoubtedly, hn pays for the comments to be served, pays for the infrastructure to accept, store, and display comments, and has users moderating discussions. So I don't really see how it is different.
It's a great thing for startups that OVH provides servers at such an amazing low cost. Yes, there is always a risk that someone will make a mistake in the building design. There's a chance that eliminating some redundancies increases the possibility of a failure. There's always a chance that something bad will go wrong.

However, this isn't just a matter of Hanlon's razor (incompetence vs malice), but more of a matter of an intelligent guesstimate of risk versus a lack of knowledge in some areas (wasn't this OVH's very first datacenter?), and a strong focus on reducing costs. Perhaps the latter went too far, and definitely some obvious mistakes were made by not having a universal power cut off of some sort, but dealing with the amount of power on tap in a datacenter is always dangerous, even when there is no fire at all.

I'm not saying we need to give OVH a complete pass on this. I'm just saying that there are a lot of extenuating circumstances and, except for the power cut off, it's not clear that OVH made any choices due to extreme negligence or cost-cutting. In other words, they didn't do anything immoral. At worst, it appears that (even from the most anti-OVH party here), this was just a mistake in the design of a new (at the time) style of datacenter, and it did work properly for many years before there was a problem. Making a mistake is not immoral.
There is something I've been developing over the years which I call "Konerding's Empirical Observation #7": every attempt to improve health care with technology in the US will only every increase the cost while also decreasing the quality of service (on average).

This goes hand in hand with Konerding's 3rd empirical observation, which is that there is a never ending supply of "machine learning geniuses" who are naive about how health care works in the US, and spend some 20 years learning how hard it is to actually do anything actionable with health care data.
Because we thought the author was Bari Weiss.
It's like inflation. Not everyone sees it at the same time
no. I'm still pissed off at facebook for doing that, and I tried at one point to convince a class action firm that deals in privacy related things to take it up as a case. I'd like if people who are upset at truecaller for this, aim some of their ire at facebook.
There are more interesting and less implausible TESTABLE hypotheses out there?

Dark matter and dark energy are the simplest (literally single parameter) fits to the cosmological data we see. Why we see data consistent with these parameters (e.g. what is the non-interacting massive particle) is up in the air, but adding multi-parameter new forces without more justification seems a little too interesting.
I’m in the process of moving to exactly this approach.

I’ve been trying to pick the right Linux distro to base my images on. Ubuntu Server is the low effort route but a bit big to redeploy constantly.

I’ve also been looking at the possibility of using Alpine Linux which feels like a better fit but a bit more tweaking needed for compatibility across cloud providers.

Unikernels are also interesting but I think that might be going too far in the other direction for my use case.

For others doing this, I’d be interested in what distros you’re using?
the phones in the pictures are in navigation mode. maybe they are weighted differently?
True, but the release did say they are recovering all precious metals, not just gold.
10^999, really?

Rule of thumb is that 10^100 of anything doesn't fit in the observable universe.
The major releases generally change quite a lot in one go, for example:

https://blog.gitea.io/2022/02/gitea-1.16.0-and-1.16.1-releas...

https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/

But I'm sure Github changes a lot more. However, the question is if those changes are worth the instability. For my workflow I just want my repos to be accessible, have my source, issues, and wiki accessible, and of course my basic git operations working. If that core functionality is actually not working at times, I'd definitely consider changing the git provider.
I just got bunch of errors - error: failed to push some refs to 'github.com'. Luckily after a while the error disappeared.

I was going nuts. For my own products I use gitea and host repos myself. Some clients of mine however use github so in this case I have no choice
It's easy enough to unintentionally box yourself into a hard 3rd party dependency. Like the github secrets store, conditional logic or triggers in the ci.yml files, pipeline driven semantic versioning, etc.
Looks quite OK as-is on a phone, though.
Personally, I can't deploy if GitHub is down. CI pulls from GitHub. One of my projects includes libraries as submodules, with GitHub as the origin. The deployment configuration has everything cloning from GitHub.
Somewhat old news, I think the only cipher of Zodiacs that has not been cracked is the link to his actual name.
Don't you define things in your repository first (usually via a `Makefile`) and then call those things in the CI environment? Or are you building things differently in the CI environment compared to the local environment?

I mean, if you're working on a project that has tests, code coverage and binary builds setup, you usually have a `Makefile` or `package.json` or whatever to run your scripts, and your CI setup just calls those very same scripts but in their environment (sometimes with different arguments/environment variables).

Not sure why it would be different for GitHub Actions. It's certainly how I use it day-to-day.
That's what the spam button is for. Enough spam reports causes them real financial costs.
Nomad is used by large financial institutions, Cloudflare, EBay, Target, Walmart etc. It’s a solid tool for orchestration and scheduling. I use it personally at home for ArchiveTeam-esq archival operations.

https://www.nomadproject.io/docs/who-uses-nomad

(have advocated for its use in multiple financial orgs as part of my day gig, no affiliation with Hashicorp)
It certainly is if in the process you establish a colony there and start taking lands by force. People who do that also try to erase any previously existing culture, good and evil beliefs alike.

Otherwise, no. In this particular case, you'd simply be trying to get people to stop killing innocents in the name of spiritual/religious beliefs; something that is clearly evil and, in my opinion, so is anyone who tries to pretend it is not whether they believe that honestly or is just arguing in bad faith.
I get what you're saying but I cracked up at this "GitHub is releasing too many features and breaking things!" because when I clicked your link the latest entry is:

> Diffing Adobe Photoshop documents is no longer supported
I think you're being overly apologetic here. This entire discussion is an excessive amount of mindshare for receiving a single email or two. I regularly get email I don't care for. I deal with it. I don't think you're a bad person for sending 2 emails. This is the internet making a mountain out of a molehill. In a week, the pitchforks will move onto something else.
I know nerd rage-bait about anything Facebook is "cool," but the submitted title is misleading and against HN rules. Flagging.

https://news.ycombinator.com/newsguidelines.html "Please use the original title, unless it is misleading or linkbait; don't editorialize."

The title of the AP article is "‘Kill more’: Facebook fails to detect hate against Rohingya." The submission title is "Facebook approved 8 paid ads inciting violence and genocide against the Rohingya." The editorialized version intentionally misrepresents Facebook as endorsing violence and genocide rather than automated systems failing an explicit test (these weren't real ads).

Can we please do better?
I find this valuable.

-Sometimes for conversations about alternatives

-Sometimes for conversations about the product's stability history

-Sometimes just for solidarity in frustration
In fact, before the term was applied to machines, it was a job title.
no, it's only for IO. It lead to way too much breakage if they changed how the string behaves.

I generally like the idea to use UTF-8 strings, but if they didn't want to break string indexing, the indexing would take O(str.length)...
'Be what's next', or how to ruin the brand of a 7.5B acquisition.
I work on a team that runs following a high trust and domain ownership model. When I joined our process was "write some code, test it, be confident in the code, commit it to trunk". A number of years ago we worked our way through "Clean Code" in a reading group and decided to try out code reviews. Each week one of us would present our recent work and the team would tear it apart line by line, and in the process we developed a better understanding of our group philosophy around style and practices.

When we switched to Git we decided that we liked code reviews and wanted to make them part of merging to develop. Depending on the content the reviews are deeper or more superficial. Many times even when I review the code of somebody making changes in their own subject matter domain I have found bugs that simply needed another set of eyes to catch.

I like code reviews and in the context I use them find that they are a complement to trust, not a substitute.
Why Pelikan
I can understand your viewpoint but just to offer a counter I always check HN for major outage news when it comes to github/AWS/GCP/Azure. There have often been comments with bits of information as to the cause and remediation efforts.
Windows 7 spotted on 3:33
GitHub's feature churn is irrelevant to the comparison unless those features are used in parent poster's workflow.
I think the way to fix it is the create a website called stupid interview questions and allow people to post about company's stupid interview questions anonymously.

And if a company requests to take it down and keep the list public of how many times the had a question removed, now you have some kind of pressure to come up with a better process.
> A self-hosted Gitea instance my organization has been using had exactly zero downtime in the past year.

> Yes, I know, GitHub is 10⁹⁹⁹ times larger than our puny Gitea instance, and that's why they're having issues

Exactly. That is also my overall point. [0] It makes no sense to go 'all in' on GitHub and something goes down and everyone is stuck once again.

[0] https://news.ycombinator.com/item?id=30711442
This is quite similar to the somewhat philosophical question of having backups: if your job is to make sure your company has backups of their data, and you entrust a single vendor with that data because they take care of backups so you don't have to, are you really doing your job? Said another way: if you (or your immediate team) are not the party that turns one thing into two things, then there is still a SPOF in your wheelhouse, and the whole point is for that to not be the case.
The point is notifying the active community here and discussing the reason(s) and impact of the outage, or in GH's case their regularity I guess
I Do Not Think That NFT Means What You Think It Does
Mind sharing some details on your install? Which database are you using (especially wondering about sqlite with gitea)? Are you using the docker install, or from package, or in k8s?

No pressure, but I'm seriously considering standing one up but it would need to be production ready.
The CM4 is technically rated -20 to +85C on the datasheet: https://datasheets.raspberrypi.org/cm4/cm4-datasheet.pdf
So you send candidates a repo invite that they have a few hours to complete a task then the repo gets revoked. Pretty cool!

The only other problem I see is to come up with enough take home problems
Opposite anecdata my GitLab install absolutely self destructed itself at one point and I had to rebuild it myself, waste of a weekend
I was really surprised how that was seen as a "far right" view

well because the guy that would actually say it ran on a far right platform, but I think its still odd how people aren't willing to separate various causes

or more so that its disappointing that we don't have a consensus mechanism that allows us to express interest in some causes while rejecting others and still getting a head of state that represents all of the chosen platforms
Yeah that would work, but like you said it is expensive - or at least it is a cost that doesnt exist in the current model and would need specific attention. And we cannot assume customer requests / issues are uniformly distributed - it's not unlikely that 80% of issues come from 20% of customers. But if you give 80% of agents access to the same 20% of customers - you havent really solved the original problem. Albeit the risk factor is certainly lower and I would prefer this setup, who knows if that justifies the additional overhead and access control management.

Technically, the current model is a full M customer x N agents mapping. All customers served by all Agents. Adding some 0's to that mapping should certainly be possible without sacrificing much from current system. No way to know how many is reasonable

All that said, there is a natural logic that arises from this 'analysis' - Limit access to customers who are inactive, or who rarely have issues. A common sense addition would be to raise their default priority for when they do interact.
Belarusian Military Could 'Soon' Join War in Ukraine – US and NATO Officials Say
Same because some of the applications we use cannot move up.
Well, if they're the ones who are nominally in control of the self driving car, because they activated it and are occupying the car, I would say that they have a portion of the responsibility.
That's not the real problem with checked exceptions in Java.
You actually have the same problem with any result type in a language with static types and mandatory explicit types in function signatures - you change one type and you have to adjust the callers, sometimes many levels above. This is just life ;)

One of biggest troubles with checked exceptions is that in Java it is impossible to generify them the same way you can do with argument and return types. You can't write a generic filter or map function that throws the same checked exceptions as the lambda (or any other interface object) that gets passed as an argument. This makes it impossible to use code that throws checked exceptions in some contexts and forces developers to wrap them in RuntimeException.

And because those situations are extremely common these days, especially after some FP techniques influenced how Java code is being written, almost noone uses checked exceptions and you typically get runtime exceptions flying around the whole codebase. Which are even worse - they turn very quickly into an unmaintainable mess - because now any function can throw just anything at any time, and that's not even explicitly visible.

And here we get to the next big problem with exceptions (not just checked exceptions): they add a high number of alternative control flows you need to analyze in addition to the main "happy path" of the program. An exception can happen anywhere and it might leave the data in incorrect, partially updated state. In reality many devs simply pretend the problem doesn't exist, and they check the happy path only. In languages with no exceptions, a function can exit only by an explicit return - and that is way more readable and easier to analyze.

And the last thing which seems to be more a cultural problem, rather than a Java problem, is that somehow most Java programs communicate typical, expected problems with ugly and mostly useless exception stacktraces. Can't connect to a host? I get a stacktrace. File not found? Two screens of stacktraces... That's IMHO a terrible approach to error handling. As a user I am totally uninterested in what code was being executed when something failed (that should be reported only for bugs so the developers can fix). I'm interested in getting a human-readable message with context helping me understand what went wrong and how to fix it.
Self-promotion with virtually zero content.
Not this reader, FWIW. The headings "10x faster", "speeding up by 25x", and "23% win" painted a clear picture for me.
>However, if all else isn't equal and you are well acquainted with a Mr Bayes you can probably do all sorts of fancy Mathematics to estimate which model is more likely to be true.

But you still need to tell Mr Bayes what your criteria are for model-selection.

So the output of your calculations is some scalar "truth-value" (higher is better) - what's your input?

In simpler terms: the truthfulness of your model is a function of... what ?

>Mind you, I don't think this is an issue for most subjects. How often do you get different functions that spew the same output in the all observable and theoretical instances?

In curve fitting? Practically all the time! It is a mathematical fact that infinitely many curves fit a finite dataset. So we pick curves that fit approximately, not exactly with the obvious underfitting/overfitting optimisation problem that needs solving in conjunction.
Thank you tailspin2019, it definitely is an interesting day for an SSO product! :)

It is a Pulp Fiction reference but I agree it is confusing. We'll refine the intro and the CTA on the webpage, great feedback.

Our core will always be free (Apache 2.0 license) and our commercials will be based on the following models:
1) A hosted solution in the future
2) Premium features on top of our core (To ease deployment, administration and integrations with Enterprise security products)
3) Vertical specific solutions for regulated industries like Healthcare and Finance.