skysight-inc/HackerNews huggingface dataset:
Author here. Good point about DARPA serving a political-economic role. It's a different lens on the coordination role.

Is the corporate-political landscape becoming more trust-based than the Military-Industrial Complex that Eisenhower warned about?
I do not believe this to be a zero sum game. You can argue for the merits of each one independently. Along with infinite wants, we also have infinite problems.
I don't know the original reason, but that would substantially increase linking time, and wouldn't be simple to aggregate from multiple objects. It might be a good idea if you're already taking time to do things like LTO, though.
You can have as many verbs as you want, but they all need to be valid at every state of the application (i.e at every hypermedia target), because you still want a uniform interface.

Responding with a standard error code is okay for verbs that are not supported at a particular state, but it's the uniform interface constraint that forces you to keep the set of verbs small.

Also, HTTP has nine verbs: GET, POST, PUT, DELETE, HEAD, CONNECT, OPTIONS, PATCH, and TRACE.
Yes, that’s about it. Also the infinite nesting best exemplified in Workflowy. People who are into Roam seem to believe that once you start building a graph of these relationships that you can quickly click through, the result is surprisingly useful.
The growth in the administrative side of education has been incredible as money from the government kept pouring - I read an article a few years ago about a university (Arizona?) with bloated administration that had built a dorm with a pool and a rock-climbing gym in order to attract students.

This is a problem for the exact reason you mention, but also:

> This includes facilities, support services, activities, athletics. Then there is just the socialization, dorm experience, meeting people, parties

> ...they need the ridiculously high tuition money (including from out-of-state and international students as mentioned)

And these students from China, India, and elsewhere don't care about the great basketball team at the university or the football tailgating events or the pool parties! (or at least not as much :)

The bloat has also resulted in a proliferation of degree programs by focusing on what can make the schools the most money. Thus not providing the real-world/educational requirements that may be necessary but not as "fun".
Is that what the bonus levels on the computer in the basement of the hotel are?
I deployed my project and saved some money using Raspberry Pi
Short funny story
Multitasking in RISC OS was based on swapping the page tables for the application part of the address space starting at 0x8000. Applications were not relocatable, so memory protection was more like a side effect of the address space layout than a deliberate security feature.

There was some memory protection to make pages read-only for user code, notably page zero (to trap null pointer dereferences, and to protect the interrupt vectors) but my memory is that the system heap (containing the OS modules) was either directly writable from userspace, or it was trivial to make a system call to get write access.
Lematta vs. Casper Sleep Inc. et al., Complaint in U.S. District Court [pdf]
>This is, of course, the employers' problem to solve.

This is difficult for them to do so, due to stupid laws. If they had a hiring exam, and it happened to show a certain race performing worse on it, they would get sued for racism and lose. So instead, they just do the safe thing, and let collages filter out the undesirables for them.
That looks more like a task bar to me, and in the open Write document on the right it mentions "Rudamentary[sic] taskbar" which is what it's likely referring to.
> IMO it should be clear from the top of a for loop how many iterations it will run.

How would you implement something simple like a lookup in an array? From this argument even a break in a normal for-loop would be bad since I wouldn't know anymore how many iterations it will take. So if you have a nested loop and a "goto end_outer_loop" that's perfectly fine.
True enough. It's not the ubiquity of git that is laughable, nor developers using vcs. It's this sort of thing: https://news.ycombinator.com/item?id=7894288
I used to measure how annoying a REST book or post was going to be by how long it would take the author to use the phrase 'Fielding's dissertation' and followed by the HATEOAS acronym.
I became my company's go-to person when it came to other developers (or devlops) struggling with Git. In getting people more comfortable, I found there were two very dominant difficulties/wins for the situation you describe:

