skysight-inc/HackerNews huggingface dataset:
> are we now putting CSS in Javascript?

You are missing the point. Forget about client vs server, the idea is that in React you are working with components.

NOT putting component-local styles into the component's implementation is a mistake, and is equivalent to creating a cluttered global namespace with lots of stuff you shouldn't touch because the component expects it to work a certain way.

The right way is to let each component accept style props that the consumer is supposed to be able to change, but to keep the rest of the component's implementation private.

The idea of encapsulation is pretty basic in software engineering (functional and OOP) but for some reason people fail to realize that what makes components useful is that they create an encapsulation boundary that should reduce the cognitive load of using the component.
I'm really surprised and disappointed by some of the responses in this thread. It boggles my mind that some people can consider themselves "hackers" and/or follow tech news, but not understand that automation is going to require UBI for most of humanity to have any sort of quality of life. UBI is and should be a bipartisan idea. It may even be necessary for the survival of our Republic, if not or species.
A basic income would be perfect for Facebook. The people will be able to sit and consume everything social media while rotting away to obscurity.
You are being downvoted but I agree. Not everything should be a never ending monthly fee. I'll pay for a good app and happy to buy the next major release if I think it offers enough functionality to upgrade.
Questions such as these are tackled in the excellent book Infinity and the Mind [0].

[0] https://www.amazon.com/Infinity-Mind-Philosophy-Infinite-Pri...
Are you suggesting there are?

I asked for examples. Can you provide one?
@TheTon

Like another use said, I would rather pay once and receive updates than a monthly subscription. I know that you are using your own servers to pull information, but I don't know why that is even necessary. I would rather have an app that doesn't pass any information through a third party server.

I also ran into a problem when trying to create a milestone for a repo (this was the second milestone I was creating with the app) and it locked up.

Other than that, it's extremely nice, and if you ever made it into a one time purchase, I would probably pick it up right away.

EDIT: Just a couple of notes. I tried out a couple of other applications to compare features (since I can see how nice managing issues, etc from a single app is compared to the website) and I have to say that Ship is by far the nicest out of the bunch.

As posted below: https://www.realartists.com/docs/2.0/uninstall.html

T̶h̶a̶t̶ b̶e̶i̶n̶g̶ s̶a̶i̶d̶, w̶h̶e̶n̶ I̶ w̶e̶n̶t̶ t̶o̶ c̶l̶e̶a̶n̶ u̶p̶ /̶ r̶e̶v̶o̶k̶e̶ a̶c̶c̶e̶s̶s̶ t̶o̶ a̶l̶l̶ t̶h̶e̶s̶e̶ a̶p̶p̶s̶ t̶h̶a̶t̶ I̶ j̶u̶s̶t̶ a̶l̶l̶o̶w̶e̶d̶ a̶c̶c̶e̶s̶s̶ t̶o̶ G̶i̶t̶h̶u̶b̶, I̶ f̶o̶u̶n̶d̶ a̶ t̶o̶n̶ o̶f̶ h̶o̶o̶k̶s̶ o̶n̶ n̶o̶t̶ o̶n̶l̶y̶ t̶h̶e̶ o̶r̶g̶a̶n̶i̶z̶a̶t̶i̶o̶n̶ l̶e̶v̶e̶l̶, b̶u̶t̶ e̶a̶c̶h̶ r̶e̶p̶o̶ l̶e̶v̶e̶l̶. I̶ k̶n̶e̶w̶ t̶h̶a̶t̶ y̶o̶u̶ w̶o̶u̶l̶d̶ h̶a̶v̶e̶ h̶o̶o̶k̶s̶, b̶u̶t̶ I̶ a̶s̶s̶u̶m̶e̶d̶ t̶h̶e̶s̶e̶ w̶o̶u̶l̶d̶ b̶e̶ o̶n̶ t̶h̶e̶ o̶r̶g̶a̶n̶i̶z̶a̶t̶i̶o̶n̶ l̶e̶v̶e̶l̶ o̶r̶ r̶e̶p̶o̶ l̶e̶v̶e̶l̶, b̶u̶t̶ n̶o̶t̶ b̶o̶t̶h̶. E̶i̶t̶h̶e̶r̶ w̶a̶y̶, i̶t̶ t̶o̶o̶k̶ m̶e̶ a̶r̶o̶u̶n̶d̶ 1̶0̶ m̶i̶n̶u̶t̶e̶s̶ t̶o̶ c̶l̶e̶a̶n̶ u̶p̶. N̶o̶t̶ s̶u̶r̶e̶ i̶f̶ y̶o̶u̶ h̶a̶v̶e̶ p̶l̶a̶n̶s̶ f̶o̶r̶ a̶u̶t̶o̶ r̶e̶m̶o̶v̶a̶l̶ o̶f̶ w̶e̶b̶h̶o̶o̶k̶s̶, b̶u̶t̶ t̶h̶a̶t̶ w̶o̶u̶l̶d̶ b̶e̶ a̶m̶a̶z̶i̶n̶g̶ i̶f̶ y̶o̶u̶ d̶i̶d̶.

