skysight-inc/HackerNews huggingface dataset:
While I agree with Dave that the patch should not have been merged, I can understand the tone of the reply, not just from frustration but maybe even some actual panic about job security. Depending on how AMD's management takes this news, some of the people who wrote this patch may not have a job in a little while if the merge doesn't happen. I'm trying to be sympathetic.
>A lot of the interfaces are still compatible with prior versions as is the software that runs on it, or we'd be on Kernel v50+ by now.

Linux doesn't follow SemVer.
Sorry, not even close.

18 million would be on the high end for the estimated indigenous population of pre-Columbian North America. 90% of those were wiped out by imported diseases before the United States even existed. It would be quite a trick to murder 100 million people based on a starting population of only 1.8 million (not all of whom, or even most of whom, were killed, by any means).

It is not reasonable to blame the United States for things that happened before it existed.

Also, it is pretty much accepted nowadays that killing off indigenous people is a Bad Thing. Unfortunately, the same is not true of communism. There are still plenty of people who think it's a wonderful idea.
I recall that as well... Mostly from reading it 90 seconds ago in the linked article ;)
I think that the problem for quick and easy memorizations is that it could also be easy for an algorithm to crack it.

For example you have:

[qWeRtY4$] + [bananas] + [ibdlfsofxt]

If your password is exposed:

[qWeRtY4$] = remains the same for all passwords

[bananas] = remains the same for all passwords

[ibdlfsofxt] = changes for all passwords

Cracking the part that "changes" is probably not going to be difficult for a machine since you are associating the place name (hackernews or aws) with the part that changes (same number of characters). Then it won't take long for a machine to guess that you are replacing with the next alphabet letter or something else that is easy for a human to remember.

In that sense, I believe QWERTY cards are a bit more secure in this sense since it's just random characters assigned to each key, and each card is unique. It takes away the "easy to remember" part since you will have to look at the card, but it will be some orders of magnitude harder for a machine to guess it.

After multiple breaches, however, your encryption table might be exposed too. At this point you will have to change your passwords and get a new card. Probably do it every 3 months?

I don't know, sounds like a lot of work and maybe too paranoid, but I'm hopeless when thinking about password creation and making it easy to remember.
Not particularly aimed at this project, but I'm wondering if operating systems are still evolving from a functional point of view. Somehow it feels as if we're stuck with the functional requirements that were posed back in the 70s, when Unix was invented. On the other hand, I guess that the simpler an OS, the better; so perhaps its functionality should also minimally evolve.
> Now when I have what seems to be a unique idea I spend a while googling different formulations of it to make sure it's truly original.

The problem is that you often can't really find this through Google, unless you know the name we've given it (or happen to phrase your question in almost the same way someone else did on StackExchange). That's why it is so valuable to have a good human search engine to talke to (say, a professor who knows their field really well).
Hey tastyface. I feel you. I'm here. I didn't graduate from college, and my knowledge is ad-hoc, learned-by-doing and incomplete. I told myself I wouldn't give up until I was making a living writing code. I'm doing that, and it's been arduous, but I've never been more intellectually fulfilled.

It's scary, to think there's a whole new generation of programmers who probably can learn faster and more fully internalize algorithms and data structures and design patterns... but we can all keep learning. There's no limit to how much you can learn in this field, so to supercharge your work the answer is simple: work 80-100 hour weeks like Elon, but make sure you're actually producing at least 80% of those hours.. meaning, writing and creating code not just reading or consuming knowledge. I don't know how many people I've met that assume poking around reddit, HN or s/o means "working." Those people will never outshine you if you continuously push your limits and are always feeling in awe. That means you're on to something.

Keep it up, you're doing exactly what you should be doing - reflecting.
Seems to be the case in France as well, i.e, devs don't own their side projects.
So, I don't know that this is universally "a thing" but when I had a 3-5 hour break down in June I got in contact with the University of New Mexico's SHAC[1], I was registered but not yet taking a class and I think its open to the general public. They give you a little 10-15 minute "counseling triage" and then give you an appointment or whatever as they feel appropriate.

If you feel like you're in a bad place I encourage you to call your local university. Even if you aren't a student: schools are extremely used to dealing with people who don't know how to get started with the mental health (or any health) industry and they won't fucking kidnap you.

[1] http://shac.unm.edu/ they accept any one by the way. Please look for help if you feel like everything is awful, even if it's just finding some one to talk to.
Yeah, this seems like the kernel devs are making the classic "the perfect is the enemy of the good" mistake.

They're sending the message that AMD would be better off shipping closed source drivers, like Nvidia, because that would save them the headache of trying to get their merely good but not perfect open source drivers into the hands of users via dealing with Kernel politics.