* Are you using gitk viewer?. Specifically "gitk --all". Open it, leave it open, and refresh it after running any Git command to see what you did. Stick with gitk too, don't be tempted to reach for a viewer in your favourite toolkit/webapp implementation just yet. A long time ago, too many GUI were either focused on single branch, or did not render the whole branching/merging adequately. I'm sure that's changed, but gitk is part of git, and experience with it will mean you're in a position to evaluate alternatives later.

* Erase all knowledge of "git pull" from your brain. Basically a "fetch+merge" in one step, it's like leaving a parked car in gear, but with more mess when you get it wrong. Replace it with "git fetch", followed by inspecting in gitk, and deciding if a "git merge" is what you want.

With both of these I found developers were often more developed in their understanding than they thought they were; they just needed a 'leg up'. With these their confidence and understanding improved dramatically.
All it would have taken, all these years, is a single phone call to a Philippines bank, apparently. Cmon, people didn’t want to know.

It’s not a regulatory failure. There were shareholders selling into the fraud, for a decade. Are they culpable? The Bernie Madoff beneficiaries were. There’s going to be an incredible amount of pain for many, many parties.

The reality is 9 out of 10 people on this forum would be happy selling Wirecard stock at “the right time.”
You can apply the Lindy power law :)
“Yes, we can think that shorter certificates are a little bit better to trust for the user, but that should be the choice of the website that you visit.”

I would think the choice on how long to trust a certificate should be on the user, possibly using the hint that the creator of the certificate gave. You wouldn’t trust a certificate from evil-empire.com, no matter its expiration date, would you?

The discussion should be about whether the browser should make that decision on behalf of the user. I’m not sure I’m in favor of that. On the other hand, browsers already do a lot in that domain, for example by their choice of trusted root certificates (and changes to that list)
The great irony with soap is the whole point (iirc) was to avoid having to even look at the XML and just have your IDE and language tooling let you treat web services as libraries. If we had just swapped out XML for JSON (to please the ridiculous syntaxists that always plague technology choices) and maybe had someone write “SOAP: The Good Parts” to ditch some of the more “ambitious” subspecs we probably would have been better off. The book could have even had a clever title like “Clean SOAP” to ensure it caught on in our fashion-driven industry.
> For the Linux kernel, things get slightly more complicated with -mgeneral-regs-only. (https://bugs.llvm.org/show_bug.cgi?id=30792 / https://reviews.llvm.org/D38479).

That looks like an ARM issue.

> Further, it uses an 8B stack alignment, which makes it so that when FP is used, the compiler cannot select instructions that require 16B aligned operands to be loaded/stored from/to the stack.

On x86_64, on a recent GCC, this all works correctly. If you end up with a 16-byte-aligned variable (like an SSE vector) on the stack, GCC will correctly align the stack in the prologue. On older GCCs, there were a serious of obnoxious I-know-better-than-you-isms in the command line option handling that made this all malfunction.

I seem to be missing the Share button on godbolt.org, so no link. But you can test with:

typedef int v4si __attribute__ ((vector_size (16)));
v4si *v;

int func(void)
{
v4si z;
v = &z;

return 0;
}

Add -mpreferred-stack-boundary=3 to the options.
> The font is whatever you have as the default in your browser—if you don’t like it then set a better one :)

The default serif fonts on most systems aren't the best choice for a site that is trying to imitate print media.
IE had 95% market share at some point, Chrome is nowhere close, thanks primarily to Apple with its Safari browser.
But the trend is worrying, with more and more sites working only in Chrome (or another Chromium derived browser), and many software developers testing only for Chrome.
I do not use git flow. Only mentioned it here as a lesser evil than getting rid of git at all.
Any reasonable predefined flow will do.

Besides, in my experience, a review system such as Gerrit or GitHub has a huge impact on whatever flow is convenient to use.
If your domain is built with all nouns as a core part of what it inherently already is (like a Database being built on "records" or "documents"), then a RESTful interface for it "might" be workable, with the limited CRUD verbs.