Either way, I will be keeping my eye on Ship because I really enjoyed it for the most part and it is better than the alternatives I found IMO. Keep up the good work!
is this Remote?
article table tl;dr: intel is roughly similar and in production right now, tsmc should be too, GF and samsung are at least 6 months out, probably a year or more ('risk production date').
It would be nifty to supress warnings on a per include directory level by passing flags directly to the compiler. This is how static analysis tools like PVS avoid flooding us with errors.
That's an oddly generic question rendering any type of answer largely useless.
Hey, ever since we started using REMs it made scaling much easier as well. There are times when we had to work around for example bugs in Chrome with font scaling and transform under certain conditions which made chrome resize things incorrectly, but only chrome.

Its little things that take up a bunch of time. In theory we're already 80% of the way there, but the last bit is what makes the big difference.
Usually what people do is they develop with -Wall -Werror but then turn off -Werror for the shipping version.
Hi, I'm a software developer with 9 months experience in a big company with a b.s. In computer science from a top European school.

It seems impossible to get into the US at the moment, and my few attempts have failed. What should my expectations be in terms of getting a good company to accept to sponsor a visa in the current circumstances? Thank you very much for your AMA.
> An event that had the implicit backing of the school administration sent a widespread message.

If you check the thread you'll clearly see my interest wasn't whether discrimination happens at all, it's whether it is to the point of being literally ostracized, as was stated.

>> Could you name a two or three so we have some idea what you're talking about?

> sure..

Perhaps don't impersonate other people if you don't want to be mistaken for someone else.

Then again, I suppose by now I should know better than to expect reasonable discussion in threads such as these.
Really not the case. Space X have built, um, not many rockets. Tesla are planning to churn out hundreds of thousands of cars.

The key isn't being able to do it (as someone else said joining metals is a solved problem), it's being able to do it with high quality and in a reliable way. Do you think Space X joining techniques are optimised for making 100k joints in a factory environment?
It is cherry picking to analyze only obstacles faced by women in tech and then conclude that women face extra challenges without even considering that men spend their lifetimes facing predominantly male-unique problems.

The same flawed perspective leads to generalized racism like the now popular opinion that white people should be treated poorly because they all had it easy.
> What you are not understanding is that a smart contract is a protocol amongst people. You don't code it anywhere in the blockchain directly. It a a protocol that explains how, if each party runs code independently, assuming everyone as a criminal, still achieves its goal.

Okay, I see your point. This kind of smart contract you describe definitely needs strong cryptography and a blockchain would not be needed. I guess the issue is still about what a smart contract truly is and how it should work. I personally prefer the term self-executing contract as the "smart" seems too sensitive. Regardless of the language or definitions, I am interested in a platform were multisig applications can be executed safely and efficiently.
Of course your sister should make her own choices, but the pressure on a mom in tech to leave is still absolutely immense. The more of us who tough it out, the better for our daughters.
It's an interesting idea. The problem I see, is applying these types of metrics to creative endeavors would lead down a path of quantity over quality.

I think it would be a useful tool for people who have trouble finding a 'creative groove' and need guidance. I think it could also be abused by people who oversee/hire creative people and want to track and micro manage.

It works for fitness, because in general more = better. When it comes to writing, especially non-technical or non-explanatory writing, brevity is king and where the beauty is found.