But then again, what else is new.
At one point the way to do that was to post it to reddit. A bunch of things which are not what HN wants to cultivate rose to the top, and HN's core material sank into obscurity.
You should do some data analysis on where you are spending most of your time when building software and see if there is a way to do it faster. You can read books and follow someone's advice but nothing can be more useful to yourself than trying to navigate your own mind space in search of answers that you are looking for. If you figure out that you are spending most of your time deliberating how to name variables, you should spend time reading about programming styles. If you spend time debugging, identify what sort of bugs you are creating and try to go over books that cover most common programming bugs and try to incorporate them during programming time itself.
Well, I'm not saying he has to read absolutely everything that could be read on the subject because nobody has; especially not I. I just mean that on first pass I kind of assumed he was trying to be as original as possible and I thought he was failing but then I realized he was more trying to translate inscrutable brilliance into readable form. The latter he succeeds with, the former he does not.
It's disappointing that there are no conventions or legislation to rectify this situation. I have several side projects going right now, and it gets frustrating going to interviews and being asked to give up all of it just for the supposed "privilege" of being able to write code for a larger company. The solution I've found is freelancing, but this has the problem of not really providing steady work.
Ahh, thanks for pointing those out. I completely skipped over those portions...I was expecting some Linus-level chewing out that I'd missed given the tone of the response, haha.

Certainly pretty mild considering the source, though I understand why the second quote would stir things up a bit, especially making it into an "Us vs Them" situation.
Node is not exactly "can't fuck it up" simple.
Not just that it's horrible for morale. Imagine other developers hear about this. Then they start demanding shit in their contracts.
Well it would siphon everything away from the existing 3D capture industry and open it up to smaller groups and those that aren't savvy on it yet. The consumer space generally isn't doing this so anyone that sells anything would get on board at a low enough price point and simplicity.
No kidding. The big three expenses in life are home (rent or mortgage), education, and health care. Those three expenses have gone through the roof.

Fancy TV set? Eating out? Smartphone? That stuff isn't why people are poorer these days. Not even close.
They don't bother to tell you how it will remove space junk. Does it hit them with the cable?
>So no, it's not your fault.

How can you possibly have the arrogance to tell a stranger that their analysis of their own behavior is wrong based on a paragraph they wrote about themself? GP laid out, very clearly, the insight they had in dissecting their own imposter syndrome and found it was from an incomplete model of the world. In your rush to slag Google and assure GP they're a good, valued person, you seemed to completely miss their entire point, and along with it, the feeling of success that I assume they felt after having grown personally and professionally.
It's not a random fact, it's the counterpoint to invalidate the OP's argument. It's easy to espouse individualism and not have to worry about anything when you have a whole class of people who you can order to do your bidding (to grow food, build buildings, even defend the city).
I'm curious now, because this is very close to how I see pomo and I always find myself in distress trying to express this to hardcore STEM-my people (I was one myself, but nowadays thoughts are much too layered for just that.)

Anyway, the thing I'm curious about, have you read House of Leaves? I always explain the book to people as something that exploded my senses of (traditional) scientific certainty and then I went on a huge voyage of pomo, Wittgenstein etc. It also showed me in an intensely terrifying way how fluid in concept my mind could be, something like 'The eternal silence of these infinite spaces terrifies me (Pascal)'.
Neither AMD nor Nvidia develop Linux drivers for Linux gamers. Not that they don't pay attention to us with fixes and optimizations here and there, but a good part of that is games simply being applications that make use of a lot of driver functionality that might not receive enough testing otherwise.
Not really what you are looking for, but if you wanted to research it yourself, something like https://nerdydata.com/search might be handy for you...
This Reddit comment [1] suggests that people who work around CRTs a lot have a "notch" on their hearing tests at the CRT frequency of 15.734kHz. So yes it is possible.

On the other hand, you probably don't want the tinnitus that often comes with noise-induced hearing loss. Better to be able to turn off the noise (or wear earplugs) than to hear it all the time.

[1] https://www.reddit.com/r/askscience/comments/1tepwv/why_is_t...
how about using an app like Trello for that?
Wow, excellent answer.

I would add that if you're a "pull" person, don't bother applying to the Googles and Facebooks of this world. Their hiring process is extremely oriented towards "push" learners, presumably because you need lots of those people to build something at that enormous scale.

Instead look for opportunities where you get to do something you don't really know how to do. (There's a number of reasons why people would let you do that, but often it comes down to being in the right place and being patient.) That's how you grow, not by memorizing data structure answers from "Cracking the Code Interview".

(I know, dissing the tech interview is a HN cliché... But young people seem to attach unwarranted amounts of self-worth to how well they do at interviews at the Top 4 companies, so it's worth reminding that it's really not meant for everyone and you can do well without passing that standard.)
There are 2 things i feel correlate strongly with the best devs i know:

1. Quantity leads to Quality.
This has been written about by a number of people and for good reason. As with any craft, quality is born from doing something in repetition and learning from your mistakes. There is a brilliant anecdote on this from a ceramics class of all things ( https://blog.codinghorror.com/quantity-always-trumps-quality... ). So try lots of things, even if they seem silly. You'd be amazed what a throwaway project in a language you will never again use can teach you professionally.

2. Be passionate about both Coding and Learning.
I start to look for a new job when 2 conditions are met. First is that i have been around long enough to see the consequences of my stack/coding/architectural decisions. Second is that i am no longer having "eureka" learning moments with regularity. For me, this inflection point tends to be around 3 years with a company. It will vary for others depending on role and willingness to branch out in your codebase.

tl;dr: Force yourself to learn regularly. Move on when you start to stagnate. Find excuses to code things, even if they are junk. Above all: have fun.
"1) I'd like to see a breakdown of that number."

https://www.hawaii.edu/powerkills/20TH.HTM

PRC: ~77 million.
USSR: ~62 million.

" By the same simplistic reasoning, Americans killed 20-30 million [1] just by themselves."

People dying as the result of enemy action in a war is not the same as them being murdered by their own government.
then he saved some people some clicks ;)
It also definitely does not explain at all the material relations of society that have been grounded in religious rituals and practices throughout history. In a materialist analysis of religion, it is the role religion plays in mediating relations of economic activity and power that determine the structure of religion. There's something compelling about such an argument: It explains why religion's prominence in a society fades as it becomes less entwined with economy and politics.

This idealism as opposed to materialism seems to be prominent throughout what I've skimmed of this site.
http://wordperfect.com

My impression is that the legal industry is most of the reason why WP is still being used.
Briefly: consult a lawyer.
Not anything like 100 million.

Capitalists want live customers, not corpses.
I also doubt it. But LISP dates back to 1958.

JavaScript is from 1995.

"I chose the language which exists" doesn't apply to the people in 1994 who could have had /thirty-five years/ of LISP experience (potentially) and yet still chose to write another language, in another language. And when Brendan Eich was in college around 1981, the tutors there could have had /twenty years/ of LISP experience, but weren't there to convince him that it was amazing.

Same with literally any language dating post-LISP, and I note that that covers most languages which are popular today.

"Programmers don't pick rationally" is fine on the small scale, but accross the entire industry, even among people who do love exploring programming languages, even among young entrepreneurial risk takers, even among companies in tough markets angling for any and every edge they can get over their competitors, in decade after decade, over problem domain after problem domain after problem domain, there is this empty howling wasteland of happy and productive people using not-LISP, writing world-conquering systems that do just-fine-thanks and the claimed benefits of LISP just don't seem to be making any noticable dent in anything.

Therefore, they are over-hyped.
Do you know when some naive people claim that build a "simple CRUD app" is easy, but a OS or a Database engine or a Game engine or Language or Super-Cool-Algo_performace-magnificence or Super-Science-thingy is hard?

All of them are super-wrong.

All of them are long, hard projects. All of them requiere specific skills, that maybe are hard to know because you don't find much info about how do them (for example, I haven't find good enough, simple material in how build a relational engine).

But do it are easy. Because the "science" behind them is more SETTLED. Is just niche.

> YapDatabase, Audiobus, or AudioKit

I don't know them, but it look the same as the things I'm talking about. I LOVED to have the time or funding to devote to this kind of projects and living from them (ie: I want to build a relational language.)

IN CONTRAST

The most "simple" apps, are HARD TO DO.

Them are easy projects, but DO THEM is harder. The specs are unclear, you can't rely in a cool algo that solve most of it, you can't relly in a big, large, solid foundation, you NEED TO BUILD AND PULL from several sources in how do them.

Rocket Science is "solved", but you can waste months trying to finally know what the hell is necessary to build that e-commerce website.

Just look at the madness with JS. Is now easier doing assembler than that.

----

So, I mean that the human factors are the uncertain nature of most software projects are a higher burden that the actual "hard" projects.
I'll be 35 next year and started writing code when I was 30. I have very similar experience. This year, I focused on how to write better code instead of designing and building. I'm slowly getting better this year. My biggest code base for one of my prototype was around 25k LOC. I mainly wrote iOS app, too. I spent more than one year to take care of my kids so there was a long gap. And it has been difficult for me to find a job. There are always meaningful ideas and having the ability to bring some of them to life is my biggest motivation.
Sifr is definitely a cognate for "cipher"!
Do you play? I spent ages on that game. Any word on why that would mean he isn't afraid of anything?
It's difficult to believe that orthodox Christianity is completely evidenced based and requires zero faith, blind or otherwise. If it did, I would imagine it would end up falling into the realm of science, and not religion.
OK, thanks for the info. I was going off the "almost at the limit of experimental error" phrasing, and assuming that meant a small but reproducible effect.
What's the average salary at Google? Does getting a Google Home or even a Pixel (which they can easily afford imho) really mean something to the employee?
I don't care about audio destuttering, but there will come a time when my apps will be made better by a finicky feature that requires similar expertise. Rather than dreading the process (as I do now), I want to learn how to efficiently source this kind of domain knowledge and then implement it without too much of a hassle. Deep, needle-precision learning.