However, a vast number of web developers (dare I say "most") became convinced the proper way to "think" about their architecture was "as if it were all nouns" (even when it obviously wasn't), because they thought they were having an "epiphany" about how to use REST

...when what they were really doing was conforming to software development "meme" (or trend)
too many layers of abstraction. that's our problem.
It does matter what the dissertation says if it becomes an orthodoxy, and people follow it to the letter as a way of deferring to expert opinion on how to design APIs. Deferring to expert opinion usually is, and always should be, a good plan. Here, it's a little interesting to discuss whether that's the case.
What is vegan cheese? Have folks reproduced milk proteins in the lab, or is it taste-and-texture replication?
> Git is so pervasive in software development that I think you will be at a disadvantage if you give up on it.

I would call BS on this. Yes, git is pervarsive, but if you learn alternative tool (mercurial, perforce, even svn), you will find that learning git (at least for being productive on team that uses git) is straightforward.

Also, haven't seen a company that actually tried during interviews ti figure out if you know how to use git or not.
This is really cool. I especially like the article preview text and the color image on hover (very nice touch).

Interestingly, I feel more inclined to read the articles than peruse the comment section first.
New Zealand farmers (who produce a lot of milk) have struggled with the level of subsidy the US and EU provide.

Im a New Zealander and it used to be a thing I’d read about and feel frustrated. However dairy farming trashes your land and waterways. Selling milk and milk powder is about the dumbest use of the land we could have come up with and it had caused massive harm.
> it's like leaving a parked car in gear

What, you want my car to roll off?
What does PI mean in this context? I've worked in software projects for 20 years and not once have I stumbled upon the term.
If I ever came across a magic lamp, one of my 3 wishes would be to replace all references to "git checkout" on the internet by "git switch" or "git restore", as appropriate.

Wish #2 would probably be to go back in time and get rid of the staging area.
It's just a naming problem where "REST" is used today for APIs that are almost the opposite of what Roy meant by "REST".

It's like the word "literally" being used to mean "not-literally".

Roy's design was about using custom media types, over any protocol, discoverable via hypermedia. Popular design today is to use just application/json, over HTTP, with externally defined URL schemes. There's nothing wrong with that design — use whatever fits you. Perhaps its even fair to say that Roy's design has failed to gain traction (apart from describing HTML with forms), but what Roy described as "REST" is not what is now commonly understood as "REST".
Very reasonable take, and good for you in finding some sort of inner peace is this chaotic world.

We just need to make sure we don't attribute everything to racism, white people get passed over for a lesser skilled white man constantly too
Guinness style (and other types of) facts can be unimportant, hence the term "trivia", but they need not be, that's all I'm saying. Similarly, the disputation of these facts can be pedantic quibbling or interesting and informative.
> At this point, I think I have tried at least 3 times...

I hate to be the one to break it to you, but you haven't fiddled with git enough times.
You should probably run iostat in your tests too, to have high bandwidth is completely useless if it has high latency. Just like a high framrate game is unplayable if the frames are instead delayed so the motion to photon delay is many frames.

Companies are now cheating in every way they can to extend and pretend, and now as the peak density on the flash media reveals that they break with time it's going to get messy!
Muon detectors are also application of particle physics. I will not be surprised if we’ll see more exotic particles being used, maybe in some areas of manufacturing, as a convenient carrier of certain energy. Particle colliders are the way to develop accessible technology for that purpose.
Git is not complicated. Version control is. If you sit and think hard enough about what you'd want a VCS to do, you'll come up with about the same set of features, I believe. And then think about how you'd implement those in an abstract CLI tool. So, as I said, it's the process that's complicated and that complexity can't be hidden behind just one simple button (or one CLI command).

I couldn't wrap my head around git for a while when I started. Some time later I decided to write a procedure for our branching flow at work. I wanted it to cover all the common cases like: checking out a branch, squashing and rebasing, undoing things, amending commits, etc. All of which I knew was possible with Git, but I didn't feel comfortable with most of those operations and had to go to Google almost every time. So in order to put that all down in simple steps with some short explanatory comments I, obviously, was supposed to very clearly understand all of those cases myself to be ready to answer some questions and moreover to be sure that each step is a correct way to do git and it wouldn't cause any permanent damage to anybody's repo. To get that understanding I created a few nested directories with some really small text files in them and used those to actually run and inspect consequences of various git commands which took me, maybe, about two hours maximum. I've never had a single problem with git ever since.
Assuming non-chained root CAs remain trusted.

I can forsee the browsers eventually treating self-created CAs like they currently treat self-signed certs. if they're not traceable to a trusted root CA then there's no accountability, from a browser perspective, in the event of abuse or breach.
Well, it’s not literally nothing, it’s literally a massive amount of pollution. Puffing on cigarettes is literally inhaling pollution without air so I’m fairly certain you were never intending to engage in good faith in the first place.
> "Most subjects also do not need expensive facilities or specialized equipment."

The sciences, medicine, and engineering disciplines do. Computer science is a rarity in being a high-paying field that doesn't.

(Although, given that the average developer doesn't really require a CS education, as many on HN say, I wouldn't count on CS remaining a high-paying field.)
That would be better, but it's harder to set and mark the test. Also it doesn't solve the problem of having a better student take the test or coach you through it.
Show HN: Angular Material Admin Template is released
The exact point is that what is called “race” is a sociological sense isn’t based on meaningful generic clusters — saying someone’s (genetic cluster) race has a 1:1 mapping to skin colour is like saying their (genetic cluster) race has a 1:1 mapping to their hair colour.
I agree with this first paragraph. But disagree with the second. Depends on what kind of learning style you have but I don't think a book is the best format for learning git (or most programming concepts for that matter). You probably already understand most concepts of git already anyway, but the devil is in the details and it sounds like that's where you're getting stuck. If you're a book person for technical things, though, then go for it.

I'd suggest that anytime you go into a situation where you're not sure if you'll mess something up, just make a full copy of your project on your local file system. Then try stuff out on the copy. Then you can try branching and such without the fear of messing anything up. Once you get it, you can repeat the process over and over to make sure you know it. You have to be able to fail without fear of wasting days of your time.
I don't think he's talking about the 90s. But the late 2000s were definitely better than now. Computers were powerful enough to do most things we do today, and yet both OSes and applications seemed to be much better. Compare the quality and stability of Windows 7 (or even Vista) and their macOS counterparts to their nowadays' versions.
I want to build software that lasts, but I don't think you really can at this point.

We haven't even figured out fully how we should represent a string or date or number in software let alone have an enduring language or ABI.

I feel like I am building everything on a foundation of sand at it will need to be rebuilt every 5 years, 10 if you're lucky.

I do think it will change, but it will be awhile and by then it will probably just be a few big players making software anyway, kinda like car companies.
SBIR? Totally corrupt.

Please don't ask. Can not, will not, must not tell.

I can tell you one thing. If not the best but the second best or third best proposal is accepted, IT IS a problem for the US in the long run. Side node: there is money on China!

Fell free to down vote me down. Again
Please don't ask. Can not, will not, must not tell.
contact lense implants. Changed my life. Can't wait for more bio upgrades
Stuck with your Media Player and no internet? Check how you can create your own
I did consider that in my reply. But then the poster is really getting to grips with branching, and so I didn't feel the tool was the weakness here.

However, it's worth considering if subversion is actually what you need (I haven't used Perforce but I have heard its underlying structure is conceptually similar?) I saw sysadmins struggling with Git when all they needed was to enforce good use of a single branch, and central repository and some history. They felt they should be using Git, and in doing so threw away a tool that was already a good match to their workflow.
This is awesome, the revolt of the postmillenials
Huh, I didn't know that. This week was the first I'd heard of it.
The author's a China shill, he prefers a Chinese order to what we have now. Read some of his articles, seems like a nasty character.
>Bypass Paywalls Clean for Chrome Lot of updates/bug-fixes and custom sites (and no Google Analytics tracking)