There's also danger in distraction. The writer could end up focusing more on trivial details of their process ("how many times have I used 'as such' THIS time?") instead of focusing on getting the main idea out and then revising and editing.
Let's fix Social Security first; worry about UBI later.
What you want as a plutocrat is a system where you have (high) taxes redistributed in a way so that you can recollect the taxes through the organizations (companies) you control by having the recipients of the redistribution purchase your organizations' goods and services.
Doesn't that already describe Earth?

We could accidentally fire nukes, accidentally let a GM smallpox strain out, accidentally start WW3, we could do so much as it is. That is beside the point anyway.

Presumably the first people to go to Mars are going to be vetted for some level of education and skill. This will likely prevent the fear mongering, demagoguery and other forms of lying that allow some successful politicians argue against singularly true facts, at least for a little while. Likely until the mars colony is self sufficient.

Even then it seems unlikely you will get an anti-global warming lobby on Mars, because it is good for every business (presuming breathable air is government utility/service).
>The government in capitalist societies can't force someone to open a business when unemployment gets too high

It does all the time, no? At least here, town halls give stupid jobs to people when unemployment is too high. Obviously, the results are catastrofic.
Engineering team creates solar powered tent. Wouldn't even get one like or retweet.

How's this:

10 blind and paralyzed transgendered teens sell lemonaid in attempt to fund Engineering project they've created to design a solar powered tent for homeless veterans.
>Take the "black lives matter" movement. If we followed the OPs advice, they should just protest that "all lives matter" instead,

That might have been more effective, even if it isn't as fair or correct.

Hard to say, but in the lead up to the the latest US presidential election, there were many movements that I absolutely agreed with that I wish had shut up for just 1 year, because I could seem them fueling resentment on 'the other side' much more than energizing their own side. The rural side of my family was in the middle of being completely out of their minds over having a black president and gay marriage made legal when media started pushing for black lives matter and transgenders in bathrooms. They revolted, and now we have a moron as a president. "Deepened the divide" indeed.

This may be an evolution in my own thinking, that there can be more important things than being "right". Think long term.
I love this series - it is what inspired me to have a crack at it in rust (https://github.com/rthomas/rust_net) - however I am only at the stage of responding to arping, and other shiny things have come along to distract me.
Did you even try looking before asking this? I can think of a bunch in just the couple months, mainly in regards to Uber and other SV companies taking concrete steps to fix their culture.
Yes but like all async ops not without expense to the UX.
> Is styled-components better? I don't know yet, but so far I like it.

Consider these two scenarios:

a) Someone using your component must also understand your component's full stylesheet and must determine (through analysis or through your naming conventions) what she can safely change about your component's styling, vs which parts are likely to be changed by you (or completely refactored) in future versions.

b) Someone using your component gets an API for the things they should be able to change about your component. The rest of your component can be updated (and its implementation changed) as you see fit, and as long as the consumer has followed your public API, the new version will work.

I think that with scenario A you lose most of the benefit of components, since you expose (and force the user to understand) some of the implementation details that she should not modify.

Whereas with scenario B you get the benefit of having an encapsulated unit of code with a clear interface, while being free to modify its implementation as long as the public interface continues to work as expected.
Here's a good explanation of 'why CSS-in-JS': https://medium.com/seek-blog/a-unified-styling-language-d0c2...
It seems like the brunt of your statement is that we should be fighting human nature itself. No wonder the problems seem so unapproachable. If you don't want to discuss reality, that is fine, but you lose the moral and intellectual high ground that you seem to think you so unquestionably have.
"Nothing is terrible except fear itself" from an essay by Sir Francis Bacon

(Way before FDR said it BTW).
The question is not how far China has come in recent decades, it is what is going to happen in the future. You seem to be taking the position that it is absolutely impossible that China will get in serious trouble and wind up going backwards.
A guy worth ~$62 Billion talking basic income; someone who's looking to lead the world in automation alongside Google and Amazon. Not to get all nutty, but it seems strange that billionaires are the ones to lead the conversation in basic income.