Most programmers don't have books written about their work, but I think most great programmers (of the kind I admire) could write an in-depth book about the unique things that they've written and discovered.
> Sure you can sign a contributor agreement, but its not yours to give away. The employer owns the code you contributed to a FOSS project. The project got the signature from the wrong entity.

Which is why the FSF requires documents from contributors' employers: https://www.gnu.org/prep/maintain/html_node/Copyright-Papers...
First, you're comparing two different domains. App developers (whether mobile, web, or some other environment) live at the top of the stack. As such, they must wrangle many disparate frameworks and libraries to achieve their goals. Framework developers can focus on a narrower set of concerns--albeit sometimes quite deep.

I would suggest that you stop comparing yourself to them and their achievements. Rather, use their example as a starting point in your pursuit of improvement.

Many others offer good advice here, but one of the cornerstones is to look at what others are doing--often and deeply. Many have asked, "How do I become a great writer?" The answer invariably is, you must be a great reader. You need to read A LOT.

The same goes for math. You must solve problems. That's the other half of the coin. You need to do. So pick a problem that hasn't been addressed. Maybe there's something you haven't found a library or framework for. Take the opportunity to build it, package it, and open source it. You'll see that the set of concerns is different from that of an app developer.

Edit: typo
He's not trying to talk to the philosophers. He's trying to talk to STEM people. So he chooses his writing style and terminology to that end.
Police shouldn't be able to shoot someone merely because they "felt threatened" (as shooting someone in the back who wasn't armed who was running away), or if someone backs their car into a police car.

The problem with these cases is the police have attempted to carve out large categories where they can do anything ("they feel threatened") and that's unacceptable. They are licensed to carry guns, they need to use discretion.

Driving your car at high speed into a police car in an attempt to hit them is different than a fender bender at 5 miles an hour in the real world. When I have a fender bender and the car in front of me stops too suddenly and I hit them (happens 1000s of times per day), you don't get to shoot the person who hit you because it was "textbook vehicular assault". And it shouldn't be different if the other car was driven by a policeman.
I got a little confused of this article. Firstly, the author try to say that side projects are belong to the company hires you as full time employee, and, then throw the game designer example, but it sounds to me like the game designer is contractor not a full-time employee, so, it follows the default copyright, I am ok with that, and then, the author start using this case to approve the relationship between your side project and your employer as you are a full time employee. Am I missed some info?

I remember that in Canada, the full time employee contract mentions something like, 40 hours per week, and also explicitly mention if you use company's property or equipments to produce some, or you produce some at company venue, then all copyright belongs to the company.
Have you looked into Snowflake? Seems like their solution satisfies most of your requirements, including native ingestion of unstructured data. The one caveat is that all source data must first be loaded to S3. https://www.snowflake.net/
Carmel Developer Preview Launches Today
My search for a MacBook Pro alternative
If you read the full article, it covers the law in California which has three tests. Two of those tests are straightforward (company time and company equipment), but the third (related to the company's business) is less straightforward. My impression as a non-laywer is that the courts will probably take a somewhat narrow view of that third test, but the actual language in the law is pretty vague and some companies are involved in many fields.

EDIT: May be a bit less narrow than I thought. This [1] journal article cites some relevant case law.

[1] https://digital.law.washington.edu/dspace-law/bitstream/hand...
I was referring to the Google+ fiasco and how + is no longer an operator. Instead, now you have to "quote" "for" "inclusion".

https://productforums.google.com/forum/#!topicsearchin/webse...
We kind of do that already. We identify user groups that have low response rates and cull them automatically, or put them on a lower frequency program. Good, quality leads are expensive and you don't want to completely burn them out.

We also have built-in stopgaps that limit the amount of emails people get. Nobody gets more than x per unit of time, the ratio of which we are always trying to push down.
They didn't announce it so is it really marketing?
It saddens me that we're living in an age where a static HTML / JS website ends up hosted on Google App Engine and can go "over quota".
I get so many of these, that upon receiving the first one, I just immediately setup a filter to move everything from that sender into the Trash. They never have an "unsubscribe" and they are always followed by a series of ever more desperate messages, so that's really the only way to keep them out of my inbox.
seems to me the more accurate title would be "debugging a function in libc"