Seems this fork removes the bit that tracks the user.
Now someone please ELI5 how this compares to the algorithm Unreal Engine employs?
In my country this would never happen
I am not sure I agree. Many factories involve organizing skilled labor in a repeatable well defined process, where there may be experiments but they are managed top down.

Also, inept government agencies employee more than you might imagine.
> However, a vast number of web developers (dare I say "most") became convinced the proper way to "think" about their architecture was "as if it were all nouns" (even when it obviously wasn't), because they thought they were having an "epiphany" about how to use REST

I don't think "developers thinking their architecture was 'as if it were all nouns'" is somehow limited to REST or even web APIs. It's a fundamental part of objected oriented design philosophy.

http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom...
This was a very effective way to demonstrate the venality and homogeneity of techie PMCs. Unfortunately, donating that money to BLM is itself a manifestation of that venality and homogeneity.

If only we could devise a way to get money from the wealthy to fund projects that benefit the non-wealthy instead of the billionaire-supported NGO class...
What’s Node? Is that like Deno?
An AI Made All of These Faces
PyTorch Computer Vision Library for Experts and Beginners
SVN is infinitelly easier, and more understandable by juniors. Its also well known and supported by huge number of tools and virtually any OS - even GitHub supports git via svn clients.

It is central only, has sequential revision numbers, you don't need to pull others code if you work on some stuff that is unrelated to them, it can grab any part of repository (a folder or file), supports metadata on anything (key value store), can contain subrepositories (like git submodules) etc.

I always use it when I work with non technical people. That was mostly on larger static sites where SVN makes collaboration part easy.

On Windows, you can install Visual SVN Server in a matter of seconds (most of features are free) and it has nice Web UI, AD integration, PowerShell management and other nice stuff... TortoiseSVN has idential interface as that of git and also allows you to have private server by just creating a local folder.
It's a systemic problem, meaning that there isn't one specific cause. Government policy created the conditions, individuals perpetuate them, and the companies in question have the candidate pool that they have because of where they hire from and the expressed preferences of their individual workers. Because it is a systemic problem, there isn't a side of right and a side of wrong except for the few true malicious actors. And because it is a systemic problem we are all of us responsible for addressing it. We can't fob it off on the government or on private enterprise or on specific individuals. We must each individually make different choices if we want to change things.
I agree. Fielding's dissertation was exactly that - an academic dissertation. A lot of what it proposed wasn't even possible given the languages, software, and protocols. What's important now is that there are REST-ful qualities that people understand and agree upon and even more importantly, future specifications like GraphQL are more rigid and more practical. The industry has learned its lesson.

The author mentions SOAP as what REST came out of, but there were really at least two camps - the formal SOAP camp and Wild West of doing it however you want with POST calls. People were frustrated at these extremes. Regardless of the intention, Fielding's dissertation came at the right time and showed us a path that was simpler than SOAP, but more formal than the Wild West method.
For DIY sandwiches, salads, etc., crème fraîche is nicer than cheddar.
I'd guess it's due to more process, procedure, and regulatory structure.

It's very common for private companies to have little to no formal criteria for evaluating candidates. Intuition is more subject to bias than a formal process.
Best practice guidelines for building computer vision systems
The Saturday and Sunday are the "weird" death data in most of the countries, and not because people die less on these days, but because not all those that report the deaths do that on these days: even in hospitals in the middle of epidemics some people in administration simply don't work on weekends.

So what I see for Germany is the number of detected cases increased the last week, therefore I expect in 2-4 weeks the increase of deaths in Germany, that's how much the delay is between more cases and more deaths.

I don't see anything else that is a realistic "signal" about anything.