Sure they know more than anyone that automation is coming, but exactly how soon and far stretching?
Have you ever built an SPA with globally defined stylesheets? It's a huge pain that's near impossible to maintain. I still have nightmares from that time I tried to migrate a backbone application from Bootstrap 1 to 2.

It's not about CSS in JS, it's about having locally scoped CSS. Using JS to do it is just one approach.
This is what Shadow DOM and CSS Custom Properties are for: Let the browser encapsulate styles, with both upper and lower bounds, and let specific values inherit through the encapsulation boundary.
> They are finding the best female developers. There just aren't that many (for whatever reason)

This sounds like you think companies don't have an obligation to improve their environments so that women feel included. Consider a developer that you would say is among the best: would she accept a position at your company? Why not?
Lack of free speech brings certain risks, but I don't see any reason that it must necessarily hamper progress. In fact, by simple observation of earth for the last 30 years one could easily come to the opposite conclusion.
poor performance and harassment are discreet issues. both can be true (or both false). as such, any record of performance isn't by nature proof of non-retaliation.
There's no "conclusive" evidence of anything other than her not being familiar with radio and her being off course. There are several strong possibilities of what happened. It's most likely she crashed at sea, but that's not known for sure...there are other accounts that say she didn't. Nothing wrong with a little mystery.
Trello Scrambles to Rescue Users Who Used Its Service to Store Passwords
Then he made it very poorly, as the other responses here attest.
Yes. These concepts are gradually starting to take hold in the web and traditional DOM world as well. Oh what a wonderful world it will be!
I disagree. Yes most of what each person says will not apply in any given case, but discussions like this where everyone is just kind of throwing it at the wall can be useful to try and pick out large trends. Plus as people discuss specifics of their workflow, individual threads can become more interesting.
Also the more esoteric workflows can be interesting to hear people describe to put our own systems into context.
Interesting, that's the same experience I had trying to get a job in Germany!
> I've never worked anywhere that I felt the need to start critiquing the code of people from other teams who were working on systems that I might not even have experience with.

This is probably a side effect of how GitHub evolved. Watching some of their earlier talks and comparing that with how they function now, the introduction of managers was a recent addition. It probably didn't change how past engineers operate in the company, e.g., "chime in if your comments are relevant, even if you aren't necessarily requested to chime in."
Thanks for the link, the referenced article would be so much more balanced if it included it as well.
Donkey Car – An opensource DIY self driving platform for small scale cars
There's something like a Godwin's law for the Gaussian distribution.

Whoever claims that the other person is making an unwarranted Gaussian assumption has lost the discussion.
Or better, don't add more tech debt!! The todo-list will just keep growing and for every todo it will slow down further development. Just do the extra work.
More like it seems relatively (compared to other countries) unlikely.
> I've mentored young women in high school interested in STEM in a program specific for them. The content is the same, but there's value in having these to counter the obstacles specific to women that they'll face.

Taking for granted a priori that this group will face obstacles isn't exactly what this post is about?!?
People talk about whether or not it can be afforded and then point out the dollar coat of living, taxes and so on. Money is not a real thing, its a construct. Its so complicated that nobody here is going to be able to prove we couldnt afford ubi. But rhat doesnt even matter since money is only a framework we use for our markets and economies. Instead of fussing with money figures, which will never do anything besides confuse people, we can look at concrete things instead. The physical and chemical reality of this world. It is undeniable that because of automation, a complete restructuring of our society will be needed. The only limits in such a reorganization are those of the physical world, not those of our current paradigm. So, how much energy is there to go around? How much food and how many materials? What is the maximum amount of any of those things that we might collectively have? What are the limits of physics for how much energy we can harvest from the sun? That is where the conversation needs to begin. And i think we will all find that even with todays technology there is plenty of everythong to go around.
I understand and agree, but most biological components at a sub-cell scale are membranes and pores in membranes, or even linear or circular structures like RNA/DNA.
Vonnegut isn't dead.
I've never met a C programmer or C compiler author who felt correctness should take a backseat to performance. And as I demonstrated, the Rust designers are hardly immune to poor decision making on this score.

Someone else corrected me regarding the stack probes--Rust didn't have probes but actually checked the size of the stack. It's also worth pointing out that often times decisions are premised on maintenance burdens. Performance was one excuse for removing the stack checking in Rust; the other was the maintenance burden of maintaining a feature outside of LLVM.

That goes directly to the heart of the undefinedness issue in C. Doing the "obviously correct" thing wrt to choosing between possible undefined- or implementation-defined behaviors isn't as easy as we think. Good compilers are built on abstractions and code reuse, like any other piece of well-written software. Doing the correct thing in some obvious cases can result in having to make non-obvious tradeoffs elsewhere, possibly having to choose between adding (or maintaining) complexity, or removing a powerful feature, such as deterministic stack overflow prevention.

The history of C (indeed, Unix and the whole "worse is better" school of design) is about favoring less complexity in the tooling while shifting more of the burden onto the user. That's a judgment not about runtime performance, but a very unintuitive judgment about the performance and efficiency of programmer time; that you quickly reach a point of diminishing returns, much sooner than most people believe, putting complexity into, and relying on intrinsic features of, the tooling; that it's often better to make it easier to implement and integrate specialized tools, and easier to reuse existing tools as part of a more focused solution. From that perspective the design of C makes a ton more sense, even if reasonable people can still disagree about the results.

The notion that C--the language design, the ecosystem--is principally about performance is something mostly held by inexperienced programmers. It's a strawman of critics. There were plenty of other languages from the 1970s that were capable of generating faster code than C. Certainly performance was and continues to be of significant concern, but C is hardly unique in that sense. If the debate about how to balance performance with other issues stands-out, I'd argue that's primarily because of C's ubiquitous position and how it and the computing industry (including hardware industry) has co-evolved.

When something seems so "obvious" (security vs performance), yet everybody continues to seemingly repeat the same dumb mistakes, often times what we're missing is that our premises are flawed. Maybe C didn't become ubiquitous because of it's performance, but more so because it was easy to port and easy to build upon. After several years Rust still has a single implementation. Even Go has two production-quality implementations. That's not a criticism of Rust, just an observation that the "security vs performance" axis is hardly the only relevant dimension for judgment and explanation.
The Civil War begat the Reconstruction. Two steps forward, one step back.
Nintendo says there are no game overs, EVER, in upcoming Super Mario Odyssey
Net Neutrality “Day of Action” Banner
They're well-styled widgets that are composable and easy to integrate into client code without adding a bunch of dependencies (like globally-defined CSS classes). What's not to love?
> I also ran into a problem when trying to create a milestone for a repo

I think I was able to find this failure in our logs, and api.github.com returned a 504 GateWay Timeout. Not much we can do in that case except fail.
This also makes it impossible to use for Github Enterprise because the installation is (usually) not available from the public internet and most enterprises won't be cool with the data being accessed/stored by a third party.

It's too bad, it looks like a cool product.
Congratulations, I think you managed to set a new record for ableism on Hacker News. I'm actually struggling to formulate a response because disqualifying people from discussing their issues because of mental illness is so extraordinarily low.

You literally just said, "I'm all for being compassionate and helping people through tough times," then proceeded to shit on her for undergoing exactly that.

For one, I hope you aren't in a management position in a company, because discriminating by mental illness is illegal. Second, I hope you never get mentally ill -- which can happen to anyone -- because you would have to confront people with attitudes like yours and you would realize what garbage this is.
Depends how you define results. As a "woman in tech," I don't actively participate in these movements that much, but I certainly benefit from the extra visibility they give to women who are succeeding in this industry. I often think one of the biggest hurdles is finding relatable role models that can serve as a template for your own success and career path. When I first started out, there were a couple of obvious examples, but it was hard for me to picture what a female 'leader' should look like, aside from the old stereotype of a ball-busting corporate woman who acts like a man. That has meaningfully changed in the last few years. I now know -- and see -- a lot more examples of women who I can relate to, who are finding lots of success in this field. I realize this is anecdotal but in terms of my own career development, it feels significant. I tend to think it will benefit other women as well, and perhaps serve to normalize the idea of women succeeding in what was traditionally a male-dominated field, thereby attracting more young women to the field.

That said, I definitely recoil at the idea of being selected for any role or being treated differently simply because I'm female, since I would put my own abilities up against my male peers without hesitation. Special treatment feels condescending.